Twitter | Search | |
Felix Arntz
WordPress site owners can now still access their backend even when a fatal error occurs - thanks to the new recovery mode. And this time, it's here to stay!
Reply Retweet Like More
Jaki Levy Mar 21
Replying to @felixarntz
This is helpful
Reply Retweet Like
Abdullah Mar 21
Replying to @felixarntz
Awesome :-)
Reply Retweet Like
Adam Silverstein Mar 21
Replying to @felixarntz
Amazing!
Reply Retweet Like
Mukesh Panchal Mar 21
Replying to @felixarntz
Great news
Reply Retweet Like
Morten is on a prolonged break from all this Mar 21
Replying to @felixarntz
Great work my friend!
Reply Retweet Like
Mike Schroder Mar 21
Replying to @felixarntz
Thanks so much! Super stoked.
Reply Retweet Like
Takayuki Miyauchi Mar 21
Replying to @felixarntz
Great work! Awesome!
Reply Retweet Like
Carole Olinger 🤘 Mar 21
Replying to @felixarntz
🎉🎉🎉
Reply Retweet Like
Stop scrolling! Mar 21
Replying to @felixarntz
Nice. Can I suppress this? Does the frontend still keep running when one plugin fails? For shops and other apps that need to follow some compliance I want them to fail and stay blank until the whole system is fixed. It would kill my compliance if one thing get paused.
Reply Retweet Like
Marius Jensen Mar 22
Your site is still broken, this just gives the right people a way to access wp-admin to resolve an issue
Reply Retweet Like
Stop scrolling! Mar 22
Replying to @ClorithMJ @felixarntz
Ah, nice! I haven't found that in the changeset. If this is limited to admins only then I am happy. Because other user roles just do their daily work and won't notice. But I guess I block them by watching for paused plugins / themes.
Reply Retweet Like
ʀɪᴄʜᴀʀᴅ ᴡᴇʙꜱᴛᴇʀ 🎮 Mar 22
Replying to @felixarntz
Reply Retweet Like
meisterlen Mar 22
Replying to @felixarntz
no more changing all the plugins folder names - brilliant
Reply Retweet Like
Pete Moore Mar 22
Replying to @felixarntz
Reply Retweet Like
Cathi Bosco Mar 22
Replying to @felixarntz
Wonderful news - outstanding!
Reply Retweet Like
Greg Schoppe Mar 22
Replying to @felixarntz
is there a wpconfig constant to deactivate this feature? if my site is protected by a two-factor plugin, for example, triggering a fatal error could allow an attacker to get around my security plugin with only access to my email (which is not necessarily two-factor protected).
Reply Retweet Like
Greg Schoppe Mar 22
Replying to @felixarntz
I realize that it may seem secure enough to email the admin email, but if the user has chosen to have a stronger form of security (imagine requiring a hardware token, like a Yubikey), then this feature would forcibly lower their security standards.
Reply Retweet Like
Greg Schoppe Mar 22
Replying to @felixarntz
perhaps even better would be the option to define a list of plugins which would be whitelisted in recovery mode, similar to listing chrome extensions that can be used in incognito.
Reply Retweet Like
Awais.dev Mar 22
Replying to @felixarntz
THIS IS SO IMPORTANT!!! Just retweeted it, everyone should cherish the amount of work that goes into improving UX like this one. Thank you, everyone! 👏 Mad props!
Reply Retweet Like