I would have really helped you if you asked.
The plugin doesn’t crash WordPress installs; otherwise, you would have seen hundreds or thousands of reviews/requests saying so.
Why is it crashing yours? That should be a concern. There is an issue with your install and blaming the first obvious outcome is not the solution. I don’t think that’s not how we learn and improve.
Why did you write this review, in fact? I would love to know. I personally believe reviews should help the community (users, developers).
PS: Your name appears as “ljclark@ljclark.com (@ljclarkljclarkcom)” currently. This is the best way to give away your e-mail address to all the robots parsing the web for them. I honestly think you should be more careful.
1. Email from WordPress:
“Howdy!
“Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
“In this case, WordPress caught an error with one of your plugins, Meow Gallery.
“First, visit your website (http://www.<snip>.com/blog/) and check for any visible issues. Next, visit the page where the error was caught (http://www.<snip>.com/blog/blog/wp-login.php) and check for any visible issues.
“Please contact your host for assistance with investigating this issue further.
“If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.
“http://www.<snip>.com/blog/wp-login.php?action=enter_recovery_mode&rm_token <snip>.
“To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.”
2.
> PS: Your name appears as “<snip>@<snip>.com (@<snip-snip>)”
> currently. This is the best way to give away your e-mail address to all
> the robots parsing the web for them. I honestly think you should be
> more careful.
Thank you for your deep concerns regarding my online privacy.
3. You asked for a review, and it appeared on the same page as the warning flags from WordPress. So…
Not sure why you copy/paste all that. This is a debugging tool. It doesn’t tell you the origin of the error. It tells you only where it crashes.
If you would like to help yourself and others, let me know what the error is; have a look at your PHP Error Logs. If a fix is required in my plugin, I’ll do it. I always do. If it’s another plugin, the developer of that plugin should be contacted. Why not trying to help? What’s the point of bashing a plugin instead? If you get no reply from the developer, of course, that would be something to do.
Deep concern? No need to use irony. I am actually pointing at something I think you should be really careful with. I would have changed that right away if I were you.
I was just trying to help you.
