mekatrig

Thanks, Joel.

I’ve tried it and all is back to working OK and I’ve reinstalled it. Looking forward to seeing what the issue was.

I’ve had another look, running the website on WordPress default themes, 2019, 2017, 2016 with just this plugin activated gives the same error message.

Using health check in troubleshooting mode, once convertalink is enabled, the error message appears, then the plugin cannot be disabled and my admin is stuck in troubleshooting mode…… Weird….

I can’t help feeling that there is a simple explanation, but can I find it….No, so if anyone has a similar problem and found a fix please let we know

I’ve run the updated theme on my test site and all seems OK.
Well done for chasing up the developer and even more for showing me how to contact them just in case of future issues.

I hope your better soon.

Changeset can be viewed here

https://themes.trac.www.ads-software.com/changeset?old_path=%2Fsg-window%2F1.2.2&old=86305&new_path=%2Fsg-window%2F1.2.2&new=86305&sfp_email=&sfph_mail=

Hi.
Would you look at that, finally an upgrade to SG themes.

I am however a little wary as there has been a lot of examples recently of abandoned plugins being bought by dodgy people then being injected with malicious code.

The SG themes seemed abandoned, now suddenly an update, is the developer back on track, have the themes been taken over by someone else?

How do we know what is happening when there is no information and I cannot find any communication or explanation from the developer about anything, let alone whats in this update.

My child themes based on SG Windows are all OK at present so I’m just updating my test site for now until I can check out that this update is safe.

This may sound a little paranoid but with the millions of daily attacks aimed at WP sites we cannot be too careful.

Mind you some communication from the developers would be more than welcome.

Hi Joel.

Thanks for the quick reply and I am very happy to know you are still supporting it.
I’m looking forward to seeing what you have planned for the new version.

Thanks

I think you will find that all the SG themes are child themes of SG Window and none have been updated for a long time, SG Diamond and SG Window were last updated in July 2016, other SG themes have not been updated for over 2 years.

The Original SG Window still seems to be working OK I am using PHP 7.1 and I have no issues with any of my own SG Window child themes.

I think we can gather from this that support for these themes has stopped and we are going to have to work out any fixes, upgrades or compatibility issues ourselves.

I don’t know what plugins you are using or what set up you have but if you cant tweak your theme to bring it up to date then it may be time to look for something else with ongoing support.

SGwindow is already such a powerful theme the pro plugin makes it (for me) by far the best free theme available I use it as a basis for all my themes.

Sadly the pro plugin seems to have disappeared, the link page is not working and I can’t find it anywhere.

As SGwindow is released under the GNU General Public License v2 or later and the pro plugin was released as a free add on I have the original unmodified free Pro plugin zip file in my public GitHub repository.

If you do decide to download and use it you do so at your own risk.

https://github.com/mekatrig/Meka-bits

Well that was a speedy fix, well done Joost & the Yoast team 3.0.3 seems to have cured the problem.
Looks OK too.
Let that be a lesson to all, only use plugins with on-going support as you never know when a conflict will arise.
Thanks
Mike

Hi Misplon
I have already spent a good few hours on testing, updating all plug ins, deactivating & reactivating each one, changing templates etc… Looking at my own experinance and the dozens of posts on this & other forums it seems that the conflict is caused by the 3.0.1 update.
I note Greg Priday has the view as Joost de Valk, that this is a caching issue and maybe flushing caches has worked for 90% + users with these issues, but that still leaves about 10% (Yoast SEO has over 1 million users) of us gnashing teeth and tearing hair out (if we have any left).
So I’m taking the easy option, 2.3.5 will do me fine until Joost winkles out the problem and we get a fresh update.
Mike

Well, I did it and all my data seems unaffected, but I may have a diffrent set up to you.
For instance I dont use Yoasts site map i use XML Sitemap & Google News feeds instead.

It all depends on if you can wait for Yoast to fix this issue, or if you need to work on your site right way, if so then you may have to do a bit of work.

The thing to do is have a ‘test site’ get a cheap domain and build a 2 or 3 page test site you can mess around with so when issues like this happen you can test fixes on it without comprimising your main site.
take a look at my test site to see what I mean.
My mistake was not updating Yoast SEO there first and catching the problem early, a mistake I wont be making again.

Hi Volkovv
You and many others have the same issues, all I can suggest is that you first try clearing your browser cache, if your using cloudflare, w3 total cache or any other plug in that caches your content clear those caches too, then try again.
If the problem is still there than deactivate the Yoast SEO plug in, delete it then use the link in my last post to download 2.3.5 ( we all know that one works) then just upload it and activate as normal.
Give the Yoast boys a week or so to sort this out then you can try updating again.
Good Luck
Mike

12 websites down and I have had to delete 3.0.1 and reinstall 2.3.5 along with many other WP users a massive waste of valuble time as it seems that whatever the Yoast boys have been up to, they’ve overeached again and this problem is endemic. Despite claims of clearing Brower caches resolving 90% (or 95% depending on which post you read) of issues this is not the point, this should not have happened in the first place from a team as experianced as this, one wonders did they actually test this update before release?
Then again I learned long ago not to use the Yoast sitemap and I only use the free plug in which has given me great service, so I should’nt really be complaining about the occasional glitches, this latest one just means I will continue deffering paying for the premium version.
So to anyone else with this problem, if you can sit it out and wait for them to fix the bug or roll back to 2.3.5 and use that for now.

https://downloads.www.ads-software.com/plugin/wordpress-seo.2.3.5.zip

Mike