carinvazef
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Dashboard Slow but Site FastThe REST API is one way that WordPress and other applications communicate with the server. For example, the block editor screen relies on the REST API to display and save your posts and pages.
The REST API did not process the
contextquery parameter correctly.Forum: Fixing WordPress
In reply to: Dashboard Slow but Site FastDeprecated: ElementorProDeps\DI\create(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 32
Deprecated: ElementorProDeps\DI\autowire(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/functions.php on line 44
Deprecated: ElementorProDeps\DI\ContainerBuilder::writeProxiesToFile(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/ContainerBuilder.php on line 231
Deprecated: ElementorProDeps\DI\Definition\Source\ReflectionBasedAutowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/ReflectionBasedAutowiring.php on line 17
Deprecated: ElementorProDeps\DI\Definition\Source\Autowiring::autowire(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/Autowiring.php on line 21
Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionFile::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionFile.php on line 25
Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionArray::__construct(): Implicitly marking parameter $autowiring as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionArray.php on line 33
Deprecated: ElementorProDeps\DI\Definition\Source\DefinitionNormalizer::normalizeRootDefinition(): Implicitly marking parameter $wildcardsReplacements as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Source/DefinitionNormalizer.php on line 42
Deprecated: ElementorProDeps\DI\Proxy\ProxyFactory::__construct(): Implicitly marking parameter $proxyDirectory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Proxy/ProxyFactory.php on line 38
Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $definitionSource as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87
Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $proxyFactory as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87
Deprecated: ElementorProDeps\DI\Container::__construct(): Implicitly marking parameter $wrapperContainer as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Container.php on line 87
Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::__construct(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 62
Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setClassName(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 75
Deprecated: ElementorProDeps\DI\Definition\ObjectDefinition::setLazy(): Implicitly marking parameter $lazy as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/ObjectDefinition.php on line 158
Deprecated: ElementorProDeps\DI\Definition\Resolver\ObjectCreator::setPrivatePropertyValue(): Implicitly marking parameter $className as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ObjectCreator.php on line 158
Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $definition as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34
Deprecated: ElementorProDeps\DI\Definition\Resolver\ParameterResolver::resolveParameters(): Implicitly marking parameter $method as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/elementor-pro/vendor_prefixed/php-di/php-di/src/Definition/Resolver/ParameterResolver.php on line 34Forum: Fixing WordPress
In reply to: Dashboard Slow but Site Fast@threadi , the dashboard is now loading. At the Plugins > Add Plugin page, I received the following message:
Warning: plugins_api(): An unexpected error occurred. Something may be wrong with ww.wp.xz.cn or this server’s configuration. If you continue to have problems, please try the support forums. (WordPress could not establish a secure connection to ww.wp.xz.cn. Please contact your server administrator.) in /home/tothvioldj/www/wp-includes/functions.php on line 6114
Forum: Fixing WordPress
In reply to: Dashboard Slow but Site Fast@threadi, hi again! I have not been able to identify what exactly is going on. I performed all these steps and nothing. The website is running after I enable WP_DEBUG. However, the dashboard is still struggling to load.
I am hoping to the hosting provider will have someone onboard who can assist me because I am not sure what else to do and my client is getting anxious.
Forum: Fixing WordPress
In reply to: Dashboard Slow but Site FastI was able to work on the site locally and noticed that the WooCommerce plugins significantly slow down the dashboard—particularly Bookings/Appointments, Gift Cards, PayPal Payments, Google Reviews, and Smash Balloon Instagram. After deactivating them locally, the dashboard performance improved.
However, when I deactivated them one by one on the Live site, the lag persisted. This suggests there might be additional factors affecting performance. Do you have any insights or recommendations on further troubleshooting?
Forum: Fixing WordPress
In reply to: Dashboard Slow but Site Fast@threadi, I contacted them, but they are slow. I will keep trying to troubleshoot. Thank you for all your help.
Forum: Fixing WordPress
In reply to: Dashboard Slow but Site Fast@threadi, thank you for your reply!
I am trying to set up staging with WP Staging Pro. I will test locally then. Thank you for that suggestion. I did receive these errors on the dashboard. Are they related to WP Staging?
ce\PayPalCommerce\WcGateway\Settings\SettingsListener::__construct(): Implicitly marking parameter $logger as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce-paypal-payments/modules/ppcp-wc-gateway/src/Settings/SettingsListener.php on line 197
Deprecated: WPStaging\Vendor\GuzzleHttp\HandlerStack::create(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/HandlerStack.php on line 37
Deprecated: WPStaging\Vendor\GuzzleHttp\HandlerStack::__construct(): Implicitly marking parameter $handler as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/HandlerStack.php on line 49
Deprecated: WPStaging\Vendor\GuzzleHttp\Handler\StreamHandler::invokeStats(): Implicitly marking parameter $response as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Handler/StreamHandler.php on line 59
Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::tap(): Implicitly marking parameter $before as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 103
Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::tap(): Implicitly marking parameter $after as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 103
Deprecated: WPStaging\Vendor\GuzzleHttp\Middleware::retry(): Implicitly marking parameter $delay as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/wp-staging-pro/vendor_wpstg/guzzlehttp/guzzle/src/Middleware.php on line 144
ooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\DotNotation::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/DotNotation.php on line 27
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\DotNotation::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/DotNotation.php on line 72
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\TransformerInterface::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/TransformerInterface.php on line 24
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\TransformerInterface::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/TransformerInterface.php on line 33
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayColumn::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayColumn.php on line 26
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayColumn::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayColumn.php on line 41
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayKeys::transform(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayKeys.php on line 23
Deprecated: Automattic\WooCommerce\Admin\RemoteSpecs\RuleProcessors\Transformers\ArrayKeys::validate(): Implicitly marking parameter $arguments as nullable is deprecated, the explicit nullable type must be used instead in /home/tothvioldj/www/wp-content/plugins/woocommerce/src/Admin/RemoteSpecs/RuleProcessors/Transformers/ArrayKeys.php on line 38I updated the hosting package, which definitely helped speed things up, I also solved some issues with several plugins that weren’t updating and I disabled some others that weren’t really doing much to the website. I have cleared up the database tables and have cached left and right. I want to believe it has something to do with the hosting provider. They did report an issue with various clusters one of which was ours.
Speaking of, would you recommend disabling plugins through via FTP? I was thinking I could disable one by one and see how the dashboard reacts.
Thanks again for all your help!