David

@netpagz, you got to it before me. ??

@mikko, thank you for your suggestions. Worked like a charm.

HEAR YE! HEAR YE!

To re-authenticate, you will need to follow Mikko’s instructions:

SQL query to find plugin’s options:
SELECT * FROM wp_options WHERE option_name LIKE ‘%yst_ga%’

(Replace wp_ with your table prefix.)

You will need to delete all the database rows that come up in the results, then go and authenticate like normal.

Never had this many issues with GA by Yoast. Same problem here on the latest version (5.4.2): it will not authenticate. It seemed to appear to work today at one moment, and I was able to select my UA profile, but then once I saved it, the profile number truncated and changed entirely. Now it’s back to not showing up anymore and it says I have to authenticate again…

@mikulator, improbablejulia posted it above:

From Pair support:

“Back in 2012 there was a massive PHP vulnerability that was
discovered that was present in all versions of PHP, both current (for May
2012 current that is) and all previous versions. Information on this bug
can be found at the link below.

https://bugs.php.net/bug.php?id=61910

When the bug was discovered, there were no immediate patches
available. As a work-around, pair Networks gave every domain we host
special lines in an .htaccess file to secure users against this issue.
About a week after the bug was discovered, patches were available and all
versions of PHP on our servers were updated, but the .htaccess file lines
were left in place as they were not causing any issues.

As PHP has long since been patched, these lines are no longer
needed, so commenting them out (disabling the specific lines) poses no
threat to security.”

@improbablejulia, thanks for your input! This solved the problem for me as well. I guess I just needed to talk to the right person at Pair Networks. ??

It would be great if this thread would get some responses from WP associates as well. This is a significant issue which has left the site useless on 4.1. Are there any experienced WordPress professionals here who could provide some insight?

try reviewing this codex: https://codex.www.ads-software.com/Using_Javascript

Thanks, but I’m not sure how reviewing this codex would help. As I also said before, I have tried switching to just the default WordPress theme, as well as disabling all plugins.

First, check to see if those files exist on your server.

Yep, those files do exist. I even manually deleted the WordPress system files (except wp-config.php and the wp-content folder), then uploaded fresh copies from the WordPress download.

Josh, I’ve been having similar trouble, but I don’t find any javascript errors. Only 403 forbidden errors on some of the tinymce css files. See my post here.

Tara, thanks for taking the time to reply. However, as I mentioned in my original post, I have gone through all these basic troubleshooting steps. I’m hoping a WordPress specialist can get back to me regarding this, as I am suspicious of a deeper, code-issue with WP.

Thanks for the info/update @dartiss

I’m going to add my voice here too. This same problem happens on all my WordPress sites. Yoast, we have a problem…

That’s great news. I’ll keep an eye out for the update then.

@abossola, thanks for starting that! @tacoverdo, Cart66 support let me know they have been in contact with you all about this but haven’t seen any progress. Hope this helps speed things along. Thanks!

Looks like this is working now. Closing this thread. Thanks!