Multistore - modules enabled and hooked only on default store

[gabriiel]

I have installed the PS 1.6.1.0, upgraded it to 1.6.1.1 and set up completely for multistore (multidomain, each domain is with different currency and language settings).

 

The PS looks just fine on the test domain, which is in the default group store. But I have another group with my multistore domain configuration and when I enter e.g. german or english domain, the PS is completely screwed up. Majority of modules is missing, hooks are not enabled etc.

 

I thought when I'm in context "all shops" and make changes in this context, it will propagate the changes to "all shops" as the context says.

 

Seems like not.

 

Any help will be very appreciated.

 

[gabriiel]

I have fixed the hooks by adding the respective parameters into the db table. I can see the hooks in my back office now. But in front office the web pages are still without any change.

 

Probably some modules need to be enabled for the multistore as well.

 

I just wonder the multistore option is not well developed yet. At least the basics.

[gabriiel]

I am going to open a bug against that because it is clearly visible the modules are enabled/disabled/configured without any respect to context.

 

I have just discovered that by luck. I have enabled home text editor few days ago and then disabled it. It is disabled in the all shops context, in default shop context as well. But it is still enabled in the mulstistore group and each respective store. So it has ignored the all shops context when being disabled.

[gabriiel]

And some modules are even active and configured for all shops, groups, sites etc. but still are not visible in the front office. I don't get it...

[gabriiel]

Fixed by manually editing the db entries in respective db tables.

[joseantgv]

I had same problem but in table ps_module_shop.