Bagisto Forum

    Bagisto
    • Register
    • Login
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups

    Slider issue in Customized theme with velocity.js file.

    Bug Report
    3
    8
    502
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      mannansamcom last edited by mannansamcom

      Hello , I have customized the velocity theme as per the bagisto documentation , Now I wanted to use the Vue components of the bagisto velocity theme and for this I am including the velocity.js file inside the "themes/velocity/assets/js/velocity.js". After the including the file the Vue components are working but the customized theme slider is stop working. If I am removing the velocity.js file from the blade then it's working fine. so what's the solution for it ? we need Vue component of the velocity theme and accourding to our needs we will modify it.

      1 Reply Last reply Reply Quote 1
      • V
        Vaishali Agarwal last edited by

        @mannansamcom
        please specify your bagisto version on which you have customized the theme..

        Thanks

        1 Reply Last reply Reply Quote 0
        • M
          mannansamcom last edited by

          Hello @Vaishali-Agarwal , I am using bagisto version 1.2.0

          1 Reply Last reply Reply Quote 0
          • D
            deepak227 last edited by

            @mannansamcom after changes you have run the command npm run prod in velocity theme ?

            1 Reply Last reply Reply Quote 0
            • M
              mannansamcom last edited by

              @deepak227 said in Slider issue in Customized theme with velocity.js file.:

              npm run prod

              I have run npm run watch and npm run dev for updated changes.

              1 Reply Last reply Reply Quote 0
              • D
                deepak227 last edited by

                and you have the php artisan vendor:publish ?

                1 Reply Last reply Reply Quote 0
                • M
                  mannansamcom last edited by

                  Hello , I have already included dependency so why I need to run php artisan vendor:publish ? it will be publish your assets which will be listed below :

                  Copied Directory [/vendor/laravel/framework/src/Illuminate/Foundation/Exceptions/views] To [/resources/views/errors]
Copied Directory [/vendor/laravel/framework/src/Illuminate/Notifications/resources/views] To [/resources/views/vendor/notifications]
Copied Directory [/vendor/laravel/framework/src/Illuminate/Pagination/resources/views] To [/resources/views/vendor/pagination]
Copied Directory [/packages/Webkul/Admin/src/Resources/lang] To [/resources/lang/vendor/webkul/admin]
Copied Directory [/packages/Webkul/Admin/publishable/assets] To [/public/vendor/webkul/admin/assets]
Copied Directory [/packages/Webkul/Ui/publishable/assets] To [/public/vendor/webkul/ui/assets]
Copied Directory [/packages/Webkul/Shop/publishable/assets] To [/public/themes/default/assets]
Copied Directory [/packages/Webkul/Velocity/publishable/assets] To [/public/themes/velocity/assets]
Copied Directory [/packages/Webkul/Velocity/src/Resources/views/shop] To [/resources/themes/velocity/views]
Copied Directory [/packages/Webkul/BookingProduct/publishable/assets] To [/public/themes/default/assets]
Copied Directory [/packages/Webkul/SocialLogin/publishable/assets] To [/public/themes/default/assets]
Copied Directory [/packages/Webkul/Marketplace/src/Resources/views/shop/default/customers/account/partials] To [/resources/themes/default/views/customers/account/partials]
Copied Directory [/packages/Webkul/Marketplace/src/Resources/views/shop/velocity/customers/account/partials] To [/resources/themes/velocity/views/customers/account/partials]
Copied Directory [/packages/Webkul/Marketplace/publishable/assets] To [/public/themes/default/assets]
Copied Directory [/packages/Webkul/Marketplace/publishable/assets] To [/public/themes/velocity/assets]
Copied Directory [/vendor/laravel/framework/src/Illuminate/Mail/resources/views] To [/resources/views/vendor/mail]

                  Hope you understand.
                  My question is why velocity.js is not working with the custom theme which we are using ? Why we need to create new velocity.js or new Vue component ?

                  Before buying plugins we already show the theme as well , you have to raised before this all the things like it will be not work with the custom theme.
                  if we need to modify all the things then why we will go with your plugins we can create with our own way.

                  Please do a need full and just give us the solution regarding the velocity.js file include in custom theme without and conflict and need to use your Vue component.

                  Thanks

                  1 Reply Last reply Reply Quote 0
                  • D
                    deepak227 last edited by

                    @mannansamcom said in Slider issue in Customized theme with velocity.js file.:

                    Before buying plugins we already show the theme as well , you have to raised before this all the things like it will be not work with the custom theme.
                    if we need to modify all the things then why we will go with your plugins we can create with our own way.

                    Hello @mannansamcom whenever you make the changes you have to run npm run prod this will compile you assets and make a new file or override the veloclty.js because every time you make the change you must to run command. And after the changes you have to run php artisan vendor:publish --force and select the package where you have make the changes because in public directory there is a theme folder in this folder you have to override the velocity.js if you not run this command you can't get the changes you have done.

                    For making a custom theme you have to make your own files and you have to setting regarding the custom theme in backend also. Because every custom theme have there own ui for this you required new file and new component also.

                    Thank you hope this will work for you.

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post