websanity

Well researched nlpro!

I checked out the changelog for blankshield and 0.6.3 was released 23/8/18. It doesn’t mention anything about fixes and there are two comments from the last few days with people reporting the problem that we are all seeing, so I don’t think the latest version works either.

https://github.com/danielstjules/blankshield/issues/15

I added my own comment and hope the author will be able to fix it or say that it is not fixable. One commentor puts it down possibly to this:
https://www.chromestatus.com/feature/5989473649164288

Doesn’t look hopefully.

Hi nlpro,

tabnabbing – good to know correct terminology, thanks!

Yes I think you are right and it is a Chrome issue, but iThemes will probably have to work around that because I doubt Google give a hoot about real world problems – unless they can squeeze money out of it they ain’t interested.

Hi David,

Thanks for replying. Yes, it’s a weird one isn’t it.

The Avada theme (claiming to be the #1 selling WordPress theme, so it’s popular)
https://avada.theme-fusion.com/

Is so big (they say) that they have to have the “Theme” as a theme and two plugins with “required” functionality.

What happens when they update is that it only shows the Theme as needing updating. Only after you have updated that the updated theme decides that its “essential” plugins need to be updated as well and then, and only then, they show up as updates in the WordPress update list.

Hence to update the “theme” you have to update the theme then update the “required” plugins afterwards.

Maybe they view it safer if the theme updates and then the plugins that are needed for it update afterwards. Maybe updating the plugins first would break the theme, hence why they decided to do it that way?

I appreciate it is all a bit odd and very theme specific (albeit it a popular theme). I think I’ve seen the odd update in the past when an update to WordPress made another update to a plugin suddenly appear (a patch/fix for that WordPress release?)

A solution (just an idea – and easy for me to say) might be an option to “double check” for updates. So do what you do now but – if enabled – then schedule to repeat a couple of minutes afterward. In almost all cases this would result in nothing, but in Avada it would catch it if those “required plugins” needed updating afterwards.

OR

Is is possible to have an option to change the order of checking – check the theme first for updates and then the plugins afterwards??? That would do it.

Thanks for getting back to me and I hope you have a happy new year!
Gerald

Even better ?? than 5 stars!

There’s an option in options that says

“X Disable caching a page that contains a shortcode or API call to geo-dependent functions.
At least WP SuperCache, W3TotalCache and ZenCache are supported.”

So that should work for you, although the cost of not caching a page this is used on might be “expensive” if on a home page for example, therefore not being cached. Or – worse – if in a header or footer that will stop the site being cached at all.

G

We also have iThemes security in place which to be quite honest with you has caused us SOOO many problems in the past, yet your site can still get hacked. We tried turning the settings for this off AND disable settings but it still seems to leave behind a shadow of itself even when no active. Anybody else using any security plugins?

Same here – I can get one post to work but then it just errors. This happened BEFORE and AFTER secure certificate went in place, so I don’t think it is that (although that can change IP address which might have a knock on effect???)

I killed the original registration of a new version of jQuery (a WordPress cardinal sin) which just enables us to get to the rest of their scripts killing Revolution Slider ??

I get the same, but it appears because the developers of the original theme cleverly swap in their own version of jQuery and then their other script code effectively kills Revolution Slider (remove their junk scripts and it works, but then mobile menus fail etc.) – your theme doesn’t happen to be based on Foundation 5 by any chance???

A bit late now but I just ran into this problem too. I think it is an issue with the secure cert setup.

https://docs.woothemes.com/document/ssl-by-proxy-problems-network-solutions/

Shame that WooThemes can’t climb off their technical high horse and just provide us a with a work around/hack for the real world.

I just tried on a complete new install with mostly the same components on one of the same hosts and I didn’t encounter the problem. All I can think is that it is something odd to do with the way CRON jobs are handled in those two accounts. One is on a host I have no intimate knowledge of, the other was imported via a cpanel import into the host which might have meant that CRON jobs were handled differently to their normal hosting.

Sorry I can’t throw debug on, on either of the two sites: they’ve had enough down time as it is, and I’d need to break them then debug then get working again. I’ll keep any eye out for this and if I find anything I’ll get back in touch. In the meantime I’ll mark this as resolved. It isn’t. I just can’t see how to pin down the exact circumstances of this. If somebody else encounters this problem this might help for reference.

Thanks.
G

Hi there,

Leave it with me. When I looked in the past the returned page was completely blank (but it did give a proper http response header), but I’ll turn debug on and see what comes up for you.

Yes that it is the backup plugin (the free one). Both sites are setup with automatic weekly backup jobs using that plugin (just of the database and plugins). It has setting to schedule ” with WordPress cron”. A bit dumb having two backup systems but I backup to dropbox using Backwpup and that can sometimes be unreliable (i.e. not there).

More on debug results shortly.

G

I feel for your frustration! I think we can mark this thread as resolved now?

You’re right: I was being paranoid and could have shared the code with you! Sorry – thanks for pointing that out.

But hopefully all good now!

Cool, thanks Chris for your speedy resolution.

Have a good rest of the day,
Gerald