Michael Torbert
Forum Replies Created
-
First of all, there’s no need to use exclamation points. You’re using free software and asking volunteers for free help. Have some respect and stop yelling.
As for the issue you’re reporting, we’re unable to reproduce it, which indicates it’s something specific to your website, such as a plugin or theme conflict. You can narrow it down with these troubleshooting steps: https://semperplugins.com/documentation/how-to-troubleshoot-issues-with-all-in-one-seo-pack/
As 3.3 was just released yesterday, we don’t have an estimate at this time for 3.4. You can follow along with development on the official Github repository. https://github.com/semperfiwebdesign/all-in-one-seo-pack/
- This reply was modified 6 years, 7 months ago by Michael Torbert.
This is actually on the roadmap for the next major version, 3.4. https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/1331
As I said above, we’ve got an issue open for this already. https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/3014
There’s no need to pile on the comments. We’re aware of the problem, have developed a fix, and are in the final stages of testing and code review now so we can get the fix out ASAP. Additional comments and threads will delay our ability to get the release out quickly.
If you can’t wait for the release and need to install it now, you can download it here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/archive/2aa275f968b12677c34820eb1d696d3fbc3155e2.zip
You can also turn off debug mode on your live site so that you don’t see these warnings.- This reply was modified 6 years, 7 months ago by Michael Torbert.
Right, we get that deactivating AIOSEOP resolves the issue. However, activating just AIOSEOP doesn’t recreate the issue on our end. Therefore, it’s a good bet that there’s a plugin/theme conflict, or some other issue specific to your environment. The troubleshooting steps provided are the first steps to narrowing down a conflict so that we can fix it for you. These are the same steps that any other plugin/theme developers provide so that the problem can be narrowed down and reproduced.
If you would like us to assist you with them, you can contact us here: https://semperplugins.com/contact/
Where it asks for a license key, just paste the URL to this forum thread.I’ve opened a Github issue here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/3023
Please try these troublehshooting steps to narrow down a possible plugin or theme conflict: https://semperplugins.com/documentation/how-to-troubleshoot-issues-with-all-in-one-seo-pack/
Make sure to clear all caching.If you’ve been able to confirm a plugin/theme conflict, you can create an issue on Github to report it: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/new?assignees=&labels=&template=bug_report.md&title=
If, with all other plugins deactivated, and your theme switched to an unmodified default theme (Twenty Nineteen), and you’re still experiencing problems, you can open an issue for those as well. Please make sure to provide exact steps to reproduce each issue, along with any additional helpful information such as screenshots.
First, please stop spamming us. You’ve posted on multiple sites in multiple threads.
As you know, we’ve opened an issue to look at resolving it here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/3014
Fortunately it’s only a warning, not an error, so you can safely ignore it. Turn off debug mode on your live site and the warning should go away.
- This reply was modified 6 years, 7 months ago by Michael Torbert.
- This reply was modified 6 years, 7 months ago by Michael Torbert.
I’ve opened an issue to look at resolving it here: https://github.com/semperfiwebdesign/all-in-one-seo-pack/issues/3014
Fortunately it’s only a warning, not an error, so you can safely ignore it. Turn off debug mode on your live site and the warning should go away.
Thank you for your kind words! 🙂
It’s a warning, not an error. Turn off debug mode on your live site: https://ww.wp.xz.cn/support/article/debugging-in-wordpress/#wp_debug
Hi Jason, thanks for the kind words. We’re glad you’re enjoying the plugin. 🙂
Since this was posted in two places, I’ll post my reply from the other thread here: https://ww.wp.xz.cn/support/topic/litespeed-vs-all-in-one-seo-conflict-on-output-handler/#post-12084145 Please don’t double-post in the future. It creates more work for everyone.
To summarize, the log is simply pointing out that it noticed output buffering from Litespeed. It is not saying there’s a problem.
Unless you’re encountering a problem, you can safely ignore it, and should disable logging on a production site.
Eventually, AIOSEOP will avoid output buffering entirely so none of this will matter anyway.
This thread has been marked as resolved.- This reply was modified 6 years, 7 months ago by Michael Torbert.
Forum: Plugins
In reply to: [LiteSpeed Cache] Litespeed vs All in One SEO: conflict on output handler?AIOSEOP dev here. I can confirm that what you’re seeing in the log is simply a notice that LiteSpeed’s output buffering was detected, not that there’s any actual problem from it.
Unless you’re experiencing a problem, you can safely ignore the notice.
We typically recommend having logging off on production sites unless you’re encountering a problem.Hi Ray! Thank you for the kind words. 🙂