Categories

• Announcements

  Announcements regarding our community

  2
  Topics
  2
  Posts

  

  The Wait is Over, releasing Bagisto v0.1.4. Download today: https://bagisto.com/en/download/ Major Updates inside: Support to Multi-Vendor Marketplace Extension Enhanced Multi-Warehouse Inventory Management GUI Installer Implementation of Product Flat Get to know more about the updates here: https://dev.to/pathaksaurav/bagisto-v014-major-release-announced-pi8
• General Discussion

  A place to talk about whatever you want

  1
  Topics
  3
  Posts

  B

  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.
• Comments & Feedback

  Got a question? Ask away!

  0
  Topics
  0
  Posts
  No new posts.
• Installing Bagisto
  3
  Topics
  4
  Posts

  B

  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
• Modules
  1
  Topics
  2
  Posts

  B

  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.
• Bug Report
  31
  Topics
  51
  Posts

  B

  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.
• Technical Help
  0
  Topics
  0
  Posts
  No new posts.
• Knowledge Base
  3
  Topics
  9
  Posts

  B

  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.
• Modules
  0
  Topics
  0
  Posts
  No new posts.
• Compatibilty
  0
  Topics
  0
  Posts
  No new posts.
• SEO
  0
  Topics
  0
  Posts
  No new posts.