Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
General Support / Product Reviews, Transaction list and invoices
« Last post by databit on June 30, 2025, 06:21:55 AM »

Few things I've come across
Cant seem to find where to approve a product review?
Cant disable transactions view. No point the customer having a transactions list if nothing is entered there automatically by the system, cant find where to add a transaction type either.
They might have bought something but the list stays empty unless I enter it but cant because I cant add a transaction type.
The cart doesn't seem to create an invoice for the customer, just an order. But there is an invoice number in the system (Maybe this is to be manually entered to correlate with an accounting package which is 3rd party?) But cant modify the invoice number.
Transactions is annoying me, cant make it disappear on the customer dashboard.
22
General Support / Re: Disabling/Enabling stores in a multi-store set up
« Last post by Basara on June 30, 2025, 01:13:07 AM »
Hello.

In the admin panel, you should still see the store selector even if multiple stores are currently disabled. Additionally, when you edit a store’s settings, you’ll notice the URL includes something like store_id=0. You can manually change that ID in the URL to access the settings page of other stores, this can be helpful if, for some reason, the store selector isn’t visible.
23
Support / Re: Error log image issues
« Last post by Basara on June 30, 2025, 01:08:37 AM »
Hello.
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.
24
Support / Error log image issues
« Last post by perplexed on June 29, 2025, 09:19:32 PM »
This 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
25
General Support / Re: Disabling/Enabling stores in a multi-store set up
« Last post by MatYoungblood on June 28, 2025, 05:36:06 AM »
I 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?
26
Support / Re: Upgrade to AbanteCart 1.4.2 Fails with SQL Syntax Error on DROP INDEX
« Last post by Ali Arslan on June 27, 2025, 09:31:33 AM »
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`
27
Tips and Tricks / Exploring Cursor AI for Cloning Themes – Share Your Prompts!
« Last post by Basara on June 27, 2025, 09:08:58 AM »
Hi 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!
28
Support / Re: Upgrade to AbanteCart 1.4.2 Fails with SQL Syntax Error on DROP INDEX
« Last post by Ali Arslan on June 27, 2025, 06:54:03 AM »
Server version: 8.0.38 - MySQL Community Server - GPL
29
Support / Re: Upgrade to AbanteCart 1.4.2 Fails with SQL Syntax Error on DROP INDEX
« Last post by abolabo on June 27, 2025, 06:06:52 AM »
what 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)
30
Support / Upgrade to AbanteCart 1.4.2 Fails with SQL Syntax Error on DROP INDEX
« Last post by Ali Arslan on June 27, 2025, 04:22:46 AM »
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.
Pages: 1 2 [3] 4 5 ... 10

Powered by SMFPacks Social Login Mod