Support » Plugin: Constant Contact for WordPress » [Plugin: Constant Contact for WordPress] CC broken due to dev/live conflicts

  • Resolved jdhobbs

    (@jdhobbs)


    A fellow developer built the site I’m currently maintaining, and he’s away for 2 weeks…so I turn to you for help!

    The site has the (paid for) Constant Contacts feature, and is implemented using the ‘Constant Contact API’ WordPress plug-in. It was implemented firstly through the development/staging server before being pushed live.

    The dev site had Constant Contact working fine, but it’s broken on the live site. There shouldn’t be any issues, as the live is simply a copy of the dev.

    From what I can see, the issues lies in what’s available in the admin. Live only has ‘Settings’ available, whilst the dev has others…including ‘Lists’. It’s this ‘Lists’ that populates part of ‘Settings’ part, supplying a tick box of site areas to determine where the CC Widget should appear.

    It appears these extra items are only available if you have a CC account, as pulling out the credentials removes the items.

    My thought is that because the CC credentials have already been used (the dev), that the second attempt at use (the live) is been disallowed.

    I’ve double-checked that the code is being included in the correct place:<?php $sbw = new constant_contact_api_widget(); $sbw->widget(); ?>

    I’ve compared the databases to make sure all there’s no missing tables.

    I’ve logged into the Constant Contact website, to see if there’s any options there to pick what web URL the account is to be used on (my hope was that I could swap out the dev URL for the live URL).

    Dev URL: http://174.143.247.190/~amaracha/
    Live URL: http://www.amaracharles.com/

    (it’s the form underneath ‘Celebrate our Launch’)

    Thanks in advance for any help!

    http://wordpress.org/extend/plugins/constant-contact-api/

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘[Plugin: Constant Contact for WordPress] CC broken due to dev/live conflicts’ is closed to new replies.