Message-ID: <358536671.378408.1711662456613.JavaMail.root@confluence-doc2-production> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_378407_1868443291.1711662456609" ------=_Part_378407_1868443291.1711662456609 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Sample Usages and Specifics

Sample Usages and Specifics

Sample= Usages and Specifics

=20 =20

Managi= ng a catalog in multistore mode

In multistore mode, some of the PrestaShop administration pages feature = a prominent drop-down menu, titled "Multistore configuration for". This men= u gives you the context of what you are doing: it enables you to set the sh= op or shop group to which the changes you are making are to be applied.

For instance, when creating a new product, the selection in this menu wi= ll determine whether the product will be available for all shop, only one s= hop group, or a single shop.

When editing a product, PrestaShop displays notifications to help you un= derstand the scope of your changes. For instance, when editing a product wh= ile in the "Shop A" context, the notification will say "Warning, if you cha= nge the value of fields with an orange bullet, the value will be changed fo= r all other shops for this product", with said orange bullet appearing on a= ll the implicated fields, such as "Type of product", "Reference", the packa= ge's size, etc.

Likewise, if you change a product while in the "All shops" context or in= the context of a shop group, some fields will be disabled: since they have= a global impact, you cannot edit them. If you really need to edit this con= tent, each field has a box that you can check to edit that field in all the= shops under this context.

If you edit a disabled field, the product is created in all the shops of= the context which do not already have it in their own catalog. Make sure t= o double check your context.

Data exchange= between stores

Duplicatin= g data between stores

Duplicated data in PrestaShop are set during the setup of any individual= shop, by importing all or some of the content from an existing shop into t= he new one. The content that can be imported is varied: products, categorie= s, employees, modules, cart rules, suppliers, etc. Data importation is done= once and for all: once a store has been created, you cannot easily import = data again from another store.

= Sharing data between stores and store groups

Stores can share data. Shared data are fundamentally handled at the stor= e group level: one of the important things to understand when dealing with = PrestaShop's multistore mode is that all the stores within a store group ca= n share the same details share data =E2=80=93 or more precisely, three type= s of content: customers, available quantities, and orders. Once the store g= roup is set, the sharing of data between its stores is mostly finished: whi= le you can change the setting for the available product quantities, you can= not change the customers and orders settings anymore as soon as any store w= ithin the group as at least one customer or one order.

Sharing pr= oducts and categories

When you create a new store within a group, you can choose to have all o= r some of the categories in the new store be exact duplicates of the catego= ries in any other store on your installation of PrestaShop.

When creating a category, either for a specific store or for all the sto= res in the PrestaShop installation, PrestaShop registers the category for a= ll the stores =E2=80=93 it is simply hidden from any store where it has not= been set.

By associating the new stores with a given category, any change in this = category will impact all the stores which are associated with it, even if t= he stores are from different store groups. You can therefore change the cat= egory's content once and for all from one place, including its products.

Shari= ng customers and customer groups

As indicated above, stores within the same store group can share clients= : all you have to do it set the proper option when creating the store group= .

Groups are less detailed: if you change one of the default customer grou= p in one store, the change is applied to all the other stores, regardless o= f the store group.

If you want to have different customer group for each store, you must cr= eate a new group and use the "Multistore con= figuration for" selector to associate the group with the current sto= re or store group.

If the option "Share customers" has been disabled, then your customer li= st will need to be empty before you can enable this.

If you'd rather keep your customer list you can do the following:

  • Go to your database management software such as phpMyAdmin.
  • Search for the table ps_customer. It might be different, d= epending on your database prefix.
  • Export this table.
  • Empty the table. Dot NOT drop it. If you do want to drop it, make sure = you recreate the table afterwards.
  • Go back to the multistore settings for the shop group.
  • Enable the "Share customers" option.
  • Import the table.

Sharing customers between the shop group has now been enabled without th= e loss of customer information.

Sharing orders

It is possible for stores within the same store group to share orders: a= ll you have to do it set the proper option when creating the store group.

If the option "Share orders" has been disabled, then your order list wil= l need to be empty before you can enable this.

If you'd rather keep your orders you can do the following:

  • Go to your database management software such as phpMyAdmin.
  • Search for the table ps_order. It might be different, depe= nding on your database prefix.
  • Export this table.
  • Empty the table. Dot NOT drop it. If you do want to drop it, make sure = you recreate the table afterwards.
  • Go back to the multistore settings for the shop group.
  • Enable the "Share orders" option.
  • Import the table.

Sharing orders between the shop group has now been enabled without the l= oss of order information.

Using a different theme for each shop/shop group

To install a theme on PrestaShop, you must use the "Theme Import/Export"= module to import the theme's zip file. Once that file is uploaded, the mod= ule will ask you some module-specific questions. When in multistore mode, i= t will also ask you whether you want to enable this theme with all stores i= n your PrestaShop installation, only some store groups, or only some specif= ic stores =E2=80=93 with the current stores being already selected. Th= e theme will still be available for the non-selected stores, but will be di= sabled.

This setting can be changed: once a theme is installed on your PrestaSho= p, you can use the "Themes" page in the "Preference" menu to change the the= me of the current store, or of the current store group, depending on how th= e "Multistore configuration for" selector is set.

Using specific settings for each shop/shop group

"Multistore configuration for" selector is the go-to option when you wan= t your changes to have an impact on a given store or set of stores. It shou= ld even be the first option to look at when an administration screen opens = up, as PrestaShop will change the available options depending on the contex= t you are in: store, store group or all stores.

This makes it possible for you to:

Managi= ng CMS pages in multistore mode

When viewing the list of CMS pages in the "All shops" context, all the C= MS pages from all shops are displayed. Likewise, when in a shop group conte= xt, the pages for all the shops in that group are displayed.

When creating a page in a shop group context, all the shops in this grou= p will display this page, yet the page will be unique: editing it in one sh= op will apply the changes in all the shops from this group.
On the crea= tion page, a section appears with a list, indicating which ones will be imp= acted.

Manag= ing discounts in multistore mode

When creating cart rules or catalog price rules in a multistore context,= an additional condition is available, with which you can choose the shops = on which the rule should be available.

Web-service an= d multistore

Access to the web-service is also highly configurable, both at the shop = level and at the shop group level. When creating a web-service key, you can= choose to associate it to all shop, some shop groups, or select shops.

------=_Part_378407_1868443291.1711662456609--