Module · LNK Pro Accounts
  • PrestaShop

Open your PrestaShop shop to professionals

LNK Pro Accounts separates the registration of individuals from that of professionals on your PrestaShop shop. A 100% business shop in one click: registration for individuals closes, and checkout and guest orders follow. The professional gives their company name, SIRET and intra-community VAT number; the module checks them, puts the customer in the right customer group according to their tax zone and, if you wish, waits for your approval before opening the account. Your prices can also stay reserved for pro accounts.

  • Version 2.1.4 · PrestaShop 1.7.6 to 8.x
  • Version 2.9.4 · PrestaShop 9
  • PrestaShop 1.7.7 to 9.x
  • PHP 7.1 to 8.4
  • No override

Key points

  • A 100% business shop in one click: registration for individuals closes, checkout and guest orders follow
  • Separate individual and professional registration, forms built field by field
  • SIRET checked (INSEE Sirene API, with your key)
  • VAT number checked while typing and verified by VIES
  • Automatic customer group by tax zone, pro groups created on request
  • Manual approval of pro accounts, with an email to the customer
  • Email reminders for missing SIRET and VAT numbers
  • Reserved catalogue: prices hidden from visitors, catalogue closed as an option
  • reCAPTCHA or Cloudflare Turnstile anti-bot, if enabled
  • Attachments outside the module folder, data kept on uninstall
  • 3.9 KB compressed at most, on the two registration pages; 1.6 KB on login, account and checkout; nothing elsewhere
  • French, English, Arabic from right to left, plus Spanish and German
  • PrestaShop 1.7.7 to 9.x, PHP 7.1 to 8.4, no override, multistore

Two registrations, two forms

The visitor chooses their path: “I am an individual” or “I am a business”, two buttons added under the login form, each one leading to its own page (/compte-particulier and /compte-professionnel). You can close registration for individuals, show a CMS presentation page before the pro registration and have professionals accept their own terms of sale.

Each form is built field by field: text, text area, switch, single or multiple choice list, radio buttons, checkboxes, file upload (a certificate of incorporation, for example), information message and date. Each field has its label in each language and can be required. The first address can be asked for at registration.

A 100% business shop in one click

Turn off the “Individual registration” setting: your shop is reserved for businesses.

  • The “I am an individual” button disappears from the login page.
  • The native registration page, the old authentication?create_account=1 address, account creation in checkout, guest checkout and the /compte-particulier page lead to the business registration, with this message: “This shop is reserved for businesses: create your business account to order.”
  • In checkout, the visitor only sees the login and the “Create a business account” button. On PrestaShop 1.7.7, the theme's form stays visible, but submitting it leads to the business registration.

Your existing customers sign in as before, recover a forgotten password and edit their account. Customers created in the back office are still possible, and PrestaShop's native “Guest checkout” setting stays as you left it. No override, from PrestaShop 1.7.7 to 9, shop by shop. One limit: a third-party module that creates customer accounts by itself (social login, express registration) gets around it.

SIRET and VAT number checked

  • SIRET: 14 digits and check key verified locally, then, if you turn it on, existence of the establishment checked with the INSEE Sirene API, with your own access key.
  • Intra-community VAT number: format checked while typing according to the country, then, if you turn it on, verified with VIES, the European Commission service.
  • A “Subject to VAT?” question can come before the field.

Each field can be shown or not, and can be required. A pro customer whose SIRET or VAT number is missing can be reminded by email: you set the gap between two reminders and their maximum number, then have the tokenised address shown in the back office called once a day (cron task at your host or native scheduled tasks module). A customer who completes their details leaves the queue.

The right customer group for the tax zone

Three zones, each set separately: your shop's country, the European Union, the rest of the world. For each one, you choose the pro customer's groups and default group; your shop's tax rules then apply the right regime. The module sets no rate.

Your shop has no pro groups yet? The module creates the three groups on request, and aligns their access rights (categories, carriers, payment and other modules) with those of the default customer group, without ever removing a right. Without this alignment, a customer placed in a new PrestaShop group finds an empty catalogue.

Your company accounts created before the module can be brought in in one click: they receive the groups of their zone on top of those they already have. A customer without an address, so without a known country, is never moved.

Manual approval of pro accounts

Turn on manual approval: a pro account is created inactive, the customer is told that their request is being reviewed, and you find the pending accounts in the back office. One click activates the account and the customer receives an email. You also choose the emails sent to the customer and to the merchant (account creation and update) and the employees notified.

Catalog reserved for businesses

  • “Catalog reserved for businesses”: prices are hidden from visitors, through the native “Show prices” setting of the Visitor and Guest groups. Instead of the price, the theme shows “Sign in to see prices”, with the links to log in and to open a pro account.
  • “Also hide the catalog from visitors”: categories and products are closed to visitors through native category access (home included, root excepted). They lead to the native “access denied” page (403), completed by the “Reserved for businesses” block.

Everything is put back as before when you turn these options off or uninstall the module.

Anti-bot, only if you turn it on

Google reCAPTCHA (v2 or v3, with an adjustable threshold) or Cloudflare Turnstile, with your own keys. The provider's script only loads on the module's two registration pages, and only when the protection is on.

Your customers' attachments kept safe

The files sent by your customers (certificates, supporting documents) are stored outside the module folder, in var/lnk_b2baccount/, which a module update does not touch. They are never served directly: only the back office opens them, for a logged-in employee. Under Apache, an .htaccess refuses all access. Nginx ignores .htaccess files: add the block given in the FAQ to your server configuration.

On uninstall, the fields, the values entered by your customers, their attachments and the reminders are kept by default. Deleting them is asked for in two steps, under “Advanced”.

Léger et rapide

Figures measured on the delivered module, gzip-compressed (level 9). The form script: 2.4 KB (2,378 bytes), loaded only on the module's two registration pages. The stylesheet: 1.6 KB (1,570 bytes), loaded only on the login and registration pages (and on the identity, addresses and order pages, where the pro fields are shown). Nothing on the home page, categories or product pages. The four renderings of the theme contract (instead of the price, reserved page, account status, registration link) add no stylesheet and no script of the module: the theme styles them.

A clear settings screen

A single settings page, in tabs, on the common skin of the LNK modules: at most twelve visible settings per screen, rare settings folded under “Advanced”. The form fields are translated in each language of the shop. The module page and the forms read from right to left in Arabic.

For themes and integrators

Theme contract lnk.b2b.account/1, designed for the LNK B2B theme and usable by any theme that calls its hooks:

  • displayLnkB2bPriceLogin instead of the price (product card, list view, product page);
  • displayLnkB2bRestricted in the “access denied” page;
  • displayLnkB2bStatus: “Business account active” or “legal information to complete”, nothing for a visitor, compatible with page caching;
  • {widget name='lnk_b2baccount' mode='link'}: the “Open a business account” link.

Without these hooks, PrestaShop keeps its native behaviour. Templates can be overridden in the theme.

Multistore

Forms, reminders and settings per shop; the module page always shows the scope of what you save. A new shop receives the forms, a deleted shop is cleaned up. The reserved catalogue settings are common to all shops, like PrestaShop's customer groups.

Compatibility with PrestaShop 1.7.7, 8 and 9

PrestaShop 1.7.7 → 9.x
PHP 7.1 → 8.4
Delivery Two packages: 2.9.N for PrestaShop 9, 2.1.N for 1.7.7 to 8.x
Contains an override No
Multistore Yes
External calls VIES (European Commission); INSEE Sirene API with your key; reCAPTCHA or Turnstile if enabled

Each version is verified by a real installation: PrestaShop 1.7.8 and 8.1 for the 2.1.N package, PrestaShop 9.0 for the 2.9.N package. The tests cover installation, display, the back office and uninstallation.

Frequently asked questions

How do my customers choose between an individual and a pro account?

Two buttons, “I am an individual” and “I am a business”, are added under the login form. Each one leads to its own registration page, with its own form. You can close registration for individuals if you only sell to professionals (next question).

How do I reserve my shop for professionals?

Turn off “Individual registration”, in General settings › General. What closes for a visitor: the “I am an individual” button, the native registration page, the old authentication?create_account=1 address, account creation in checkout, guest checkout and the /compte-particulier page. All of them lead to the business registration, with the message “This shop is reserved for businesses: create your business account to order.” In checkout, the visitor only sees the login and the “Create a business account” button (on PrestaShop 1.7.7, the theme's form stays visible, but submitting it leads to the business registration). On PrestaShop 9, one-page checkout (the ps_onepagecheckout module) follows the same rule: the visitor is sent to the login page and no guest is created.

What stays open: sign-in for your existing customers, forgotten password, the Identity page where the customer edits their account, and the customers you create in the back office. The native “Guest checkout” setting (Shop Parameters › Order Settings) stays saved as you set it, but no longer applies to visitors while the shop is reserved for businesses. The setting applies shop by shop in multistore. One limit: a third-party module that creates customer accounts by itself (social login, express registration) gets around it.

Which fields can I add to the forms?

Text, text area, switch, single or multiple choice list, radio buttons, checkboxes, file upload, information message and date. Each field has its label in each language of the shop and can be required. The values entered show on the customer's page in the back office.

To open accounts on proof (company register extract, trade card), drag the “Proof of business” model into the B2B form: a required file upload, labelled in each language. With manual activation, the document opens from the pending account's row, in Customers › Business customers.

How is the SIRET checked?

The format (14 digits and check key) is verified locally, with no external call. If you turn on the automatic check, the module also asks the INSEE Sirene API whether the establishment exists. This check uses your own API access key, entered in the SIRET tab.

How is the intra-community VAT number checked?

The format is checked while typing, according to the country. If you turn on the automatic check, the number is then verified with VIES, the European Commission service. It needs the PHP soap extension on the server: without it, the VIES check is skipped instead of blocking the registration.

Why does the VAT number need an address?

In PrestaShop, the VAT number belongs to the customer's address. If you ask for the VAT number at registration, also turn on “Address creation” in the Address tab: without an address, the number cannot be saved anywhere.

Does the module apply VAT itself?

No. It puts the pro customer in the groups of their tax zone (shop's country, European Union, outside the European Union). Your tax rules and your group prices then apply: you stay in control of your taxation.

What happens to my professional customers already registered?

The “Existing accounts” tab counts your company accounts and brings them in with one click: they receive the groups of their zone, on top of those they already have (discounts, negotiated prices). A customer without an address, so without a known country, is never moved.

How do I hide my prices from visitors?

Turn on “Catalog reserved for businesses”: the native “Show prices” setting is turned off for the Visitor and Guest groups, and the theme shows “Sign in to see prices”. With “Also hide the catalog from visitors”, categories and products are closed to them and lead to the “access denied” page. When you turn these options off, or on uninstall, everything is put back as before.

Does my theme need to be changed?

For registration, checks and groups, no. The “Sign in to see prices” text, the “Reserved for professionals” block and the pro account status show if the theme calls the hooks of the lnk.b2b.account/1 contract (the LNK B2B theme calls them). Without them, the price stays hidden and the “access denied” page stays PrestaShop's own.

Where are the files sent by my customers stored?

In var/lnk_b2baccount/ at the root of the shop, outside the module folder: an update does not erase them. They are never served directly; only a logged-in employee opens them from the back office. Under Apache, an .htaccess refuses all access. Nginx ignores .htaccess files: add this block to the site configuration. The Nginx configuration recommended by PrestaShop in its recent versions already denies /var/; this block makes sure of it.

location ^~ /var/lnk_b2baccount/ { deny all; return 403; }
What happens to the data on uninstall?

It is kept: the fields, the values entered by your customers, their attachments and the reminders. To delete everything, tick under “Advanced” “Also delete the data when uninstalling”, then “I confirm the permanent deletion”. The visitors' price and access settings are put back as before in every case.

Does the module make external calls?

Only the ones you turn on: VIES (European Commission) for the VAT number, the INSEE Sirene API with your key for the SIRET, and Google reCAPTCHA or Cloudflare Turnstile if the anti-bot protection is on. No other.

Does it work in multistore?

Yes. Forms, reminders and settings belong to each shop, and the module page always shows the scope of what you save. A new shop receives the forms, a deleted shop is cleaned up. The reserved catalogue is common to all shops, like PrestaShop's customer groups.

Does the module slow down my shop?

No. The 2.4 KB script (compressed) only loads on the module's two registration pages, the 1.6 KB stylesheet only on the login, registration, account and checkout pages. Nothing on the home page, categories or product pages.

In which languages does it ship?

In French, English and Arabic (right to left), plus Spanish and German. The labels of your fields are entered in each language of the shop.

How do I present the benefits of a pro account?

In General settings › Business benefits: a title and a list, one benefit per line, in each language. Left empty, the module suggests its own and only announces what your active LNK modules allow. An LNK theme shows them on the home page (with “Open a business account” and “I already have an account”), the sign-in page and the business-only page, to visitors and customers without a pro account.

Release history

10 versions released for PrestaShop

  1. Version 2.9.4 PrestaShop 9 Security fix

    Security

    • Account activation in multistore: an employee can no longer activate or deactivate a customer of a shop they have no access to, or outside the selected shop or shop group. An employee of all shops keeps access to every customer in the "All shops" context.
    • Manual reminder in multistore: likewise, an employee can no longer send the reminder email to a customer outside their shops or the selected context.

    Fixes

    • Module page titles in each language: the "Create an individual account", "Create a business account" and "Business account" pages took the French, or English, title in every language. They now have their title in French, English, Arabic, Spanish and German (English for any other language), like the "Business customers" entry of the back-office menu. On update, titles still in English or copied from another language take the one of their language; a title changed in the shop is kept, and page addresses do not change.
    • Language added after installation: these pages receive their title and address in the new language, instead of the copy of the default language. A text entered in the shop is never replaced.
    • Developer mode: form field attributes are no longer shown as text above the fields.
    • Terms and conditions checkbox: the registration forms showed "I have read and accept I agree to the terms and conditions of sale.". The sentence now reads "I have read and accept the terms and conditions of sale", in every language.
    • Back-office labels: the automatic group assignment settings, the custom fields of the forms, the anti-bot score thresholds and the business customer list are written without em dashes (colon, brackets or comma instead, "-" in an empty cell).
    • Reserved catalogue help texts: "Sign in to see prices" and "Reserved for businesses" only show when the theme places the displayLnkB2bPriceLogin and displayLnkB2bRestricted hooks. Without them, the price is simply hidden and the visitor lands on PrestaShop's native access-denied page; the help texts now say so.
    • Documentation: README and COMPATIBILITY give the PrestaShop versions of this package (9.0 to 9.x), the twin package 2.1.4, the PHP versions tested on the bench, the exact names of the "I am an individual" and "I am a business" buttons and the five translation languages.
  2. Version 2.9.3 PrestaShop 9

    New

    • Business account benefits (General settings › Business benefits): a title and a list, one benefit per line, in each language, which the theme shows on the home page (with “Open a business account” and “I already have an account”), the sign-in page and the business-only page, to visitors and customers without a pro account. Left empty, the module suggests its own and only announces what your active LNK modules allow. Hook displayLnkB2bBenefits (or widget mode='benefits'), see docs/THEME-CONTRACT.md §11.
    • Proof of business: a model in the form palette (required file upload, labelled in each language), and a “Proof of business” column in the list of pending accounts, to open the document before activating the account.

    Fixes

    • In English, the “Contact us” button of the business-only page read “Already a customer? Sign in.”.
  3. Version 2.9.2 PrestaShop 9

    Behaviour change: if “Individual registration” was turned off, PrestaShop's native registration, account creation in checkout and guest checkout now close too and lead to the business registration.

    New

    • A 100% business shop in one click: with “Individual registration” turned off, the native registration page, the old authentication?create_account=1 address, a direct submission of the account creation form, account creation in checkout and guest checkout lead to the business registration, with the message “This shop is reserved for businesses: create your business account to order.” In checkout (PrestaShop 1.7.8 and later), the visitor only sees the login and the “Create a business account” button; a signed-in customer keeps their theme's step. On 1.7.7, the theme's form stays visible and its submission is redirected. No override, set per shop. Sign-in, forgotten password, the Identity page and customers created in the back office do not change.
    • PrestaShop 9 one-page checkout (ps_onepagecheckout) covered too: the visitor is sent to the login page and no guest is created; any account creation outside the business form is also refused through actionSubmitAccountBefore.

    Fixes

    • Module's “Guest checkout” setting removed: it had no effect. PrestaShop's native setting (Shop Parameters › Order Settings › Guest checkout) does the job; the old value is deleted on upgrade.
    • Closed individual form: /compte-particulier leads to the business registration, with the same explanation, instead of a page not found.
    • Uninstalling no longer resets PrestaShop's guest checkout to its value from before the installation: the module never touches it, so a setting changed in the meantime stays as you chose it.
Show the 7 previous versions
  1. Version 2.9.1 PrestaShop 9

    New

    • Emails in Arabic, right to left: the module's six emails (account created, account pending, reminder, account approved, and the two merchant notices), in HTML and plain text.

    Fixes

    • Customer emails in the customer's language, subject included, even when sent from the back office (account approval, SIRET and VAT reminders): the employee's language no longer leaks in, and the list of missing details follows too. The merchant notice keeps the shop's language.
    • Stated weight in the listing and FAQ, measured on the delivered package (gzip level 9): 3.9 KB in all, stylesheet 1.6 KB (1,551 bytes), script 2.4 KB (2,378 bytes).
  2. Version 2.9.0 PrestaShop 9 Security fix

    First version from the LNKBOOT factory, taken over from the original module. Branch 9: PrestaShop 9.0 to 9.x only. PrestaShop 1.7.7 to 8.x use the prestashop/legacy branch (2.1.0).

    Security

    • Security probes replayed for each version on the module's public entry points: Ajax actions, reminder address without a token or with a wrong token, registration forms, pro presentation page, direct access to attachments.

    New

    • Catalog reserved for businesses: prices hidden from visitors through the native setting of the Visitor and Guest groups, “Sign in to see prices” instead of the price; option “Also hide the catalog from visitors” through native category access (home included, root excepted), native “access denied” page completed by the “Reserved for businesses” block; everything put back as before when turned off and on uninstall.
    • Theme contract lnk.b2b.account/1: hooks displayLnkB2bPriceLogin, displayLnkB2bRestricted, displayLnkB2bStatus (“Business account active” or “legal information to complete”, nothing for a visitor) and link {widget name='lnk_b2baccount' mode='link'}, with no stylesheet or script of the module.
    • Multistore: forms, reminders and settings per shop, scope shown, forms copied into a new shop, rows of a deleted shop erased.
    • Arabic, from right to left, in the back office and on the forms.
    • Option “Also delete the data when uninstalling”, in two steps, under “Advanced”.

    Changes

    • Customers' attachments stored outside the module folder, in var/lnk_b2baccount/, never served directly; those of previous versions are moved there on update.
    • Data kept on uninstall by default (fields, values entered, attachments, reminders).
    • New back office on the common skin of the LNK modules: at most twelve visible settings per screen, rare settings under “Advanced”.
    • Front on the common design of the LNK modules: registration, business fields of the identity page, account type choice and business invitation in checkout use lnk-b2baccount__… classes, theme colors through the --lnk-* variables, neutral values otherwise (no imposed color).
    • Translations completed: 89 strings of the code and 18 of the front office that were translated nowhere; labels of the fields created on install and names of the pro groups written in the language of each row.
  3. Version 2.1.4 PrestaShop 1.7.6 to 8.x Security fix

    Security

    • Account activation in multistore: an employee can no longer activate or deactivate a customer of a shop they have no access to, or outside the selected shop or shop group. An employee of all shops keeps access to every customer in the "All shops" context.
    • Manual reminder in multistore: likewise, an employee can no longer send the reminder email to a customer outside their shops or the selected context.

    Fixes

    • Module page titles in each language: the "Create an individual account", "Create a business account" and "Business account" pages took the French, or English, title in every language. They now have their title in French, English, Arabic, Spanish and German (English for any other language), like the "Business customers" entry of the back-office menu. On update, titles still in English or copied from another language take the one of their language; a title changed in the shop is kept, and page addresses do not change.
    • Language added after installation: these pages receive their title and address in the new language, instead of the copy of the default language. A text entered in the shop is never replaced.
    • Developer mode: form field attributes are no longer shown as text above the fields.
    • Terms and conditions checkbox: the registration forms showed "I have read and accept I agree to the terms and conditions of sale.". The sentence now reads "I have read and accept the terms and conditions of sale", in every language.
    • Back-office labels: the automatic group assignment settings, the custom fields of the forms, the anti-bot score thresholds and the business customer list are written without em dashes (colon, brackets or comma instead, "-" in an empty cell).
    • Reserved catalogue help texts: "Sign in to see prices" and "Reserved for businesses" only show when the theme places the displayLnkB2bPriceLogin and displayLnkB2bRestricted hooks. Without them, the price is simply hidden and the visitor lands on PrestaShop's native access-denied page; the help texts now say so.
    • Documentation: README and COMPATIBILITY give the PrestaShop versions of this package (1.7.7 to 8.x), the twin package 2.9.4, the PHP versions tested on the bench, the exact names of the "I am an individual" and "I am a business" buttons and the five translation languages.
  4. Version 2.1.3 PrestaShop 1.7.6 to 8.x

    New

    • Business account benefits (General settings › Business benefits): a title and a list, one benefit per line, in each language, which the theme shows on the home page (with “Open a business account” and “I already have an account”), the sign-in page and the business-only page, to visitors and customers without a pro account. Left empty, the module suggests its own and only announces what your active LNK modules allow. Hook displayLnkB2bBenefits (or widget mode='benefits'), see docs/THEME-CONTRACT.md §11.
    • Proof of business: a model in the form palette (required file upload, labelled in each language), and a “Proof of business” column in the list of pending accounts, to open the document before activating the account.

    Fixes

    • In English, the “Contact us” button of the business-only page read “Already a customer? Sign in.”.
  5. Version 2.1.2 PrestaShop 1.7.6 to 8.x

    Behaviour change: if “Individual registration” was turned off, PrestaShop's native registration, account creation in checkout and guest checkout now close too and lead to the business registration.

    New

    • A 100% business shop in one click: with “Individual registration” turned off, the native registration page, the old authentication?create_account=1 address, a direct submission of the account creation form, account creation in checkout and guest checkout lead to the business registration, with the message “This shop is reserved for businesses: create your business account to order.” In checkout (PrestaShop 1.7.8 and later), the visitor only sees the login and the “Create a business account” button; a signed-in customer keeps their theme's step. On 1.7.7, the theme's form stays visible and its submission is redirected. No override, set per shop. Sign-in, forgotten password, the Identity page and customers created in the back office do not change.
    • Guest checkout turned off for visitors, for the duration of the request and without changing the saved setting: a checkout module relying on PrestaShop's guest checkout no longer creates a guest; any account creation outside the business form is also refused through actionSubmitAccountBefore.

    Fixes

    • Module's “Guest checkout” setting removed: it had no effect. PrestaShop's native setting (Shop Parameters › Order Settings › Guest checkout) does the job; the old value is deleted on upgrade.
    • Closed individual form: /compte-particulier leads to the business registration, with the same explanation, instead of a page not found.
    • Uninstalling no longer resets PrestaShop's guest checkout to its value from before the installation: the module never touches it, so a setting changed in the meantime stays as you chose it.
  6. Version 2.1.1 PrestaShop 1.7.6 to 8.x

    New

    • Emails in Arabic, right to left: the module's six emails (account created, account pending, reminder, account approved, and the two merchant notices), in HTML and plain text.

    Fixes

    • Customer emails in the customer's language, subject included, even when sent from the back office (account approval, SIRET and VAT reminders): the employee's language no longer leaks in, and the list of missing details follows too. The merchant notice keeps the shop's language.
    • Stated weight in the listing and FAQ, measured on the delivered package (gzip level 9): 3.9 KB in all, stylesheet 1.6 KB (1,551 bytes), script 2.4 KB (2,378 bytes).
  7. Version 2.1.0 PrestaShop 1.7.6 to 8.x Security fix

    First version from the LNKBOOT factory, taken over from the original module. Branch 1: PrestaShop 1.7.7 to 8.x. PrestaShop 9 has its own package (2.9.0), with the same business code.

    Security

    • Security probes replayed for each version on the module's public entry points: Ajax actions, reminder address without a token or with a wrong token, registration forms, pro presentation page, direct access to attachments.

    New

    • Catalog reserved for businesses: prices hidden from visitors through the native setting of the Visitor and Guest groups, “Sign in to see prices” instead of the price; option “Also hide the catalog from visitors” through native category access (home included, root excepted), native “access denied” page completed by the “Reserved for businesses” block; everything put back as before when turned off and on uninstall.
    • Theme contract lnk.b2b.account/1: hooks displayLnkB2bPriceLogin, displayLnkB2bRestricted, displayLnkB2bStatus (“Business account active” or “legal information to complete”, nothing for a visitor) and link {widget name='lnk_b2baccount' mode='link'}, with no stylesheet or script of the module.
    • Multistore: forms, reminders and settings per shop, scope shown, forms copied into a new shop, rows of a deleted shop erased.
    • Arabic, from right to left, in the back office and on the forms.
    • Option “Also delete the data when uninstalling”, in two steps, under “Advanced”.

    Changes

    • Customers' attachments stored outside the module folder, in var/lnk_b2baccount/, never served directly; those of previous versions are moved there on update.
    • Data kept on uninstall by default (fields, values entered, attachments, reminders).
    • New back office on the common skin of the LNK modules: at most twelve visible settings per screen, rare settings under “Advanced”.
    • Front on the common design of the LNK modules: registration, business fields of the identity page, account type choice and business invitation in checkout use lnk-b2baccount__… classes, theme colors through the --lnk-* variables, neutral values otherwise (no imposed color).
    • Translations completed: 89 strings of the code and 18 of the front office that were translated nowhere; labels of the fields created on install and names of the pro groups written in the language of each row.
    • Translations through PrestaShop's historic system, the only one 1.7.7 reads (files translations/fr.php, en.php, ar.php, es.php and de.php).

Your cart

Your cart is empty.