We don't have an account with WPML so I don't know about getting a key for that. I'm not seeing the screenshot you said to look at.
I unregistered Toolset and got the key from our account here and re-registered. It gave a green checkmark that it is registered, but that connection message at the top is still there. That message only appears on the main plugins page and the Add Plugins page. I tried clearing the site cache and that didn't solve it. I cleared my browser cache and that didn't solve it either.
I tried disabling Toolset Blocks because that is the one causing the error. When I went to our Freelancers page then, it didn't work because the plugin was disabled. I didn't get another instance of the error. Then I reactivated the plugin and went to the page again, and another instance of the error occured.
I'm unclear on anything with Woocommerce and Toolset. I don't think I've used any of Toolset's Woocommerce features. We do not have a product archive page created with Toolset. We're using the product template provided by the theme for that.
I tried deactiving Toolset Woocommerce Blocks and that did not stop the warning. So the problem is in Toolset Blocks somewhere.
OK, I think I did everything correctly. Let me know if you need anything further. Thanks for trying to figure these out.
Note that in the Dashboard, you'll see a red top admin menu item that says "Site Errors" if it is doing the same thing with this warning:
Date: [20-Sep-2023 19:44:26 UTC]
Type: PHP Warning
Message: Undefined array key 0
In: /_____/________/public_html/wp-content/plugins/toolset-blocks/application/models/WooCommerce/WcQuery.php on line 428
Click on that and that will show you the WPMemory page where it is saying it can't run because of the errors and then it shows the error log files below that. The one I posted above looks like it is the only one still happening currently.
No wait, now I'm seeing two others after scrolling deeper into the middle error log file:
Date: [20-Sep-2023 18:39:08 UTC]
Type: PHP Warning
Message: Trying to access array offset on value of type bool
In: /_____/________/public_html/wp-content/plugins/contact-form-7-mailchimp-extension/lib/handler.php on line 201
Date: [20-Sep-2023 15:03:23 UTC]
Type: PHP Warning
Message: Undefined array key "section_content_sticky_mobile"
In: /_____/________/public_html/wp-content/plugins/riode-core/elementor/elements/riode-section.php on line 2779
I'll have to figure these out on this end. This is very frustrating as these were not happening on the development site when I used Duplicator Pro the second time.
I hope you're able to see the Toolset blocks one on the migrated version. If you can't see it, then I have no idea how to fix it on this end.
Hi there,
Thank you we have the website available on:
hidden link
We will not consider a log created by another third party plugin and instead, we will rely on the WordPress debug mode itself.
We enabled the debug mode and there is no such warning generated by WordPress itself. You can check the dashboard which will list the warnings and errors at the top.
Please consider that we do not claim that we are compatible with WP Memory plugin and checking the WordPress default debug feature we do not have any warnings like the one you shared.
thank you for your understanding.
The log is not created by the third party plugin. It is simply displayed by it. The log file where the warnings are showing is here:
/_____/________/public_html/error_log
I'm thinking the warnings would be adding to this file regardless of the presence of the WPMemory plugin.
On the live site, that WPMemory plugin is showing 3 different error log files and the second one of the three is where these warnings are happening.
The 3 different error logs files being shown on the live site are:
1) error_log
2) /_____/________/public_html/error_log
3) /_____/________/public_html/wp-admin//error_log
On the live site, error logs #1 and #3 above have not had any new entries since September 17, so I think we're OK there. Only the #2 one has new and ongoing entries, including the toolset-blocks one.
On the migrated version of the site on your server, WPMemory is showing only one log file here:
/___/____________/____/_______._____________.___/__________/public_html/wp-content/debug.log
That log location is not present among the three that are present on the live site.
Is there any way you can have one for .../public_html/error_log on the migrated site show so we can see if the warnings are appearing there.?
I do not know the difference between these different locations for so many different log files or why our live site has 3 different ones. I don't know what has been set up that has all of these appearing on the live site. I do not think I've set anything up to generate them. I think they are present from whatever our ISPs default settings for hosting and WordPress installations are.
Hi there,
I am also not familiar with any sort of a file named error_log, which is not a WordPress-generated file so I am not sure about that.
The one that WordPress generates is called debug.log and that should be the main error log to check.
I installed the FIle manager plugin on the copied website and accessed the debug.log file:
[25-Sep-2023 20:31:53 UTC] PHP Warning: Undefined array key "plugins" in /mnt/BLOCKSTORAGE/home/1055182.cloudwaysapps.com/czcyearejj/public_html/wp-content/plugins/contact-form-7-mailchimp-extension/lib/deactivate.php on line 223
[25-Sep-2023 20:31:53 UTC] PHP Warning: foreach() argument must be of type array|object, null given in /mnt/BLOCKSTORAGE/home/1055182.cloudwaysapps.com/czcyearejj/public_html/wp-content/plugins/contact-form-7-mailchimp-extension/lib/deactivate.php on line 223
There are only two warnings that are generated from Contact form 7 Mailchimp extension. The rest are some deprecation messages which are not important as it is a message to show that in the future releases of PHP the code might not work but it has no effect on the current version.
The only Toolset-related messages that I see there are:
[25-Sep-2023 09:12:00 UTC] PHP Deprecated: ctype_digit(): Argument of type WP_Post will be interpreted as string in the future in /mnt/BLOCKSTORAGE/home/1055182.cloudwaysapps.com/czcyearejj/public_html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php on line 134
[25-Sep-2023 09:12:00 UTC] PHP Deprecated: ctype_digit(): Argument of type WP_Post will be interpreted as string in the future in /mnt/BLOCKSTORAGE/home/1055182.cloudwaysapps.com/czcyearejj/public_html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php on line 134
[25-Sep-2023 09:12:00 UTC] PHP Deprecated: ctype_digit(): Argument of type WP_Post will be interpreted as string in the future in /mnt/BLOCKSTORAGE/home/1055182.cloudwaysapps.com/czcyearejj/public_html/wp-content/plugins/cred-frontend-editor/vendor/toolset/toolset-common/inc/autoloaded/field/group/factory.php on line 134
Which are deprecation messages for the Toolset forms plugin.
I do not see any warnings regarding the Toolset.
Thank you.
Understood that you're not able to duplicate the problem we're having. But that still leaves me unable to solve this. Any further suggestions as to how to proceed to stop the warning we're seeing on the live site?
The ISP we are with has a support team that has gone considerably downhill in quality in recent years. I already know the results will be futile asking them to look into this for us. I've urged the client to move to another host where I know their support is superior. It's looking like that's our only remaining chance at solving this.
Hi there I would love to be able to do something, but the issue is that I can not see the issue on our server and on the local installation.
We are plugin developers, so we will need to have the warning on the local machine or our server to be able to investigate and do debugging.
The fact that it is not happening on our server and local installation shows there is no code related issue that we can find a solution for and it must be something on the server.
But we are not server experts to be able to pinpoint the potential issue.
I can suggest the server requirements below:
https://toolset.com/toolset-requirements/
But I am not sure how helpful it can be honestly.
