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

Bagisto

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

address does not work - I have to add a new address each time to make an order work

Bug Report
2
22
1.7k
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.
  • V
    Vaishali Agarwal @mikeyapina last edited by 22 Jul 2020, 06:35

    @mikeyapina said in address does not work - I have to add a new address each time to make an order work:

    @Vaishali-Agarwal yes this is what I get and the address doesn't populate so it will fail. How I got around this is to add an other address. Even if its the same. And then it will populate, In the database it is another compete record as well.

    Billing Address
    Michael Pina
    ,
    CA
    United States 90405
    Contact : 5034074649

    DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/contentscript.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
    DevTools failed to load SourceMap: Could not load content for chrome-extension://nkbihfbeogaeaoehlefnkodbefgpgknn/sourcemaps/inpage.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
    DevTools failed to load SourceMap: Could not load content for https://ov3rt.com/themes/velocity/assets/css/bootstrap.min.css.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
    Grammarly.js:2 [DEFAULT]: WARN : Using DEFAULT root logger
    Grammarly.js:2 [WARNING] Using default timeseries implementation.
    inpage.js:1 MetaMask: MetaMask will soon stop reloading pages on network change.
    For more information, see: https://docs.metamask.io/guide/ethereum-provider.html#ethereum-autorefreshonnetworkchange
    Set 'ethereum.autoRefreshOnNetworkChange' to 'false' to silence this warning.
    
    ​

    Regarding the address issue, this is the bug exist in 1.1.0 which is already resolved in higher version, you can check https://github.com/bagisto/bagisto/issues/2868
    and update the files as mention in this issue PR.

    M 2 Replies Last reply 22 Jul 2020, 07:54 Reply Quote 0
    • M
      mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 07:32

      @Vaishali-Agarwal there is no fix here .. just a bunch of talking but bo code to fix or change .. where ei the fix I don't care about the conversation.

      M 1 Reply Last reply 22 Jul 2020, 08:19 Reply Quote 0
      • M
        mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 07:54

        @Vaishali-Agarwal this is my file that is their file they do not match which ones is right!!!!!!!!!!!! only one line is the same!

        my old file
        {
        "/js/velocity.js": "/js/velocity.js?id=a8a0bb91fbd4d49c1cb6",
        "/css/velocity-admin.css": "/css/velocity-admin.css?id=612d35e452446366eef7",
        "/css/velocity.css": "/css/velocity.css?id=4109f5e05451bbc83138"
        }

        their new file

        {
        "/js/velocity.js": "/js/velocity.js?id=d1e8a6d2c78f6d0657a7",
        "/js/velocity.js": "/js/velocity.js?id=35c906902bbed040ee39",
        "/css/velocity-admin.css": "/css/velocity-admin.css?id=612d35e452446366eef7",
        "/css/velocity.css": "/css/velocity.css?id=c93522195912f75d54dc"
        "/css/velocity.css": "/css/velocity.css?id=65eba575daf9327bd20a"
        }

        1 Reply Last reply Reply Quote 0
        • V
          Vaishali Agarwal last edited by 22 Jul 2020, 08:15

          @mikeyapina
          You can update your code with the bagisto version 1.1.2, as in 1.1.0 their are bugs which are resolved in 1.1.2 version.

          I hope then this issue will be resolved.

          M 1 Reply Last reply 22 Jul 2020, 08:20 Reply Quote 0
          • M
            mikeyapina @mikeyapina last edited by 22 Jul 2020, 08:19

            I made all the changes and still have the issue

            Screen Shot 2020-07-22 at 1.17.05 AM.png

            1 Reply Last reply Reply Quote 0
            • M
              mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 08:20

              @Vaishali-Agarwal is this a forklift upgrade? Meaning any changes I made will be over written?

              1 Reply Last reply Reply Quote 0
              • V
                Vaishali Agarwal last edited by 22 Jul 2020, 08:30

                @mikeyapina
                have you done changes as mention in this PR ??

                yes the old customization will be removed while upgrading.

                M 2 Replies Last reply 22 Jul 2020, 23:59 Reply Quote 0
                • M
                  mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 08:42

                  @Vaishali-Agarwal yes I did the exact changes and noting changes ..

                  1 Reply Last reply Reply Quote 0
                  • V
                    Vaishali Agarwal last edited by Vaishali Agarwal 22 Jul 2020, 08:44 22 Jul 2020, 08:43

                    @mikeyapina
                    Kindly raise your ticket at here https://bagisto.uvdesk.com/en/customer/create-ticket/

                    Also share you SFTP details, so that we can look into it.

                    Thanks.

                    M 1 Reply Last reply 22 Jul 2020, 23:28 Reply Quote 0
                    • M
                      mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 23:28

                      @Vaishali-Agarwal I HAVE DONE ALL OF THIS NONE IS RESPINDING AND MYSTEM IS DOWN

                      1 Reply Last reply Reply Quote 0
                      • M
                        mikeyapina @Vaishali Agarwal last edited by 22 Jul 2020, 23:59

                        @Vaishali-Agarwal guess what the instructions took me to 1.1.0 exactly where I was before but worst because I lost all my custom configs and guess what !! I am getting https HTTP errors the same problems I had before that took you guys a week to fix!

                        1 Reply Last reply Reply Quote 0
                        • M
                          mikeyapina last edited by 23 Jul 2020, 01:44

                          I fixed the https issue but now the issue is the upgrade did to work althuiogh I pulled it form the git

                          but the issue is i am not in 1.2.2
                          even after the upgrade
                          i am literally in the same place I was before in 1.1.0

                          1 Reply Last reply Reply Quote 0
                          20 out of 22
                          • First post
                            20/22
                            Last post