Company 50

It is adding it, but it’s an official Woo plugin, and we have no plans to get rid of it. Any plugin we have installed is needed and provides critical functions. Plus, the version of the order notes that the plugin adds is preferred over the one in the table that causes the Product column to collapse really small.

• This reply was modified 7 years, 2 months ago by Company 50.

If I did that there wouldn’t be much purpose for the WebP plugin since the vast majority of images on the website are Envira galleries.

For what it’s worth @zorem your plugin version 1.9.5.2 produces nearly the same results as Woo’s plugin. While yours correctly loads the different types of emails as you select them (Woo’s does not), none of the styling or CSS shows on the live previews with yours either.

@britner For what it’s worth, don’t expect a major developer like WooCommerce/Auto to modify their apps to be compatible with yours. Generally the lesser known plugins work to ensure compatibility with the more well-known plugins. Not to mention, I’d -hope- they have a good grasp on the proper hooks, classes, etc. to ensure other plugins work with theirs since more plugins need to worth with theirs than the opposite. One of you guys has introduced a conflict here. I’m merely pointing it out.

I’m guessing @zorem probably forked Woo’s plugin and that explains why both conflict with the Kadence plugin.

@zorem No, the conflict is with the official WooCommerce Shipment Tracking plugin – the one made by Woo that’s been around forever.

Canceled page has nearly the same thing 10 times:
wc-admin_process_customers_batch, and then non-repeating, but arguments for each entry is one higher than prev (eg. 0 =>2, 0=> 3, etc.)

Completed page has one item from today and then nothing going back until 4/24. Item from today is wc_admin_unsnooze_admin_notes

Not to sound like a jerk, but I don’t really have the time to get this to work. If I did, I’d have started a Support ticket. But the review was important since the plugin doesn’t work at all out of the box actually makes things worse. Once the plugin comes out of Alpha, I’ll definitely revisit and of course change my review accordingly.

I don’t need to reply to him. Nothing he said is relevant to my review. I do not have a special use case. The entire plugin did not work as described. Period. It didn’t sort of work. It didn’t work except for one small insignificant glitch. It flat out did not do what it said it would do. The end. Full stop.

One thing this thread has changed for me is going forward I will be much more likely to leave negative reviews for plugins that don’t work. I rarely did this before but the completely uncalled for response has led me to believe I’ve been much too forgiving. Knowing there are devs out there like you gives me pause. It’s so important that the really good free plugins, and there are many of them, rise to the top. There are so many great authors out there that not only produce great work but when they get a bad review all they care about is fixing the issue. Authors who produce plugins that both don’t work as advertised and who think they are entitled to only a 5 star rating or no rating because their plugin is free should be called out more often.

Basically, it all comes down to this: Your plugin isn’t “bad”. It’s not evil. It’s not malware. It just doesn’t work. And the reason it doesn’t work isn’t because I have some weird setup or plugin conflicts. It simply is designed poorly – subject to PHP timeouts which means anyone with more than 1,000 or so images cannot use this plugin – which is a huge huge number of installs. Your existing install base is tiny, which is why this doesn’t crop up much. But checking your support threads, it’s cropped up enough to be considered a major issue.

That’s great that you do this for free, but that doesn’t in turn exempt you from honest reviews. If you choose voluntarily to submit your plugin to the WP repository, you are subject to many rules including licensing restrictions and the fact that people can review your plugin. Nobody is making you do any of this. I’d be happy to pay for a plugin that works – in fact that is what I did.

As promised, I will change my review once the plugin can support all but the smallest of image folders.

Yes – I consider it whining. Big-time. What, because the plugin is free, 1 star ratings are prohibited? The fact is, it times out after 1 minute on an ultra high-speed VPS server with PHP 7.1 and with all the PHP and WP limits set well beyond what a normal user would have them set for. That’s awful. The fact that a plugin of this nature is programmed to still be dependent on PHP timeouts and does not use AJAX as others have for years is insane.

Next time, read my whole review where I said I’d change it when you supported Ajax.