admin, plain, plain_admin?

«

Previous topic

|

|

Next topic

»

Author	Message
Cliff Cottell	Tuesday 05 December 2006 9:16:37 am Hi, I'm doing some work for a client who uses ezPublish. I've never used it before and am finding it quite confusing! One thing in particular I'm confused about is the difference between admin, plain, plain_admin. The url for the login page I was given ends in "...index.php/plain_admin" - am I going to have full access to the CMS features so I can carry out my work? or should I be logging in as a full admin. Please help!! Thanks, Cliff.
Claudia Kosny	Tuesday 05 December 2006 10:15:05 am Hi Cliff This sounds like your customer has used the plain package. That means the public site is under the url .../index.php/plain and the admin site is under .../index.php/plain_admin. I am actually not sure what the .../index.php/admin url is for, as it is usually not used. I assume that this is just a remainder of the installation, but as I am not sure whether it safe to remove, better just ignore it. By the way - depending on what login the user gave you you still might not have full access rights. If you log in as 'admin' you have them for sure as this is the default admin name. But if you log in as someone else, it depends on the permission the admin gave to your login. Claudia
David Boman	Wednesday 06 December 2006 6:16:38 am Hi all, Maybe eZ-crew can give us some clarification here? I have the same questions and would like to know what you can remove and what you should keep. As eZ is using the override paradigm quite a lot I sometimes find it hard to know which directories are safe to delete and which must be left alone. (I didn't ask this myself as I wasn't sure if I had missed some basic stuff or not... But as Claudia doesn't know either it feels safe to ask :) ) Cheers,
Cliff Cottell	Wednesday 06 December 2006 9:11:51 am Thanks for the reply Claudia, I'll get on to them and find out if I have full admin rights. Cliff.
Jeroen Sangers	Thursday 07 December 2006 4:06:03 am I deleted the /settings/siteaccess/admin directory without any problems, but after upgrading eZ Publish this folder had been recreated. I decided not to bother anymore...

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 30 2025 22:27:16
Script start
Timing:	Jan 30 2025 22:27:16
Module start 'layout'
Timing:	Jan 30 2025 22:27:16
Module start 'content'
Timing:	Jan 30 2025 22:27:16
Module end 'content'
Timing:	Jan 30 2025 22:27:16
Script end

Main resources:

Total runtime	0.0257 sec
Peak memory usage	6,144.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	588.1016	151.1953
Module start 'layout'	0.0057	0.0038	739.2969	220.6563
Module start 'content'	0.0096	0.0144	959.9531	1,001.7578
Module end 'content'	0.0240	0.0016	1,961.7109	33.9922
Script end	0.0256		1,995.7031

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	11.5201	14	0.0002
Check MTime	0.0011	4.4137	14	0.0001
Mysql Total
Database connection	0.0009	3.5880	1	0.0009
Mysqli_queries	0.0023	8.9872	3	0.0008
Looping result	0.0000	0.0427	1	0.0000
Template Total	0.0011	4.4	1	0.0011
Template load	0.0009	3.3233	1	0.0009
Template processing	0.0003	1.0951	1	0.0003
Override
Cache load	0.0006	2.3415	1	0.0006
General
dbfile	0.0017	6.4664	8	0.0002
String conversion	0.0000	0.0390	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs