Shopping Cart Operations > Feedback

Feedback and most wanted features after few weeks with AbanteCart

<< < (2/2)

OneMore:

--- Quote ---I think 1.2.16 and 1.3.0 can run on PHP 7.1 why did you choose 1.2.11?
--- End quote ---

* Because for AbanteCart 1.2.16 the minimal PHP version was not mentioned. We know there is PHP 7.4 support, but there is no mention about compatibility with previous PHP versions.
* Because of similar issue with AbanteCart 1.3.0, for which PHP 8 support was mentioned, but not PHP 7. So, I believed it was incompatible with PHP 7.
* Because I knew from another post read on the forum that the 1.2.11 version was compatible with PHP 7.1. Hence, it was for me a hassle-free choice.So, in short, the lack of information about PHP compatibility is why I chose AbanteCart 1.2.11 rather than a newer version.

One big strength of Prestashop is that their documentation is very clear about system requirements, with a very clear "PHP compatibility chart" where you instantly see which version of their shopping cart system is compatible with which (lowest - uppest) version of PHP.
See https://devdocs.prestashop-project.org/1.7/basics/installation/system-requirements/

I believe that a similar PHP compatibility chart would be very useful fo AbanteCart.
I understand that testing a large codebase with all versions is lot of work, but even if not all cells of the compatibility matrix are colored in green or red, they could be left in grey color, until someone in the forum confirms wether a combination is working or not.

abantecart:
OneMore , Thank you for the feedback. We will work on the update

OneMore:
Thank you abantecart.

I added two more ideas (6 and 7) in my original post.

I want to detail more my thoughts about why the pictures of products should not be resized nor renamed (apart for those duplicated as thumbnails).

There are two kind of merchants:

* those who pre-process / optimize product images,
* those who don't.1. Merchants that optimize product pictures
They have several reasons for doing so:

* Products have by nature different sizes, and their visual inspection may require different level of details.
Example: A 30cm motherboard might need a high-resolution picture so that one can inspect tiny inscriptions on components, whilst a 2cm CMOS clock battery is smaller by nature and doesn't need close inspection.
* Make images faster to load (size, color depth, compression) and still good enough for the given purpose.
* Metadata can be embedded inside the pictures for SEO optimization.For this category of merchants, pictures being resized and renamed by AbanteCart is painful.
Hence, image processing by AbanteCart should be disabled by default.
2. Merchants that don't optimize pictures, either

* because they are ignorant
* beause they don't care much about the quality of the pictures for their webshop
* because they don't have time, and just want to upload pictures form their smartphonesKeeping in mind this category of merchants, AbanteCart could perform several successive checks after the picture was uploaded, and fire dialogs where the user can accept or reject a suggested image optimization.

* is the picture too large in size?

* is the picture large is pixels (e.g. over 800x800)?

* could the picture be in a better format for the web (e.g. webp instead of png)?
The dialog(s) could:

* ask the user if he wants AbanteCart to rezize the picture or keep it as it is
* suggest toggling on the image resize feature in the "Admin > Settings > Apparence" section.
* offering a "Don't ask again" checkbox" (useful for those users who are doing image preprocessing)
* make users more instructed, suggesting some softwares for image pre-processing (e.g. IrfanView, Gimp), or provinding a link to a documentation topic about thisIn summary: a shopping cart system is not an image processing software and should not do what can be done better by a well-educated merchant using dedicated software.
However, AbanteCart could detect images that a priori seem unoptimized and suggest (not impose) resizing them.

N.B. CubeCart is doing things well, by placing the original images in a "image/source" folder.

Cheers.

OneMore:

--- Quote ---I think 1.2.16 and 1.3.0 can run on PHP 7.1 why did you choose 1.2.11?
--- End quote ---


--- Quote ---Because for AbanteCart 1.2.16 the minimal PHP version was not mentioned.
(...)
I believe that a similar PHP compatibility chart would be very useful fo AbanteCart.
--- End quote ---

See this link for AbanteCart's PHP compatibility chart:
https://abantecart.atlassian.net/wiki/spaces/AD/pages/3768390/AbanteCart+System+Requirements#AbanteCartSystemRequirements-PHPcompatibilitychart

Many thanks to the developers, testers, and editors fo the documentation.

Navigation

[0] Message Index

[*] Previous page