Hi,

Thanks for your reply. I hope that it will be finish soon 😄

Hi @zh1lu0,

It is always recommended that never done any changes in the the package folder but if you are familiar with Laravel codes and upgrade then you can feel free to do this.

Take an example of the vendor folder, we never do any changes in the vendor folder instead we override this and publish our files.

So I recommend you to publish all the Bagisto content in one shot and then customize your theme in the resources/ folder. Always take a backup of the resources/ folder.

Did you add any expiry dates?

Because this is very strange behavior by your application.

Hi @userbagisto,

Image is shown on the basis of asset path. So APP_URL should be correct.

Hello,
The actual french locale has some weird translations that don't make sense.

What is the procedure if we want to contribute to the translation in order to improve them ?

This point is not clearly explained in the contributing guide.

Thanks for your reply

Hi there,

In recent new docs, we have updated some URLs and following conventions. So, some URL which are camel casing converted into kebab case, below is the latest URL,
https://devdocs.bagisto.com/1.x/advanced/create-shipping-method.html

Hi @samparker,

First, set up all your Vue dependencies in a custom module. Second, adjust your webpack in your custom module. Third, start developing your component. Fourth, once done compile your package. Fifth, publish your changes where you want. If you want to override the theme file then publish as per the theme path.

Thanks for the answer! You helped solve the problem

Every time when you have done any changes in the config, then run,
php artisan optimize

It can be easily done from the config as the default. But if you want like at the time of installation default then your approach is right.

Then, in this case, you need to customize this as per your need.

Yes, it will cause an issue, that's why I told you to have the compatibility at your end. Because you are removing the default things.

Suppose if other modules are using some methods of Velocity package then you need to take care of this and also update that method with your new modules.

@devansh-webkul said in Layered navigation to filter out search.:

Hi @harsha-m friday night funkin,

For velocity layered navigation, you can include this file,
packages/Webkul/Velocity/src/Resources/views/shop/products/list/layered-navigation.blade.php

For default theme, you can include this file,
packages/Webkul/Shop/src/Resources/views/products/list/layered-navigation.blade.php

I am just sharing the file rest you need to customize as per your need.

Thank you very much for your reply !! It is very valuable.

Issue not present here. The issue is due to the product_attribute_values table.

The new version from the doc article in here
https://devdocs.bagisto.com/1.x/advanced/render-event.html

Yes, you will lose your data because in the backend we run fresh command. Just make sure if you are using an existing one then that means Bagisto is already installed in your system.

Just follow this discussion and add your opinion,
https://github.com/bagisto/bagisto/discussions/5142

Hi @sonalichopra712,

Please check the @KiwiNFLFan answer.

Hi @sonalichopra712,

Follow this guide,
https://devdocs.bagisto.com/1.x/api/

Well, sometimes not all are coming. You can add all the missing in the generated XML file.

Hi, @Martin,

Thanks for the update.

Also, if you like our support, you may give us the review here:- https://www.trustpilot.com/review/bagisto.com

That would be grateful for us.

Thanks & Regards,

Bagisto Team