Bagisto Forum

    Bagisto

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

    Illegal offset type in isset or empty

    General Discussion
    5
    16
    1391
    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.
    • O
      osensy @sanjay-webkul last edited by osensy

      @sanjay-webkul Thanks Alot for the response, It did not help though. I am still facing the same error.
      I used composer to install it

      composer create-project bagisto/bagisto
      

      Then I ran into an error and had to do;

      composer update
      

      After that, i created a database, and included it in the .env file and then ran:

      php artisan bagisto:install
      

      The screenshot attached may help in debugging the error
      Screenshot from 2022-12-12 20-10-24.png

      1 Reply Last reply Reply Quote 0
      • sanjay-webkul
        sanjay-webkul last edited by sanjay-webkul

        @osensy said in Illegal offset type in isset or empty:

        composer update

        Hi there,
        The issue is because you run this command,

        composer update
        1 Reply Last reply Reply Quote 0
        • sanjay-webkul
          sanjay-webkul last edited by

          The issue is raised for the same in our git repository.

          Can you please let me know the reason of run composer update command?

          O 1 Reply Last reply Reply Quote 0
          • O
            osensy @sanjay-webkul last edited by

            @sanjay-webkul No, the Update didnt help either☹

            1 Reply Last reply Reply Quote 0
            • sanjay-webkul
              sanjay-webkul last edited by

              Hi there,
              For now, you can add this line on your composer.json file and then run the below command

              "laravel/framework": "9.35.1",
                 
              composer update
              

              Because the issue is in db blade compiler dependency of laravel

              1 Reply Last reply Reply Quote 1
              • sanjay-webkul
                sanjay-webkul last edited by

                Hi there,
                We will update all the dependency in our major version

                1 Reply Last reply Reply Quote 0
                • A
                  ashwattha last edited by

                  Hello,

                  I am facing the same issue. Even after putting the line in the Json and updating the composer doesn't help.

                  My composer version is: 2.1.5

                  1 Reply Last reply Reply Quote 0
                  • sanjay-webkul
                    sanjay-webkul last edited by

                    Which version of Bagisto are you using?

                    1 Reply Last reply Reply Quote 0
                    • danieldino
                      danieldino last edited by

                      I have the same problem, but the installation was correct, only when I got the add-ons, the administration works normally, the latest version bagisto

                      1 Reply Last reply Reply Quote 0
                      • sanjay-webkul
                        sanjay-webkul last edited by

                        Hi there,
                        I guess you run the " composer update " command that's why this issue is occurring.
                        Please take reference from Here for the same.

                        1 Reply Last reply Reply Quote 0
                        • danieldino
                          danieldino last edited by

                          I did so, but nothing helped.

                          the update went without errors

                          but no effect

                          1 Reply Last reply Reply Quote 0
                          • sanjay-webkul
                            sanjay-webkul last edited by

                            Hi there,
                            You run the composer update command that's why this issue is occurring.
                            Please take a reference from Here

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