Carolina

Hi @dyin,

Thank you for reporting this issue. We really appreciate your feedback. Our team will investigate what’s causing it and work on a fix that will be included in an upcoming release.

Regards,

Carolina

Hi @csdsubscriber,
Thanks for the detailed feedback and for your kind words about Code Snippets!

From what you’ve described, it sounds like the issue may involve cached versions of your snippets being served, rather than the latest saved copy. The fatal error you encountered (with duplicate function or procedure names) often happens when an older version of the code is still loaded alongside the newer one.

Since you’re using SiteGround shared hosting, there are a few additional caching behaviors to be aware of that may explain why older snippet versions sometimes persist.

Here’s what we recommend:

1. Fully Clear All SiteGround Caches
• In your WordPress dashboard, open Speed Optimizer → Caching → Dynamic Cache and click Flush Cache.
• Then go to File-Based Cache and click Flush Cache again.
• If Memcached is enabled (via Site Tools → Speed → Caching → Memcached), click Flush Cache there as well to clear the object cache

2. Temporarily Disable Dynamic Cache
• In Speed Optimizer → Caching, turn off Dynamic Cache entirely for testing.
• SiteGround’s Dynamic Cache sometimes retains compiled PHP output even after changes, so this step helps confirm if the cache is masking a snippet update

3. Confirm Code Snippets Regeneration
• Open your snippet, make a simple edit (like adding a comment), save, then deactivate → reactivate it.
• This forces Code Snippets to recompile and reload your snippet

4. Exclude Critical Pages from Caching
• If your shortcode displays dynamic output, consider excluding its page from Speed Optimizer caching.
• Then, purge the cache once from Site Tools → Speed → Caching → Dynamic Cache → Flush Cache .

Test in an incognito/private browser, with your CDN disabled, to ensure you’re seeing a fresh request.

If you’ve gone through these steps and the issue persists, it may help to reach out directly to SiteGround’s Support Team. They can perform a server-level cache purge for Dynamic Cache, Memcached, and PHP OPcache to completely clear out stale data.

Thanks again for using Code Snippets 🙂

Best regards,
Carolina

Hi @robbert444

Thank you so much for your kind words and for taking the time to leave this review. We’re a small team, and your support truly means a lot to us. We’re also really glad to hear that the Pro version has been even more useful for you. 🙏

Hi @rgpe ,

Thank you so much for reaching out and for reporting this issue. I was able to replicate the problem on my end using WordPress version 6.1.1 together with the latest version of our plugin.

Please note that WordPress 6.1.1 was released on November 15, 2022—almost three years ago. Unfortunately, we can’t guarantee full compatibility with versions that old, as our plugin is designed to work best with more recent WordPress releases.

To better understand the issue, I tested several versions of our plugin with WordPress 6.1.1 in a clean installation—without any additional plugins or custom themes. Based on these tests, I found that version 3.5.1 does not work properly with this WordPress version, while version 3.5.0 appears to function correctly and allows you to edit snippets as expected.

If updating isn’t possible in your case, you can download version 3.5.0 of our plugin from the plugin’s Advanced View on ww.wp.xz.cn here:
👉 https://ww.wp.xz.cn/plugins/code-snippets/advanced/

Or directly from GitHub here:
👉 https://github.com/codesnippetspro/code-snippets/releases/tag/v3.5.0

Upgrading is very important for both security and stability. The recommended approach is always to work with the latest stable versions of WordPress and your plugins to ensure optimal performance and to prevent compatibility or security issues.

I hope this helps you! Please don’t hesitate to reach out if you need any further assistance.

Regards,

Carolina

Since we haven’t received any further feedback, I’ll go ahead and close this ticket for now. Please don’t hesitate to reopen it anytime if needed—we’ll be happy to help.

Hi @eskimopies ,

Since we haven’t received any further feedback, I’ll go ahead and close this ticket for now. Please don’t hesitate to reopen it anytime if needed—we’ll be happy to help.

Best regards,

Carolina

Hello @secretja,

As promised, we brought up this issue in our team meeting. With the recent changes on the frontend of our plugin—moving to a React-based approach—it is expected to be more demanding on the browser, which can result in the kind of issue you reported.

We’ll be running deeper tests with scenarios involving several large snippets, and if improvements are possible, we’ll definitely work on addressing this in future releases.

Thank you again for your valuable feedback. I’ll go ahead and close this ticket for now, but please feel free to reopen it anytime if needed.

Best regards,
Carolina

Hi @jbradt ,

Thank you so much for reaching out and for reporting this issue. I was able to replicate the problem on my end as well, so we’ll be investigating it more deeply. If needed, we may also open an issue on our GitHub to track progress.

I’ll keep you updated as soon as we have more information. Thanks again for bringing this to our attention—it really helps us improve the plugin.

Best regards,
Carolina