chatmandesign

Any chance of getting a response to this?

Thanks for getting back to us, Dion. Sorry to hear you were getting all those complaints on a free product, I can understand that must get frustrating. That said, it’s always worked great for me! And I think this thread shows for plenty of others as well. So while people are unfortunately more inclined to reach out when they’re having problems, I just want you to know there are lots of us out here grateful for the work you’ve done as well. Thanks, man!

I agree no one should be panicking yet, but bottom line, we don’t know why it was removed, and we need to. It’s been a couple days now with no response from the developer. Anyone know how to reach them?

ETA: I DM’d the developer, Dion Hulse, over on WordPress Slack, so hopefully we’ll hear something soon as to what’s going on.

• This reply was modified 6 years, 8 months ago by chatmandesign.

I was excited when I heard WooCommerce was adopting semver, but this is another frustrating example of the fact that that hasn’t really happened. Even if hooks are the preferred method of customization, template replacement is a supported option that’s sometimes necessary – it’s not some weird hack. As such, changes to how templates work are breaking changes, and under semver this means the first version number MUST be bumped.

However, since version 3, WC has repeatedly made breaking changes to templates without the required version bump or any other form of notice. This is actually worse than the state of affairs before; in the past, we never knew when breaking template changes would occur, so we always knew we had to test everything carefully. Now you release new versions with numbers that explicitly tell us there are no breaking changes, lulling us into a false sense of security, but more often than not that turns out to be a lie.

Please either fully embrace semver, or stop pretending to use it.

This happened across like half a dozen different sites. Wordfence auto-updates should be enabled on all of them, so you would know if Wordfence updated on the 29th better than I would. I didn’t save a list of all the sites that reported this, but I believe those were most likely on Modernizr 3.5.0, or thereabouts.

@mikejolley, glad to see you’re on the case! You might want to take a look at WooCommerce Support ticket #487212. I discussed this issue with a Michael K., who came to the conclusion that the cron job couldn’t be removed because its index did not match its content. However, we were never able to come up with a satisfactory explanation as to what caused that.

Thanks for clarifying.

This plugin does NOT allow customers to choose their own gift card values – it even explicitly says that feature is not available in the description. This review appears to be for the wrong plugin. Why is there no way to flag reviews?

Giving a plugin 5 stars when you admit it is fundamentally broken is misleading, and does a disservice to the community.

• This reply was modified 8 years ago by chatmandesign.

Ok, it took some deep digging, but I finally did it. Here’s how you can deliver the headshot that will put down the Braintree plugin zombie for good:

1. Deactivate all plugins, including WooCommerce.
2. Once WooCommerce is deactivated, you can deactivate and delete the Braintree plugin.
3. Using phpMyAdmin (or any database management tool of your choice), find the wp_options table for your WordPress install, and search for the option_name “cron”.
4. Delete the option_value content for this record.
5. Reactivate all plugins.

That’s all there is to it. Note that this will wipe out ALL registered cron jobs. This should be okay, though, because WordPress and its plugins will re-register new cron jobs as needed. It’s possible some plugins might rely on cron jobs they only register upon activation, but reactivating all plugins as the last step should ensure that’s taken care of as well.

So what unholy force caused the plugin to rise from the dead to begin with? I believe the issue was due to unescaped quotes inside a quoted string in the serialized cron event data stored in the database, which was most likely created by the WooCommerce Setup wizard. I couldn’t find any of the related strings in this plugin’s code, so it looks like the Braintree plugin itself is most likely not to blame, but rather a bug in the WooCommerce Setup wizard code.

I’ve filed a support ticket with WooCommerce and referred them to this thread, so I hope they’ll be able to track down the source of the issue and fix it in a future version.

• This reply was modified 8 years ago by chatmandesign. Reason: Fixed typo

I’m experiencing the same problem. WooCommerce PayPal Powered by Braintree Gateway is a zombie plugin that just will not die. Despite the developer’s claim above that “a plugin can’t reactivate itself,” this plugin does in fact do exactly that. If I deactivate it from the plugin screen, it is immediately reactivated behind the scenes, making it impossible to delete from that screen:

So I took the next logical step and deleted the plugin files entirely via FTP. Guess what? The plugin reinstalled itself within seconds, just as reported by @anphira and @joshuaacnewman.

Now, even though @fernashes’s casual dismissal of this issue is incorrect, we all know that her claim is technically true—it’s not possible for the plugin itself to reinstall/reactivate itself after being deactivated, because at that point its code is no longer running. Despite this, the fact remains the plugin is being reactivated and even reinstalled. So what’s going on here? I could only think of one possible answer: WP-Cron.

Using the WP Crontrol plugin, I was able to confirm that there is a “woocommerce_plugin_background_installer” event scheduled to install and activate this plugin. Problem solved, right? At this point, I should be able to just delete that event using Crontrol, deactivate/uninstall Braintree, and the nightmare should be over… Right?

No. That would be too easy.

It seems that even if I delete the event, a new one is immediately rescheduled. WTF?

I figured if I could find out where this event is being scheduled from, that should get me closer to a solution. So I did a search of the Braintree plugin’s code, but it does not contain the string “woocommerce_plugin_background_installer.” In fact, I could only find that string in two places, and they’re both associated with the WooCommerce install wizard.

So, while this is definitely a real issue, it’s starting to look like it may be a bug in WooCommerce, rather than the Braintree plugin itself. Is there a way we can ping someone from @woothemes to look at this?

• This reply was modified 8 years, 1 month ago by chatmandesign. Reason: Fixing image links
• This reply was modified 8 years, 1 month ago by chatmandesign. Reason: Added links to full-size screenshots
• This reply was modified 8 years, 1 month ago by chatmandesign. Reason: I like to tweak things, ok?

According to the latest bug scrub post, it sounds like they’re planning on addressing this issue in 4.5.1. So your best bet might be to just wait it out.

Vicki, theme creation cannot be done through the dashboard, it requires file system access. It also involves writing code. It’s normally handled by developers, and is honestly over the head of most non-technical end users.

If you’re feeling brave and want to give it a try yourself, you’ll need to download and install an FTP program such as Filezilla, then use it to login to your web server. If you do not know your FTP credentials, you will need to get them from your web hosting provider. From there, you should be presented with an interface not too different from Windows Explorer (or the Mac Finder) that will allow you to access your file system, create new folders, upload files, etc.

No.

R3kTGAMING.com is your domain name, which points to your web host. When you change web hosts, it is normal for it to take up to 2 days for the domain name to update to point to your new web host. Simply wait a day or two and the issue will most likely right itself.