tags:

views:

124

answers:

3

Could anybody point me towards a good technical explanation of Magento's Store Views/Websites system on a programming level?

I am considering a customization of the system, but am not yet sure which one of these levels to use.

+1  A: 

Not meant to be rude, but your best bet about Magento related questions is their website. Try the Resource Section, the Wiki, the Community Forum, etc.

Gordon
How's that rude? :O Sounds like a friendly advise to me :) (This comment aint meant to be rude btw ;))
cwap
@cwap just saying it because someone might get it as "go away, we wont help you here".
Gordon
Yup, you probably have a point: SO does not seem to be the meeting point for a huge lot of Magento experts (yet). Too bad - I have a number of questions I'd be ready to give away huge bounties for. I'll try finding info on their site!
Pekka
silvo
+2  A: 

First thing to read is the Magento Designer's guide : http://www.magentocommerce.com/design_guide

Yep, "Designer" rather than "Developper" :) But this is a great background to undestand how things do articulate. And, let's be honest... in Magento, "Designer" is really the same as "Developper" and sometime as "System engineer". One can't be a good Magento Designer if not a Developper (imo).

Now, the SO community of Magento is still shy because there are not loads of Magento experts yet I guess. Being not humble enough, I may think that, as a brand new SOer, I found I could help in a few areas. So feel free to ask and I'm sure when someone knows, someone answers. At last, please keep in mind that Magento is so powerful and featured that one can be expert in design integration but not in sales workflow management nor in back-office use for instance. Expertise may be very segmented.

Have fun !

vrnet
Problem is, since the design_guide was written, apparently many a file has been moved in the structure and more often then not the file described in the guide will not be where it is supposed to be. Frustrated me to no end. Gets even worse when you buy books about magento that start with "When designing a new shop you should start with Extension XYZ", which, of course, is not available for 1.4 and will bring it crashing down if you try to install it anyway.My first and foremost suggestion: BACKUP, BACKUP, BACKUP! Before installing each extension, after each mayor edit - make a backup!
Sorcy
+2  A: 

There's no canonical resource on this. The best way to think about these views are with the concept of scope. Certain data in Magento is returned differently depending on which level (website, store, etc. you're on)

I'd start by getting a good understanding of the Layout system. Basically, layouts are abstracted out into a tree of "Block" objects. Most of these Blocks objects render a specific phtml template file.

The phtml template files are considered the store's theme. You can point to a different group of templates depending on which store, store view or website is currently selected.

Step Two would be to get familiar with the configuration system. Magento takes certain actions based on the values set here, and the values can be set on a global, website, or store level. The obvious example here is locale.

Finally, Magento's EAV model system allows even the models to have have values scoped at the global, website, or store level.

Alan Storm