entrepreneuraj
Forum Replies Created
-
Forum: Plugins
In reply to: [SVG Support] Version 2.4 breaks WP-CLIConfirmed my site is now having the same issues after auto updates with WP-Cron ran via WP-CLI.
Now every minute WP-Cron is emailing me an error log having to delete plugin until fixed.
logs:PHP Fatal error: Uncaught Error: Call to a member function setAllowedTags() on null in /home/eajglobal/public_html/wp-content/plugins/svg-support/functions/attachment.php:246 Stack trace: #0 /home/eajglobal/public_html/wp-includes/class-wp-hook.php(307): bodhi_svgs_apply_filters() #1 /home/eajglobal/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #2 /home/eajglobal/public_html/wp-includes/plugin.php(474): WP_Hook->do_action() #3 /home/eajglobal/public_html/wp-settings.php(565): do_action() #4 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1271): require('/home/eajglobal...') #5 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1192): WP_CLI\Runner->load_wordpress() #6 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start() #7 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process() #8 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() #9 phar:///usr/bi in /home/eajglobal/public_html/wp-content/plugins/svg-support/functions/attachment.php on line 246 Fatal error: Uncaught Error: Call to a member function setAllowedTags() on null in /home/eajglobal/public_html/wp-content/plugins/svg-support/functions/attachment.php:246 Stack trace: #0 /home/eajglobal/public_html/wp-includes/class-wp-hook.php(307): bodhi_svgs_apply_filters() #1 /home/eajglobal/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters() #2 /home/eajglobal/public_html/wp-includes/plugin.php(474): WP_Hook->do_action() #3 /home/eajglobal/public_html/wp-settings.php(565): do_action() #4 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1271): require('/home/eajglobal...') #5 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Runner.php(1192): WP_CLI\Runner->load_wordpress() #6 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/WP_CLI/Bootstrap/LaunchRunner.php(23): WP_CLI\Runner->start() #7 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/bootstrap.php(77): WP_CLI\Bootstrap\LaunchRunner->process() #8 phar:///usr/bin/wp/vendor/wp-cli/wp-cli/php/wp-cli.php(27): WP_CLI\bootstrap() #9 phar:///usr/bi in /home/eajglobal/public_html/wp-content/plugins/svg-support/functions/attachment.php on line 246 Error: There has been a critical error on this website.Learn more about troubleshooting WordPress. There has been a critical error on this website.
Forum: Plugins
In reply to: [LiteSpeed Cache] PHP 8.0 BugSeems to be working now, only difference I can see is the WordPress Version auto updated. @ductm seems to work now on PHP 8.0
Forum: Plugins
In reply to: [LiteSpeed Cache] PHP 8.0 BugDowngrading to 7.4 does remove the error but PHP 7.4 reaches EOL FOR ACTIVE SUPPORT in 3 months leaving only security updates after that.
The cache headers show your using browser caching which is done by wp optimise. Personally I always opt for the built in server cache in litespeed and use wp optimise purely to keep my database lean.
Hi Collins,
When authenticating it sends me to the US data center which Zoho then redirects me to the EU data center.
All I got back was error code 1007 which a bit of googling came across a Zoho support thread that mentioned checking which servers it was connecting to.
I’ve looked in your code in plugin editor and had to change the API URLs that are hard coded in ../authlify/zoho.php to the .EU servers.
That fixed it for me I can’t see anywhere in the code where it autodetects the data center.
- This reply was modified 4 years, 7 months ago by entrepreneuraj.
@totallyminimad I am successfully running it with OpenLiteSpeed on Ubuntu 18 with LSCache it detected LSCache and disabled its own cache but still works great at optimising the database on schedule.
Just make sure that wp-cron can bypass the no abort check with a htaccess rule for example.
<IfModule LiteSpeed>
DisableCgiOverride On
RewriteEngine On
RewriteRule (wp-cron|backupsolution|someothersolution)\.php – [E=noabort:1, E=noconntimeout:1]
</IfModule>