aloeroot

Also, I had to change the H3s in framework/widgets/widgets.php to H2s, to avoid a nesting issue with header sizes.

Yes, this is persisting. It’s a child-theming issue, actually. I used the Child Theme Configurator plugin to generate a child theme for this site. With the v1.4.9 update, the child theme develops problems – it looks like a missing style sheet. Reverting to the parent theme fixes the issue.

I think some of your css files must have changed paths with the v1.4.9 upgrade; it’s persisting with the latest release.

I suspect I’m going to have to re-make my child themes, either by scratch or through running the plugin again. I’ll try this when I have some extra time, and will report back.

Further to this, the parent theme is fine. My original child theme, created manually, and the new child theme done with Child Theme Configurator, have non-functioning navigation dropdowns.

I’d hugely appreciate any help you may have to offer on this topic.

Same issue for me. I “live previewed” the parent theme, to see if it’s something in my child (which is nothing but a style.css file) and the dropdown menu is white text on a transparent background; unusable. There are some other layout issues too. I reverted to a backup copy.

I have the same problem here. I restored an older version of the theme, and my front-end and wp-admin are now working again.

The warning about wfDict.php may have happened before the plugin was reinstalled, so it may have been a side-effect of the other issue.

You’re right; the new scan completed without issue and WF seems to be working fine again. Thanks for your help!

I didn’t think to check if there were files in the WF folder when I deleted it, so I can’t answer that. A reinstall seemed to be the fix after all. Thanks.

Thanks; I just wanted to follow up to say that I used this plugin to create the responsive columns, and used CSS styling to round the images off. I like things a bit more hands-on than what the builders offer. This plugin did the job: WEN’s Responsive Column Layout Shortcodes

Thanks for the reply.

^ I should mention this is only the case with the centered header. I’ve switched to the standard header and it’s ok. Thanks!

Hi there; further to this thread, I just purchased the premium version of this theme (because of this post) and was able to upload a header image at a more comfortable size. That said,the height is greater than the recommended 91 pixels, and the logo is now overlapping the navigation bar.

Can you assist, thanks? I had overcome this in the free version of the theme by forcing a new header height in the CSS layer of a child theme, but I was hoping to avoid that messy workaround by purchasing the premium version.

Thank you!

If you guys look in the /docs folder for the theme, there’s a sample child theme. I just installed it and it works fine. Good luck!

My host was blocking incoming traffic from WordPress.com’s IP address as a result of the new Owasp modsec settings…

I disabled rules 960011 and 959151 for my account and Jetpack is fixed. You may just need to ask your host to relax their security as regards any traffic from WordPress.com.

Also, it’s worth noting that you’re probably triggering entirely different rule numbers when you do the things that are making you get redirected to the homepage. Your host will be able to tell which rules by checking your IP against the modsec logs, and hopefully they’re willing to adjust the rules for you (and other WordPress users on the server)

I’m having similar issues at present and if I find the answer today I’ll share it.

I suspect (and this may give you a starting point) that your host may have recently enabled new mod security tools (ie the Owasp ruleset), which is touchy and is causing me to be frequently redirected to the homepage after doing routine tasks.

I’m having the same errors with Jetpack and have a suspicion that it’s also related to the Owasp rules.

You might want to send your IP to your host along with the timeframe of when you were running into these errors to see if they can find evidence in your server’s modsec logs. If they can identify a specific rule you’re tripping, they may be willing to disable it for you. I’ll check in here if I can solve this same issue myself.

Right; thanks.

Ah, I hadn’t configured the “dequeue” line properly, among other things – thank you SO much for your help. That worked.

Thanks very much. I see how this should have done the trick, but I’m now seeing this in the source:

<link rel='stylesheet' id='sigma-parent-css'  href='https://site.com/newsite/wp-content/themes/sigma/assets/css/sigma.min.css?ver=4.0' type='text/css' media='all' />
<link rel='stylesheet' id='sigma-child-css'  href='https://site.com/newsite/wp-content/themes/sigmachild/style.css?ver=4.0' type='text/css' media='all' />
<link rel='stylesheet' id='sigmatheme-css'  href='https://site.com/newsite/wp-content/themes/sigma/assets/css/sigma.min.css?ver=0.1.2' type='text/css' media='all' />

The calls to sigma-parent and sigma-child are there, but the original call to sigmatheme-css seems to be enqeued lower down, still, so my customizations aren’t working. I tried deregistering sigmatheme-css in the functions file but I’m not doing it right, clearly.