forums.bagisto.com

@rahil This type of functionality can be customized, but as of now, Bagisto does not automatically add a free product to the cart based on the purchase of another product. For example, if the customer purchases Product X, we can customize the system so that Product Y is automatically added to the cart as a free product. This would require custom development to implement the required promotion logic. Thanks

Hello @barnaddy06 The best approach is to implement this as a custom shipping carrier. You should not read the destination country directly from the request or session. Get the current cart and retrieve the country from the cart's shipping address: use Webkul\Checkout\Facades\Cart; $cart = Cart::getCart(); $country = $cart->shipping_address?->country ?? $cart->billing_address?->country; The country value will be the ISO country code, for example: US GB NL AU For weight, if you are using Bagisto's native weight attribute, you should use the cart item total_weight instead of recalculating the product weight manually: $totalWeight = 0; foreach ($cart->items as $item) { if (! $item->getTypeInstance()->isStockable()) { continue; } $totalWeight += (float) $item->total_weight; } Using $cart->items is important because all_items may include child items and can result in double-counting for configurable or bundle products. Then create a custom carrier extending AbstractShipping and perform the country + weight calculation inside the calculate() method: class InternationalRate extends AbstractShipping { protected $code = 'international'; public function calculate() { if (! $this->isAvailable()) { return false; } $cart = Cart::getCart(); if (! $cart || ! $cart->haveStockableItems()) { return false; } $country = $cart->shipping_address?->country ?? $cart->billing_address?->country; $weight = 0; foreach ($cart->items as $item) { if (! $item->getTypeInstance()->isStockable()) { continue; }

Hi, Welcome to Bagisto! The syntax itself is correct, but that declaration (const int USER_ID = 1;) uses typed class constants, which are only supported in PHP 8.3 and later. This error usually means your server is running an older PHP version (such as 8.2, 8.1, or below), so PHP doesn't recognize the int type before the constant name and throws the parse error. You can verify your PHP version by running: php -v or by checking the output of phpinfo() if you're using a web server. If you're using a PHP version below 8.3, please upgrade to PHP 8.3, as the current Bagisto version requires it. Thanks Aviral Team Bagisto

Hello Gwenaelle, Greetings! Thank you for reaching out and for sharing your findings. We were able to identify this issue, and it has already been fixed in the latest version of the Marketplace package ( v2.4.6 ). If you continue to experience any problems after changes in database, please let us know. We'll be happy to assist you further. Regards, Kartikey Dubey Team Bagisto

Hello Gwenaelle, Greetings! Thank you for reaching out and for sharing your findings. The @csrf token is already included in our shop form component located at: packages/Webkul/Shop/src/Resources/views/components/form/index.blade.php Therefore, there is no need to add @csrf manually on pages that use the component. Could you please clear your browser cache and try again? If you still encounter the same 419 (CSRF Token Mismatch) error, kindly let us know. We'll investigate it further. Thank you as well for your suggestion regarding the seller approval documentation. We appreciate your feedback and will consider improving the documentation to make this process easier to find. Regards, Kartikey Dubey Team Bagisto

Hello, Thanks for flagging this. You're right — the rating, status, and sort filters on GET /api/shop/products/{productId}/reviews were not being applied. This has been fixed in the latest release (v2.0.0) — the filters now work as documented. Please update to the latest version of the package, and the filtered requests will return correctly. Let us know if you still see any discrepancy after upgrading. Best regards, Bagisto Support

@01aviral-webkul Thanks alot, these points helped to fix the issue.

Hello Gaurav, Greetings! Thank you for reaching out. Yes, UTM parameters can be implemented in Bagisto to track affiliate clicks and conversions. Since UTM parameters (such as utm_source, utm_medium, utm_campaign, etc.) are used for tracking marketing sources, they can be captured when a customer lands on the website and associated with their complete purchasing journey. Proposed Implementation Flow 1. Capture UTM Parameters Create a middleware or use an event listener to capture UTM parameters from incoming URLs. For example: https://yourstore.com/product/abc?utm_source=affiliate1&utm_medium=partner&utm_campaign=sale The captured UTM values can then be stored in the customer session or browser cookies. 2. Maintain Tracking Throughout the Customer Journey Ensure that the stored UTM data remains available while the customer: Browses products Adds items to the cart Proceeds to checkout This ensures the original affiliate or campaign information is retained until the order is placed. 3. Save UTM Details with Orders Add custom fields to the orders table and store the captured UTM information during the order placement process. This will allow you to identify which affiliate, campaign, or marketing source generated the successful sale. 4. Generate Affiliate Conversion Reports Once UTM data is stored with orders, custom reports can be created to analyze: Affiliate performance Campaign effectiveness Conversion and sales data Please note that Bagisto v2.3.6 does not provide built-in

@negarahmady Hi, thanks for reporting this. The install failure was caused by a dependency version mismatch in the API Platform packages we rely on. We've fixed it and published a new release (v1.0.5) that pins those dependencies to a compatible set. Please pull the latest version and run the installer: composer require bagisto/bagisto-api php artisan bagisto-api-platform:install If you have a partially-installed/old copy, run composer update bagisto/bagisto-api first, then php artisan bagisto-api-platform:install. Let us know if you encounter any further issues.

Hello, Thank you for reporting the issue. We checked the Bagisto image handling flow and found that Bagisto does not permanently store resized product images. Instead, images are dynamically generated at runtime through the CacheFilters system based on the configured image dimensions. The image quality issue generally occurs because: generated image dimensions are smaller than the display/zoom size runtime resizing causes interpolation blur GD image driver reduces sharpness during resize operations We recommend checking the following configuration: Admin → Configuration → Catalog → Products Please increase the image dimensions, especially the Large Image size. For example: Small Image: 300 × 300 Medium Image: 700 × 700 Large Image: 1600 × 1600 or higher After updating the configuration, kindly clear the cache and generated images. Additionally, if the server is using the GD image driver, switching to Imagick can significantly improve image sharpness and overall quality during runtime image generation. We are also reviewing the CacheFilters resize logic to ensure images preserve aspect ratio properly and avoid unnecessary quality reduction. Thank you. Kartikey Dubey Team Bagisto

Hello @divya Please provide the folder path relative to the following directory: /project-root/storage/app/import For example: product-images import-images/products image-issue.png Also, kindly make sure the folder exists inside the import directory before proceeding Best Regards Rishabh Yogi Team Bagisto

Hello @Zeryab We have already raised this issue. You can track and review it through the following link, and also share your observations there: https://github.com/bagisto/bagisto/issues/11294 Regards