|
Akhilesh Singh
|
Friday 06 May 2011 11:20:05 pm
Hello There i need some suggestions from eZ experts.
I am going to develop a site which has iphone and ipad support also.
This is the first time i am going to work on such project so was concern in how should my eZ backend will be.
what is the best way of having eZ admin for such sites.
1. Should i have a separate admin for all 3 sites like.
plain_site_admin for main site.
iphone_admin for iphone site.
ipad_admin for ipad site.
as contents an navigation will be different for all 3 sites.
2. Or i should just use 1 main admin and have separate fields(attributes) in content class for different sites. Like:
bodymain for main site.
bodyiphone for iphone site.
bodyipad for ipad site
can any one suggest me the best one to go for or other ways of simply achieving this.
Thanks in advance.
Akhilesh
|
|
Quoc Huy Nguyen Dinh
|
Saturday 07 May 2011 3:30:14 pm
Hi there It depends. Is it three different websites? Or the same website but in different versions? I guess it's more the second case. So the best would be to have one single admin interface. But regarding the management of the different content there are several ways:
- as you said you can use different attributes, one for each version of the website.
- the best way, but not possible now until eZ Systems add the feature, would be to be able to create a channel for each version of the website.
- a workaround point 2, if you only have one language, is to create two custom languages but instead of being real languages you would name them 'ipad', 'iphone', they would all be clones of the language, the real language, you are using. Then when you create a new page you create it as 'eng-GB' (or the language you are using), and you can translate it to 'ipad' or 'iphone'. Then you create a siteaccess for each version and configure the INI files to assign each of them their own language between the three you selected.
- at the root of your content structure, create 3 folders: 'normal', 'ipad', 'iphone'. Each of them will be the root of their related website. Then you configure site.ini and content.ini to use their respective NodeID as IndexPage and RootNode
|
|
Akhilesh Singh
|
Wednesday 11 May 2011 1:50:29 am
Hello Friends thax for the replay and sorry for delayyyy.
Heath: I am using eZ 4.3 currently. should i switch to some other.?
This idea of creating iphone site as an different siteaccess taking an example of language site is prety good will implement it an check it.
thank you,
Akhi
|
