PrestaShop compatibility — one module, from 1.6.1 to 9
Updated on 25 Jul 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 precisely 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 isn't a commercial detail but an architectural choice: the code respects the constraints of the oldest supported version, and isolates the differences between versions in a dedicated compatibility layer. Concretely, for you:
- the same functions everywhere — no comparison table with grey crosses in the 1.6 column;
- one licence, 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 — not us, because the installed base is still enormous. 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.
PrestaShop 8
Full support, tested in real production — the content API, catalog synchronisation 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 — every change to the module is validated on all four.
What is identical everywhere
- The blog: full CRUD, categories, tags, multilingual, multistore, RSS, sitemap, title/meta/canonical tags.
- The licence 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 synchronisation, 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, over HTTPS preferably;
- The ability to install a module (a ZIP to upload, like any other module);
- For the connection to the app: that your store be reachable over HTTPS from the internet — 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 customised — 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 colours and fonts detected on your theme — visual integration is the default behaviour, not an option.
And version 10, when it lands? Supporting new versions is part of the module's normal maintenance, not of a new licence.
---
The simplest thing is to see it on your own store: the install walk-through takes a quarter of an hour, and a demo shows you generation on your catalog — whatever your version. Remaining questions have their answer in the FAQ.