- This topic has 6 replies, 2 voices, and was last updated 6 years, 11 months ago by
Andrew Misplon.
Tagged: CSS fail
- AuthorPosts
- May 24, 2018 at 7:59 am #9852
Andrew MisplonKeymasterHi Annemette
Thanks for reaching out. For what it’s worth, I think the Hero looks really nice as it is in white text 🙂 How are you adding the red? Via the settings in the Hero widget?
So put another way, the settings of the SiteOrigin Hero widget aren’t maintaining is that correct or are you styling the Hero with Custom CSS?
May 25, 2018 at 7:39 am #9858
alaursen.dkParticipantHi Andrew. Thank you for your reply. 🙂
The site(provan.dk) is supposed to have the white txt on the hero, but this changes to red every day and I don’t want the red and I don’t know how it becomes red. So, yes the hero widget arn’t maintaining but I don’t use Custom CSS on this area or page at all.
If you enter Provan.dk or Stined.dk right now you’ll see both pages as they should look like.
If you look at the images again you’ll see that I’ve named the dumps wrong- or true layout:
linkKind Regards
May 25, 2018 at 8:00 am #9860
Andrew MisplonKeymasterThanks.
I’m not at my computer for a few hours. To help I’d need to see the site as it is now so I can inspect the red text and let you know where it’s coming from. So if you can leave it up, I’ll get back to you in a few hours.
May 25, 2018 at 8:24 am #9861
alaursen.dkParticipantIll try to leave the pages unupdatet for a few days so that you can catch them on their wrong layouts.
May 25, 2018 at 3:44 pm #9870
Andrew MisplonKeymasterThanks, on Stined.dk I managed to see a loss of formatting. I’m not quite sure what would cause that. For the moment, please try going to WordFence Tools and open Live Traffic. Change the filter to Block, is there anything being blocked? For example, is the Headline widget being blocked at any point, if it is, click Whitelist Parameter.
Is anything being blocked? If so, does the whitelist option help?
May 25, 2018 at 3:51 pm #9872
Andrew MisplonKeymasterAhh ok, ignore the above. This almost certainly is a caching issue. I’m not quite sure what needs to be adjusted in WP Fastest Cache but it’s most likely the cause.
- AuthorPosts
You must be logged in to reply to this topic.