Forum Replies Created
-
Posts
-
Preferably, I would want to overlay the website (except for the cookie consent message bar) with a dark layer just as it happens when you select the modal popup window to appear on page load.
I don’t think I’ve expressed myself well enough.
The cookie consent message bar can disappear just like it does now but when a user visits the website the first time, he should be prompted with the cookie consent message bar and shouldn’t be able to browse the website without first chosing which cookies he wants to allow.
That was meant by “mandatory”.Yes, the separator shows up if placed outside the 1/1 column but only due to sliding up a little.
The padding of the tab section doesn’t show up though and therefore it still does look messed up.I just figured out that this problem only exists if the tab section setting “content height” is set to “auto adjust to content”.
If set to “same height for all tabs” everything is being displayed correctly.
This is no solution but could help identifying the problem.
So far, it seems like a bug.I have tried the advice with changing the vertical alignment of the tab content to top but it didn’t solve the issue.
The separator has not been placed there for additional padding but as a pure visual component.
As you can clearly see in the screenshot (private content) somehow the applied padding-bottom and the separator both get swallowed by the footer.
This happens in all tabs despite the different content.Thank you for the workaround.
I am looking forward to a fix with the next update.
The ticket can then be closed now.Thank you for the clarification, your statement definitely makes sense.
It would still be great if this would work in maintenance mode also.
The ticket can then be closed now.Unfortunately it doesn’t work with either option.
I have also cleared the cache after switching between the options.I have tried your advice but unfortunately it didn’t solve the problem.
The login credentials are attached.Thank you for the reply, which definitely answers my question to full extent.
The ticket can therefore be closed now.Ok, this resolves some of my questions.
I noticed though, that your recommended links all refer to the analytics.js, even though Google has introduced gtag.js in the meantime.
When I am using Google Analytics nowadays, only gtag.js is being used and there are some differences in those libraries.
I would like to ensure that there are no incompatibilites when your theme is still using code elements from analytics.js and I am using the tracking code for gtag.js.Could you clarify with the colleague responsible for Google Analytics at Kriesi to what extent this has been taken into account in the integration of the code (e.g. opt-out cookie etc.) as the above mentioned link clearly states differences?
In the meantime we have decided to change the appearance of the content element and therefore the issue doesn’t apply anymore.
The ticket can therefore be closed now.I would rather want to use the implemented function of the Enfold theme.
Could you please answer the questions of the initial posting?
The two links you sent over don’t refer to different sections on the same page, at least not for me.
They booth link to the top of the same page and therefore I don’t know which of the advices on there to follow.Could you please let me know which two sections you were talking about?
I always hard refresh when doing changes, so that shouldn’t be the problem here.
Unfortunately, the first advice didn’t work and the link on the second advice is the same as on the first advice.
Thank you, I just wanted to report this for you to forward it to the dev team as it seems like this behaviour is not intended.
Hopefully it can be fixed in the next release.No problem, I am talking about the top social share buttons right below the header.
Right now I have added a whitespace with 0px so it looks ok, but as soon as you remove the whitespace, the social share buttons “swallow” the margin of the next element.
I have added a comparison screenshot in the private content section for you as well.Thank you for passing this ticket on to the dev team, I am looking forward to a fix.
This ticket can then be closed now.It seems that Victoria has answered to this post but I somehow can’t see the answer.
Anyways, this ticket has been left open and can be closed now.That sounds like a plan.
Is there – so far – a general workaround for the Quick CSS section, which eliminates empty cells, not just in one specific table but rather in all table content elements used page wide?
