Topics

Hope you're doing well,

I'm encountering a issues:

I'm using PayPal in Test Mode, and when I place an order, it shows as successful. I can see the invoice in the order history, but in the Transaction History, the amount is always shown as 0. I'm not sure why this is happening. Could someone please help me with this as well?

Thank you in advance for your support!

Hope you're doing well,

I'm encountering an issue where, when I go to the "Account" section and try to edit my personal details, no form or fields are visible on the page(See the attached image). There are no error messages displayed on the page, and even the Admin Panel shows no errors.

I'm unable to edit my personal information, and I'm unsure what the issue is. Could someone please help me resolve this?

Thank you in advance for your support!

When I click on Checkout after adding products to my cart, I'm redirected to the first checkout page. However, instead of showing all the available payment methods (e.g., PayPal), the page only displays the Order Summary. I checked the browser console and server logs, and I noticed a 400 Bad Request error for one of the checkout-related AJAX/API requests:

Request URL
https://domain/shop/index.php?rt=r/checkout/pay
Request Method
GET
Status Code : 400 Bad Request

The request fails due to what appears to be database field issues (you can see this in the attached admin log screenshots).

Hi AbanteCart Team,

I've encountered an issue on the checkout page related to the phone number input field. The field doesn't seem to accept any phone number format even the format shown in the placeholder example is marked invalid.

I've tried multiple formats but none of them work. I'm currently using the Mercato theme and I believe this issue might be related to the frontend. It seems that the input value isn't even being sent to the backend, so the validation error might not be coming from there. The frontend appears to be misbehaving on that field.

When I enter any number the field highlights with a red outline indicating that the input is not acceptable. However, no specific validation error message appears so I'm not sure whether this is a formatting issue, a validation rule misconfiguration or a bug in the input component.

Could you please confirm:

What is the correct phone number format expected in this field?

If it's a bug, can you suggest a fix?

Thanks in advance for your help!

I hope you're all doing well.

I'm reaching out to seek guidance regarding an inconsistency I've encountered in the product editing interface after upgrading two different sites to version 1.4.2.

Issue Description:
On Site A (upgraded to v1.4.2), when I navigate to:

Products → Edit Product → Options Tab

I can see a plus (+) icon located above the Save button. This icon allows me to conveniently add more option values for that product.

However, on Site B, which has also been upgraded to the same version 1.4.2 and follows a very similar configuration:

Products → Edit Product → Options Tab

I do not see the plus (+) icon for adding more option values in the same location.

Thank you in advance for your support!

Hello,

While attempting to upgrade the core from version 1.4.1 to 1.4.2, we are encountering a critical SQL syntax error during the upgrade process. The upgrade consistently fails with the following error logged:

SQL-ERROR: "You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'IF EXISTS `ab_lang_definition_idx` ON `ab_language_definitions`' at line 1"
The error is being triggered from:

/core/lib/package_manager.php on line 832

This suggests that the upgrade process is executing a DROP INDEX IF EXISTS statement, which appears to be incompatible with the current MySQL server version.

Request for Support:
Could the team or anyone from the community kindly advise:

Where exactly this DROP INDEX IF EXISTS statement is being generated from during the upgrade?

If this is a known issue in the 1.4.2 upgrade package?

Recommended approach to prevent this SQL error and complete the upgrade successfully?

Looking forward to any guidance or a possible patch from the core team.

Hi Community,

I'm experiencing a persistent issue with AbanteCart v1.4.1 on a live deployment. After submitting the login form, the user is redirected to the expected account/account URL, but then immediately redirected back to the login page without any error message.

Observed Behavior:
Login form submits via POST to account/login with valid credentials.

The response returns 302 Found to account/account (as expected).

Then the browser is redirected again with 302 back to login page.

Final status is 200 OK on the login page – but the user is never authenticated.

No errors appear in AbanteCart logs or server logs.

The customer cookie is issued after login, but gets immediately deleted in the next request.

We are currently in the process of upgrading our AbanteCart installation from version 1.4.0 to 1.4.2.

However, during the upgrade process, we encountered the following error:

2025-06-02 13:57:56 - Unknown Error: AbanteCart core v.1.4.1 SQL-ERROR:
"array (
  'error_text' => 'Can\'t DROP \'isgt_lang_definition_idx\'; check that column/key exists',
  'errno' => 1091,
)"
in /core/lib/package_manager.php on line 832

This error suggests that the upgrade script is trying to drop the index isgt_lang_definition_idx, but it does not actually exist in our database. To further investigate, I attempted to manually drop the index using a SQL query, but MySQL returned the same error 1091, confirming that the index is not present in the current schema.

It seems the upgrade script may be assuming the presence of this index without verifying its existence first.

We would greatly appreciate any insights or solutions from the AbanteCart community or developers on the following points:

Is this a known issue in the upgrade process from v1.4.0 or v1.4.1 to v1.4.2?

Any support to help us proceed with a clean and successful upgrade would be sincerely appreciated.