Content Variables for PrestaShop
You published four new products last month. Somewhere on your shop a headline still promises thirty, and you cannot remember whether it is the homepage, a category intro, two product pages, or all of them at once. You certainly cannot remember which of those you also wrote in German.
Content Variables gives that number one home. You write it once, place it in any page, and every page that mentions it stays right.
Better, it can count for itself. Tell it once which products you mean and the sentence on your homepage corrects itself the day you publish the next one, in every language you sell in, while you are busy doing something else.
Setting one up takes a name and a value. Nothing moves, nothing is rewritten, and your pages keep the wording you chose.
It also counts for itself in more than one way. The same selection can return how many products match, what they total, what they average, or what the cheapest one costs, so a line like "from" stays honest without anyone checking it.
And it stays grammatical. The words after a number are stored per language and chosen from the value, so a language that changes the ending as the number moves still reads correctly.
Works on PrestaShop 1.6 to 9 and PHP 7.1 upward, in English, German, French, Spanish, Italian and Polish.
What does Content Variables actually do?
Content Variables gives a fact one definition and resolves it everywhere your shop shows it. You describe the number once, and every page that mentions it stays correct on its own.
- One definition, every language. A variable holds a value per language, so the same fact reads correctly in all of them and changes in a single place.
- Three ways to place it. Write the token straight into content, call it from a template, or read it from PHP. The same value comes back through all three.
- It counts your catalogue. A computed variable asks the catalogue instead of a person, and the answer follows your stock as it changes.
- More than counting. The same selection also returns a total, an average, the lowest price or the highest, which is what a line like "starting at" needs.
- Conditions you click together. Category, brand, price range, feature, combination, included or excluded. If you can describe the group, you can measure it.
- Grammar that follows the number. Plural forms are stored per language and chosen by the value, so counting languages stay correct as the number moves.
- Nothing leaks. An unresolved placeholder is removed before the page is sent, so a customer never sees markup where a number should be.
- Fits the shop you have. PrestaShop 1.6 to 9, PHP 7.1 upward, multistore aware, with its own cache per shop.
What happens to a number after you publish it?
It starts drifting the moment you look away. A count of products, a delivery time, a refund window or a starting price is true on the day you type it and quietly wrong a month later. Nobody notices, because the number sits in the middle of a sentence you wrote once and never reread.
The damage is not that a figure is stale. It is that a visitor reads one number on your homepage and a different one on your about page, and learns something about how carefully your shop is kept.
How do you keep six languages saying the same thing?
Today you do not, and it is not your fault. The same fact lives in a German banner, a Polish category intro and four Spanish product pages, and there is no way to see them together. Fixing one means finding the other five from memory.
With Content Variables a fact has one definition and every language reads from it. Change it once and all six pages agree, immediately, with nothing to search for.
Can it count the catalogue for you?
Yes, and that is where the work disappears. Instead of typing a number you tell it which products you mean, and it counts them itself: everything in a category, a brand, a price range, or a combination you build by pointing and clicking.
Your shop then maintains its own copy. Publish a product and the sentence that mentions it is already correct. Retire one and it corrects itself again.
What if the number should not be a plain count?
Counting is only the start. The same selection can tell you a total, an average, the cheapest item or the most expensive, so a line like "starting at" stays honest without anyone checking it.
You can be as specific as your shop needs. Products in one category and one colour, everything under a price, a brand minus its clearance range. If you can describe the group, you can put a number about it on the page.
Does it stay correct in languages that change the word?
This is where most shops quietly break. A Polish bike shop does not say "155 rowery". It says "155 rowerów", while 152 and 154 take a different ending again, and a shop that simply drops a number into a sentence gets it wrong most of the time without ever being told.
Content Variables knows those rules and keeps the phrase grammatical as the number moves. Languages that only need a singular and a plural are handled the same way, and if you would rather show the bare number you leave the words empty.
What does a mistake cost?
Almost nothing, and that is deliberate. If a value is not set, or the shop cannot work it out at that moment, the placeholder is removed before the page is sent. A visitor sees a sentence with a missing number, never a page with a piece of code showing through.
It is the difference between an imperfect page and an embarrassing one, and it is the reason you can put these into live copy without watching them.
How little work starts it, and how far does it go?
The first one takes a minute: give it a name, give it a value, and put it in a page. Nothing else in your shop changes.
From there it reaches as far as you need. The same fact can appear in product descriptions, category text, pages, titles and the short summaries that search engines show, and other parts of your shop can read the same value so they never disagree with your copy.
Runs on PrestaShop 1.6 to 9 and PHP 7.1 upward, works with multiple shops, and is translated into English, German, French, Spanish, Italian and Polish.
-
ReferenceMPRVARIABLES
-
In stock2147483647 Items
-
PrestaShop CompatibilityPS 1.6 – 9.x
-
Pricing ModelOne-time Purchase
-
Module TypeFront & Back-office
-
GDPR RelevantNo
-
Business GoalStreamline Operations
-
External Account NeededNo
-
Module ComplexityFeature-Rich Module
-
Customer Journey StageManage Store
-
Works With PlatformNo External Platform
What customers say about us
Company reviews
5.0
★
★
★
★
★
(4 reviews)
Loading customer reviews...
No product reviews yet
Be the first to share your experience with this module.
Write a Review
Content Variables gives a fact one definition and resolves it everywhere your shop shows it. You describe the number once, and every page that mentions it stays correct on its own.
Have a question about this product?
Our experts are here to help. Ask anything about installation, compatibility, or specifications.
1301
questions
9
categories
2013
building modules since
1.6–9
PrestaShop versions
v1.0.12026-08-08
- Fixedinstall seeding variables that described the mypresta.rocks catalogue rather than the shop installing the module
- Changedthe back-office example token to one that exists after a fresh install
- Updatedall six translations to match the new wording
Loading full changelog...
Works Well With Content Variables
Modules our team genuinely pairs with this one, and exactly why each belongs in the same setup.
Complement
Second Category Description gives a category a second block of text, usually further down the page, where you explain the range rather than repeat the heading. That is exactly the place a merchant writes a sentence with a number in it: how many styles the range holds, or what it starts at.
Content Variables keeps that number right. You describe the group once, by category, brand, price or a combination, and place its token in the category text. The sentence then follows the catalogue instead of the day it was written, in every language the description exists in.
Together the pairing is simple: one module gives you room to describe a range properly, the other makes sure the facts in that description stay true as the range changes. Neither depends on the other, and each is configured from its own screen.
Complement
Blog Revolution gives your shop articles, buying guides and seasonal posts. Those pieces age differently from the rest of the site: a guide written in spring still ranks in autumn, and the numbers inside it, a range size or a starting price, quietly stop being true.
Content Variables lets an article carry a fact by reference rather than by hand. Put a token where the figure belongs and the article updates itself as the catalogue moves, so an old post that still earns traffic is not also an old post that misinforms.
The two work at different layers. One publishes and organises the writing; the other keeps the facts inside the writing current, including across the languages an article is translated into, so nobody has to reread archived posts hunting for stale figures.
Complement
FAQ Manager is where a shop answers the questions it gets asked repeatedly. Those answers are full of figures: how long delivery takes, how many days a return window runs, how large the range is. They are written once and then trusted for a long time.
Content Variables gives each of those figures a single definition. Change the delivery time in one place and every answer that mentions it agrees, in each language, without anyone rereading the FAQ list to find the ones that still say the old number.
The pairing matters because a wrong answer in an FAQ costs more than a wrong number elsewhere: the customer went there specifically to check. One module organises and publishes the answers, the other keeps the facts inside them consistent.
Complement
Subtitles Manager adds a short supporting line under a product or category name, the place for a fact rather than a slogan. Short lines are where merchants most often put a figure, because there is no room for anything else.
Content Variables makes that figure maintainable. Define it once and reuse the same token across many subtitles, so one edit reaches every line that quotes it, in each language, instead of a search through the catalogue for the pages that mention it.
This pairing suits shops that repeat the same claim in many places. One module gives the claim somewhere prominent to sit, the other means repeating it does not multiply the work of keeping it true.
30 days return right
Easy return - no questions asked
Plug & Play Modules
Install, set up and take profit
Dedicated Support First
Priority Help & Satisfaction Over Sales
You might also like
