I have also tested this with all other modules disabled. And also by changing the theme to standard themes like Twenty Seventeen, Twenty fifteen etc. All show the same error only on the main page.
So it seems that on the main page Here the markup Blog/ publisher / logo is not defined.
Because when you test the actual blogposting Here the value Blog/ publisher / logo is correctly added.
logo
@type
ImageObject
url
https://www.gpsdokter.com/wp-content/uploads/2018/10/storm.png
width
600
height
60
Actually it does seem that the markup on the main page is mixed up (see image).
Image link click here 
“>Markup main page.
So can this be fixed for the main page ?
Good Day ampforwp,
Thank you for the follow up. Applied the update and upgraded to 0.996 and the issue is solved.
Thanks you for your support. One of the best i have seen.
Regards,
Bernhard.
Hi Havig,
Actually the two updates after receiving this error did not solve the problem.
There was a request from the team to have ftp acces, but i actually decided to turn of this amp module for the time being and wait some time for a new version. The regular APM module amp-wp works without any problems.
Not that i do not trust the tech people from ampforwp team, but actually i do not run an ftp on my own server. And in general i do not allow third party to my system since i also run a commercial website on it where i receive payments and such. WordPress i actually only use for SEO.
Conclusion, problem not yet solved. But i guess this is also because i did not provide accces to solve the issue. In my opinion these people work hard to deliver a good product. And you cant complain for such a free module with great support. Ill just wait it out untill its solved.
Hi already did send the email to team@magazine3.com
Regards,
Bernhard
Thank you. My issues are solved.
Actually, is it possible to downgrade Nextscript to the previous version before version 4.20 ? If so how to do this ?
Crashing the website because of upgrading to 4.20 is not so nice when having an older version of PHP. Would be good for nextscript to implement an php version check before upgrading, so that it states whats needs to be upgraded first instead of taking down the website after upgrading to 4.20
Hi dcooney, Ok so now i understand why i could not make it work correctly 🙂
Ill reconsider my options. Thanks for your fast response.
