Forum Replies Created
Thank you Rikard,
I fixed the duplicated “about” colour sections with unique names now and the Location DIV is now as we discussed before.
The results are exactly the same even after these changes.
Any other ideas?
This is how it is at the moment (except in the first link).
To explain in a better way the page is organised by:
1) Code Block on the top section (to keep it full screen)
2) Multiple Color Sections with an unique ID
However, the problem remains.
I did that now for the only DIV that is in the page.
The other “sections” are using a tag ID on a Color section shortcode, please check it here: http://d.pr/i/1f3WY/5YXLrWnp
Perhaps the best option is to remove all Tag IDs from each color section and then create two divs (start / end) inside each color section?
Thank you for your suggestion. Can you please tell me a real example for the start div and end div?
If the DIV is ‘home’ for example, how shall the code be?
Unfortunately nothing changed.
Quick note: the gap is only visible in the warning messages to fill in the form http://d.pr/12eHw/1wVtDmKg when you click on submit button with empty fields.April 13, 2015 at 6:20 pm in reply to: CSS conflict with FormidablePRO (forms) in the calendar element #427688April 13, 2015 at 5:39 pm in reply to: CSS conflict with FormidablePRO (forms) in the calendar element #427639
Thank you Yigit! It worked :)
Any chance to reduce the red part below the drop-downs and make the drop-downs slightly smaller (in height)?
Here is how they look now: http://d.pr/i/1aIDs/4zn7fPtS
Thank youApril 12, 2015 at 2:07 pm in reply to: CSS conflict with FormidablePRO (forms) in the calendar element #427138April 12, 2015 at 2:06 pm in reply to: CSS conflict with FormidablePRO (forms) in the calendar element #427137
Thank you Yigit,
Is there a way to simply disable the custom CSS codes with the default ones using the Quick CSS?
Basically, the code to simply make the buttons back to the default ones…
A simple CSS code would be enough.
I just would like to know what CSS may be causing this, or any other incompatible issue that is overriding the theme’s default behaviour in the homepage.
On other (internal) pages, this problem does not exist.
Many thanks.March 30, 2015 at 8:39 pm in reply to: Blog posts issues: Sidebars and dark pages / unreadable contents #420796
Thank you Elliott,
I will override the settings on each post if they do not follow the default behaviour, might be easier.
Many thanks for now.March 29, 2015 at 2:59 pm in reply to: Blog posts issues: Sidebars and dark pages / unreadable contents #419980
Thank you Andy,
I was not sure what was the problem as nothing solved it. I re-created the post from scratch and it is all ok now.
Regarding the sidebars on blog posts only, is there a way to make all post pages look the same using a general rule for all, instead of a rule for each post? I tried through these settings http://d.pr/i/1gCbC/5Otx8wu9 but doesn’t seem to be working. I still need to change each post to make it work.
Thank youMarch 12, 2015 at 2:06 pm in reply to: Colour Changes: Meta Colour and H1, H2, H3 colours #410449March 10, 2015 at 8:09 pm in reply to: Colour Changes: Meta Colour and H1, H2, H3 colours #409048
Great news then!
Thank you Kriesi for the great work and progress made on this theme, and others.
Looking forward to install 3.1 as soon it is out.
Cheers to the whole team.March 10, 2015 at 11:47 am in reply to: Colour Changes: Meta Colour and H1, H2, H3 colours #408742
Thank you Gunter,
The Meta Colours is in some parts of the editor such as Special Headings: http://d.pr/i/13IDL/bXEJCvJ1
That Meta Colour is usually grey, how can I change Grey to something else?
Thank you Gunter,
It is getting better now. I had to remove the label as it wouldn’t be adjusted properly.
Is there a way to have the form centered and not aligned to the left?
Thank you Yigit,
However, it is still not 100%: http://d.pr/i/5yzG/2r6CFMWO
The .ae drop-down should also be very small compared with the text field.
The domain label is not aligned any more and the button Go should be in the same line as the other two.
Any other idea?
I have no idea on how to do that.
Could you please give me the ready-code based on my code below?
We have this problem as well. Is it a bug that will be fixed on a future release or do we need to keep this code always?
I would like to use the ?iframe=true as a CSS style if possible to work with certain elements such as the Buttons for example.
If I select an internal page as the link for that button, I can not add the code ?iframe=true since the link is automatically controlled by WP.
The solution I see feasible is to add directly on each button (or other elements) that allow a CSS code to be added in.
Is this possible?
For now, I have disabled the Avia layout builder and the page is displaying fine. This is ok for now, I don’t really need any complex layout features for the “Thank you” page so let’s keep it as it is.
Thank you for now.