Fandango Interactive
Forum Replies Created
-
Just thought I’d let you know that a guy found a solution for this that only requires a couple of extra lines in php.ini.
The solution is posted in this Facebook thread – https://www.facebook.com/groups/advancedwp/permalink/1365808633481347/ – and is as follows:
The PHP variables manager [SiteGround] wouldn’t allow it [php.ini] to be modified so I dropped it in manually and seems to be working with these customisations [in php.ini]:
opcache.interned_strings_buffer = 8 opcache.memory_consumption = 256 opcache.enable = OnI have tested this with the combination that caused so many issues before (Yoast + Wordfence + various plugins + PHP7 + SiteGround) and can confirm that everything now works 🙂
- This reply was modified 9 years, 2 months ago by Fandango Interactive. Reason: highlight code
@kevinmamaqi – Do you get the same error if you disable Wordfence and then enable Yoast?
Hi
@stodorovic – I don’t know how to disable opcache so would need some help.
@hristo-sg – I am not using Broken Link Checker but still get this kind of error on all web sites where Yoast is activated. I have an open ticket over at Siteground where your techs have access to a staging copy of a web site where the issue is present.
I looked at the link but to be honest I haven’t much of a clue about the technical aspects of this – just trying to report issues and symptoms from a user/admin perspective.
But here is the permalink to the Facebook post where someone mentioned Siteground as the most likely culprit. It’s in a closed group so I don’t know if you can see it, but I’m posting it anyway. Please remove if inappropriate.
https://www.facebook.com/groups/advancedwp/permalink/1309688169093394/
Someone in the Advanced WordPress group on Facebook said a while ago that this is most likely a Siteground issue and not related to either WP or any of the plugins. I never even thought of that until this guy pointed it out but he is probably right. I still have the same issues on all of the web sites in question, and they’re all with Siteground (although on cloud hosting).
So @kevinmamaqi, please open a ticket at Siteground. If more people report the issue then they hopefully will put some priority on it.
- This reply was modified 9 years, 3 months ago by Fandango Interactive.
Forum: Plugins
In reply to: [WP Jump Menu] Breaks admin on PHP7?After further investigations, it turned out that WP Jump Menu was not to blame. It is verified as PHP 7 compatible by https://wordpress.org/plugins/php-compatibility-checker/
Marking this as resolved.
After further investigations it turned out that Yoast was not the culprit here. Marking this as solved.
This is an example of the error that is causing the problem. Sometimes they are displayed like this, and sometimes they just result in a 404:
Fatal error: Allowed memory size of 2147483648 bytes exhausted (tried to allocate 292751915857477136 bytes) in /home/XYZ/public_html/wp-admin/includes/menu.php on line 49
- This reply was modified 9 years, 6 months ago by Fandango Interactive.
Forum: Plugins
In reply to: [Weather Station] Parse errorEdit: Seems to be working for me now. Not sure why though!
Forum: Plugins
In reply to: [Weather Station] Parse errorSame message here. Can’t even access WordPress backend because of this. Please help!
Parse error: syntax error, unexpected T_USE, expecting T_FUNCTION in /wp-content/plugins/live-weather-station/includes/class-live-weather-station.php on line 30
No, I have not installed any extra firewalls.
After a series of updates to the theme and other plugins, this seems to have been resolved. So probably not a problem with the Zoom Magnifier in the first place.