silb3r

Thank you Mike.

I confirmed with my client that they have not been updated directly and the ticket also has not seen any updates or activity. I also confirmed that since I sent your team a login and pass to our staging server 20 days ago, not a single attempt has been made to log in using the credentials.

Furthermore, there have been two updates to this plugin since we first brought this issue to your attention and neither changelog mentions anything about this issue. It is still very much a problem and this feature does not work.

We disabled ALL plugins except for WooCommerce and WooCommerce Square and we still cannot use Apple Pay for the reasons discussed in my original post above. If I disable WooCommerce Square and instead activate WooCommerce Stripe, then Apple Pay works perfectly. This tells me that the issue is almost certainly with the WooCommerce Square plugin and this has been verified in multiple browsers by multiple team members and customers.

The support links you provided are not relevant to getting Apple Pay working with the WooCommerce Square gateway. We also don’t yet plan to use this on iOS, so the “fix” you mentioned is not relevant to us at this time; all devices this was tested on are running the latest versions of macOS and Safari.

In the interests of the community, please unmark this thread as resolved because it has NOT been resolved at all and it’s my goal to keep the community updated when it truly is resolved because I’m clearly not alone.

This plugin has very poor ratings for several reasons, one of the common reasons mentioned is its failure to work with Apple Pay, and another reason is the lack of support when troubleshooting the Apple Pay problems.

Let’s please stay honest here and not rush to mark this resolved.

Please unmark this as resolved.

This issue is NOT resolved.

We’ve been cooperating fully but haven’t heard any reply from the Woo team on this at all.

Despite two recent updates to the plugin this issue is still unresolved.

Issues like this are pushing more and more clients to Shopify and I don’t blame them.

• This reply was modified 3 years, 6 months ago by silb3r. Reason: Adding more detail

Ok, but I’d like to post the resolution here in case anyone else encounters the same issue.

I just want to update the thread and let you know that the results are identical when I switched the theme to Storefront and disabled all plugins except for WooCommerce and Square.

The best solution is to remove the stylesheet completely by adding this to your functions.php:

function remove_stampedio_widget_css() {
  wp_dequeue_script('woo-stamped-io-public-custom');
}
add_action('wp_enqueue_scripts', 'remove_stampedio_widget_css', 100);

Or you can add this repetitive CSS to your stylesheet and hope that your stylesheet is enqueued after Stamped.io’s CSS:

[class*=" fa-"]:before,
[class^=fa-]:before {
  font-family: FontAwesome !important;
  margin-right: 0 !important;
  width: auto !important;
  text-align: unset;
}

Adjust that CSS as needed.

Neither of these solutions are ideal, so if Stamped.io could stop overriding the default Font Awesome styles that would be much appreciated.

• This reply was modified 5 years, 6 months ago by silb3r.
• This reply was modified 5 years, 6 months ago by silb3r.
• This reply was modified 5 years, 6 months ago by silb3r.

it’s by far the best Instagram plugin out there

I second this, Scott!

Please keep us updated about its status and don’t make us go back to those horrible other plugins!

• This reply was modified 5 years, 10 months ago by silb3r.

The error I experienced was Fatal error: Call to a member function remove_hooks() on null in /wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 228.

I deactivated all plugins except for Yoast and then began reactivating one by one. Turns out this was caused by WPSEO Pinterest Rich Pins for WooCommerce for me, which is a very old plugin that hasn’t been updated in some time. I removed that plugin and Yoast now works fine, although I haven’t found a suitable substitute.

The error I experienced was Fatal error: Call to a member function remove_hooks() on null in /wp-content/plugins/wordpress-seo/inc/options/class-wpseo-options.php on line 228.

I deactivated all plugins except for Yoast and then began reactivating one by one. Turns out this was caused by WPSEO Pinterest Rich Pins for WooCommerce for me, which is a very old plugin that hasn’t been updated in some time. I removed that plugin and Yoast now works fine, although I haven’t found a suitable substitute.

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

@marpstar you saved my ass. Thank you!

I just created a pull request on Github to get this going in the right direction.

If you don’t mind editing a core plugin file you can see the necessary changes here: https://github.com/scottsweb/wp-instagram-widget/pull/56/files

Or you could fork my branch and install that plugin but remember that may all stop working when the plugin is updated.

Ron,

Thank you so much for sharing this, it’s outstanding!

For my multisite network I needed to add these to my wp-config.php because without them I couldn’t directly log in to my subsites:

define('ADMIN_COOKIE_PATH', '/');
define('COOKIE_DOMAIN', '');
define('COOKIEPATH', '');
define('SITECOOKIEPATH', '');

Source: https://tommcfarlin.com/resolving-the-wordpress-multisite-redirect-loop/

Thank you again!

This worked for me too except I needed to add priority 0 to my action hook.

Here is a diff file for anyone looking to patch this: https://gist.githubusercontent.com/CFXd/f8e0e1d4559c8be1a8ae/raw/3cf62e25258520f8467f0785387c46d570af47ba/gistfile1.txt

Thanks for posting this!

Done, for anyone who may want to follow or contribute: https://github.com/Automattic/jetpack/issues/1844