Newbie question on SiteDesign

Author Message

Michael O C

Thursday 04 October 2007 8:07:37 am

Hi,

I've just installed eZPublish v 3.9.3 and am trying to override the eng and / or the ezwebin_site design.

I am trying to follow instructions on this tutorial: http://www.sitepoint.com/article/ez-publish-3-1-take-spin/3

Having created a new file site.ini.append in ezpublish/settings/siteaccess/mydesign/
with the following code:

#?ini charset="iso-8859-1"?
# eZ publish configuration override file.
#

[SiteAccessSettings]
RequireUserLogin=false

[DesignSettings]
SiteDesign=mydesign

I then try to browse to: http://www.newblastbeat.org.php4-4.websitetestlink.com/ezpublish/index.php/mydesign/
and expect to load the site with the old design but I get the following error:

Module not found

Can anyone help here and see what I might be doing wrong?

Many thanks,
Michael

Xavier Serna

Friday 05 October 2007 12:56:34 am

Welcome to the eZ community!

You are following a tutorial for v3.1, quite old, but using v3.9.3, and also just released the 3.10.0. I recommend you to read the docs that can be found here: http://ez.no/doc/ez_publish/technical_manual/3_10 as you have a concept mix between site designs and siteaccess.

Basically, ezwebin is an extension, that have a custom design. If you define a new siteaccess and want to use the design from ezwebin you have to activate the extension and define its design as the design for your siteaccess.

hth!

--
Xavier Serna
eZ Publish Certified Developer
Departament de Software
Microblau S.L. - http://www.microblau.net
+34 937 466 205

Michael O C

Friday 05 October 2007 2:40:31 am

Ok,

I'm actually really confused!

Can you tell me the step by step instructions to "get started" with a new custom design for the frontend.

I have it as follows but it's not working.

STEP 1:
Create new folder called 'mydesign' in /settings/siteaccess/

Step 2:
Create new folder called 'mydesign' in /design/

Step 3:
Somehow override an ini file to point to mydesign and fallback to standard design
if there is a problem.

Step 4:
Visit the new design at www.mysite.com/index.php/mydesign/

Now the problem I have is in Step 3.
How do I override the design to point to mydesign?
Do I create 'site.ini.append' in /settings/siteaccess/mydesign?
If so what should I put in there?

At the moment I have:

#?ini charset="iso-8859-1"?
# eZ publish configuration override file.
#

[SiteAccessSettings]
RequireUserLogin=false

[DesignSettings]
SiteDesign=mydesign
StandardDesign=standard

OR should I put this file in /settings/siteaccess/override?

Would love to hear some STEP by STEP instructions on this and not just a link to the documentation as I'm a newbie to this.. I'd LIKE to use eZpublish but I find the documentation terribly confusing..

Many thanks,
Michael

Michael O C

Friday 05 October 2007 2:40:50 am

PS: I'm now using version 3.10

Michael O C

Monday 08 October 2007 9:34:55 am

Anyone?!

Jeroen de Jong

Monday 08 October 2007 9:40:43 am

:-) i had the same startup trouble as you. The best way is to copy the default site design with all its setting files. I'll try to explain:

step 1: create a new folder in the design/
step 2: here you can make your own file structure of images / scripts and (override)templates
step 3: goto /settings/override/site.ini.append.php
step 4: add you new siteaccess name to the AvailableSiteAccessList[]=<yoursiteaccess>
side step 5: add:

[ContentSettings]
ViewCaching=disabled

This will make sure EZ is not caching your templates so your not wondering why nothing on the page gets updated

step 6: goto settings/siteaccess and make a new folder with the name of your site design. Copy all the files from the default sitedesign (plain_site?) to this folder.

step 7: edit site.ini.apend.php in the new siteaccess folder.
step 8: edit these parts:

[SiteAccessSettings]
RequireUserLogin=false
RelatedSiteAccessList[]=<name>

[DesignSettings]
SiteDesign=<name>
AdditionalSiteDesignList[]=<name>

Step 9: make sure the names make sense. In siteaccess "site1" you have sitedesign=site1 and additionalsitedesignlist=site2 and reversed in siteaccess "site2". This makes sure the correct override fallback system is used

This should work. I wrote it from the top of my head...please reply if still havonf trouble

Cheers,

Jeroen

Michael O C

Tuesday 09 October 2007 5:12:06 am

André R.

Tuesday 09 October 2007 5:18:50 am

you are still mixing siteaccess and design like pointed out above, design and siteaccess are two separate things.

A Siteaceess is kind of a 'site', or just a variation of another site with different language or design or some templates or all.

Corrected version of your walk through:

Step 3:
In /settings/override/site.ini.append.php added

AvailableSiteAccessList[]=mysite 

So entire block reads:

[SiteAccessSettings] 
CheckValidity=false 
AvailableSiteAccessList[] 
AvailableSiteAccessList[]=eng 
AvailableSiteAccessList[]=ezwebin_site 
AvailableSiteAccessList[]=ezwebin_site_admin 
AvailableSiteAccessList[]=mysite 
MatchOrder=uri 
HostMatchMapItems[] 

Step 6.
Created a new folder in /settings/siteaccess called 'mysite'
and copied all files from 'eng' folder in

Step 7.
Edited /settings/siteaccess/mysite/site.ini.append.php to read:

[SiteAccessSettings] 
RequireUserLogin=false 
RelatedSiteAccessList[] 
RelatedSiteAccessList[]=eng 
RelatedSiteAccessList[]=ezwebin_site 
RelatedSiteAccessList[]=ezwebin_site_admin 
RelatedSiteAccessList[]=mysite
ShowHiddenNodes=false 



and...

 
[DesignSettings] 
SiteDesign=mydesign
AdditionalSiteDesignList[] 
AdditionalSiteDesignList[]=ezwebin 
AdditionalSiteDesignList[]=base

This makes your design override the other designs

Step 8
If you want someone to have access to the new siteaccess you need to add user/login (mysite) to the users / groups you want grant access.
To test go to <root_url>/mysite/user/login and login as admin to verify if it is a setup or access problem.

Step 9
Clear all cache (minimum ini cache and template override cache)

While you are developing it might be useful to use these settings (change to own preference)
settigns/override/site.ini*:

[ContentSettings]
ViewCaching=disabled

[DebugSettings]
DebugOutput=enabled
ScriptDebugOutput=disabled
# enable this if you develop your own modules/view or need to debug whats going on
DebugRedirection=disabled
DebugToolbar=disabled

[TemplateSettings]
# the following will add xhtml comments to the source code to more easily
# trace what template is used where, but will cause ie to work in quirks mode
# breaking your site design in ie
Debug=disabled
ShowXHTMLCode=disabled
ShowUsedTemplates=disabled
# You will get more detailed and stricter template errors when this is turned on
# remember to test your site with this enabled before you go live and always 
# enable it on production sites
TemplateCompile=disabled
TemplateOptimization=enabled
# cache blocks:
TemplateCache=disabled
# makes the template system check if template needs to be re compiles
# and also affects a couple of other things
DevelopmentMode=enabled

For more documentation on different settings look in settings/*.ini or in the online documentation:
http://ez.no/doc/ez_publish/technical_manual/3_10/reference/configuration_files

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Jeroen de Jong

Tuesday 09 October 2007 6:34:18 am

Dont know if you have it working allready but if you get an access denied message: your site design is working but an anonymous user doesn't have acces. You have to make a new policy and add it to the anonymous usergroup

Andre pointed this out in step 8.

A step by step intruction of step 8:

1: log into the CMS
2: goto the user account tab
3: on the left click "roles and policies"
4: select the anonymous role
5: click edit
6: click new policy
7: select module "user" -> click 1 function
8: select "login" -> click limited access
9: choose your new siteaccess

Now you should see the new sitelayout without the access denied.

Cheers,

Jeroen

Michael O C

Tuesday 09 October 2007 8:40:37 am

Guys,

Thank you both for coming back to me.

I have tried Jeroen's solution first and unfortunately it is not yet working.
I am experiencing some odd behaviour after trying Jeroen's solution.

Here is what is going on:

1. I login as administrator @ http://127.0.0.1/index.php
2. I click 'User Accounts' -> 'Roles and Policies'
I can see the 5 standard Roles
3. I click 'Anonymous'
4. I can see the following policies

content  	 read  	 Section( Standard )
content 	pdf 	Section( Standard )
rss 	feed 	No limitations
user 	login 	SiteAccess( ezwebin_site )
user 	login 	SiteAccess( eng )
content 	read 	Class( Flash , Image , Quicktime , Windows media , Real video , Banner ) , Section( Media )

5. Notice no mention of the mydesign policy which was setup.
6. I click 'Edit'
7. NOW I can see the policy I just added, so I now can see:

content  	 read  	 Section( Standard )
content  	 pdf  	  Section( Standard )
rss  	           feed    No limitations
user  	          login   SiteAccess( ezwebin_site )
user  	          login   SiteAccess( eng )
content  	read  	Class( Flash , Image , Quicktime , Windows media , Real video , 
                              Banner ) , Section( Media )
 user  	         login    SiteAccess( mydesign )

So as you can see there is a descrepancy between the policies and the policy I just created following Jeroen's instructions is not assigned / assignable to the Anonymous User Group..

Anyone any ideas on how to make this work?

Will go over André R's post now, but wanted to troubleshoot in a standardised manner and not have it broken because of changes to setting files etc which would be harder to trace..

Many thanks
Michae 

Jeroen de Jong

Wednesday 10 October 2007 1:23:18 am

thats's very odd behaviour. You click the anonymous role and see the assigned policies (6) and the when you click edit you see 7 policies??? Hm sounds more like a bug to me.

Maybe andre can help?

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.