suitsjen

I kept going at this thinking the date wasn’t being updated, when it looks like it was updating, but not showing in the posts list column.

After adding the ‘Admin Columns’ plugin, I was able to add the “Last Modified” field to the post list, which now shows the correct modification dates. This resolved the problem, as the “Date Modified” was updating correctly but not being displayed.

• This reply was modified 1 month, 1 week ago by suitsjen.

It isn’t fixed. I just tried to update the new version, but it broke my site again. Screenshot here: https://tinyurl.com/yvxpjwnj

• This reply was modified 1 month, 2 weeks ago by suitsjen.

I’m not sure what you are asking me to do. I’ve done the conflicts test and found that Subscriptions for WooCommerce is where your plugin is having problems. I also discovered that both PayPal Payments versions 2.9.1 and 2.9.2 will cause the conflict.

Subscriptions for WooCommerce is where your plugin is having problems. I also discovered that both versions 2.9.1 and 2.9.2 will cause the conflict.

Here is the full error from my hosting account:

[2024-10-02T19:49:05.410425+00:00] PHP Fatal error:? Uncaught TypeError: WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package::addModule(): Argument #1 ($module) must be of type WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Module\Module, Wps_Subscriptions_Module given, called in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php on line 37 and defined in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php:244#012Stack trace:#012#0 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/bootstrap.php(37): WooCommerce\PayPalCommerce\Vendor\Inpsyde\Modularity\Package->addModule(Object(Wps_Subscriptions_Module))#012#1 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(77): {closure}(‘/nas/content/li…’)#012#2 /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/woocommerce-paypal-payments.php(92): WooCommerce\PayPalCommerce\init()#012#3 /nas/content/live/hac2024stg/wp-includes/class-wp-hook.php(324): WooCommerce\PayPalCommerce\{closure}(”)#012#4 /nas/content/live/hac2024stg/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters(NULL, Array)#012#5 /nas/content/live/hac2024stg/wp-includes/plugin.php(517): WP_Hook->do_action(Array)#012#6 /nas/content/live/hac2024stg/wp-settings.php(555): do_action(‘plugins_loaded’)#012#7 /nas/content/live/hac2024stg/wp-config.php(119): require_once(‘/nas/content/li…’)#012#8 /nas/content/live/hac2024stg/wp-load.php(50): require_once(‘/nas/content/li…’)#012#9 /nas/content/live/hac2024stg/wp-blog-header.php(13): require_once(‘/nas/content/li…’)#012#10 /nas/content/live/hac2024stg/index.php(17): require(‘/nas/content/li…’)#012#11 {main}#012? thrown in /nas/content/live/hac2024stg/wp-content/plugins/woocommerce-paypal-payments/lib/packages/Inpsyde/Modularity/Package.php on line 244

PROBLEM SOLVED: In the interim there was a push from our staging site to our live site. This wiped out the first order. I have since learned that I need to either export all orders from the live site, push then import them back, OR exclude the WooCommerce tables from the push.

• This reply was modified 1 month, 3 weeks ago by suitsjen.

I’m not sure which report you need. There is nothing that says “stack report.” Here are a few with fatal errors.

It’s on auto-update and I have received several emails that the update has failed.

The snippet is intended to change the font size of the name on the Person element. Here is a page where the person element is displayed: https://archframestage.wpenginepowered.com/art-consulting/ (scroll down the page until you see the people).

Here is the snippet:
.person-name {
font-size: 20px !important;
}

It’s been working while in our theme’s (Avada) custom CSS formula but it does not work when using the Code Snippets plugin.

• This reply was modified 3 months, 3 weeks ago by suitsjen.

Update: the snippet that eliminates the gap in content spacing is now working. The snippet that changes font size of an element is not working.

That worked perfectly. Thank you!

Thank you for the reply, @coloradocranes. It worked. I hope GoDaddy doesn’t delete it again.
I don’t know the story behind the blacklisting, but that seems harsh!

Having the same problem. Can we expect NextGen to be updated so we can get back to using it, or should we be scrambling for an alternative plugin?

No more gap! TY!

Perfect! Thank you!

Oh, thank you so much for such a detailed response. The product wasn’t set to allow back orders, but your code snippet did the trick. I had tried several other snippets but none worked. Yours worked perfectly!

It’s a thing of beauty to have something work the first time after struggling with an irritating problem like this one.

I will post the other issue on the theme’s support forum.

Thank you again! You made my day!