Hello,

Thank you for reporting the issue.

We checked the Bagisto image handling flow and found that Bagisto does not permanently store resized product images. Instead, images are dynamically generated at runtime through the CacheFilters system based on the configured image dimensions.

The image quality issue generally occurs because:

generated image dimensions are smaller than the display/zoom size runtime resizing causes interpolation blur GD image driver reduces sharpness during resize operations

We recommend checking the following configuration:
Admin → Configuration → Catalog → Products

Please increase the image dimensions, especially the Large Image size. For example:

Small Image: 300 × 300 Medium Image: 700 × 700 Large Image: 1600 × 1600 or higher

After updating the configuration, kindly clear the cache and generated images.

Additionally, if the server is using the GD image driver, switching to Imagick can significantly improve image sharpness and overall quality during runtime image generation.

We are also reviewing the CacheFilters resize logic to ensure images preserve aspect ratio properly and avoid unnecessary quality reduction.

Thank you.
Kartikey Dubey
Team Bagisto

Hello @divya

Please provide the folder path relative to the following directory:

/project-root/storage/app/import

For example:

product-images
import-images/products

image-issue.png

Also, kindly make sure the folder exists inside the import directory before proceeding

Best Regards
Rishabh Yogi
Team Bagisto

Hello @Zeryab

We have already raised this issue. You can track and review it through the following link, and also share your observations there:

https://github.com/bagisto/bagisto/issues/11294

Regards

Hello @kapilmaharjan-km

Can you please let us know on which server your current website is running, where you are facing this issue?

Regards
Rishabh Yogi

Hello @aabumousa

Kindly follow the official Rest API docs below for reference.

https://devdocs.bagisto.com/api/rest-api.html

Regards
Rishabh Yogi
Team Bagisto

@gauravjain1 Hi gauravjain is the issue is resolved or still opened i can help you out

@rishabh-webkul could you please check laravel.log which is i posted?

Hello @divya

Can you share the logs from laravel.log file to debug the issue more at our end.

Usually this error "Unexpected non-iterable value for to-many relation" in Bagisto Swagger occurs when API Platform tries to serialize a relationship field (like images, categories, or variants) that should return an array/collection, but instead returns null or a single object.

Regards

This happens because Bagisto expects a default channel before most services boot. Easiest fix is to run the initial migration and seed in isolation by temporarily disabling the API package or commenting the channel call in Core.php, then run php artisan migrate --seed to recreate the default channel, and restore the code after.

Hello @huynp139

Okay Great..!!

Regards

Hello @rishabh-webkul

Thank you for your response.

We are currently using Bagisto version v2.4.x-dev.

Also, we have not implemented any customizations on our end; the installation is completely default.

Thanks.
Ahmet Sefa Arşiv

Hello @mohamedali850

Our default tax rate calculation feature in Bagisto should be able to fulfill your requirement, as it also provides an option to define tax rates based on zip codes.

Kindly refer to the following documentation for more details:
https://docs.bagisto.com/settings/taxes.html

However, if you need to implement a separate tax logic or integrate tax calculation via any external API, that will require custom development and implementation from our side.

Regards

Hello @zeeshsoft

Kindly let us know the current Bagisto version you are using. This will help us identify the issue. Also, please provide images/screenshots of the issue for reference.

Regards

hi!
thanks for help

Hello @syiroth

The issue occurs on the Customer Order Detail page because the Vue-based tab component (Information, Invoices, Shipments, Refunds) fails to initialize when it encounters invalid characters in dynamic data. This usually happens if special symbols such as ™, #, /, &, smart quotes, emojis, or HTML are used in shipping method names, payment method titles, order statuses, addresses, or translation strings. These values are converted into DOM attributes/IDs, and invalid characters trigger the “DOMException: String contains an invalid character” error, which stops the tab switching functionality. To fix it, remove special characters from shipping/payment/status titles and translations, clear Laravel caches (php artisan optimize:clear), rebuild frontend assets (npm run build after deleting public/build), and hard refresh the browser. Note: Make sure you perform these steps on a staging environment first, not directly on production.

Regards
Rishabh Yogi
Team Bagisto

@MyCity

You can remove or change the “Powered by Bagisto” badge — but only if doing so is allowed by Bagisto’s license and you keep required copyright notices where legally required.

Here’s a clear, safe guide on how to do it:

⸻

Check the License First

Bagisto is published under the MIT License. That means:
• You can modify the code.
• You can remove or replace branding in your own deployment.
• BUT you must still include the original license and copyright notice in distributed copies or public code.

So you can replace “Powered by Bagisto” with your own text for your app/website, as long as you keep the MIT license text elsewhere (e.g., in your codebase).
You should not remove the copyright/license file from the source code.

⸻

How to Remove/Replace the Footer Text

The “Powered by Bagisto” text appears in the frontend footer. To change it:
Option A — Edit the Blade Template
1. Go to your Bagisto project folder.
2. Open:

resources/themes/velocity/views/layouts/footer.blade.php

3. Find the line with “Powered by Bagisto”. 4. Replace it with your own network name.

For example:

<p>
© {{ date('Y') }} Your Network Name
</p>

⸻

Option B — Override the Footer in Your Custom Theme

If you’re using a custom theme:
1. Copy the footer template:

resources/themes/your-theme/views/layouts/footer.blade.php

2. Edit it exactly the same way.

This keeps the core Bagisto code unchanged and makes upgrades safer.

⸻

Clear the Cache

After editing, run:

php artisan view:clear
php artisan cache:clear

⸻

Notes

This change only affects the display text.
Do not delete the MIT License file or required notices from your code repository — that would violate the license.

⸻

⚖️ Legal Reminder

The MIT License allows removing branding in your own deployment, but:
• If you distribute modified code publicly (e.g., on GitHub), you must include the original MIT license text somewhere.
• Always check the license text for compliance.

⸻

If you want, I can show exact code snippets from your footer file — just let me know!

@rishabh_yogi hi thanks for the response and also can you guide me how to implement cc, bcc it is not working properly I have followed the forum and solution. I am trying to add bcc and cc using env.

Seems like a configuration issue with your .env file. Double-check if the APP_URL is correctly set, especially if it differs between local and production environments. Sometimes clearing the cache again after updating the .env file can help resolve the issue.

@webepic Gracias men eres el mejor, estuve mucho tiempo tratando de arreglar ese problema, gracias...

Hello @noorealam

Just confirming with you that are you checking this official bagisto devdocs of docker installation?

https://devdocs.bagisto.com/getting-started/installation.html#🐳-docker-installation

Regards