Known issue with v2.10.9

When I updated to v2.10.9, I couldn’t login to my website anymore. Plus my affiliate links (thirsty affiliate plugin) directed to a 505 error. Also my htaccess file was completely different with all kind of code lines added. I had to delete it and reuploaded the default one. After removing the add meta tag plugin update, all was working fine.
Now, on my dashboard it says to update the plugin again which is normal since I deinstalled the update but I will wait the next release to update again.

@ioweuiraosjfosj

Hi Capobis,

Add-Meta-Tags does not incorporate any functionality that could possibly explain the aforementioned errors. And, of course, it would never touch your htaccess file. It is actually a very simple and straightforward plugin.

I highly recommend to look elsewhere for the cause of these issues, because it is very unlikely that they have been caused by Add-Meta-Tags, as it does not contain any code the execution of which could possibly justify these claims.

I had to delete it and reuploaded the default one.

What do you mean by the “default” one?

What was the version of the plugin before upgrading?

Also, what exactly did you find in your htaccess file that is related to this plugin?

More feedback is very welcome.

Kind Regards,
George

@ioweuiraosjfosj

Hi Capobis,

First of all, I’m sorry if my reply has been a little harsh yesterday, but it was a bit of a shock to read about all these issues with the htaccess file and the 505 HTTP responses when your affiliate links were accessed and also about how things returned back to normal after downgrading Add-Meta-Tags. I’m really out of ideas about how all this could have happened, so I’m going to need your help.

This is because the plugin does not contain any code that reads from or writes to the htaccess file and also it makes no HTTP requests and has no involvement in any HTTP protocol checks or modifications which could possibly result in 505 error responses from your web server.

However, it is possible that some API functions used by Add-Meta-Tags are not supported by your WordPress version. In that case, getting a white screen, a 500 error and an error message recorded in the web server’s error log could be the case.

The 2.10.9 release of AMT uses the term meta API, which has been introduced in WordPress 4.4, but any calls to it are enclosed in version checks and this functionality is automatically deactivated when the plugin is used in older WP releases.

In this regard, in addition to feedback about the htaccess content changes, could you please provide me with the following information?

1. The wordpress release you are using.
2. The add-meta-tags release that works ok on your web site.
3. Any error messages that have been recorded to your web server’s error log when add-meta-tags 2.10.9 is used. (For more information about how to access these logs, please consult your hosting provider’s documentation.)

This information could help me replicate the issue locally. Without it I would have to wild guess.

Thanks in advance for your feedback.

Kind Regards,
George

Also, this topic is about another issue. I’d appreciate it if you opened a new topic and provided the information I need there.

Thanks in advance!

George

The issue in the OP has been fixed for the new release. The contents of fields that accept an image URL or an attachment ID will now be escaped properly without being affected by the addition of the scheme by esc_url() in case the field contains an integer (attachment ID).

The topic will now be marked as resolved.

George