Conversation
supportHi there, the last update makes it impossible to work on the website in backend, the other problem it kills my sites on the frontend. The First Problem: all websites (excluded Posts) are not editable, it shows only a blank site, no gutenberg editor, nothing. Sites on frontend shows only the header rows of my theme (Blocksy) but without an menu, logo or searchfield. The rest of the site blank too. For heavens sake, I have a daily backup and wpvivid can roll back Plugin updates to the former version, instead of these security measures my whole website were broken! T That’s not okay… Don’t ask for access to my website, I rolled back to the former version who works okay and I will not test this version again, because it’s a productive site not a private or hobby website!
Hi @jackmac71 , My apologies for the issues you encountered with our plugin and all the inconvenience it caused you. Some changes in a recent update caused fatal errors on a small number of websites. We released a new update early on Monday, and we have not received any reports of issues since then. Please update to the latest version of the YouTube Feed plugin (version 2.6.2 or higher) and check if that resolves your issue. If it does not, please let us know and if possible, please share the error message you are getting as that will help us address the specific issue. You can get the error message by activating the WordPress debugging and retrieving the WordPress debug log file as described in this article: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/#wp_debug_log Please let me know if you have questions. Best Regards,
Hi @jackmac71 , My apologies for the issues you encountered with our plugin and all the inconvenience it caused you. Some changes in a recent update caused fatal errors on a small number of websites. We released a new update early on Monday, and we have not received any reports of issues since then. Please update to the latest version of the YouTube Feed plugin (version 2.6.2 or higher) and check if that resolves your issue. If it does not, please let us know and if possible, please share the error message you are getting as that will help us address the specific issue. You can get the error message by activating the WordPress debugging and retrieving the WordPress debug log file as described in this article: https://developer.wordpress.org/advanced-administration/debug/debug-wordpress/#wp_debug_log Please let me know if you have questions. Best Regards,