tim_lb

That’s great news. And the explanation makes a lot of sense to me.

Thank you. That’s very encouraging news. I’m very impressed by Yoast’s products and attitude, so I’m not keen to switch in the long term.

I’m hoping that the reason for the delay is because some major upgrade is being created, but I think it would be great to have some response from Yoast about that. Incorporating GTM might be exciting.

As things are at the moment, I am getting nervous that the GA tracking plugin is not going to be developed.

Tyler, if your client could use a dummy parameter on reload instead of an anchor, something like this

URL?mc_signup=1

Then you would be able to track that straight away in GA and configure goals etc.

It’s also possible to configure GA to use the # in tags etc, but that would take you into the ‘slightly heavy coding’ area because it would have implications for all other GA campaign tracking for a start.

Brilliant. Thank you. Done!

Thanks, mc_nate,

I had spotted the existence of the self-hosted option for “Confimation thank you” but had missed the fact that you can also host the “Sign up thank you”. Why, I do not know, since it’s made very clear in the documentation. Momentary blindness…

I would hope that the “Sign up thank you” is an extremely close equivalent to the number of people submitting the form, unless something has gone wrong. And if I want to really check on that I can add my own signup form, as you suggest.

But while we’re on the subject, how about adding GA tracking as an option on the standard “Thank you pages” in the same way as you offer it as a feature on the emails themselves?

Tim

To complete the story, for the benefit of anyone else who stumbles upon it…

Things got even weirder. Having discovered that I could suddenly log in again, I decided to bring all my plugins up to date and then upgade to the current version of WordPress (2.6.3).

All went well and everything seemed to be working fine.

But the next day I discovered yet another new phenomenon. When I logged into one of the blogs all I could see was a blank page. By typing the URL of, for example, the plugin admin page, I found that I could see some admin pages but not others. The links in the pages worked, so I was able to work out that the only pages I could not see were the dashboard and the themes page.

And this was only affecting one blog.

One of several ‘blank dashboard’ thread provided the necessary idea:

https://www.ads-software.com/support/topic/183222?replies=15

Having read that, it seemed to me that the strange intermittent behaviour on my blogs and the varying symptoms (despite nothing seeming to have changed) started suggesting that something odd might be affecting the server involved.

So I raised a ticket with my hosting company.

They were very quick to act and within an hour or so things were all back to normal (at least I believe they are). The specifics of the Apache and PHP issues which may have been involved are not known to me. But the lesson of “don’t assume it’s NOT anything to do with the server and NOT worth troubling support” is worth sharing.

Furthe update.

This gets stranger.

This morning I found that I could log in again.

I was too busy yesterday to even look at the blogs, let alone change anything, so it wasn’t anything I did.

That’s not very reassuring! A problem which persisted for a week seems to have suddenly healed itself.

Tim

Updating this thread…

I’ve continued with the investigations so far with no luck.

I now have one of the blogs upgraded to 2.6.3 and still cannot log in. Disabling the plugins via FTP renaming of the directory doesn’t get me in either.

I’ve left the other one on 2.5.1 for the time being as that one is public and I don’t want to risk trying to upgrade ‘blind’. Deleting/renaming the plugins, as suggested here

https://www.ads-software.com/support/topic/201746?replies=8

doesn’t make any difference.

I will keep searching.

Tim

Thanks, Samboll. I’ve been the disabling plugins and upgrading approach today on another of my blogs which is also affected, but so far with no success. This is most curious. Fortunately the blog in question is not even really a public one, so no real harm done. But no solution yet, either…

Tim

Thanks Samboll, but if all that does is change the password, then I don’t see how that will solve the problem.

Even if I create a new account, and use the password which is sent to the new account address, I have the problem. The new password does not work. The screen just reloads without an error message.

So I would expect re-setting the admin password using the script would have the same effect.

Or have I misunderstood something?

Tim