threadi

I would strongly advise against modifying files from the WordPress core such as version.php – especially in this way. Doing so will ruin your project.

Your screenshot also shows something completely different as the cause. According to this, the plugin you are using, “EMC – Easily Embed Calendly Scheduling,” is missing a file. I suspect this was a faulty setup on their part.

To solve this, I would recommend the following:

• Log in to your hosting via FTP and delete the directory /wp-content/plugins/embed-calendly-scheduling/. Your host’s support team can tell you how to connect via FTP.
• You should then be able to log in to the backend as normal.
• After that, you can simply reinstall and activate the “EMC – Easily Embed Calendly Scheduling” plugin. The previous settings of the plugin should still be there.

According to the manual, you can also pass the WP_Post object directly to get_the_post_thumbnail(): https://developer.ww.wp.xz.cn/reference/functions/get_the_post_thumbnail/

However, you may then receive a different error message stating that a string is not possible.

I would therefore recommend checking whether the message really refers to this exact line. Because something doesn’t add up here. With the complete code and the complete message, we could certainly tell you more.

Which variable is the output from var_dump()? If it is from $primaryList, then the error is logical. foreach attempts to loop through an object, which is not feasible in this case. You would need to adjust your code accordingly, e.g. as follows:

foreach( array( $primaryList ) as $primaryListItem ):

$primaryListItem appears to be a string. Use var_dump() to check what exactly is in $primaryList and where its values come from. This should enable you to find the cause of the message.

I would recommend contacting the MailPoet support forum: https://ww.wp.xz.cn/support/plugin/mailpoet/

Unfortunately, the Block Editor does not provide many options for controlling the mobile view here. As already mentioned, the order is determined by the styles used.

In my opinion, you have three options:

• I use this plugin for mobile optimization: https://ww.wp.xz.cn/plugins/tzm-responsive-block-controls/ – it gives you full control over the order.
• You can also solve the order issue with custom CSS, as described above.
• Contact the Gutenberg team with a request for optimizations or additional configuration options. My recommendation would be to first check here to see if there is already an issue on this topic, otherwise create one yourself: https://github.com/WordPress/gutenberg/issues

I also like to use Media & Text. I would by no means describe it as “outdated.” It is an actively maintained block in the Gutenberg directory. And yes, it can be a bit tricky, but it is still well suited for many use cases.

Your PHP deprecated message means that what is happening here will cause an error in future versions of PHP. Usually, you don’t need to worry too much about this, even if it is annoying to see so many entries. Nevertheless, it is good to be aware of this and take a look at it.

The messages are apparently caused by the Responsive Menu plugin. Check whether you are using the latest version of the plugin and, if not, update it. If the messages still appear with the latest version of the plugin, contact their support forum: https://ww.wp.xz.cn/support/plugin/responsive-menu/ – and be sure to mention the PHP version you are using so that they can reproduce the problem and ultimately adjust their code.

The fatal errors in debug.log refers to a database action by WooCommerce. And yes, this could be caused by an outdated database system in your hosting. Unfortunately, based on your description, it is unclear to me which database system you are using. I would recommend meeting the minimum requirements for WordPress, which you can find here: https://ww.wp.xz.cn/about/requirements/ – your host’s support team should be able to help you with this, as it would require replacing the entire database system in your hosting.

At the same time, however, the PHP notice (which should only be understood as a hint) indicates that you may not be using the latest version of WooCommerce. This could also be a reason for the error. So be sure to check whether you are using the latest version of WooCommerce and, if not, update it.

And always remember to make backups before making any changes.

It will work as long as WordPress continues to offer classic widgets. As of today, there is no known end to support of them. Whether and when this will change is impossible to say. I would recommend simply using the plugin. You will probably have no problems with it in the coming years.