Messages

Thanks for your response! Let me try this solution, and I'll update you if anything goes wrong with the proposed solution.

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!

Thank you for your suggestion.

I already had an empty system/config.php file in place, but as advised, i deleted it completely and attempted the installation process again. Unfortunately, the same error persists during the Data Load step.

Please let us know if there's anything else i should try?

First of all, thank you for your support and clarification regarding the option types. That was really helpful.

Now, I am facing an issue while installing AbanteCart on my domain. I downloaded the official package from the AbanteCart website, extracted it on my server, and accessed the installation via browser.

1-License agreement step completes successfully.

2-Compatibility validation also shows all checks as passed.

However, during the configuration step, after entering the database and admin details and clicking Continue, the installation proceeds to the data load phase and then throws the following error:

"Parse error has occurred during installation."

Error.txt :

2025-07-10 8:09:44 - Unknown Error:  AbanteCart core v.1.4.2 ADB::__construct(): Argument #1 ($driver) must be of type string, null given, called in /home/server/public_folder/domain/shop/install/model/install.php on line 260
Trace:
#0 /home/server/public_folder/domain/shop/install/model/install.php(260): ADB->__construct(NULL, NULL, NULL, NULL, NULL, NULL, Array)

Could you please help me understand the cause of this error and how to resolve it?

As requested, I've recorded a video demonstrating the issue. In the first half of the video, you'll see that on one site (with the same version), the product section does not have the "+" button to add values. In the second half, on another site with the same version, the "+" button is visible and working.

yes sure!

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!

Thank you for the response earlier.

Just following up on this issue regarding the failed upgrade to v1.4.2 due to the DROP INDEX IF EXISTS syntax. As mentioned, our MySQL server version is 8.0.38, which supports this syntax  yet the upgrade still fails with the SQL error referencing:

DROP INDEX IF EXISTS `ab_lang_definition_idx` ON `ab_language_definitions`

Server version: 8.0.38 - MySQL Community Server - GPL

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.

I had previously posted regarding the persistent login loop issue in AbanteCart v1.4.1 on my live store. I received some suggestions (thanks to the contributors!) and have now tried several of those recommendations, but unfortunately, the problem still persists.

What I've Tried So Far:
Checked Session Creation
Session is successfully created after login (verified in debug logs and $_SESSION array).
customer_id, zone_id, etc. are set correctly.

Secure Cookie Handling
Set a secure, HTTP-only customer cookie using setcookie() inside ControllerPagesAccountLogin.
Cookie is visible in browser, path and domain are correct.

Session Loss After Redirection
On next request after login, session appears to be reset  user is redirected back to login.
We checked .htaccess, index.php, and ensured no session reset is triggered in code.

But after redirection to account/account, session seems wiped.

Thank you for the suggestion.

We've checked our extensions and we've already switched back to the default extension (replacing the existing one). However, the issue still persists the login completes, but the redirection loops back to the login page instead of proceeding to the account dashboard.

My Observation on this issue !

During the login process, we observed the following behavior:

Credential Submission:
When valid login credentials are submitted via the login form, a POST request is initiated to the login route.

Initial Response

Unexpected Session Deletion:
Upon redirection to the /account page, the server immediately deletes the customer session cookie, as seen in the response headers. This results in the authenticated session being dropped unexpectedly.

Second Redirection (Loop Back to Login):
Because the session is no longer valid, the system interprets the user as unauthenticated and redirects them back to the login page. This creates a loop, preventing access to the account area even with valid credentials.

The table already exists in the database. I'm attaching a screenshot of the customer_session fields. Is the table structure okay?

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.