No worries. You can even take the same pattern for developing the theme for admin as i explained in shop. Overriding existing views might be the key after you have implemented the above process carefully.

Yeah you are absolutely right @cerahil in your site configuration which seems to be an Apache server your project path had to be till public directory not the root directory. This is how it will work fine.

This is required because no one want to fill address everytime for checkout. In magento also if user have checkout with any address then at next time of checkout that address will appear on checkout page, if user has use multiple address than all those address will appear on checkout page. Please check the magento checkout functionality for this.Also please add an option on checkout page to add new address at time of checkout.

This functionality is required according to customer perspective because it is not mandatory that user will checkout with his default address , what if user want to checkout with other address,in this case he need to go to his profile first and then change his default address. You can take the reference from below attachment: https://prnt.sc/lljir6 Also you can take the reference from amazon

You need to create the folder of same locale_code and file inside it with the same locale code. And enable that locale in channels as default locale or select multiple locales in the channels.

Hello @murl1dhar Currently we have not implemented any type of event system that would be responsible adding the fields in admin section forms. Yet, the same thing is not true for storefront i.e customer section. If you check the view files of shop package in Root\Webkul\packages\src\resources\views , you will find this type of syntax, check the screenshot below: This type of syntax in the picture above can be found in almost all views of the shop package. And it serves the purpose of the question that you've asked for. To use this functionality you have to just implement the event subscribers for adding any extra functionality that you want like adding fields, static information, any dynamic information, etc. You have to wait shortly for this type of thing get added for admin views. As this will rollout in new releases. But soon in later releases we will add the blade event system through which you can add the things that you have asked for.

Looking on it.

The operations for cart cannot be provided in minicart as it would require AJAX to solve the issue. We are not using AJAX anywhere in the project except checkout.

Sure, thy will be done.

We are looking into the possibility of doing so in the next two upcoming releases.

It ain't possible to do so because it requires translations for certain fields, so the users will find very difficult to enter translated values in a single form.

Design guidelines have been followed.

This will be fixed in the next release.

Design team issued all the design guidelines and they have been properly followed.

This will surely be in the next release.

Orders are not dependent on channels, even the whole admin panel is a place where all the channels can be managed in a single place.

Only forms with AJAX capabilities can have such ability but we ain't using AJAX in our project. So the possibility of implementing this is very narrow and almost ignorable as an enhancement also.

This will be done in the next release. Will post the commit hash here when this gets done.

Hello, ismael I wanted to tell you that mariaDB and MySQL are same and there ain't no difference in DML of both databases. I am afraid that your database version is older as support for json columns came late in 2016/7. So please update the version of your database: Please check out the system requirements also before installing Bagisto on https://github.com/bagisto/bagsito

Hey @np glad you asked this. I suggest you follow our core payment package of (vendor)Paypal, follow the same pattern as its made. Breaking the process in simple steps: Create a folder for your new payment gateway and use composer init command to initialize composer.json in it. Make your own vendor payment's package by using a service provider. Register the package in config/app.php. Register your package in project's root composer.json file. Follow the same declaration used in service provider file of Paypal in your own service provider also to turn up translations, migrations, views, assets. or follow laravel's own guide to create a package Guide create an entry point of class for your own payment method by extending Bagisto's abstract class called Payment. Its present in packages/webkul/payments/payments Define your own routes and controllers and then check the checkout process and use browser console for debugging the checkout process. Kindly ask any issue, if you find some trouble in making a package.