Support » Plugin: Constant Contact for WordPress » conflict between Constant Contact plug-in v. 4.1 and Toolset Types/Views

  • Resolved smarttinc

    (@smarttinc)


    I am reporting a possible conflict between Constant Contact plug-in v. 4.1 and the Toolset Types/Views plug-in modules.

    Currently running the latest version of WP and PHP v.5.6.24

    I recently enabled my Constant Contact email list sign-up plugin and found that saving TOOLSET VIEWS content template plugins cause a “CONTENT NOT SAVED” error. This is a back-end error, not visible to visitors, but troubling for the admins.

    After selectively disabling plug-ins, I found that the Constant Contact plug-in was causing the error.

    All other plug-ins and the WP install is up to date as far as the dashboard can tell.

    Right now, I can disable the CC plug-in, but this is a service that I use, and I will need to re-enable it at some point.

    My entire post system is built around TOOLSET’s custom fields so I cannot disable that without disabling much of my site.

    Please advise.

    https://wordpress.org/plugins/constant-contact-api/

Viewing 3 replies - 1 through 3 (of 3 total)
  • This is NEW INFORMATION. This is NOT a BUMP! PLEASE DO NOT DELETE…

    TOOLSET Technical Support has investigated this issue. Here are their findings…

    Our 2nd tier supporters have investigated the issue and the problem is not coming from views.

    Its on the Constant Contact plugin side .

    This was the response of our 2nd tier supporter
    Views saves the content template using ajax
    In both of cases (The contact plugin active and inactive) , Views returns the same response
    So, it’s not a Views issue
    It’s an issue with the contact plugin that hooks into every ajax call and modify the response.

    I’ve commented lines number 171,172,173,174,175,176,177 to resolve the issue.

    This is the line that was commented out.

    // setup common ajax setting
        $.ajaxSetup({
            url: ajaxurl,
            type: 'POST',
            async: false,
            timeout: 500
        });

    So I would recommend contacting the support team for the Constant Contact plugin.

    Plugin Author Zack Katz

    (@katzwebdesign)

    Thanks, @smarttinc, this will be fixed in the next update.

    Thank you.

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