When seeking help with this issue, you may be asked for some of the following information:
WordPress version 6.5.2
Active theme: ANIMACEWP (version 1.1.8)
Current plugin: Site Reviews (version 7.0.1)
PHP version 8.1.28
Error Details
=============
An error of type E_ERROR was caused in line 43 of the file /srv/htdocs/wp-content/plugins/site-reviews/plugin/Plugin.php. Error message: Uncaught BadMethodCallException: Method [filterString] does not exist. in /srv/htdocs/wp-content/plugins/site-reviews/plugin/Plugin.php:43
Stack trace:
#0 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Plugin.php(205): GeminiLabs\SiteReviews\Application->__call(‘filterString’, Array)
#1 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Modules/Migrate.php(96): GeminiLabs\SiteReviews\Application->path(‘plugin/Migratio…’)
#2 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Modules/Migrate.php(31): GeminiLabs\SiteReviews\Modules\Migrate->availableMigrations()
#3 [internal function]: GeminiLabs\SiteReviews\Modules\Migrate->__construct()
#4 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Container.php(110): ReflectionClass->newInstanceArgs(Array)
#5 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Container.php(219): GeminiLabs\SiteReviews\Container->construct(‘GeminiLabs\\Site…’)
#6 [internal function]: GeminiLabs\SiteReviews\Container->GeminiLabs\SiteReviews\{closure}()
#7 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Helper.php(353): call_user_func(Object(Closure))
#8 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Helper.php(239): GeminiLabs\SiteReviews\Helper::runClosure(Object(Closure))
#9 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Container.php(220): GeminiLabs\SiteReviews\Helper::ifTrue(true, Object(Closure), Object(Closure))
#10 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Container.php(67): GeminiLabs\SiteReviews\Container->resolve(‘GeminiLabs\\Site…’, Array)
#11 /srv/htdocs/wp-content/plugins/site-reviews/plugin/Application.php(151): GeminiLabs\SiteReviews\Container->make(‘GeminiLabs\\Site…’)
#12 /srv/htdocs/wp-content/plugins/site-reviews/site-reviews.php(32): GeminiLabs\SiteReviews\Application->init()
#13 /wordpress/core/6.5.2/wp-settings.php(517): include_once(‘/srv/htdocs/wp-…’)
#14 /srv/htdocs/wp-config.php(83): require_once(‘/wordpress/core…’)
#15 /wordpress/core/6.5.2/wp-load.php(55): require_once(‘/srv/htdocs/wp-…’)
#16 /wordpress/core/6.5.2/wp-admin/admin-ajax.php(22): require_once(‘/wordpress/core…’)
#17 {main}
thrown
Here is the error –
Fatal error: Uncaught ArgumentCountError: Too few arguments to function feedthemsocial\updater_init::__construct(), 0 passed in /home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/feed-them.php on line 121 and exactly 1 expected in /home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/updater/updater-check-init.php:70 Stack trace: #0 /home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/feed-them.php(121): feedthemsocial\updater_init->__construct() #1 /home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/feed-them.php(572): Feed_Them_Social::instance() #2 /home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/feed-them.php(576): feed_them_social() #3 /home2/bloomjo0/public_html/wp-settings.php(447): include_once(‘/home2/bloomjo0…’) #4 /home2/bloomjo0/public_html/wp-config.php(90): require_once(‘/home2/bloomjo0…’) #5 /home2/bloomjo0/public_html/wp-load.php(50): require_once(‘/home2/bloomjo0…’) #6 /home2/bloomjo0/public_html/wp-admin/admin.php(34): require_once(‘/home in?/home2/bloomjo0/public_html/wp-content/plugins/feed-them-social/updater/updater-check-init.php?on line?70
]]>We website is running on the latest version of woocom and wordpress with your plugin, many users have reported “critical error” after payment, while looking upt he logs, your plugins name came too often, the problem disappers when we disable the plugin.
We reported this problem to our payment gateway (razorpay) and they also pin-pointed your plugin’s name to cause the error.
Could you please look into this and have this addressed?
2022-08-25T06:26:53+00:00 CRITICAL Uncaught Error: Call to undefined function attribute_slug_to_title() in /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php:286
Stack trace:
#0 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php(191): readCartCB('14693')
#1 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/woo-razorpay.php(1536): handleCBRecoveredOrder('14693')
#2 /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/woo-razorpay.php(1402): WC_Razorpay->updateOrder(Object(Automattic\WooCommerce\Admin\Overrides\Order), true, '', 'pay_K9laQOjswl3...', NULL)
#3 /home/u707151460/domains/durvient.com/public_html/wp-includes/class-wp-hook.php(307): WC_Razorpay->check_razorpay_response('')
#4 /home/u707151460/domains/durvient.com/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters('', Array)
#5 /home/u707151460/domains/durvient.com/public_html/wp-in in /home/u707151460/domains/durvient.com/public_html/wp-content/plugins/woo-razorpay/includes/support/cartbounty.php on line 286
]]>After the most recent wordpress 5.9.2 update, wordpress sent me a message that the pagebuilder plug in could not be updated and was deleted. So, now my website has lost all of its template formatting. Yet, when I try to reinstall the plug in, I get the message: “Installation failed: Destination folder already exists.”
What can I do to rectify this error?
]]>Deactivated all the plugins except Events Calendar (required to run Pro) and still crashes to white screen.
Running latest versions of WordPress and Php – don’t know what to do next.
Could the Pro Plugin be corrupt? – tried a backup from 2019 and same crash to white screen.
Thanks
]]>https://maxim.hipedigital.net/
When I deactivate the plugin, thankfully, it reverts and works again. I read through the documentation and there’s nothing that denotes that a homepage would go completely blank if something is not set up correctly.
Please advise with the proper protocol? i am trying to translate the site from English as the default language and to have a spanish version.
]]>