In the navigation section, we are able to add Section Links. Both the Target Section field and the … graphic to the right of it are unclickable on all browsers (in Firefox, I can click the field, but am unable to type in it). There is no hover effect and no curser change to a pointer. When we do click and wait, nothing pops up.
Matt,
The “Target section” text field for Section links is not meant for text input because it gets filled out by selecting the browse button to the right of the text field (the blue ellipsis) and browsing through your navigation tree and selecting a section. I too am not seeing a pointer cursor when I hover over this button (in Windows or in Mac OS), which I agree is inconsistent with how menus typically display and should be fixed. But, in my case using Firefox 13, 14 and the latest version of Chrome (again, in Windows and in Mac OS), clicking on the browse button does in fact open up a new box through which you can select your section.
It’s possible this issue is tied to your “Slow Response Time” issue. Can you verify when you click on the browse button and wait for 15 / 20 seconds, that still nothing pops up?
Thanks,
Nathaniel
Confirmed. We’ve tried waiting 20 seconds during a conference with Jonathan, and just now with the response time being remedied a bit via a server stop/start. The “…” button is not clickable.
This is true on the latest versions of Chrome (21.0.1180.79) and Firefox (14.0.1).
Matt,
As I mentioned in your Slow Response Time post, I have been unable to recreate this issue here while testing it under various circumstances and on various machines. Assuming you’ve had a chance to duplicate this error on a machine other than your Mac, can you give me an estimate of how many individual sections there are in you navigation tree? I know you have a very high quantity of pages on your site, and I wonder if a similarly dense navigation tree could cause this tool to timeout when retrieving your section information.
Thanks,
Nathaniel
We’ve found that this is also the case on Windows computers (running IE9).
As far as our navigation tree, virtually all of our index pages are sections within our tree, and we’ve got 1020+ pages. Will this be a problem?
Matt,
Unfortunately CM1 does not support IE9 at the moment, so we can’t totally rule out your environment as the issue unless you can test this on the latest versions of Firefox or Chrome running on Windows OS.
However, the quantity of items in your navigation tree could very well be causing this issue too. I’m going to run some tests on my end to see if I can recreate your problem. While I do that, you can also try something simple on your end to help us narrow this down: Try creating a new test site in CM1 populated with a very minimal navigation tree (five or less sections) and see if you can load up the “Section link” menu for that test site. Let me know how that goes.
For now as a workaround, you can create an “External link” as a section in your navigation tree, and point it to the desired page using a relative URL such as “/section1/section2/index”. Note that the links won’t resolve properly when you preview the pages, but should work fine once you actually publish the pages. However, if you ever rearrange your navigation structure, you will need to manually update these links.
Nathaniel
Matt,
I have identified a bug which might very well relate to your issue here. It appears that if you have a section and landing page with only number characters in its “display title” (“section name” is unaffected by this bug), the “Section link” menu will not display at all. For instance, a display title of “123a” works fine, but just “123” does not. I know you say you have over a thousand sections, so this might be hard to check, but do you know if you have any sections with only numbers in their display title?
I have submitted a bug report to engineering regarding this, and I will keep you posted as to what we learn about this issue, and when we might expect a fix.
For now, if going through your navigation tree and editing the names of sections with only number characters in their “display title” is too tedious or not an option for any other reason, the workaround I posted earlier will still achieve similar – if less flexible – results as the section link.
Nathaniel
Quick update. This bug has been confirmed by engineering and a fix has been identified, which we plan to include with the 2.8 release. Matt, did you have a chance to look over your navigation tree for any sections containing only numbers, or is that not going to be worth your effort considering the quantity of sections you would have to look through?
Nathaniel,
Thanks for looking into this. I’m glad it will be fixed in the coming version.
I took a look, and we definitely named all our sections according to what they are (i.e. Undergraduate Admissions as a display title, and undergraduate-admissions as a section name).
In the time before the fix is released, is there anything we can do to link to internal pages on a navigation? (Using the external link, perhaps, with the whole page address?)
Yes, in my slew of responses earlier I mentioned the current workaround for this, which, as you already guessed, uses an External Link section type. Here that is once again:
“For now as a workaround, you can create an “External link” as a section in your navigation tree, and point it to the desired page using a relative URL such as “/section1/section2/index”. Note that the links won’t resolve properly when you preview the pages, but will work fine once you actually publish the pages. However, if you ever rearrange your navigation structure, you will need to manually update these links.”