Bagisto Forum

    Bagisto

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    1. Home
    2. Popular
    Log in to post
    • All categories
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics
    • All Time
    • Day
    • Week
    • Month
    • G

      Unable to Update Configuration Settings – 403 Forbidden in Bagisto 2.4
      Bug Report • • gkdev

      6
      0
      Votes
      6
      Posts
      1911
      Views

      admin

      Hello, @gkdev

      Greetings!

      As you confirmed, you were previously working on the master branch, which contains the newer Bagisto 2.5 version, and then switched to the 2.4 branch.

      Please note that once Bagisto has been installed, you cannot move back to an older version simply by switching branches. If you need to use the older branch/code, you will need to reinstall Bagisto using the required version.

      If your project contains any production data, we strongly recommend that you do not downgrade or switch to an older version, as the database structure of a newer Bagisto version may not be compatible with an older version.

      If you do not have any production data and want to start with a fresh Bagisto 2.4 installation, you can clone the Bagisto 2.4 branch and install it using:

      composer install php artisan bagisto:install

      Note: If you have any important data, customizations, or changes, please make sure to take a complete backup before reinstalling.

      Also, please note that the database of a newer Bagisto version cannot simply be used with an older Bagisto version, as the database structure and migrations may differ between versions.

      Regarding the 403 Forbidden Error
      The 403 Forbidden error is generally related to server configuration or file permissions. Please ensure that the web-server user has the required read/write permissions for the Bagisto application directories.

      For a standard Linux server using www-data as the web-server user, you can use the following commands from the Bagisto project directory:

      sudo chown -R www-data:www-data storage bootstrap/cache sudo chmod -R 775 storage bootstrap/cache

      If your web server uses a different user, such as nginx or nobody, replace www-data with the appropriate web-server user.

      You can check the web-server user based on your server configuration/processes before applying the ownership command.

      If the issue persists, you can also ensure that the Bagisto project directories are accessible by the web server:

      sudo chmod -R 755 /path/to/bagisto sudo chmod -R 775 /path/to/bagisto/storage sudo chmod -R 775 /path/to/bagisto/bootstrap/cache

      Please replace /path/to/bagisto with your actual Bagisto project path.

      After updating the permissions, clear the application cache:

      php artisan optimize:clear

      Important: We recommend avoiding chmod -R 777 on the Bagisto project, as it provides unnecessarily broad permissions and is not recommended for a production server.

      Thank you.
      Aviral
      Team Bagisto

    • H

      image
      Bug Report • • hermit

      2
      0
      Votes
      2
      Posts
      489
      Views

      admin

      Hi, @hermit

      Thank you for the update.

      We have noted that the backend is working correctly. For the frontend image issue, please clear the Bagisto cache and regenerate the images, then check the storefront again.

      If the issue still occurs after these steps, please share the error details or a screenshot of the frontend so we can investigate it further.

      Best regards,
      Aviral
      Bagisto

    • B

      Bagisto Theme Page Showing Blank After Configuring Store URL
      Installing Bagisto • • B4ALLB4U

      2
      0
      Votes
      2
      Posts
      103
      Views

      admin

      Dear @B4ALLB4U ,

      Thank you for contacting us, and we apologize for the inconvenience.

      If your storefront appears blank after changing the URL from localhost to your domain, the issue may be related to the channel domain configuration, .env settings, theme assets, or cache. Please follow the steps below in order.

      1. Check the Channel URL

      Go to Admin → Settings → Channels and open the channel you are using.

      Make sure the Host Name matches your domain. Enter the domain without http:// or https://.

      For example:

      ✅ www.yourstore.com ❌ https://www.yourstore.com

      The value should match the domain you use to access the storefront in your browser.

      2. Update the .env File

      Open the .env file in your Bagisto root directory and update the application URL:

      APP_URL=https://www.yourstore.com APP_ENV=production

      Use https:// only if your domain has an active SSL certificate. Make sure the protocol matches the URL you use in your browser.

      3. Check Your Domain Document Root

      Make sure your domain points to the Bagisto public directory.

      For example:

      /path-to-bagisto/public

      Also, make sure the .htaccess file exists inside the public directory and that Apache's mod_rewrite is enabled.

      4. Clear the Bagisto Cache

      If you have SSH access, run the following commands from your Bagisto root directory:

      php artisan optimize:clear php artisan config:clear php artisan storage:link

      Then reload the storefront.

      5. Check the Theme Assets

      Make sure the required theme assets exist in the following location:

      public/themes/shop/default

      If the directory or required files are missing, reinstall or regenerate the Bagisto theme assets.

      6. Check File Permissions

      Make sure the web server has permission to read the application files and write to the required directories, especially:

      storage/ bootstrap/cache/ If the Storefront Is Still Blank

      Please share the following details with us so we can investigate further:

      The latest entries from storage/logs/laravel.log A screenshot of the Console tab from your browser's Developer Tools Your PHP version Your Bagisto version The domain URL you are using

      You can temporarily set the following in your .env file to display the actual error:

      APP_DEBUG=true

      After identifying the issue, please set it back to:

      APP_DEBUG=false

      Once we have the above details, we can investigate the issue further.

      Best regards,
      Aviral
      Bagisto