Hi Roland and Tharuna,
We have a high suspicion Virtuemart is responsible for this, but maybe you have a clue about these settings:
From the shopping cart page, the customer is redirected to the payment page. This could be either iDEAL or PayPal. The customer can proceed with payment, and the process is handled normally.
However, when a customer cancels or closes the payment page without completing the payment and then returns to the shopping cart page to place a new order (or attempts the same order again), VirtueMart appends the order number with "-1" or "-2".
The order numbers before the dash remain the same.
iDEAL only accepts alphanumeric characters for payments and then generates an error message. PayPal, on the other hand, can handle these non-alphanumeric characters and does not show an error.
ERROR: {"errorCode":5017,"consumerMessage":"merchantOrderId should only contain alphanumeric characters"}
Problem: Why does VirtueMart create a new order number with that dash and incrementing number?
For example: QUJS03, QUJS03-1, QUJS03-2, QUJS03-3, etc.
The customer is also unable to place another order after that, as cookies or cache seem to remember the previous attempts
- LaScuderia
- RO CSVI
- Wednesday, 25 September 2024
- Subscribe via email
0
Accepted Answer
Pending Moderation
Hello,
This is the first time we are hearing such an issue with VirtueMart orders. We are not aware of VirtueMart settings in this case. This issue should be posted in VirtueMart forum. They should be able to help you with a solution.
Problem: Why does VirtueMart create a new order number with that dash and incrementing number?
This is the first time we are hearing such an issue with VirtueMart orders. We are not aware of VirtueMart settings in this case. This issue should be posted in VirtueMart forum. They should be able to help you with a solution.
Kind regards,
Tharuna
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Tharuna
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer
Pending Moderation
Hi,
We posted this on the virtuemart forums:
https://forum.virtuemart.net/index.php?topic=152118.0
We added the line as discussed there, however, then we receive the same error. Sometimes however, we receive an error as added in the screenshot
For reference and ease of reading here is the screenshot in plain text:
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\Money::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/Money.php on line 82
Deprecated: strtoupper(): Passing null to parameter #1 ($string) of type string is deprecated in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/Psp/Onlinekassa.php on line 354
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\request\MerchantOrder::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/request/MerchantOrder.php on line 232
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\request\MerchantOrderRequest::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/request/MerchantOrderRequest.php on line 43
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\AccessToken::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/AccessToken.php on line 88
Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/connector/TokenProvider.php on line 34
I see a lot of ropayments mentioned here. Do you happen to have a clue?
We posted this on the virtuemart forums:
https://forum.virtuemart.net/index.php?topic=152118.0
We added the line as discussed there, however, then we receive the same error. Sometimes however, we receive an error as added in the screenshot
For reference and ease of reading here is the screenshot in plain text:
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\Money::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/Money.php on line 82
Deprecated: strtoupper(): Passing null to parameter #1 ($string) of type string is deprecated in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/Psp/Onlinekassa.php on line 354
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\request\MerchantOrder::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/request/MerchantOrder.php on line 232
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\request\MerchantOrderRequest::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/request/MerchantOrderRequest.php on line 43
Deprecated: Return type of nl\rabobank\gict\payments_savings\omnikassa_sdk\model\AccessToken::jsonSerialize() should either be compatible with JsonSerializable::jsonSerialize(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/model/AccessToken.php on line 88
Deprecated: DateTime::__construct(): Passing null to parameter #1 ($datetime) of type string is deprecated in /home/deb126311n3/domains/gmpartsonline.nl/public_html/libraries/Jdideal/vendor/opensdks/omnikassa2-sdk/src/connector/TokenProvider.php on line 34
I see a lot of ropayments mentioned here. Do you happen to have a clue?
Accepted Answer
Pending Moderation
Hello,
The deprecated messages can be ignored, they are just telling us that something will change in a future version of PHP. Those will be dealt with in the respective packages used by RO Payments. On a production site you should have error reporting turned off and that way you will not see them on screen.
In the VirtueMart thread, the solution is already posted as far as I can see. That configuration change should not cause of error reporting to be turned on.
The deprecated messages can be ignored, they are just telling us that something will change in a future version of PHP. Those will be dealt with in the respective packages used by RO Payments. On a production site you should have error reporting turned off and that way you will not see them on screen.
In the VirtueMart thread, the solution is already posted as far as I can see. That configuration change should not cause of error reporting to be turned on.
Kind regards,
RolandD
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
RolandD
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
Accepted Answer
Pending Moderation
We set the payment method to send the order ID instead (in payment options).
Then, a number is used for the payment.
Then, a number is used for the payment.
Accepted Answer
Pending Moderation
Hi,
I did not realize that showing the deprecated info was the issue here as the topic is about the order numbers. What you see is actually not an error but an informational message. There is something I see that could be causing this and looks like some left over code from testing.
If you open the file components/com_jdidealgateway/controllers/checkideal.raw.php and remove line 50 and 51and save the file:
I did not realize that showing the deprecated info was the issue here as the topic is about the order numbers. What you see is actually not an error but an informational message. There is something I see that could be causing this and looks like some left over code from testing.
If you open the file components/com_jdidealgateway/controllers/checkideal.raw.php and remove line 50 and 51and save the file:
error_reporting(-1);
ini_set('display_errors', 1);
Are the messages gone then? Kind regards,
RolandD
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
RolandD
=========================
If you use our extensions, please post a rating and a review at the Joomla! Extension Directory
- Page :
- 1
There are no replies made for this post yet.
Be one of the first to reply to this post!
Be one of the first to reply to this post!
Please login to post a reply
You will need to be logged in to be able to post a reply. Login using the form on the right or register an account if you are new here. Register Here »