A few questions, can you _____ with ez publish?

Author Message

William Gourlie

Thursday 06 May 2004 8:24:39 am

I have a few pretty simple, "can you do this..." type questions. Here goes...

Can you...

1. Create a site that is viewable to the public but allows for a member login to view special portions of the site? I read through the tutorial and something like this was not mentioned.
If so...

2. Instead of using the admin interface to approve such things such as a guestbook entry, could this be done by priveledged users logged into the site?

3. Run multiple sites off the same codebase? I heard a mention of being able to do this, but found no documentation on it.

That is all I have for now.

Thanks,

Brian

Tore Skobba

Thursday 06 May 2004 10:48:36 am

Hi

1: Yes, you can either use sections to dividede your site or other methods (subree three only available to some users for example). I have made a site with 6 different user groups with different access, not very difficult.

2: I do not know.

3: Yes that is be possible, and not to difficult. But little documentation on how to do it, you would have to play around with the system to learn how to do it.

EZ is very flexible cms. However, everything is not so very well documented meaning that lots of advanced stuff is possible in a theoretical sense. However, in pratical senses it can be difficult.

Cheers
Tore

Mark Marsiglio

Thursday 06 May 2004 1:36:40 pm

In regards to question 2, is it the admin interface that is a problem or is it the potential to work on other parts of the site than the guestbook? If you don't mind the admin interface, you can allow users only the ability to edit/publish certain content types (such as a guestbook entry) within the admin interface. They could see the rest of the content the same as if they were on the user site, just with the admin templates. You can disable the access to any setup functions, to adding content, or to seeing user accounts.

Also, I think that you can override the admin interface to make it look any way you want (i.e. like your user site), but I am not sure if you would want to try that, as it seems like it would be a lot of work.

In regards to question 3, you can use the same design folder for many sites without any trouble. Each site would be listed in the site.ini.append.php and each would have its own settings folder. However, the site.ini.append for each site would list the design as being the same. You would have to duplicate the override settings for each of the sites so that they would use the same templates.

Mark

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

William Gourlie

Friday 07 May 2004 8:33:56 am

Thanks for the replies!

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

eZ debug

Timing: Jan 18 2025 19:19:10
Script start
Timing: Jan 18 2025 19:19:10
Module start 'layout'
Timing: Jan 18 2025 19:19:10
Module start 'content'
Timing: Jan 18 2025 19:19:10
Module end 'content'
Timing: Jan 18 2025 19:19:10
Script end

Main resources:

Total runtime0.0176 sec
Peak memory usage4,096.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0055 589.1719152.6406
Module start 'layout' 0.00550.0029 741.812539.4766
Module start 'content' 0.00840.0068 781.289193.3359
Module end 'content' 0.01520.0023 874.625034.3047
Script end 0.0175  908.9297 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002715.3634140.0002
Check MTime0.00126.8185140.0001
Mysql Total
Database connection0.00063.520610.0006
Mysqli_queries0.002815.814430.0009
Looping result0.00000.107310.0000
Template Total0.001911.010.0019
Template load0.00116.260310.0011
Template processing0.00084.665710.0008
Override
Cache load0.00084.808310.0008
General
dbfile0.00148.167380.0002
String conversion0.00000.188840.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs