I am so frustrated that I am about ready to give up on MODX. I cannot get it to correctly show any document below the second level. I am sure I have it organized correctly under "Resources". I have carefully made sure that all documents are referencing the correct "Category" it even shows the correct url IE www.top/level2/level3.html but it brings up broken versions of other pages, usually the top. This even happens using wayfinder. What am I doing wrong? I have been trying to figure it out for weeks. I am very discouraged because I cannot find what I am doing wrong.
I had a similar problem a few years back.
What config are you using in the wayfinder snippet.
There are others you can use.
I found Fancypants worked for me.
Let me know if this is what you are after
NB on the image There are 3 levels below the main one- I just havent styled the 3rd level as I dont yet need it.
It was just for illustration purposes.
Sorry slow to respond. I work my 40+ at the computer factory before I get to come home and work on this. The issue happens regardless of which type of menu I am using. I mention wayfinder because I tried it as a part of my debug. (Changed nothing.) I mention "Category" because I am self teaching from "The Official Guide" and it said to use them. I am beginning to suspect I am OVER using them. My site consists of a top level and 4 major sub levels.
For example: My site is called Planet Body Mind and I have split them into 6 different "categories" (screen shot attached) Can you suggest when I would properly make use of this feature? The screen shot shows my revision and the categories I am trying to menu. Interestingly, I have been able to get some third levels to work, but only if I use the entire path (http:/etc)instead of the [[~xx]] call. the Catalog/kitchen ( [[~33]] ) will not work regardless of what I do.
With more debugging I believe I have narrowed down the issue. The links work or don't work depending upon how many style.css calls are being made. If there aren't too many they work. However if there are a bunch of calls; for instance :
<body>
<div id="contact"> </div>
<div id="full-width">
<div id="btm-shadow">
<div class="main_wrap">
<div id="header">
<div id="top-bar">
<div id="solcial-network">
<p><span><h2p>SHOP ETHICAL, NON-TOXIC, GREEN </h2p></span> </p>
</div>
<a href="[[~1]]" class="logo"></a>
<ul id="menu">
<li> </li>
<li class="sep"></li>
<li ><a href="#"><span>Shop Ethical</span> </a>
<ul class="lf3">
<li><span class="dp1"><a href="[[~33]]" class="nobd">Kitchen Appliances</a>
(On and on in a complicated menu feature)
Here the kitchen call does not work: In a place with fewer calls it works fine.
Unfortunately I really wanted to use the menu feature from this page because it would have organized my store .
Any comments on where to look to cure this, or should I just give up and make a less complicated menu?
First, be sure that all the documents are published and that the "Hide from Menus" checkbox is not checked.
If you're seeing broken copies of other pages, it's likely that your HTML is invalid -- either in your template, or in your Wayfinder Tpl chunks. The validator here can be very helpful with that:
http://validator.w3.org/.
I did the menu at Bob's Guides with Wayfinder (and some borrowed JS). Each top-menu item (and it's descendants) is generated by a separate Wayfinder tag.
http://bobsguides.com.
The JS came from here:
http://code.stephenmorley.org/javascript/collapsible-lists/
BTW, it's kind of unfair to blame MODX for this kind of problem. It just takes what you give it and sends it to the browser, though doing a complex menu is always a challenge, with or without Wayfinder. I very much doubt if you'd be having any less trouble doing the same thing on another platform.
Thank you for the response BobRay. Honored to talk to the author. I did check and everything is published. Also I can call any page perfectly fine as long as it is done from an area on a page with simple css formatting. I bought this template from Template World and purposely kept it simple because I am a newbee. At this point I suspect the style.css file. The templates are tested I am sure, but perhaps not with ModX.
It would be interesting to know what is breaking it, but I am not capable of debugging into it and I have already spent way too long pulling my hair out trying to get it to work. I have decided it is not worth further effort and I will do something simpler. After all it does work just fine outside a complex menu. (Wish I had tried that sooner.)
BTW did not intend to make it sound like I blamed MODx. As I gain experience I expect I will get better. (It's that newbee thing again.) I do admit that in my frustration I went and looked at alternatives, but then decided they did not offer the flexibility I wanted. I decided to try to work my way through it. That's when I went to the Forum.
Thanks again
Larry
Thanks for the kind words.
If it's not a MODX template, it may have some embedded PHP code in it, which MODX will strip out. That would explain the issue.
-
☆ A M B ☆
- 24,524 Posts
Good grief! I had completely forgotten about that. I need to find the time to get back and finish it. It's based on this presentation I made at MODXpo in Utrecht last year.
http://modxpo.eu/schedule/sessions/building-a-modx-site-in-90-minutes