If I create a new package with the same name (CMS) does that disable the original one in the Webkul directory?
Posts made by porl
RE: Product store without inventory management
Any update on how to disable the inventory system? I am customising pretty heavily the front-end so I can avoid adding in the field to display it, but wondering if there is a cleaner way to disable it entirely (including the quantity fields in the back end).
Is there a way that I can override an entire package? For my use case I essentially want to heavily customise the CMS package.
Rather than modifying it in place (risking losing changes on an update) is there a way I can essentially copy it into my own package directory and tell bagisto/composer etc. not to use the original?
Obviously I can go in and modify the autoload stuff to stop loading the original one and load mine in place, but again, on an update I would have to remember to go back and make all those modifications again.
Is there a more clean way I can tell the system that my "CMS" package overrides the Webkul one (or use some config to disable the Webkul one)?
RE: Product with Uploadable Image
On a similar note, is there a way to have customer option fields in general for a product?
As an example, a customer wants to order a custom card or mug where the product page has a "Your message:" field on it so they can enter the text they wish to appear on the card or mug.
Product with Uploadable Image
Hopefully a quick question. Is there any way to use a file attribute as a product option so a customer can, for example, upload their own image file to be used in the production of a custom product? I have created a file attribute but can't see how to put that as an "option" for a customer to provide.
RE: Custom Theme in Separate Package
Never mind, I found the solution.
For anyone else with the same issue I needed the full path (relative to the root Bagisto directory).
'views_path' => 'packages/ACME/CustomTheme/src/Resources/views/shop', 'assets_path' => 'packages/ACME/CustomTheme/src/Resources/assets',
Not sure if there is a cleaner way to do this but it works at least.
Custom Theme in Separate Package
I am trying to determine if Bagisto suits my needs for an urgent project.
So far things are looking okay, however I am struggling to work out how to create a custom theme that is able to be kept within its own package (I do not want to be editing files in too many places outside of this package for the theme as I want to be able to easily reuse it in other projects).
How do I go about setting up the views_path etc. in themes.php to point to views within a specific package (e.g. ACME/CustomTheme)?
Secondly, is there any "minimalist" theme out there I can look at? Even the default theme has a lot of extra stuff in it I don't need and whilst I can of course start with that and remove what I don't want it would be nice to have something that is the absolute minimum for a working "shop".