Message-ID: <1923997931.379272.1711712529239.JavaMail.root@confluence-doc2-production> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_379271_694267802.1711712529234" ------=_Part_379271_694267802.1711712529234 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 the multistore mode, some of the PrestaShop administration pages feat= ure a prominent drop-down menu, titled "Multistore configuration for". This= menu gives you the context of what you are doing: it enables you to set th= e shop or shop group to which the changes you are making are applied.

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

When editing a product, PrestaShop di= splays notifications to help you understand the scope of your changes. For = instance, when editing a product while in the "Shop A" context, the notific= ation will say "Warning, if you change the value of fields with an orange b= ullet, the value will be changed for all other shops for this product", wit= h said orange bullet appearing on all the implicated fields, such as "Type = of product", "Reference", the package'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, = or some, of the categories in the new store to be exact duplicates of = the categories 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 c= ategory's content once and for all from one place, including its products.<= /p>

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 groups for each store, you must c= reate a new group and use the "Multisto= re configuration for" selector to associate the group with the = current store 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. Do NOT drop it. If you do want to drop it, make sure y= ou recreate the table afterward.
  • Go back to the multistore settings for the shop group.
  • Enable the "Share customers" option.
  • Import the table.

Sharing customers between the shop group have now been enabled without t= he 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. Do NOT drop it. If you do want to drop it, make sure y= ou recreate the table afterward.
  • Go back to the multistore settings for the shop group.
  • Enable the "Share orders" option.
  • Import the table.

Sharing orders between the shop group have now been enabled without the = loss of order information.

Using a different theme for each shop/shop group

Once a theme is installed on your PrestaShop, you can use the "Theme &am= p; Logo" page in the "Design" menu to change the theme of the current store= , or of the current store group, depending on how the "Multistore configura= tion 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:

Managing = pages in multistore mode

When viewing the list of the content pages in the "All shops" context, a= ll the pages from all shops are displayed. Likewise, when in a shop group c= ontext, 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 creat= ion page, a section appears with a list, indicating which ones will be impa= cted.

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 with all shop, some shop groups, or selected shops.=

------=_Part_379271_694267802.1711712529234--