Just the Doctor

Possibly even worse for those not ‘in the know’, clicking on the relevant link in the ‘recommendation’ leads to a ‘This page does not exist’ with a search field. The search function lends to the impression that WordPress do not know what they are talking about because, searching manually for Persistent Object Cache renders a zero result !!!

Clearly not – even with each subsite having its own separate Google entry which works well outside the Site Kit environment.
Thus my installation falls into the category of “plugin [used] on individual sites on the network” which, to repeat, shows errors too.

Same problem with similar system setup except this problem does not occur on all installations. However, there are no themes nor plugins on the system that does not work that are not on the functional systems – on the contrary, the functional systems have additional plugins.

Sadly, a certain jcastaneda – presumably of WordPress – has deemed that this theme, possibly one of the best, easiest to use and certainly most popular, does not conform, despite the version being 5 months old with many many thousands, if not millions, of installs.

Apparently there are security concerns about certain aspects of the coding – although Suffusion is one of the themes that, as far as I know, has never appeared in the WordFence warnings despite its massively widespread use.
Also, there is mention of a lack of translation readiness – yet again, witness the vast number of installations, this does not appear to be a problem in the real world.
And most absurd, the lack of integration into the WordPress customizer. This really annoys me personally since the customizer is an atrocious piece of kit that only serves to make customisation of the site unpredictable. Far from Suffusion being a problem with the Customizer, it is the Customizer that manages to disrupt Suffusion.

I hope that Santoyan doesn’t stop completely – or rather, I hope that enough people make their voices heard that jcastaneda and his club manage to change their stance.

This flaw has already been mentioned and explained in topics on numerous occasions by other users. Yet another new topic seems to be going over the top – it should be clear by now what the problem is: Time.ly simply ignores timezones and publishes as UTC when an event is not repeating.

Problem solved.

Disable “Hide WordPress Version” in the WordFence options and all is fine…

Hi Jeremy,

This seems an awfully long winded way to go about it and it is costing you a lot of time too.

I would like recsf.eu removed from my list please.

Thanks

If you mean does it function across all the blogs on the site, yes. It is installed in the network admin and is usable on all the sub-sites.

I am using WordPress multisite but under Network admin there is no option to update the database – that only appears under each individual site. As I say, the one site appears to have updated without a hitch, the other two just hang on updating database…