Quote from: ottogal at May 04, 2011, 10:53 PM
How is the style definition of your class [tt]sub[/tt] ? May be it’s an issue with the specifity of selectors.
You can always double check this by viewing the output HTML, and seeing if your class=sub is being output or not.
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein
From the HTML output cited in the original post you just see, that it is not being ouput (in the row marked in red). But you can not see the reason why...
I saw the original post, but was unable to tell if that was the HTML being output by WF or if that was the HTML from the original template.
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein
-
☆ A M B ☆
- 894 Posts
Do you have a class for li ul li so it adds the arrow to the child lists?
Can you post a link to the site so we can see the source code?
It seems like its a css issue not a MODx one.
Hope that helps.
Actually I think it is a modx issue - see the html from the first post here.
Each parent container should have class="sub" attached, but it only seems to have applied it to the top level container. I’m now looking at a similar issue on my own test site where I just cannot get the parentClass added to a top level container, although it is added to lower levels with no problem.
Going through the snippet source now, wondering if it might be a bug...
@ottogal - are you positive that ’Container’ is checked under the Page Settings tab for that particular resource? And calling it uncached as I suggested earlier?
Quote from: ottogal at May 05, 2011, 09:00 PM
@ottogal - are you positive that ’Container’ is checked under the Page Settings tab for that particular resource? And calling it uncached as I suggested earlier?
It’s up to argosy to answer these questions.
I know. Kind of funny that we are all running through so many hopeful answers and possibilities with no feedback....seems to me this thread has gotten out of control
"Great spirits have always encountered violent opposition from mediocre minds." -Albert Einstein
FYI, in Evo, isfolder is set automatically when a resource has children. Even if you uncheck it, it will be reset to checked if there are children, so it’s unlikely that that’s the issue.
I just made this observation: If you delete the children of a resource, in [tt]Page Settings[/tt] the [tt]Container[/tt] checkbox remains ticked, and - obviously because of that - the [tt]&parentClass[/tt] remains assigned to that resource.
So [tt]&parentClass[/tt] does not depend on the existence of children but on the property of being a container.
