supertomate
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] SEPA is not avaliableHi all and especially @osheta can you read this post and try this solution : https://ww.wp.xz.cn/support/topic/sepa-payment-method-missing-from-woocommerce-admin-subscription-view/#post-18477722
Forum: Fixing WordPress
In reply to: Title attribute no longer appears in the menu links wp 6.7add_filter( 'nav_menu_link_attributes', 'wpse121123_contact_menu_atts', 10, 3 );
function wpse121123_contact_menu_atts( $atts, $item, $args )
{
$atts['title'] = $item->post_title;
return $atts;
}@remainsunknown Thanks for the information, so I put this code because I need to have the same title as the content.
Forum: Fixing WordPress
In reply to: Title attribute no longer appears in the menu links wp 6.7Thanks for the reply and I didn’t specify the bug properly but it’s in the front and not in the admin. You can easily reproduce the bug by activating a theme like Twenty Twenty-One for example, and not the latest Twenty-Five of course. Links no longer display any attributes.
Today I noticed a new note in a subscription: Stripe Gateway: the payment method used for renewals has been updated from Sources to PaymentMethods.
This subscription was debited on 31 August with the message: The Source has not been migrated to PaymentMethods on the Stripe account.
But today, when the next payment was made, it was changed to pm_ directly by Stripe. So it seems to be working as you wrote.
Thanks for the developers@petervandoorn do you also have notice the same source transformations in payment methods?
Same thing on our site. This note appears in the subscription form and the payment is carried out correctly. During the last exchanges I had with your support team, you ensured me that the sources were going to be migrated automatically to Stripe. We don’t have access to dashboard.stripe.com/dashboard/sources-migration to migrate the sources. Are you sure that everything will work correctly for our payments?
AutomateWoo has since corrected the code in the latest version 6.1.0 but now the error is still in subscription which is not yet up to date.
Hello
Following the last Woocommerce update I got the same error in the logs. On my site it is automatewoo which is not up to date that is causing this error. I saw in the includes/Post_Types.php file that the call to Automattic\WooCommerce\Admin\Features\Navigation\Screen had disappeared as well as the code blockif ( class_exists( Screen::class ) ) {
Screen::register_post_type( 'aw_workflow' );
}Forum: Plugins
In reply to: [OSM - OpenStreetMap] Too much critical error on last version 6.0.4Thanks for your quick fix
no error from this plugin.
Forum: Plugins
In reply to: [WooCommerce Stripe Payment Gateway] How to activate WC_Stripe_Payment_TokensThank you very much for that very detailed answer, but I was still hoping that you could use it as a conventional means of payment.
I close this thread.Forum: Plugins
In reply to: [WooCommerce] Critical Error After Update To 8.6.0I understand. One of my customers is paying for this update and I had already noticed that updates were necessary to access hpos.
Forum: Plugins
In reply to: [WooCommerce] Critical Error After Update To 8.6.0Hello,
Is the Subscription up to date ? I have the version 6.0 installed with the latest version of woocommerce and no problem to view/editForum: Plugins
In reply to: [WP Image Zoom] Error js in image_zoom-init.js 1.5.2hahaha, no you are a great developer!
Thanks for your workForum: Plugins
In reply to: [WP Image Zoom] Error js in image_zoom-init.js 1.5.2You are too fast!
I just edited my message to say that on line 98
There is a plus sign. maybe it’s a semicolum insteadForum: Plugins
In reply to: [Sessions] Bug with entries statsTo sum up, currently the plugin only lists the first 4000 users and does not allow to manage the sessions of the others, but Pierre will propose in a future version a setting of the number of sessions displayed.
The problem of the user recognised with a wrong number of sessions seems to come from a browser cookie and the only solution for the moment is to overwrite the previous sessions and not to block.
Big Up to Pierre and his wonderful work on this plugin!