PLEASE NOTE: These forums are no longer utilized and are provided as an archive for informational purposes only. All support issues will be handled via email using our support ticket system. For more detailed information on this change, please see this blog post.

Fatal error: Cannot redeclare class CS_REST_NativeJsonSerialiser

  1. HI there
    I've just upgraded to business license for a clients site and installed the CM add-on and I get the following:

    Fatal error: Cannot redeclare class CS_REST_NativeJsonSerialiser in /home/guild/public_html/wp-content/plugins/gravityformscampaignmonitor/api/class/serialisation.php on line 81

    All the forms on the site break when this add-on is activated.

    Clients website uses WordPress 3.0.1.

    Can someone please help me, I have no idea how to fix this.

    Posted 7 years ago on Tuesday July 26, 2011 | Permalink
  2. It appears you have a plugin conflict. Most likely caused by having another plugin that uses the Campaign Monitor API and they aren't playing well together. Do you have any other Campaign Monitor related plugins installed and activated?

    Posted 7 years ago on Tuesday July 26, 2011 | Permalink
  3. Hi Guildaccountants,

    Would it be possible for you to send your WP login to david@rocketgenius.com? I'd like to figure out which plugin is causing the conflict and also resolve any other conflicts between that plugin and Gravity Forms. Thanks!

    Posted 7 years ago on Tuesday July 26, 2011 | Permalink
  4. I am using Campaign Monitor Ajax Login on the site also. I assume this would be the cause. I will do some testing and see if this resolves the issue. thanks

    Posted 7 years ago on Tuesday July 26, 2011 | Permalink
  5. Ok great, that has fixed the fatal error, however now when I create a Campaign Monitor feed, and save it.. it does not save? - I go back to Campaign Monitor page of my admin and it says I have no Campaign Monitor feeds and keeps promoting me to create one, which i've done twice now

    Any ideas on this one?

    Posted 7 years ago on Tuesday July 26, 2011 | Permalink
  6. Please contact David directly at his email above and he can assist you with this issue as he will have to test on your site as it's a site specific issue.

    Posted 7 years ago on Wednesday July 27, 2011 | Permalink
  7. Hi Guildaccountant,

    I've sent you an email with a bug fix.

    For any other users experiencing "cannot redeclare" errors with the Campaign Monitor add-on, send me an email for the bug fix.

    Posted 7 years ago on Wednesday July 27, 2011 | Permalink
  8. Hi, there.
    I had same issues as well..
    I am having wordpress 3.2.1
    my email address is nicholas@clickrmedia.com
    hope to get your reply soon.

    Posted 7 years ago on Friday July 29, 2011 | Permalink
  9. Hi Nicholas,

    I've just sent you the updated version.

    Posted 7 years ago on Monday August 1, 2011 | Permalink
  10. Thanks for the update. :)

    Posted 7 years ago on Tuesday August 2, 2011 | Permalink
  11. I have both the campaign monitor addon and paypal addon and receiving this error.

    Thank You,
    Robb
    partner [at] cyteworks.com

    Posted 7 years ago on Wednesday September 28, 2011 | Permalink
  12. @cyteworks Are you running the latest versions of both those Add-Ons? Please make sure no updates are available for both.

    Posted 7 years ago on Wednesday September 28, 2011 | Permalink
  13. Yes they are both the latest version

    Posted 7 years ago on Thursday September 29, 2011 | Permalink
  14. @cyteworks This issue is typically caused by a plugin or theme conflict. You need to test for plugin and theme conflicts. Here are instructions on how to do so:

    http://www.gravityhelp.com/documentation/page/Testing_for_a_Theme/Plugin_Conflict

    If a plugin or theme is causing this issue due to some sort of conflict, this will narrow it down to which one is causing it and we can go from there to determine why.

    Posted 7 years ago on Thursday September 29, 2011 | Permalink
  15. You were exactly right. I found the conflicting plugin.

    Posted 7 years ago on Thursday September 29, 2011 | Permalink
  16. If you don't mind, can you post back what the plugin was that was causing the conflict so we can take a look at it internally? Thanks.

    Posted 7 years ago on Monday October 3, 2011 | Permalink