-
… and unfortunately I already have another error to report.
My impression is that the implementation in the frontend is going crazy.
Because in the editor the pages always look very good.
When I switch to the frontend, the blocks look terrible.Here is the view in the editor: https://prnt.sc/pICI-HOwLFjx
(Note: I duplicated the first block 4x and put it in the second row.)
And this is how the blocks look in the frontend > URL in private field.
The font color is wrong, the margin-bottom is gone and the link (Read Story) is totally broken.It may be interesting to know that the “Read Story” link is a pattern.
In my other ticket, which I have just written, I also have the problem that the patterns I have inserted are completely broken in the frontend.
—-
I have just noticed that there is another error: all these cards have a background: Gradient: https://prnt.sc/7HBi3TvLXQIb
But it is not displayed! Neither in the editor nor in the frontend.
-
Hi there,
The CSS is not loading for the duplicated ones.
Can you go to generateblocks > settings and click the regenerate CSS button?
As for the gradient, you need to drag it before the image in the backgrounds option, so it can sit on top of the image.
-
Can you go to generateblocks > settings and click the regenerate CSS button?
Yes, I did that, but with no result. But I switched to Inline css now, for testing.
.. so it can sit on top of the image.
Ah, ok, I see!
Thanks! -
But I switched to Inline css now, for testing.
Does inline work?
-
No
-
Hi Ying,
I did the same test here as in my other ticket: I copied this grid into a page that is not a subsite of a multisite. There I performed exactly the same action: I duplicated the first grid container 4x and placed it in the second row.
Here it works without any problems, the CSS for the duplicated containers is loading without any problems.
But on the mulisite it’s like you say:
The CSS is not loading for the duplicated ones. -
Hi Stefanie,
We’ve raised this issue with the dev team. Once they have an update, we’ll notify you here.
-
Tom has found the issue.
I am closing this ticket.Thank you!! 🌷
-
Great! Thanks for reporting it to us; it’s good to know it’s a bug in the 2.0.2-beta so we can fix it before releasing.
- You must be logged in to reply to this topic.