aenea

I too have solved my problems. For me, none of the regular options to set the width of the header and the menu were working. But, after visiting the new option ‘Color Palettes Scheme’ and choosing a setting I didn’t actually want, lo and behold, the regular options sprang back into action. I was now able to adjust the menu and header width by ensuring the ‘full width’ options were switched off and I was able to restore the color scheme that I wanted (which had been messed up first by the update and then again by the Color Palette).

I suspect something is not being initialised correctly when the theme is updated and this de-activates some of the settings.

I too have layout problems having updated from v4.3.9 to v4.4.1
But, curiously, it is not affecting my test site which has also been updated.
Please see https://test.sustainability-in-practice.org.uk/ for what the layout should be and https://sustainability-in-practice.org.uk/ for what it shouldn’t look like.

The header width is wrong and doesn’t scale properly
and the main menu has gone full width.

Help, please.

Thanks for the prompt response.
I have restored version 3 on my test site and delighted to see that no harm has been done to the announcements previously created.

I’ll await your announcement of the inline positioning option and try the new version again then.

Solved it myself by putting a snippet into the Additional CSS to set the container background color and padding.

Thanks once again. Solution was obvious once you pointed it out. I needed to add the .site-branding-wrapper into the custom CSS to avoid a gap between my header image and the menu. Should have realised that this needed @media modification for smaller screen sizes.

With regard to the menu, I have decided not to use the mobile menu option.

Thank you so much, @manishverma That does the trick. I’ve spend ages pouring over the source code to no avail and would never have worked out that solution.

Alas, this makes no difference.
If I change the menu border color to red, say, then a red border appears along the top of the menu but the grey line is still there above it. The red line is the same width as the menu but the grey line extends wider than the menu on each side.
I think the grey line must be a header border but I can’t work out how to adjust that.

That’s fixed it thanks. The BOTTOM padding in Theme Options | Layout | Box Padding now takes effect.

I don’t really want to do that. The live web site is working fine within that memory limit and the test website has only just started giving this error message. So I would prefer to get to the bottom of why the test website is now encountering this error.

As I mentioned in my original post, the error goes away when I deactivate Wordfence so it would appear that it is related to Wordfence – most likely the Firewall IP blocking activity since this is a new feature on the test website and is not shared by the live website.

So, I was hoping that someone might be able to explain why this is happening and provide me with a workaround to reduce the memory usage.

Thanks, Gerroald.

I’m not proposing to attempt to clean the site in its current state but rather to roll back to to backups taken 3 weeks before the hack took place. At that time, nothing untoward was detected by either Wordfence or my hosting provider. I note the point in the cleaning guidelines you referred me to about the danger of old backups but I believe the backups maintained by my hosting provider are not accessible over the web so should be clean.

Once I have rolled back, I will then immediately update WordPress and all the plugins requiring updates, before asking my hosting provider to open up the site again at which point I’ll put the site through multiple malware scanners, including Wordfence.

I’ve done everything I can think of to try to find the weakness exploited by the hacker but, other than identify the hogroasterhire URL as the likely tool used to create the new username with admin permission, I’m no further forward. I was hoping a post here might find someone with an idea but knew it was a long shot.

I’m assuming that my hosting provider (TSOHost) is savvy enough to ensure that my site can’t affect other sites on the server in its current state. I’ve asked them for further details on the nature of the ‘malicious activity’ they detected on the site but don’t know if that will be forthcoming.

This bug is affecting my photo albums too. Can you give an estimate of when it will be fixed?

I just updated to WordPress 5.1.1 (from 4.9.10) and hit the same problem, getting the same error message as quoted by @webdesads above. Am using the most uptodate version of the plugin (v1.13). A bit worried that this issue was logged 5 months ago but still no response from the developer, despite the plugin having been updated in the interim.

Just adding this because I forgot to check the email notification box when I posted my previous message.

I have the same problem. I updated to v3.0.5 of the plugin but that did not fix it. Would welcome advice on how to proceed.

Update not appearing yet in WordPress repository yet but will keep an eye out. Thanks for the reassurance that, in the interim, the risk is minimal.