search

hps / heartland-woocommerce-plugin

Secure Submit Plugin for WooCommerce
GNU General Public License v2.0
13 stars 14 forks source link

Plugin broken and auto-deactivated after updating to latest Woo Update #158

Closed ChildeRoland840 closed 2 years ago

ChildeRoland840 commented 6 years ago

I updated Woo and all plugins today and after doing so noticed that the SecureSubmit plugin was auto-deactivated with the error the plugin file doesn't exist. I checked it's directory and all looks good.

I haven't tried reactivating it yet out of fear of what it may do to the store and I'm not the host so I don't have easy access to backups and so on.

So I'm posting here hoping someone can chime in as Heartland hasn't called back yet.

la-disenorita commented 6 years ago

Our team is having the same issue with the missing plugin files:

screen shot 2018-08-14 at 9 34 59 am

anyone heard back?

la-disenorita commented 6 years ago

@slogsdon can you assist?

slogsdon commented 6 years ago

@ChildeRoland840 Apologies for missing this originally! Did you get a resolution on your end?

@la-disenorita Are you seeing issues for that file specifically (HpsAltPaymentServiceInterface.php)? You can see on the file on the WordPress Plugin directory SVN repo that drives the plugin installation/update process, so if that's the missing file, there's a good chance that:

  1. The plugin installation got corrupted at some point. A reinstallation should correct this
  2. There's another Heartland plugin installed that may have an older version of the SDK included that is causing conflicts

For 2, only one copy of the SDK is loaded at a given time if there are multiple Heartland plugins activated, and WordPress's plugin loading order affects this. A quick fix can be to deactivate all Heartland plugins, activate Heartland's WooCommerce plugin first, then activate the other Heartland plugin(s)., but if this is the case and you can supply a list of the Heartland plugins you have currently activated, we can implement a better fix by ensuring the other plugins have a up-to-date copy of the SDK.

la-disenorita commented 6 years ago

Hey @slogsdon thanks so much -- number 2 was likely causing the initial error message. Because we're utilizing a few different integrations on WP, I wasn't sure which of the Heartland plugins were needed in our situation. Our staging site is a multisite installation, which may have also been messing with the plugin. However we've switched over to a staging single site installation & only using the Secure Submit for WooCommerce now.

So, quick overview, this site is attempting to utilize Gravity Forms, WooCommerce & Heartland Secure Submit for WooCommerce together. Payment & quantity are processed through WooCommerce, and product selection is controlled by conditional logic in Gravity Forms. It seems that Gravity Forms & the Heartland Secure Submit cannot work together; our testing site crashes every time we have Gravity Forms & Heartland activated at the same time. Any insight? We're happy to pass along login creds to testing site if you don't mind taking a look.

slogsdon commented 6 years ago

@la-disenorita Apologies for the delay. I've been out of the office this week and am just getting back. We should be able to update our Gravity Forms plugin to use the latest version of our SDK, which should remove the conflict you're seeing. I'll circle back as soon as we're able to push that update out to WordPress Plugin Directory.

la-disenorita commented 6 years ago

Sounds great, thanks so much @slogsdon !

slogsdon commented 6 years ago

@la-disenorita We just pushed out version 1.3.12 of our Gravity Forms plugin to update the SDK and fix a couple of other minor items. Once WordPress Plugin Directory updates its index, you should see an update available in your WP admin. Let us know if you have any questions/concerns.