Hi

After update WordPress 6.7.1, notice message displayed (in debug mode)

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the alma-gateway-for-woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /wp-includes/functions.php on line 6114

This message was not with WordPress 6.7

Regards

Johan

Hi there

“title” and “description” properties are empty in Alma gateway object. Please, fill in those properties, you have to take into account that other plugins may want to show active gateways in WooCommerce.

Regards

Bonjour,

Il y a un problème dans votre processus de paiement. Lorsqu’un utilisateur utilise le mode de paiement “in page” et qu’il finit par annuler la commande en fermant la fenêtre modal, la commande est supprimée.

Dans certains cas, par exemple si l’utilisateur a 2 fenêtres d’ouvertes, alors il peut avoir un problème. C’est ce scénario qui me semble le plus probable, mais il s’agit juste d’une hypothèse.

Exemple :
L’utilisateur fait la commande avec succès en passant par alma (sur l’une des pages) et plus tard ferme la fenêtre modal (sur l’autre page), alors la commande sera supprimée malgré que la commande soit validée.

Cela m’est arrivé ce matin, alors la commande totalement supprimée de la BDD.

Le problème se trouve ici : OrderHelper.php:383

Merci !

• This topic was modified 3 months ago by mkarena.
• This topic was modified 3 months ago by mkarena.
• This topic was modified 3 months ago by mkarena.

Hi guys,

i’m having this issue when activating alma plugin, it returns me these errors :

Uncaught Alma\Woocommerce\Exceptions\RequirementsException: The constant NONCE_SALT must to be defined in wp-config.php in /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/Helpers/EncryptorHelper.php:120 Stack trace: #0 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/Helpers/EncryptorHelper.php(61): Alma\Woocommerce\Helpers\EncryptorHelper->get_key_salt() #1 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/Helpers/MigrationHelper.php(47): Alma\Woocommerce\Helpers\EncryptorHelper->__construct() #2 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/AlmaPlugin.php(72): Alma\Woocommerce\Helpers\MigrationHelper->__construct() #3 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/AlmaPlugin.php(172): Alma\Woocommerce\AlmaPlugin->__construct() #4 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/alma-gateway-for-woocommerce.php(73): Alma\Woocommerce\AlmaPlugin::get_instance() #5 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-includes/class-wp-hook.php(324): alma_plugin() #6 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #7 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-includes/plugin.php(517): WP_Hook->do_action() #8 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-settings.php(550): do_action() #9 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-config.php(60): require_once(‘/homepages/40/d…’) #10 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-load.php(50): require_once(‘/homepages/40/d…’) #11 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-blog-header.php(13): require_once(‘/homepages/40/d…’) #12 /homepages/40/d000000000/htdocs/clickandbuilds/MySite/index.php(17): require(‘/homepages/40/d…’) #13 {main} thrown in /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-content/plugins/alma-gateway-for-woocommerce/includes/Helpers/EncryptorHelper.php on line 120

Notice: La fonction is_embed a été appelée de fa?on incorrecte. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-includes/functions.php on line 6078

Notice: La fonction is_search a été appelée de fa?on incorrecte. Les balises de requête conditionnelle ne fonctionnent pas avant le lancement de la requête. Avant cela, elles renvoient toujours le booléen false. Veuillez lire Débogage dans WordPress (en) pour plus d’informations. (Ce message a été ajouté à la version 3.1.0.) in /homepages/40/d000000000/htdocs/clickandbuilds/MySite/wp-includes/functions.php on line 6078

Can you help ?

Hello,

As you probably know, minimising CSS and Js files are highly recommended by Google to improve performance and so on … SEO
Alma CSS and JS files are not compressed, would be nice to do it on deployed version.

I know I can do it myself, but after each automatic update from the plugin it’s the same story I have to re-minimize all files from your plugin.

Thank you for your consideration of my request !

Cheers

Dear Alma Payment Plugin Support Team,

I hope this message finds you well. I am reaching out to report a performance issue I’ve encountered with the Alma Payment Plugin on my WooCommerce site that specifically affects the checkout process.

While conducting performance audits, I noticed a significant delay during the checkout phase, particularly when executing the “wc-ajax=update_order_review” AJAX action. With the Alma Payment Plugin activated, the response time for this action significantly increases, averaging between 6 to 7 seconds. However, when I deactivate the plugin, the response time dramatically improves to approximately 1 second.

This discrepancy suggests that the plugin may be affecting the efficiency of the checkout process, potentially impacting the user experience on my site. I have taken the following steps to isolate the issue:

Tested on a staging environment with a similar setup to ensure it’s not related to server performance or external factors.
Deactivated other plugins to rule out conflicts, with the issue persisting solely when the Alma Payment Plugin is active.
Ensured that all themes and plugins are updated to their latest versions.
Given the above, I kindly request your assistance in investigating this matter. I am eager to understand the cause of this delay and to explore potential solutions or optimizations that could mitigate the performance impact during the checkout process.

If there are specific logs, settings, or additional information you require to diagnose this issue, please let me know, and I will provide them promptly.

Thank you for your attention to this matter and for your continued support. I look forward to your guidance on resolving this issue.

Hello there, i can’t use HPOS because this plugin is not compatible with this new woocommerce version feature. Please can you update it ?

regards and good luck

Hi Team,

Could you please add HPOS compatibility to the plugin ?

Regards,

Bonjour,

Lors du passage de la commande et du choix de paiement, on propre le 3x et le 10x. Sauf que lorsque l’utilisateur clique sur “3x sans frais” par exemple, il doit recliquer une deuxième fois sur l’icone 3x.

C’est pas très esthétique, ni très intuitif. Est il possible d’y remédier ?

Je vous joins une image : https://imgur.com/a/oPJDHJK

Merci

Hi,

How can I translate the plugin? I copied the .po/.mo files from your language folder and pasted it in wp-content/languages/plugins, but it didn’t work.

How can I do ?

BR,

Clara.

• This topic was modified 1 year, 2 months ago by arbremojo.

Hello,

In the Class Alma_Share_Of_Checkout_Helper line 132, you try to get the total of the variable $order which doesn’t exist (because you named it $wc_order instead).

Can you fix this please?

Have a nice day!

Willy

I get an installation error: The plugin does not have a valid header in WordPress. Any solution???

I hope this message finds you well. I am reaching out to report an issue I encountered with the Alma payment system. Specifically, I am facing a problem where the payment amount does not recalculate correctly after removing a coupon.

Here’s a simplified breakdown of the issue:

1. I added items to my cart and proceeded to the checkout page.
2. On the checkout page, I applied a coupon code to receive a discount on my total payment.
3. After applying the coupon, the payment amount was correctly adjusted to reflect the discounted price.
4. However, when I decided to remove the coupon by clicking on the “Remove Coupon” button, the payment amount did not update accordingly.
5. The payment summary continued to display the discounted amount, even though the coupon was removed.

I have tried repeating this process on different devices and browsers, but the problem persists. It appears that the Alma payment system fails to recalculate the payment amount after the coupon is removed, resulting in an incorrect display.

Could you please assist me in resolving this issue? It is crucial to ensure accurate payment calculations and provide a smooth user experience for all customers. I would greatly appreciate it if you could look into this matter and provide a solution or an update on when it will be resolved.

If there is any additional information needed from my side, please let me know, and I will be happy to provide it. I apologize for any inconvenience caused and look forward to your prompt assistance.

Thank you for your attention to this matter.

For example: When I have a sum of 2890 and then add coupon 3% discount and the sum is changed to 2800, the value on the “woocommerce-Price-amount amount” element is 934, and then after I remove the coupon it should be 963 (if we choose 3x) but it still 934 and cart total 2890

• This topic was modified 1 year, 5 months ago by msakal.

Would it be possible to get oder version of the plugin ?

Wanna see if it’s the current release that does not work properly.

Thanks

Bonjour,

Votre dernière version a semble t-il changé le label du mode de paiement sur la page de paiement…

Désormais nous avons “Payer avec Alma”, mais nous vous “Payer en plusieurs fois”. Je ne vois pas d’option adéquate dans les réglages.

Une idée ?

Merci

Hi there,

Alma Widget doesn’t show up on Elementor products templates.

Any issue ?

Thank you !

Hello.

We have an issue on the checkout page when we try to validate the checkout.

On the submit button click, if we don’t choose the alma payment method, we have a woocommerce error notice that said : “Undefined array key “alma_checkout_nonce[id of the payment method]”“

We localize this issue and it seems to be located in the alma-gateway-for-woocommerce/includes/helpers/class-alma-checkout-helper.php file in the is_alma_payment_method method.

The unique way to validate the checkout without errors is to downgrade on 3.2.2 version of the plugin.

Do you have any solution to solve our problem ?

Regards.
Clément.

Hello, we are getting a issue for integrating the?Alma into our WooCommerce store. This will not showing payment option to the woocommerce checkout page. Can you guide us why this issue occurred, any reference or any help will be good for us.
Thanks

Hello,
I created an account this morning and didn’t receive any email to finalize the creation.
Can you help me ?
Thanks,
Luc

Hello,

Unable to set up the plugin, the configuration page is blank.
Thanks.

Hi,

Since the new version of WordPress/Woocoomerce, it’s not possible to access the configuration page of Alma.

Thanks

Bonjour

J’ai un souci avec le module :

2022-08-11T16:48:03+00:00 CRITICAL Uncaught Error: Call to a member function get_billing_first_name() on null in /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-customer.php:133
Stack trace:
#0 /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-payment.php(140): Alma_WC_Model_Customer->get_billing_address()
#1 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-plugin.php(750): Alma_WC_Model_Payment::get_eligibility_payload_from_cart()
#2 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-plugin.php(727): Alma_WC_Plugin->get_cart_eligibilities()
#3 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-payment-gateway.php(912): Alma_WC_Plugin->get_eligible_plans_keys_for_cart()
#4 /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-customer.php à la ligne 133

2022-08-11T17:32:46+00:00 CRITICAL Uncaught Error: Call to a member function get_billing_first_name() on null in /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-customer.php:133
Stack trace:
#0 /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-payment.php(140): Alma_WC_Model_Customer->get_billing_address()
#1 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-plugin.php(750): Alma_WC_Model_Payment::get_eligibility_payload_from_cart()
#2 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-plugin.php(727): Alma_WC_Plugin->get_cart_eligibilities()
#3 /wp-content/plugins/alma-woocommerce-gateway/includes/class-alma-wc-payment-gateway.php(912): Alma_WC_Plugin->get_eligible_plans_keys_for_cart()
#4 /wp-content/plugins/alma-woocommerce-gateway/includes/models/class-alma-wc-model-customer.php à la ligne 133

Comment résoudre le problème a la ligne 133

Hello,

I use Alma on a client site. We call the alma-product-eligibility shortcode on the product page, after the addtocart button.
You can see it on https://zeride.fr/produit/velo-electrique-pliant-eovolt-afternoon-noir/ for example.

Usually, we have no problem, and all is well.

But sometimes, it does not work any more.
Either it displays the shortcode without “using” it. (that is really weird)
Either it displays nothing at all.

Sometimes it works on a browser, and not on another browser, at the same time.

And when we empty the browser cache, it works again.

What can we do ? I didn’t see any JS error on the console when it didn’t work.

Thanks
Sylvie