A dispensary theme judged by its changelog
Most niche themes announce themselves through demo screenshots. Indicana's more useful signal is the release notes. The vendor's changelog, running from December 2018 to April 2026, is almost entirely maintenance work aimed at the stack the theme sits on: WPBakery compatibility at 7.0.x, then an update to 7.9, then 8.6.x; WooCommerce fixes through the 7.x line and a 9.0 compatibility entry; PHP 8.x support in 2021 and PHP 8.4 compatibility in the final listed release.
That pattern tells you what kind of product this is. It has not been relaunched with a new set of demos; it has been kept in step with the page builder, the shop plugin and the PHP runtime underneath it. For a dispensary site that needs to keep selling, upkeep matters more than a fresh homepage concept.
The claims below come from the marketplace description and attributes as observed on 4 November 2026. They are vendor statements about the product, not the results of running it.
What the shop actually contains
The vendor positions Indicana around WooCommerce from the first paragraph: the theme includes the pages of an online store, and the description names the product catalog, product page, shopping cart and order screens alongside about, blog, galleries and testimonials. Product variables were added in a 2019 release, which matters if you sell the same strain or edible in several sizes or strengths rather than as a single fixed item.
So the content model is a store with a supporting brochure site around it, not a brochure site with a shop bolted on. The marketplace attributes list WooCommerce 6.x through 10.x under Compatible With, and translation is covered by WPML in the same list. Events Calendar also appears there — the compatibility attribute names a plugin, and does not by itself mean any demo requires it.
If your catalogue is small and informational, this breadth is more than you need. If you are selling flower, edibles, concentrates and accessories from one site, the pre-built catalogue and cart flow save you from designing commerce pages yourself.
Editing in WPBakery, on a Bootstrap 3 grid
Pages are built with WPBakery Page Builder, which the vendor describes as a drag-and-drop tool for assembling layouts without coding. The theme adds its own material to that builder: the feature list cites 20+ custom elements, plus a set of shortcodes, scroll animations, parallax effects and easy colour customisation. What you place on a page is therefore a mix of WPBakery's rows and columns and the theme's own element types, configured through the same editing surface.
The grid is worth naming plainly, because the vendor does: Bootstrap 3. That is an older generation of the framework. It works, and the theme's layouts are designed around it, but it is not the grid a 2026 theme would choose, and it sets expectations about how much modern utility-class layout work you should plan to do yourself.
Gutenberg Optimized is recorded as No. Read that as a statement about where the theme's design effort lives — in WPBakery — rather than a claim that the block editor is broken. For a team already comfortable with WPBakery, this is unremarkable; for one standardising on blocks, it points elsewhere.
The photos are not in the package
The vendor's note is direct: images are not included in the download package. The demo photography is sourced from stock libraries, and the description lists Depositphotos, Shutterstock, Freepik, Pixabay and Unsplash as the sources used. Some of those offer free licences and some do not.
This is a budget line and a scheduling item that buyers often meet only after switching the demo content to their own. Budget time for selecting and licensing a photo set before launch, and treat any imagery that arrives with the demo as placeholder rather than something you can publish.
Fonts are covered separately in the same description: Font Awesome for icons and Karma as the Google Font. Those are font references, not image licences.
Features that shape day-to-day editing
A handful of listed features have practical consequences beyond the marketing list. The one-click demo import lets you bring in the demo without rebuilding every page by hand; the vendor's later releases have added homepage layouts, so you can expect more than one starting point rather than a single fixed design.
The multi-level menu suits a store organised by category and sub-category, and the widget-ready flag means sidebars and footer areas take standard WordPress widgets. Contact Form 7 support covers enquiry and contact forms, and MailChimp readiness covers newsletter signup. A child theme fix appears early in the changelog, which is a reminder that customisations belong in a child theme rather than the parent files.
One release entry deserves a note of its own: version 1.4.4 records that an Lt-Core plugin was added to the theme. Themes that move functionality into a companion plugin are usually doing it so the feature set can be updated independently of the theme files — but the supplied material does not describe what Lt-Core contains, so treat its role as something to confirm before you plan around it.
Declared compatibility, and the version you actually run
The compatibility attributes are declarations, not a tested matrix. They list WordPress 5.0.x through 7.0.x, WooCommerce 6.x through 10.x, WPBakery Page Builder, WPML and Events Calendar, with Firefox, Safari, Opera, Chrome and Edge as the supported browsers. The changelog's most recent entry, dated April 2026, records PHP 8.4 compatibility.
Marketplace version numbers and the copy you install are separate facts. The listing shows a latest version, but the theme reports its own version inside WordPress once installed, and that is the number to compare against the changelog when you check whether a given fix is present.
The files listed as included are PHP, CSS and JavaScript, with documentation described as well documented. Nothing in the supplied material documents hands-on testing of any specific plugin or PHP combination, so verify the combination you intend to run on a staging copy first.
Where this theme fits
Indicana makes sense for a dispensary, clinic or cannabis storefront that wants the shop pages already designed and is content to edit them in WPBakery. The niche page set — catalogue, product, cart, order, gallery, testimonials — matches that business directly, and the release record suggests the vendor keeps the stack underneath current rather than leaving it frozen.
It fits less well if your team works in the block editor, if you need a modern grid system to build custom layouts, or if you have no budget or time for licensed photography. Indicana - Medical Marijuana Dispensary WordPress Theme download questions are best answered by checking the version reported inside WordPress against the changelog, since that is the only number that describes the copy in front of you.
Questions & answers
Does Indicana include the images shown in the demo?
No. The vendor states that images are not included in the download package and lists the stock libraries used for the demo photography, so plan to source and license your own images.
Can I edit Indicana pages in the block editor?
The theme is built for WPBakery Page Builder, and Gutenberg Optimized is recorded as No. That attribute describes where the theme's design effort sits rather than proving the block editor is unavailable, so check what your build actually needs before committing to a workflow.
Which WooCommerce versions does the theme claim to support?
The marketplace attributes observed on 4 November 2026 list WooCommerce 6.x through 10.x, and the changelog records a WooCommerce 9.0 compatibility entry. These are vendor declarations, not independent test results.
