chris_c

@simbalion you can, of course, hold an opinion about what level of privacy people are entitled to. But there are judgements from courts that hold a different opinion. For example the Court of Justice of the European Union held that in some circumstances an IP would be considered to be personal data.

provided that the information stays on your server, and is deleted as soon as it is no longer needed there should not be a GDPR problem.
yes and IP address is personal information, but GDPR does not prohibit you from collecting that information for “legitimate purposes”. Spam checking to ensure the safety of the site, and visitors is arguably a legitimate purpose. You’d just need to include a notice to that effect.

Thanks Nick,
Can confirm that 0.9RC is working fine on WP4.91 / G2.53 on Siteground running PHP7.0

delete the maintenance file ….

https://wpengine.co.uk/support/wordpress-maintenance-mode-how-do-i-get-out-of-it/

Hi,
I encountered the issues highlighted above, and traced it to a timeout. Increasing the max_execution_time to 300 in php.ini solved the problem for me.

was set to 30secs which I’m guessing on a large media library might not be long enough to collate the entries?

Jordy, I was scanning media and there’s approx 33k items. PHP memory is on 40meg.

C.

I believe that using <title> within SVG is valid markup (w3 reference)
However, I also believe that to be correct the <SGV> declaration should have something like xmlns=”https://www.w3.org/2000/svg wihtin it to validate.

That being said, from an SEO point of view Bing will throw it as a “red” error -> probably not a show stopper IMO.

Thanks for the update A100.

I’ve made the switch to another login and am pleased to have done so

Done, thank you.

Sorry Merlin,

I’m sorry but that may answer Mike’s question but does not address my main concerns.

I mean no disrespect to your company, or what you are saying. My argument is with the way that this “service” has been imposed upon users of the Yoast product. Especially without an opt-out.

When I want my site to be scanned for potential problems I will carry out my own research as to who is doing it.

I for one am exercising the option to choose another SEO plugin, partly because of this issue, but mainly due to the botched nature of the latest update. Which is obviously not of your doing.

To be fair, it’s not very clear what information is being passed to onPage by the plugin when it connects to their servers. I think at the very least the plugin authors should make that clear.

However, my main objection is that Team Yoast have decided that onPage are going to see that a particular site is using the Yoast plugin on a WordPress site. And that onPage are going to scan that site.
As the owner (or manager) I prefer to make the decision about which SEO services I’m going to use (MOZ, SEM Rush etc.) and not have Team Yoast make that decision for me. Good manners (and respect) would suggest that an opt out of that service should be made easily possible.

The lack of respect mentioned in my review is compounded by the breathtaking arrogance that Yoast in particular has shown on Twitter in dealing with complaints about this update.

I won’t be renewing the premium subscriptions I’ve taken out, and shall be looking elsewhere.

Thanks for the update.

And if that’s the case it’s fine. I’d just like to know whether there is a negative aspect to the removal.