WPIntell

Source evidence

New version is severely broken.

Qyrr – simply and modern QR-Code creation · review · 2022-10-07T19:13:00+00:00

complaintsentiment
highseverity
1.0relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

4 / 29 rows with source links

13.8% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 1 stars
madrid2020 unresolved
I’ve had this plugin installed since an earlier version that worked just fine. This latest set of updates since v1 has broken its use and therefore its usefulness. I do not recommend it. Hey @madrid2020 , thanks for your review. The new version isn’t broken by any means. Qyrr switched to the Block Editor to provide a better and more efficient way to create, manage and customize QR Codes with the new default editor for WordPress. You may have deactivated Gutenberg on your website (or running an old version of WordPress) – that’s why 5.8 is now required by default. All existing QR Codes will automatically be converted from lower versions to the new version, so there shouldn’t be any showstoppers on the way as long as the Block Editor is available. Best regards, Patrick This plugin is solidly broken on a few sites I had it installed on that ran both Gutenberg and non-Gutenberg editors. There are conflicts with other plugins that cause it to appear as if the previously created QR codes had been overwritten with blank info, and new ones would not stay created. There are many problems with it, and an obvious lack of testing before deploying a release would’ve helped address some of these issues. I get the sense you have one local dev environment with Gutenberg that you constructed this new version with, and you called it a day once you were done. It’s definitely broken. You’re welcome to argue the point with me all day, but I’ll be using something else entirely now. Hey @madrid2020 , thanks for your feedback. The plugin was deeply tested before the release. My plugins have been downloaded over 600.000 times, and I’ve been working with WordPress for over 10 years now, but I guess you are the specialist here. A staging environment could have helped prevent that, but you are the pro here, so I think you know that. Not gonna wasting my (and your time) here. I still appreciate your feedback, thanks!

Comments

3 shown
patrickposner 2022-10-10T12:53:00+00:00

Hey @madrid2020 , thanks for your review. The new version isn’t broken by any means. Qyrr switched to the Block Editor to provide a better and more efficient way to create, manage and customize QR Codes with the new default editor for WordPress. You may have deactivated Gutenberg on your website (or running an old version of WordPress) – that’s why 5.8 is now required by default. All existing QR Codes will automatically be converted from lower versions to the new version, so there shouldn’t be any showstoppers on the way as long as the Block Editor is available. Best regards, Patrick

madrid2020 2022-10-10T15:51:00+00:00

This plugin is solidly broken on a few sites I had it installed on that ran both Gutenberg and non-Gutenberg editors. There are conflicts with other plugins that cause it to appear as if the previously created QR codes had been overwritten with blank info, and new ones would not stay created. There are many problems with it, and an obvious lack of testing before deploying a release would’ve helped address some of these issues. I get the sense you have one local dev environment with Gutenberg that you constructed this new version with, and you called it a day once you were done. It’s definitely broken. You’re welcome to argue the point with me all day, but I’ll be using something else entirely now.

patrickposner 2022-10-10T16:47:00+00:00

Hey @madrid2020 , thanks for your feedback. The plugin was deeply tested before the release. My plugins have been downloaded over 600.000 times, and I’ve been working with WordPress for over 10 years now, but I guess you are the specialist here. A staging environment could have helped prevent that, but you are the pro here, so I think you know that. Not gonna wasting my (and your time) here. I still appreciate your feedback, thanks!