Dave333

For some reason the green box is loading each time, indicating that the JS is running OK but the code in the box was always being treated as if it were a message and was being displayed as such to the user. The intent, however, was for that code to be triggered and run, not to display as a message to the user.

I have finally discovered a very simple method that actually works and triggers the code to run instead of displaying it to the user as a message.

Just add this to the first of the Messages fields titled: “# Sender’s message was sent successfully”:

Your message was sent successfully. <script> location.href="https://www.WEBSITE.com/thankyou.html"; </script>

Enclosing the code in the script tags was what was required to trigger the code to run. I don’t know why this is required for some installations and not others but it was the only thing that worked for me. I spent over a week, many hours a day trying many different approaches, including some very complicated hacks. This simple code is the only thing that has worked so far.

Did you get anywhere with this bethannon1?
I’ve been struggling with this for a week now without success.

The green box shows and displays the code inside the green box as a message after the message is sent. Instead of presenting the code as a message to the user I want WordPress to actually run the code:

on_sent_ok: "location.replace('https://www.WEBSITE.com/thankyou.html');"

Why is the code displaying as a message instead of being run?

After implementing this and waiting several days for it to register in the AdWords Admin panel, I’ve found it to be not triggering the AdWords conversion code.

Does anyone know of an alternative solution that works?

Please delete this thread as it is inappropriately titled.
I’ll start a new one giving the solution for others once I’ve confirmed I have it working.
Thanks.

phaber and charmedlife, did either of you get this to work successfully?

Did you get to the bottom of this? I’ve read so many pages about this issue with many conflicting suggestions. Your descriptions are the best I’ve seen of the problem on this forum but noticed that on each thread you’ve not had any success.

Did you give up in the end or did you find a a solution outside of this WordPress forum?

Thanks @wpyogi But I’ve solved the problem – I deleted the faulty plugin from all my client’s websites.

Tried upgrading NextGen plugin again after reading that it had been updated to work with the current version of WordPress (again, why the NextGEN developers didn’t feel this was necessary is startling to say the least!). Still breaks my website and throws errors. One such error is this line of code that now appears at the top of pages that have galleries:

array(1) { ["display_type"]=> array(1) { [0]=> string(20) "Invalid display type" } }

I guess it’s time to roll back again to the previous working version of NextGEN or perhaps just ditch it entirely in favour of a plugin that works.

Why is the new NGG still not compatible with the WP3.6???

There is a big yellow warning box at the top of the update page stating:

Warning: This plugin has not been tested with your current version of WordPress.

Shouldn’t it be your top priority to have it at least work with the current version of WordPress?

Do you really expect all NGG users not to upgrade to the latest version of WordPress?

This is indeed strange behaviour from a leading plugin developer!

Oh God, I wish I had read this thread before upgrading the plugin. It’s totally destroyed my site!

No offence intended Fredrick, I just want to ensure my sites are secure. I am not sure if my web server’s configuration is set in that specific way or not. So best to be safe than sorry, so I uninstalled the plugin until it gets fixed. Once it is fixed I’ll reinstall it.

But I have uninstalled the plugin as soon as I read about the security vulnerabilities. I don’t want to risk attack so won’t reinstall it until the security hole has been fixed.

I guess I’ll have to check in on your site from time to time then to see when it has been fixed.

@fredrick,

You wrote:

“If all of this is gibberish to you, then simply disable database caching to disk until the next release or use another method if available.”

So does this mean the next release still hasn’t been released yet?

Will you be posting here when the next release comes out?

I figured it out. You have to run a query in PHPMyAdmin to removed them:

DELETE FROM wp_posts WHERE post_type = "revision";

This makes this plugin basically redundant as you might as well do the optimising of the DB first while you are in PHPMyAdmin.

Here is some additional info on reducing your DB size that helped me:
https://www.wpbeginner.com/wp-tutorials/how-to-disable-post-revisions-in-wordpress-and-reduce-database-size/

I’m getting these emails again and I don’t run any blogs on WordPress.com. All my WordPress blogs are self-hosted. So far this morning I have received 4, all of which lead to a dead link.

It’s that buggy Jetpack plugin again.

I don’t use Jetpack, but I am sent an email telling me to check my stats for the year, then told I don’t have access because I don’t use Jetpack.

I thought removing this virus-like plugin after last year would stop all this nonsense but apparently not.