Forums / General / 'ignore_visibility' defaults to true

'ignore_visibility' defaults to true

Next topic

Author	Message
Benjamin Kroll	Wednesday 23 February 2011 2:54:02 pm I ran into an issue today where books on an author profile page would show up, despite the book being hidden in eZPublish. After a checking my fetch and then the docs I found that (to my suprise) the 'ignore_visibility' parameters on the 'reverse_related_objects' and 'reverse_related_objects_count' are defaulting to TRUE. Does anyone have an explanation as to why this is? It seems very odd to me, especially considering that other fetches that support this parameter seem to default to FALSE, as I (and other I've spoken to) would expect. Would love to find the reasoning behind this. cheers, Ben
Bayron Guevara	Wednesday 23 February 2011 10:46:02 pm It's because although the 'ignore_visibility' parameter had been set to true, eZ Publish still applies the filter as is defined in site.ini.[SiteAccessSettings].ShowHiddenNodes, so it have a higher priority and you content isn't retrieved. Could you try to set this parameter to true inside a file override? Web Developer & Modern Philosopher Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn
Peter Keung	Thursday 24 February 2011 8:46:10 am Philipp's good memory suggests that it defaults to TRUE for backwards compatibility reasons, because the "reverse_related_objects" fetch didn't used to have an "ignore_visibility" parameter. So I guess it's just one of those "gotchas"! http://www.mugo.ca Mugo Web, eZ Partner in Vancouver, Canada

Author

Message

Wednesday 23 February 2011 2:54:02 pm

I ran into an issue today where books on an author profile page would show up, despite the book being hidden in eZPublish.

After a checking my fetch and then the docs I found that (to my suprise) the 'ignore_visibility' parameters on the 'reverse_related_objects' and 'reverse_related_objects_count' are defaulting to TRUE.

Does anyone have an explanation as to why this is? It seems very odd to me, especially considering that other fetches that support this parameter seem to default to FALSE, as I (and other I've spoken to) would expect.

Would love to find the reasoning behind this.

cheers,
Ben

Bayron Guevara

Wednesday 23 February 2011 10:46:02 pm

It's because although the 'ignore_visibility' parameter had been set to true, eZ Publish still applies the filter as is defined in site.ini.[SiteAccessSettings].ShowHiddenNodes, so it have a higher priority and you content isn't retrieved.

Could you try to set this parameter to true inside a file override?

Web Developer & Modern Philosopher
Visit http://www.laprensa.hn, http://www.diez.hn, http://www.estilo.hn

Peter Keung

Thursday 24 February 2011 8:46:10 am

Philipp's good memory suggests that it defaults to TRUE for backwards compatibility reasons, because the "reverse_related_objects" fetch didn't used to have an "ignore_visibility" parameter. So I guess it's just one of those "gotchas"!

http://www.mugo.ca
Mugo Web, eZ Partner in Vancouver, Canada