Support » Plugin: Code Snippets » Site Broke – Plugin Conflict

  • atul99999


    I recently installed this plug in in my Dev and Testing environment and moved lot of code from function.php to different snippets. Very happy with the way it works.

    However, needed to migrate this to production site. So, I installed Code Snippet in production site. As soon as, I activated the plug-in – THE SITE WENT DOWN.

    I haven’t moved any code snippet to testing to production yet. So there is no chance that one of the code snippet might have caused site to bring down. In any case, I just deleted Code Snippet folder in Production and it got restored.

    Now, the question is, how do I enable code snippet in Production – without breaking.

    The difference between Production Site and Testing site is that there are some extra plugins in production, which I have uninstalled in Dev and Testing. These Plug-ins are:
    1. Yoast SEO
    2. iThemes Security
    3. Litespeed Cache
    4. Mail Chimp for Woocommerce
    5. Google Ads for Woocommerce
    6. Facebook for Woocommerce

    On all other subjects – Testing and Production site are exactly same.

    A request to help me if any one knows conflict of Code Snippet with any of the above 6 plugins.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Shea Bunge


    Would it be possible to turn on debug mode and see what error is being produced?



    It is happening only on Production site.

    Can’t experiment anything on Production site, unfortunately.



    Update: I installed the same set of plugins as in Production to Testing site + Code Snippet.

    Testing site is working fine with Code Snippet and all plugins in Production.

    I am not been able to understand, why it can not work in production !!

    Any hint will be helpful.

    Plugin Author Shea Bunge


    There’s nothing wrong with turning on error reporting on a production site, as long as it’s still in maintenance. If you’re worried about visitors accidentally seeing them, then turn on the error log setting.

    Once you know what the error message, then we can work out a solution.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.