Joseph G

I was seeing the same issue but updating to 14.0.2 solved this. =)

@brainstormteam Thank you!

What directories/files are you referring to and what should their permissions be? 755?

Thanks!

Same issue here… 14.0.1 broke my site and kicks out an error:

There has been a critical error on your website.

I think I may have found the culprit in my own environment. Looks like Wp-rocket might to be the blame in my case. Once I set Wp-rocket to NOT cache my contact page it began working just fine. Anyone else seeing this? Anyone using another caching plugin?

I’m gonna reach out to wp-rocket support…

@smiggynic I did the same thing and it still doesn’t work. I’ve disabled all plugins (minus CF7) and switched to twenty seventeen theme. I also, regenerated my Recapatcha key and re-entered it. Even after doing all this it still doesn’t work.

Recaptcha is producing an odd box in the middle of it…

The only thing I can now do is to remove the Captcha which isn’t so optimal. I’ve already gotten about 10 bs Pharma ads. =P

Anyone got any ideas on how to solve this?

I’m seeing the very same issue. When I include recaptch in a form is breaks the otherwise correct layout of the page. I’ll try disabling plugins and switching to default theme tomorrow and post results here.
TIA

I goofed! Sorry! Looks like it was a case of CSP (Content Security Policy) gone amok. Once I disabled it and restarted webserver seems to work fine. My bad, I made it too secure to even work. =P

Odd thing is it was all working before the most recent updates. I’ll have to go back and do some troubleshooting on it.

Can I PM it to you? I’d rather not post here.

Thanks!
J

@le_triple_effort

Yes, it only supports posts as of now and have very limited functionality. See https://www.ads-software.com/plugins/amp/ which states:
Note #1: that Pages and archives are not currently supported. Pages support is being worked on.

Thanks,
J

No, I think you are misunderstanding the goal of AMP. It is more expansive than just posts and it includes pages and other content. =P

Jan,

I agree on one level. While it is true that the age of code doesn’t necessarily mean it is vulnerable but more often than not it IS. Ever heard of Timthumb? If a plugin or theme uses an older version of timthumb and doesn’t update its plugin/theme it leaves users vulnerable. Statistically this article shows abandoned plugins to be a huge point of entry. https://www.wordfence.com/blog/2016/03/attackers-gain-access-wordpress-sites/ Fact is, vulnerabilities are coming up all the time and just because code was secure one day doesn’t mean someone will not find a way to in the future.

Additionally old/unmaintained plugins will eventually not work and this is bad for the community. Ex. PHP 7. Much is changing and if people are using unmaintained plugins they are SOL. What I’m suggesting would help people know they are in fact using something that they might want to replace.

Unmaintained code is a risk on several levels.

Hi,

It was an issue with my .htaccess file and not the plugin. I fixed it and all is good.

Thanks!

Hi,

It was an issue with my .htaccess file and not the plugin. I fixed it and all is good.

Thanks!

Hi,

It was an issue with my .htaccess file and not the plugin. I fixed it and all is good.

Thanks!

Many are and I’ve seen no issues. Why? I do wish it was integrated into Wordfence as an option (Yubikey).