Ruben Woudsma

Thank you for your response. I am experiencing this the last couple of updates I am doing on my site. Each time I update the Yoast SEO plugin I can count on it that I need to go to FTP and remove the

.maintenance

file.

Isn’t there a root cause for this issue? Can I do something on my host to identify the problem?

This can be done without any consequences. Please let me know if it worked for you.

For the Glue plugin from Yoast this issue has been resolved. They delivered a new version of the plugin to fix this.

This has been resolved with the latest update. The team of Yoast delivered a new version of the plugin fixing some of the mentioned bugs.

Thank you. This is working!

In my option this reaction is beneath contempt. You are just making a statement about the change in the algorithm which does not match your needs.

I am very happy with the new version of Yoast SEO and am delightful that the Yoast team is creating a new major version based upon many suggestions from the community. They wrote several posts about the changes on Yoast.com in which you (or the community) could have responded.

Changes in the SEO algorithm are logical as search engines are always changing there algorithms in order to provide better search results. In my opinion Yoast made changes in the algorithm in order to support the users helping that posts will get a good result on the SERP.

No ideas at the moment. I had tested this on my test environment and there is was working.

For the plugin I am using the default WP mail function.

I have updated the plugin and released a new version.

I have updated and release a new version of the plugin.

I have just release a new version which should solve this problem.

I haven’t seen this mesage before. Can you give some more details? For instance, which version of WordPress are you using.

I have analysed this and found the root cause of this. Previous before WordPress 4.3. there was an unlimited expiration time of the passwords. With the introduction of WordPress 4.3. this has been set to 24 hours.

Will change some part of the code in order to make sure the version will work with this new solution. And furthermore I shall try to investigate if it is possible to override the 24 hours expiration time.

Do you mean you have updated the plugin or are you requesting an update to the latest version of the API?

Noticed on the website that currently version 3.0 of the API is being used an maintained. The others are deprecated.

I am aware of these remarks and have it on the roadmap for the next release. This will unfortunately not come before the end of August 2015.

This is strange behavior. As the key generation solution used for this plugin is the same as for the WordPress Core.