Prestashop: [BOOM-4221] BO: Multistore: category creation

[prestonBot]

This issue has been migrated from the Forge. Read the original ticket here.

• _Reporter:_ salma.moakhar
• _Created at:_ Thu, 2 Nov 2017 11:40:43 +0100

In a multistore scenario, If we created categories in the 2nd shops then we disable the multistore mode these categories of second shop appears in the category list of the shop by default (shop_1) with wrong positions

• How to reproduce the issue ?

Enable multistore.


Create two stores in the same group.


Create a category in the second store. (category_shop2)


Disable multistore


The category "category_shop2" appear in the list of the shop1's categories but we don't have access to edit it.

[prestonBot]

This comment has been migrated from the Forge. Read the original comment here.

• _Author:_ marion_francois
• _Created at:_ Fri, 22 Dec 2017 10:06:06 +0100

Je reproduis le problème, il n'est pas possible d'éditer ni de supprimer la catégorie.

 

[khouloudbelguith]

Hi,

1. Enable multistore.
2. Create two stores in the same group.
3. Create a category in the second store. (category_shop2)
4. Disable multistore
5. Click on the Edit button of the category_shop2

I have the same issue with PS1.7.5.2, but with PS1.7.6.0, an exception is displayed when we click on the "Edit" button.

With PS1.7.5.2 there is no exception.
PS1.7.6.0: https://drive.google.com/file/d/1Tah5mQAaKlwI1pIZmemKymnsw5UyaqHy/view
PS1.7.5.2: https://drive.google.com/file/d/1fo3A_AixGKrWbTgu-G1Rj-0I3zL4grVT/view

It is a regression.

Thanks!

[marionf]

@matks
It seems the issue was already there before but the exception was not displayed.
Maybe the exception is displayed now because of the migration.
So, not sure if it's a regression or not and if we should fix it in 1.7.6.1, wdyt ?

[eternoendless]

Currently when disabling multishop all categories are displayed, but you can't edit them
if they don't belong to the current (default) shop.

Specification is needed regarding what should happen when we disable multishop, and what should be done with shop-specific data in that case. Should it be re-bound to the default shop? Should it become inaccessible until multishop is activated again? Should it be deleted?

This issue cannot be fixed until we have clear answers for these questions.