Home → MailChimp Subscribe : Problems, Questions, and Suggestions →

Ext settings will not save

Brian

02 Dec, 2011 06:50 PM via web

Admin Functions

• Edit
• Remove

Hi there. Just installed the extension, version 2.0.4. It will save the API key and list all the available lists, but it will not save any of the options below. The odd thing is there are not serialized arrays in the settings fields for any of the hooks, so I don't even know how it's saving the API key. Any insight on this? Thanks

1. Support Staff 2 Posted by Stephen Lewis on 02 Dec, 2011 07:35 PM

   

   Hi Brian,

   Let's start with the obvious questions, and move on from there:

   1. Are you ticking the checkbox next to the list? People quite regularly set a trigger field and value, but neglect to "activate" the list by ticking the checkbox.
   2. Are you seeing in JS errors in the browser?
   3. Or any PHP errors in the log?

   Cheers,
   Stephen

   Admin Functions

   • Edit
   • Remove

2. 3 Posted by Brian Litzinger on 02 Dec, 2011 07:46 PM

   

   Ah shit, man. I didn't even see the checkbox! Sorry, I'm a newb!

   --
   Brian Litzinger

   Admin Functions

   • Edit
   • Split
   • Remove

3. Support Staff 4 Posted by Stephen Lewis on 02 Dec, 2011 07:48 PM

   

   No problem.

   It's happened before a couple of times. It's obviously a UI problem, but I've yet to find a decent solution.

   Cheers,
   Stephen

   Admin Functions

   • Edit
   • Remove

4. Stephen Lewis closed this discussion on 02 Dec, 2011 07:48 PM.

5. Brian Litzinger re-opened this discussion on 02 Dec, 2011 07:53 PM

6. 5 Posted by Brian Litzinger on 02 Dec, 2011 07:53 PM

   

   Why not just check the value of the trigger field? If it's not blank, then check the box with some JS?

   --
   Brian Litzinger

   Admin Functions

   • Edit
   • Split
   • Remove

7. Support Staff 6 Posted by Stephen Lewis on 05 Dec, 2011 12:25 PM

   

   Hi Brian,

   I played around with that previously, but there were a couple of problems.

   For a start, people wanted to disable a list simply by unchecking the box (i.e. not clearing all the fields, then unchecking the box), so the JS had to accommodate that; not a massive problem, but a bit tricky to make it smart enough.

   But the real problem was that some lists didn't require a trigger field, which meant the behaviour was inconsistent: the lists with trigger fields got checked automatically, the lists without didn't. It actually caused more confusion.

   Maybe I'll revisit it, see if I can come up with a better implementation.

   Thanks for the suggestion.

   Cheers,
   Stephen

   Admin Functions

   • Edit
   • Remove

8. Stephen Lewis closed this discussion on 23 Dec, 2011 05:00 PM.

Comments are currently closed for this discussion. You can start a new one.