bolt is now disabled in payu. you can use this version https://forums.bagisto.com/topic/1586/payu-cors-error-while-integrating-payu-money-bolt-kit

Hi @KiwiNFLFan,

Never change the primary key, just try to add one more column and place your custom uuid there.

Hi @Thanos,

You need to install the debug dependencies to properly configure this.

Hi @prof-jagpreet,

Currently, there is no such API, you need to make your own.

Thanks for this.

Hi @tabish152,

Yes, you can delete it.You just need to pass the address id with DELETE method to this route,

Route::delete('addresses/{id}', 'ResourceController@destroy')->defaults('_config', [ 'repository' => 'Webkul\Customer\Repositories\CustomerAddressRepository', 'resource' => 'Webkul\API\Http\Resources\Customer\CustomerAddress', 'authorization_required' => true ]);

Hello @jignesh ,

These are just the deprecation notice, you can successfully proceed for the next steps. If you are getting any error then you can write us. Also, specify your bagisto and bulk-upload version.

Thanks

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.

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.