Conversation
supportHello everyone, Our website is built with Oxygen, and the Lucky WP TOC plugin is up to date. The PHP server version is 8.2, but we have also tested it with 8.1. For the past few days, the TOC has not been displaying in blog posts or loading on the frontend. However, it appears correctly in the backend. The TOC is integrated on the left-hand side next to the text of the article. Do you have any idea why it suddenly stopped showing? We have embedded the TOC via shortcode, and it has been working smoothly for years. No changes have been made to the settings. Would appreciate any help on this! Thanks in advance. Best regards, Paul The page I need help with: [ log in to see the link]
Hello, Paul! TOC shortcode added to Oxygen template or to Oxygen Post? PS While we don’t fix this, you can use version 2.1.9. This reply was modified 1 year, 3 months ago by LuckyWP .
Hello Dear LuckyWP Support, First of all, thank you for your quick response and support. In our setup, we use an Oxygen Blog Template , where we have placed a Shortcode Element containing the LuckyWP TOC shortcode [lwptoc] . With version 2.1.9 , the table of contents is displayed correctly. However, after updating to 2.1.10 , it no longer works. Since using an outdated version poses potential security risks , we always strive to keep all plugins up to date. Therefore, we would like to understand what you mean by “we don’t fix this.” If the issue will not be addressed in a future update, we may have to consider an alternative solution, which would be unfortunate after many years of using LuckyWP TOC. We truly appreciate your work and hope that this can be resolved, as we would love to continue using your plugin. Looking forward to your feedback and thank you again for your time! Best regards, Paul
Unfortunately, we haven’t received any response to our last message. After five years of using LuckyWP TOC, we were hoping for a solution or at least a clear statement regarding the issue with Oxygen Builder. Since keeping plugins up to date is crucial for security reasons, and there seems to be no fix or further support for this problem, we had no choice but to switch to another TOC plugin. It’s disappointing to leave a plugin we’ve relied on for so long, but without compatibility updates or communication, we couldn’t continue using it in a professional environment. Still, we’d like to thank you for the years of great service and wish you all the best moving forward.
Hello, Paul! TOC shortcode added to Oxygen template or to Oxygen Post? PS While we don’t fix this, you can use version 2.1.9. This reply was modified 1 year, 3 months ago by LuckyWP .
Hello Dear LuckyWP Support, First of all, thank you for your quick response and support. In our setup, we use an Oxygen Blog Template , where we have placed a Shortcode Element containing the LuckyWP TOC shortcode [lwptoc] . With version 2.1.9 , the table of contents is displayed correctly. However, after updating to 2.1.10 , it no longer works. Since using an outdated version poses potential security risks , we always strive to keep all plugins up to date. Therefore, we would like to understand what you mean by “we don’t fix this.” If the issue will not be addressed in a future update, we may have to consider an alternative solution, which would be unfortunate after many years of using LuckyWP TOC. We truly appreciate your work and hope that this can be resolved, as we would love to continue using your plugin. Looking forward to your feedback and thank you again for your time! Best regards, Paul
Unfortunately, we haven’t received any response to our last message. After five years of using LuckyWP TOC, we were hoping for a solution or at least a clear statement regarding the issue with Oxygen Builder. Since keeping plugins up to date is crucial for security reasons, and there seems to be no fix or further support for this problem, we had no choice but to switch to another TOC plugin. It’s disappointing to leave a plugin we’ve relied on for so long, but without compatibility updates or communication, we couldn’t continue using it in a professional environment. Still, we’d like to thank you for the years of great service and wish you all the best moving forward.