- Welcome to AbanteCart Community.
AbanteCart forum
Do you like AbanteCart? Please rate AbanteCart or share your experience with other eCommerce entrepreneurs. Go to Softaculous rating page to add your rating or write a review
Recent posts
#91
Support / Re: Error log image issues
Last post by Basara - June 30, 2025, 01:08:37 AMHello.
The image error you're seeing is most likely related to the PHP GD library on your server. Specifically, older versions of GD don't support WebP format, which can trigger those types of errors even if you're not directly uploading WebP images yourself—AbanteCart or the browser might be trying to serve them automatically if supported.
The good news is that this is usually an easy fix. I recommend contacting your hosting provider and asking them to make sure the server has an up-to-date version of PHP with full GD and WebP support enabled.
When you say the database was "corrupt," could you clarify what exactly made you think that? Were there specific errors or behaviors? Often, a proper backup restore should resolve most issues unless the backup itself was incomplete or taken while the database was in an unstable state. If you have any logs or symptoms you noticed before the crash, it might help narrow down the root cause.
The image error you're seeing is most likely related to the PHP GD library on your server. Specifically, older versions of GD don't support WebP format, which can trigger those types of errors even if you're not directly uploading WebP images yourself—AbanteCart or the browser might be trying to serve them automatically if supported.
The good news is that this is usually an easy fix. I recommend contacting your hosting provider and asking them to make sure the server has an up-to-date version of PHP with full GD and WebP support enabled.
When you say the database was "corrupt," could you clarify what exactly made you think that? Were there specific errors or behaviors? Often, a proper backup restore should resolve most issues unless the backup itself was incomplete or taken while the database was in an unstable state. If you have any logs or symptoms you noticed before the crash, it might help narrow down the root cause.
#92
Support / Error log image issues
Last post by perplexed - June 29, 2025, 09:19:32 PMThis is a fresh install of 1.4.2 and receiving multiple errors about webp images....we are not installing webp images....why are we getting this error messages?
We just lost our 1.4.1 version due to a corrupt database and restore did not work either....this is scary...
2025-06-29 23:36:36 - App Warning: AbanteCart core v.1.4.2 Error: Cannot load image /home/copperkf/garlicstore.copperkfarm.com/resources/image/18/71/2.webp. Unable to create internal image from file /home/copperkf/garlicstore.copperkfarm.com/resources/image/18/71/2.webp. Try to decrease original image size 866x203px or reduce file size or increase memory limit for PHP. in /home/copperkf/garlicstore.copperkfarm.com/core/lib/image.php on line 72
We just lost our 1.4.1 version due to a corrupt database and restore did not work either....this is scary...
2025-06-29 23:36:36 - App Warning: AbanteCart core v.1.4.2 Error: Cannot load image /home/copperkf/garlicstore.copperkfarm.com/resources/image/18/71/2.webp. Unable to create internal image from file /home/copperkf/garlicstore.copperkfarm.com/resources/image/18/71/2.webp. Try to decrease original image size 866x203px or reduce file size or increase memory limit for PHP. in /home/copperkf/garlicstore.copperkfarm.com/core/lib/image.php on line 72
#93
General Support / Re: Disabling/Enabling stores ...
Last post by MatYoungblood - June 28, 2025, 05:36:06 AMI am using 1.3.4 and turned a new store off. It then turned the default store off and other stores linked to default with no way to turn back on. Is there a way to turn it back on?
#94
Support / Re: Upgrade to AbanteCart 1.4....
Last post by Ali Arslan - June 27, 2025, 09:31:33 AMThank 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`
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`
#95
AI for AbanteCart Ecommerce / Exploring Cursor AI for Clonin...
Last post by Basara - June 27, 2025, 09:08:58 AMHi everyone! 👋
I've been experimenting with Cursor AI to clone the Novator theme into a new extension for AbanteCart. The process involves copying PHP, SQL, and XML files, updating paths, class names, and layout configs etc.
It worked quite well, but as Cursor AI adapts based on the input, I'm curious:
👉 What prompts or approaches have you tried when using AI tools with AbanteCart?
👉 Any tips for improving the cloning process or making templates more flexible with AI?
Would love to hear your experiences, suggestions, or even test cases!
I've been experimenting with Cursor AI to clone the Novator theme into a new extension for AbanteCart. The process involves copying PHP, SQL, and XML files, updating paths, class names, and layout configs etc.
It worked quite well, but as Cursor AI adapts based on the input, I'm curious:
👉 What prompts or approaches have you tried when using AI tools with AbanteCart?
👉 Any tips for improving the cloning process or making templates more flexible with AI?
Would love to hear your experiences, suggestions, or even test cases!
#96
Support / Re: Upgrade to AbanteCart 1.4....
Last post by Ali Arslan - June 27, 2025, 06:54:03 AMServer version: 8.0.38 - MySQL Community Server - GPL
#97
Support / Re: Upgrade to AbanteCart 1.4....
Last post by abolabo - June 27, 2025, 06:06:52 AMwhat version of mysql-server do you use?
https://github.com/abantecart/abantecart-src/blob/master/public_html/composer.json#L28
(see cpanel->phpMyAdmin -> server info)
https://github.com/abantecart/abantecart-src/blob/master/public_html/composer.json#L28
(see cpanel->phpMyAdmin -> server info)
#98
Support / Upgrade to AbanteCart 1.4.2 Fa...
Last post by Ali Arslan - June 27, 2025, 04:22:46 AMHello,
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.
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.
#99
Support / Re: 403 error only for the set...
Last post by barricademan - June 24, 2025, 09:08:00 AMI did find and fix the problem. It was in fact a false positive between Abantecart and Mod_Security.
There were three wrong permissions,
The permissions could not be reset with ftp, they had to be changed using the Terminal.
Although I'm happy that I fixed it, maybe this post will help someone in the future, I've decided to delete Abantecart due to the lack of resources available for free. I feel that Abantecart would have been so more popular if the resources were more widely available as they are for other shopping cart platforms.
There were three wrong permissions,
- Index.php inside the root directory
- Vendor Folder
- System/config.php
The permissions could not be reset with ftp, they had to be changed using the Terminal.
Although I'm happy that I fixed it, maybe this post will help someone in the future, I've decided to delete Abantecart due to the lack of resources available for free. I feel that Abantecart would have been so more popular if the resources were more widely available as they are for other shopping cart platforms.
#100
Support / Re: 403 error only for the set...
Last post by Basara - June 24, 2025, 02:29:24 AMHello.
Based on your description, it does sound like a Web Application Firewall (WAF) configuration issue. Most often, it is related to ModSecurity or similar server-side security rules.
Temporarily disable ModSecurity again, and this time wait at least 1 hour before testing the admin settings area.
If the issue still persists after that, it's best to reach out to your hosting provider's support team.
Based on your description, it does sound like a Web Application Firewall (WAF) configuration issue. Most often, it is related to ModSecurity or similar server-side security rules.
Temporarily disable ModSecurity again, and this time wait at least 1 hour before testing the admin settings area.
If the issue still persists after that, it's best to reach out to your hosting provider's support team.