Troubleshooting¶
When Product Bundles does not behave. The ways an install fails (a blank admin page, a menu that never appears, a route that bounces you to the dashboard) are the same for every extension sold here and are written up once, under troubleshooting an install.
Whatever the symptom, Product Bundles wrote down what it did and what it refused to do, in a file your own admin downloads in one click. See what Kyvero extensions log.
A bundle is badged Broken¶
One of its components cannot be packed. Open the bundle and the banner names what is wrong and, if you run more than one shop, which shops it is wrong in.
A component counts as broken when it is deleted, disabled, dated into the future, not in that shop's catalogue, or configured with an option value your catalogue no longer offers. Fix the component, or take it out of the bundle, and the badge clears on the next read.
Running out of a component is not this. Scarcity is your store's own question, and your store-wide "out of stock checkout" setting answers it, the same way it does for a product.
A customer says they cannot check out¶
If their cart holds a bundle whose components cannot be packed, that is deliberate: they are stopped at the cart with a line saying which bundle is the problem, and checkout will not take the order. Fix the component and they can carry on, and nothing they configured was thrown away.
The bundle page says it cannot be made, but the components are in stock¶
Availability is worked out across the whole cart, not per line. If the same component sits in two different bundles in that cart, the demand is added together: ten mugs cannot fill a kit needing six and a gift set needing six, even though each on its own would fit.
Also check the component's own Date Available. A component dated into the future is not sellable yet, and the bundle says so rather than promising a box it cannot fill.
The price in the cart is not the price I set¶
Two things on the bundle's carrier product are silently lost, and both are set on a row you are not meant to edit:
- a store-level product discount on the carrier is overwritten;
- a product special never applies at all, which is OpenCart's own change and not this extension's doing.
Set the bundle's price on its own form instead: Pricing Mode and the Discount or Price beside it.
A coupon behaves the way it does for a product: one naming a product inside the bundle does not apply, because OpenCart matches on the line's own product. One naming the bundle works normally.
I cannot edit a bundle order in the admin¶
The order editor refuses a bundle line on purpose. What goes in the box is chosen on the bundle's own page, and the editor has nowhere to keep that choice, so it declines instead of silently mangling the order. Remove the bundle line to edit the rest of the order.
OpenCart will not let me delete or copy a product¶
If that product is a bundle's carrier, it is refused deliberately: the row belongs to Product Bundles and editing it in place would break the bundle. Delete the bundle under Catalog → Bundles instead, and the carrier goes with it. While the module is on, opening a carrier's edit form takes you to its bundle's form for the same reason.
If the product is a component of a bundle, a delete is refused too, and the message names the bundles holding it. Take it out of those bundles first. Copying a component is allowed.
Both refusals are Product Bundles' own, so they hold only while Status is on. See Status off.
A bundle will not save¶
The form marks the field. The refusals that are not about a blank field:
- A bundle cannot contain another bundle.
- A bundle cannot contain a product that has subscription plans, and the message names it. OpenCart will not put such a product in a cart without a plan chosen, and a bundle has nowhere to choose one.
- A percentage discount must be between 0 and 100. 110 is refused rather than read as free.
- An SEO keyword is needed in every shop and language, may use only letters, numbers, dashes and underscores, and cannot already belong to a product, category or anything else in that shop.
Every bundle disappeared after an update¶
Switch Status back on at Extensions → Extensions → Modules → Product Bundles and press Save. An update always comes back with the module switched off, and off takes every bundle off sale. Switching it on puts each bundle back as its own Status says. See Status off.
Something a bundle used to show has gone¶
Check Where bundles show on the settings screen. An update ticks every box again, but a box somebody unticked hides that surface: the bundle card, the Bundles page, the review wording, the cart notice, or the contents on the order page, the order emails or Returns Portal. See choosing where bundles show.
It refuses to install¶
Product Bundles needs OpenCart 4.1.0.1 or newer. It is the one extension sold here that does not go back to 4.0.2.0. On an older store it installs nothing, creates no tables, and says on its own screen which version you have and which you need. See the exception on the requirements page.
If it installed but says your release is untested, that is a note rather than a fault: your OpenCart is newer than the newest one a full pass has been run against. It runs normally. If something misbehaves, please tell us rather than assume it is your data: support.
Something else¶
Support has the routes. A bundle's behaviour is easiest to diagnose with its name, the component that is misbehaving, and your OpenCart version, which is printed at the bottom of every admin page.