PrestaShop compatibility: 1.6.1, 1.7, 8 and 9
Updated on 17 Sept 2026
"Compatible with PrestaShop 1.6 to 9" appears on plenty of module listings, and often disappoints at install time: functions missing on 1.6, separate versions to buy again, second-rate support. Here is what compatibility covers at Publium, version by version.
The principle: one module, not four
Publium is a single module whose code adapts to the version hosting it. That is an architectural choice, not a commercial detail: the code respects the constraints of the oldest supported version, and isolates the differences in a dedicated compatibility layer. For you that means:
- the same functions everywhere, with no comparison table full of grey crosses in the 1.6 column;
- one license, whatever the version;
- a PrestaShop migration without surprises: the module follows, and so does your content.
The detail per version
PrestaShop 1.6.1
The version everyone else is dropping. We keep it, because the installed base is still large. Complete blog (articles, categories, tags, RSS, sitemap, friendly URLs, SEO tags), templates adapted to 1.6 themes, and the same connection to the app as on recent versions: article generation, product description rewriting, remote publishing.
PrestaShop 1.7
The most widespread version. Full support, templates dedicated to 1.7 themes, BlogPosting structured data on articles. This is the version where the module lives its quietest life, and the SEO plan for a store that stays on it fits in the 1.7 checklist.
PrestaShop 8
Full support, tested in real production: the content API, catalog syncing and publishing run daily on 8.x stores. Nothing specific to know.
PrestaShop 9
Full support on the latest generation. The module's test environments cover 9 exactly like the other three versions, and every change is validated on all four.
What is identical everywhere
- The blog: full CRUD, categories, tags, multilingual, multistore, RSS, sitemap, title/meta/canonical tags.
- The license functions: local SEO assistant, Schema.org structured data, internal linking suggestions.
- The connection to the app: signed API (HMAC, timestamp, replay protection), catalog and theme syncing, article publishing, SEO updates on product pages.
- Security: no back-office credentials exchanged, secrets encrypted at rest, rate limiting.
The technical prerequisites, plainly
- A PrestaShop store on 1.6.1 or newer, preferably over HTTPS;
- The ability to install a module (a ZIP to upload, like any other module);
- For the connection to the app: your store must be reachable over HTTPS from the internet, which is true of any production store.
No exotic dependency, no core modification, no server access required.
Three frequent questions
I'm migrating from 1.6 to 8: what happens to my articles? They live in the module's tables, which migrate with your database. Reinstall the module on the new version and your content is there.
My theme is heavily customized. Will the blog fit in? The blog front end uses templates your theme can override, like any well-behaved PrestaShop module. And articles generated as "styled HTML" reuse the colors and fonts detected on your theme: visual integration is the default, not an option.
And version 10, when it lands? Supporting new versions is part of the module's normal maintenance, not of a new license.
The install walk-through takes under five minutes, whatever your version. Remaining questions are answered in the FAQ.