Kevin Stover
Forum Replies Created
-
Hey netivity,
We’ve been trying to track this down for a bit. Would you be able to point us towards a form where you’re seeing this behaviour? I can’t reproduce it locally, and being able to see it in the wild would be very helpful.
Thanks!
Can you try this out in 2.9.37?
Are you referring to custom functions that run after a redirect? Or custom redirects that change the page being redirected to?
Thanks for getting back to me! I’ve tried the zip for 2.9.36, and I see all the files there. Can you try installing that version for me? If you do, do you still see an issue?
Hey,
Sorry that you’re having problems! We had some problems with how our files were transferred from our dev machines to WordPress.org. I think that this might have caused your issues.
We’ve since taken care of them. Can you try downloading a fresh copy of 2.9.36 from WordPress.org and let me know if you see the same issue?
@pemot – When your site fell down, did you get any errors? Do you have any errors in your server logs?
We were able to track this down. We’ll have a fix out soon. 🙂
If you download the latest version of the plugin, 2.9.24, it should take care of the issue.
Hey. This is something that was unintentionally borked with 2.9.22. Working on a fix now, and we’ll have a version 2.9.23 out very soon!
Would you mind updating your review to reflect the fix?
If you download the newest version, 2.9.15, it should take care of this issue for you.
Version 2.9.15 has been released and should address this issue.
Hey. Thanks for sharing your code!
There is a jQuery event fired whenever a submission is completed: submitResponse.
This replaces the need to listen for dom changes to the message.
If you’re using jQuery, you can hook into it with something like:
jQuery(this).on('submitResponse.myFunction', function(e, response){ // Check for errors. if ( ! response.errors ) { // No errors // Run your code here. } return true; });I’m pushing version 2.9.15 now. Could you give it a test once it gets live and let me know if it takes care of your issue?
Hey. I think I was able to track this down. It has to do with a transient that has been mangled when it was inserted into the database. I’m working on a release for 2.9.15 that will take care of the issue.
Hey. I think I was able to track this down. It has to do with a transient that has been mangled when it was inserted into the database. I’m working on a release for 2.9.15 that will take care of the issue.