Hide object as Administrator, unable to unhide!

Author Message

Marc Boon

Thursday 19 January 2006 12:12:17 pm

Still trying out eZ Publish, and wanted to see what hiding an object does at the user side. So, as Administrator User I checked the 'Hide' box on Node 2. Then got this message:

The requested page could not be displayed. (1)

The system is unable to display the requested page because of security issues.

Possible reasons:

* Your account does not have the proper privileges to access the requested page.
* The requested page does not exist. Try changing the URL.

This is ridiculous!
Even the Admin User cannot see a hidden node! Let alone unhide it. Now I'm completely stuck!

Which field in which table should I edit (with phpMyAdmin) to unhide this node?

sigh!

Marc Boon

Thursday 19 January 2006 2:22:44 pm

OK, I fixed it by running the following query in phpMyAdmin:

UPDATE `ezcontentobject_tree` SET is_hidden=0,is_invisible=0

This makes all nodes visible.

Still don't understand why it was nescessary to fix this by tampering directly with the database. Can one of the developers comment on this?

Łukasz Serwatka

Friday 20 January 2006 1:06:18 am

Hi Marc,

Which version of eZ publish do you use? If you are able to reproduce this problem on your version, please write step-by-step instructions and report it in our bug system.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Marc Boon

Friday 20 January 2006 3:31:18 am

Filed bug report 7709

Martin Ulrich

Friday 20 January 2006 4:23:03 am

have you tried this:

[SiteAccessSettings]
ShowHiddenNodes=true

_______________________

http://artenic.de ARTENIC - Publishing mit allen Mitteln!

Łukasz Serwatka

Friday 20 January 2006 4:37:14 am

For admin interface this setting is always set to true, as long as user will not change it ;)

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Marc Boon

Friday 20 January 2006 5:24:41 am

I did not explicitly set this property anywhere in my settings.

Do I need to set it in /settings/siteaccess/admin/site.ini.append.php, or is the default behaviour to show hidden nodes to admin users?

Marc Boon

Friday 20 January 2006 5:40:25 am

I guess I do have to set it explicitly :)

I did a manual install, and probably this setting is normally set by the install wizard, which I didn't use.
I added it manually, and now it works as expected.

Can somebody remove my bug report?

Łukasz Serwatka

Friday 20 January 2006 6:08:29 am

Hi Marc,

This page might be useful for future manual eZ publish configuration.
http://ez.no/doc/ez_publish/technical_manual/3_6/installation/manual_installation/manual_configuration_of_ez_publish

Check "The admin siteaccess" part and compare it with your admin settings.

Bug is closed.

Personal website -> http://serwatka.net
Blog (about eZ Publish) -> http://serwatka.net/blog

Jameel Rahmaan

Monday 02 June 2008 8:38:13 am

I think the bug may need to be re-opened as I am having the same problem with ezPublish 4.0.

Already checked my admin site access has ShowHiddenNodes=True

Public site access has ShowHiddenNodes=False as does the main site.ini file

According to my understanding of the manual and settings files, this should enable me, as the administrator, to hide nodes from the public but still view them in the admin interface. Unfortunately it doesn't and the only way I can get my nodes to become visible again is to run the SQL query posted above.

I have cleared all caches as well just in case there was a setting causing interference but to no avail.

And I used the wizard to install ezpublish.

Jameel Rahmaan

Monday 02 June 2008 9:06:59 am

Ok, I see the problem. I had an uppercase T for True. Setting the value to "true" fixed the issue.

Is it me or does anyone else think that for Boolean variables "True" should be equivalent to "true"

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 31 2025 03:34:14
Script start
Timing: Jan 31 2025 03:34:14
Module start 'layout'
Timing: Jan 31 2025 03:34:14
Module start 'content'
Timing: Jan 31 2025 03:34:14
Module end 'content'
Timing: Jan 31 2025 03:34:14
Script end

Main resources:

Total runtime0.0338 sec
Peak memory usage6,144.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0064 588.3828151.2422
Module start 'layout' 0.00640.0042 739.6250220.7500
Module start 'content' 0.01070.0215 960.37501,009.8672
Module end 'content' 0.03220.0016 1,970.242241.9922
Script end 0.0338  2,012.2344 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.00319.0360140.0002
Check MTime0.00123.4214140.0001
Mysql Total
Database connection0.00082.478910.0008
Mysqli_queries0.00288.347530.0009
Looping result0.00000.041610.0000
Template Total0.00123.610.0012
Template load0.00102.970610.0010
Template processing0.00020.630710.0002
Override
Cache load0.00061.920210.0006
General
dbfile0.005416.124380.0007
String conversion0.00000.031740.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