Andy Cook
Forum Replies Created
-
Hi Melissa –
This should be all set now if you update to Leadin 2.2.7.
Thanks again for reporting the issue and your patience while we took care of it. Let me know if you run into anymore snags and I’ll fix them. I’m going to mark this ticket as resolved.
Cheers,
– AndyThis should be all set now if you update to Leadin 2.2.7. Sorry about the issue and thanks again for reporting the issue.
This should be all set now if you update to Leadin 2.2.7. Sorry again about the issue. Thanks again for the help and your patience.
Thank you for reporting this error and so sorry for the issue. You’re not the only one to report this issue with tipped me off that it’s a problem across the board. We appreciate you taking the time to let us know and thank you for also providing the error log which made it easier to find the problem.
After the update Leadin’s front-end should start working again properly. Also, all your data is safe and sound – there’s just a PHP error that we need to take care of. I’ve isolated the cause of this and am updating the plugin now to fix it.
Hi There –
Thank you for reporting this error and so sorry for the issue.
The short story is that a line of code which creates an array of your active power-ups for the upgrade process was deleted when it shouldn’t have been, meaning Leadin reset your active power-ups along with removing your “contacts” power-up from that list, which is why you can’t see the contacts tags.
Luckily it’s an easy fix and I’m pushing the update to fix it soon. You also didn’t lose any of your data, just the ability to click the “Contacts” menu item.
Thanks again for reporting the problem and sorry for the issue. We’ll have it fixed soon.
Hi Melissa –
Thank you for reporting this error and so sorry for the issue.
The short story is that a line of code which creates an array of your active power-ups for the upgrade process was deleted when it shouldn’t have been, so PHP is searching on an array that doesn’t actually exist, thus throwing errors.
I’ve isolated the cause of this and am updating the plugin now to fix it. Thanks again for reporting the problem along with the errors (that really helped me find the cause quickly).
Hi Phil –
The 500 server errors could indeed be a factor. The one Leadin works is that it parses your form submissions, stores it in a cookie then races to the server with that information before the page refreshes to store it in the database. If the data is not saved before the page refreshes, we will check for outstanding cookies on the page reload then submit the data on the second page.
If the next page is throwing a 500 internal server error then it is indeed possibly the page isn’t storing the submission on the second page because it can’t.
It’s also possible that the intermittent 500 errors aren’t the issue at all and it’s something else. For now I’m going to mark this ticket as resolved, but once you get the server moved and if there is still problems please don’t hesitate to send a ticket into our support system – support@leadin.com.
Epic! Thanks for following up to let me know!
Hi Rob –
I just noticed I forgot to follow up with you – sorry! We added the form selector and corresponding tag that was added to the timeline + emails in Leadin 2.2.3, so if you upgrade to the latest version of the plugin (we’re on 2.2.5 now) you should start to see this information come through.
Thanks again for the awesome idea and for supporting us by using the plugin. You rock!
So the Leadin popup is created via Javascript which WordPress’s translation engines can’t detect by default. We’re discussing a way to modify the popup for to allow for translations in the text fields. I’ll make sure to circle back here with updates as we progress on figuring that out.
Cheers!
First off, sorry for the delay on your support inquiry. Our team is admittedly behind a bit on our tickets from the Thanksgiving holiday week in the U.S.
Secondly, do you mind creating andy@leadin.com an administrative login to your WordPress Dashboard so I can take a look as to what might be happening here?
Thanks!
Greetings! I wanted to follow up with you that we isolated the bug you originally mentioned and fix it for Leadin 2.2.6, which will be launching hopefully today or early tomorrow morning. Thanks again for the reporting the issue and helping us figure out what’s going on. I’ll spare you the boring technical reasons, but it ended up being and issue with forms that had IDs but no classes attached to them.
Thanks so much for the additional thoughts! We really appreciate it and I’ve shown your feedback to the rest of my team (i.e. just my co-creator on Leadin – Nelson – we’re a formidable two-person team 🙂
I’m going to mark this topic as resolved and if you have any other questions please feel free to email me – andy@leadin.com.
Cheers!
Thanks for the follow up and sorry again about the issue. Our team is going to try to figure out a permanent fix for our email deliverability issues and I’ll make sure to circle back with you once we get the problem fix. Thanks for your patience and support on this one!
Thanks for the reply – do you mind letting me know if it starts working correctly after you update your WordPress install?
I’m pretty sure (like 97.82% sure) that updating your WordPress installation will fix the problem, so I’m going to mark this ticket as resolved for now.
Cheers!
I totally understand not being able to give me access and no worries. I’m working with some other folks on getting to the bottom of what’s happening here and hope to know what’s going on soon. I’ll circle back here with what I find and thanks again for reporting the issue.
I’d love to hear about how you’re using Zapier. It’s a feature we’re thinking about building into Leadin at some point so I’d love to learn more about your setup if you don’t mind sharing – andy@leadin.com
Good luck on your campaign launch too!