[Logo] Infoglue - Official Forum
  [Search] Search   [Recent Topics] Recent Topics   [Hottest Topics] Hottest Topics   [Members]  Member Listing   [Groups] Back to home page 
[Register] Register / 
[Login] Login 
"Rightclick to add component" in inherited slots  XML
Forum Index » Component Development
Author Message
jaric

Admin
[Avatar]

Joined: 02/11/2009 10:09:03
Messages: 107
Location: Uppsala
Offline

Is there a way to turn off the "Rightclick to add component" box in inherited slots? It seems like InfoGlue i EOS mode will only look in the current site node's component structure to see if it should show the "Rightclick to add component" box even if the slot is restricted to only one component. I think the correct behavior should be: Only show that box if there is no component added to this slot in this site node or in an ancestor.

But maybe this is configurable with some setting?

Peter Jaric
Division for IT and Procurement
Uppsala University
[WWW]
astik

Expert
[Avatar]
Joined: 11/11/2009 11:41:32
Messages: 98
Location: France
Offline

"Showing the box only if there is no component added to this slot in this site node or in an ancestor" can be wrong. It is to eager.
Imagine that you defined a main menu for your website and into some inner pages, you'd like to override this menu with a new one. To make that work, you need to be able to access the box even though the component is set in an ancestor.

I'd have the same problem as you on a site which doesn't need those kind of overrides so I hide the box with CSS and it works great. The box are displayed only on the homepage.
If the administrator wishes to override an inherited slot, it still can be done using the component view.
[WWW]
jaric

Admin
[Avatar]

Joined: 02/11/2009 10:09:03
Messages: 107
Location: Uppsala
Offline

astik wrote:"Showing the box only if there is no component added to this slot in this site node or in an ancestor" can be wrong. It is to eager.
Imagine that you defined a main menu for your website and into some inner pages, you'd like to override this menu with a new one. To make that work, you need to be able to access the box even though the component is set in an ancestor.


If I am not wrong, you can always access the slot through the "Page structure" view, and mostly you can use "Add component" directly from the menu if you right click in the current component, when it is inherited, although that is kind of risky as it isn't always clear which slot you're targeting. At least that is the case in our current structure (I had to try it before writing this :) ).

astik wrote:I'd have the same problem as you on a site which doesn't need those kind of overrides so I hide the box with CSS and it works great. The box are displayed only on the homepage.
If the administrator wishes to override an inherited slot, it still can be done using the component view.


That's a good idea, but do inherited "right click"-boxes have some special CSS class or is there some other way to know which ones to hide and which ones to show?

This message was edited 1 time. Last update was at 16/11/2009 09:03:40


Peter Jaric
Division for IT and Procurement
Uppsala University
[WWW]
astik

Expert
[Avatar]
Joined: 11/11/2009 11:41:32
Messages: 98
Location: France
Offline

jaric wrote:
That's a good idea, but do inherited "right click"-boxes have some special CSS class or is there some other way to know which ones to hide and which ones to show?



No special CSS class nor id. But, my page structure is define in such a way I know where are each block and I can access them with CSS. For example, there is "right click"-boxes into the header, into the footer, for navigation and main content (with or without additionnal column). Every boxes are displayed on the home page. On inner pages I only hide header, footer and navigation ones.

In CSS, you can write something like this :
#header .foo, #footer .foo, #navigation .foo { display: none }

And overload it for homepage :
#homepage #header .foo, #homepage #footer .foo, #homepage #navigation .foo { display: block }

Of course you have to make the homage special by adding a class or an id. In my example, I add id="homepage" to the body of my homepage.

I agree, all of this is not really dynamic or easily customisable, but to be honest, I don't see lots of websites which change their header structure while browsing, so, it's enough for me =)
[WWW]
 
Forum Index » Component Development
Go to:   
Powered by JForum 2.1.8 © JForum Team