5

To make this work, in the entry for Home under the structure tab, set the Structure Page URL to "/"


5

Knowing that you will use Taxonomy does change the answer. With Taxonomy the answer is "Neither." ...Unless that's really how you prefer to build your site! Taxonomy is very flexible, and will do it's job regardless of how you set up your Channels, template groups, and templates. You don't need to set up channels to hold navigation-related data, that's all ...


5

It seems they moved this feature to be in a drop down menu rather than directly in the main UI. I loved adding links to the top of the old EE, made things quick. But now they are in the top right corner under your username dropdown. When you click on your username you'll see a "new link" option, along with any other links you've already added. You can ...


4

Depending on how your pages are constructed, have you looked at this Tutorial yet? https://expressionengine.com/learn/smarter-breadcrumbs-with-layout-lists Russ


3

You can add short cuts into the control panel using the Menu Manager. Go to Settings (button in top right hand corner) Choose "Menu Manager" from the left hand navigation (under General Settings) Click on "Add Menu Item" Choose "Single Link" Give the link a name Enter the relative path to the addon e.g. cp/addons/settings/freeform Save Save Menu Set I'm ...


3

Have you taken a look at the Yearlist Add-on? Then I would think it should be possible to do something like this: <div class="content-tile"> <div class="grid_4_desktop grid_4_tablet grid_1_mobile" id="archive-menu"> <h2 class="title">News</h2> <ul> {exp:yearlist channel="yourchannel" category="1"} <...


3

Use NavEE's Regular Expression field for the FAQs menu item. This tells NavEE to match an item as selected based on that rule (using preg_match()), rather than just matching the URL itself. So in your case you could enter /faqs/.


3

You'll need to use the Structure Entries add-on for this. Here's the basic idea (full docs can be found at the devot-ee page): <select id="Menu" name="menu"> {exp:structure_entries depth="1"} <option value="{page_uri}" {if {current_page}}selected{/if}>{title}</option> {/exp:structure_entries} </select>


3

@James Right, I really do understand that argument, but at the same time the "streams of content" philosophy requires knowing quite a lot about content before it is ever created. Yep, you're absolutely right there. Most EE sites I've made usually end up with a generic 'Pages' channel, but I always try to drill home that it needs to be for exceptional ...


3

You'll need the name of the relationship field on your parent entries. Instead of using static_parent_page == 0, try a namespaced no_results. {exp:channel:entries channel="static" sort="asc" offset="1" dynamic="off"} {static_parent_page} {if static_parent_page:no_results} <li> <a class="active" href="{url_title_path=static/...


3

With - http://ellislab.com/expressionengine/user-guide/add-ons/channel/entry_linking.html {exp:channel:next_entry} <p>Next entry: <a href="{path='site/comments'}">{title}</a></p> {/exp:channel:next_entry} {exp:channel:prev_entry} <p>Previous entry: <a href="{path='site/comments'}">{title}</a></p> {/exp:...


2

When you pass an entry_id or node_id parameter, Taxonomy is looking for that active node in the tree and assigns all the appropriate vars like {active}, {active_parent} etc. If the active node is not found in the tree, Taxonomy will not output the nav. As you're asking for a subset of the tree, flagging that you want an active branch subset, and supplying ...


2

Get yourself Zoo Triggers and you will love yourself! {exp:zoo_triggers:archive channel="news" status="open" show_counter="no" type="year"} Just make sure you give the settings docs a once over to get it set up like you want.


2

Sure, something like this: {exp:channel:category_archive channel="my_channel" style="linear"} {categories} <h3>{category_name}</h3> {exp:channel:entries channel="my_channel" category="{category_id}"} <a href="{comment_url_title_path}">{title}</a> {/exp:channel:entries} {/categories} {/...


2

As far as I know this flatly can't be done without hacking the core and even then it's possible that third-party functionality (and even base functionality) might break. Maybe explain your issue a little more -- there might be a way to accomplish your goal WITHOUT the need for extra segments? Edited to add: You can TRY the following, it should work for ...


2

You are using relative addressing for the tag that loads your javascript elements: in the page source you see tags that look like this: <script src="V2/js/clean-blog.min.js"></script> which will cause the browser to try and load the scripts from a URL relative to the current one the browser is at, rather than the site root. In your first ...


1

Many URLs with summaries in <UL> <LI> structure, No doubt channel entry is needed. You can use both Relationships and GRID to accomplish the megamenu needs. (As there are several plugins available in devote ee But I don't think they will match megamenu criteria so no other options except channel with GRID and Relationships)


1

Uninstall all third party addons, especially Accessories. I literally had this happen to me the other day when I was developing a complex addon. I can't remember if it was the Extension or Accessory that was doing it (pretty sure it was the Accessory). Do them one by one so you can find out exactly who the culprit is.


1

You need to post a page that has been assigned to use Structure. Check Structure » Settings and use one of those channels.


1

You can get information about any node via the get_node tag. From there, you can find out if the node has children, as well as the depth of the current node. Something like: {exp:taxonomy:get_node tree_id="1" entry_id="{entry_id}"} {if this_node_level > 2 && this_node_has_children} {exp:taxonomy:breadcrumbs tree_id="1" entry_id="{...


1

I'll hazard a guess here and say that the reason your "Hidden from Nav" entries are being output is because you're not actually using a Structure module tag, but the Structure Entries plugin. I'm not sure what kind of support Structure Entries has for Structure's Hidden from Nav feature. What version are you using? It sounds like there is a beta version ...


1

Using segments as Anna described in her answer definitely works well for some sites. But it can get tedious on large or deep navigation trees and is not practical when the client needs to manage the navigation. In those cases, or if you just want to cut out all the conditionals, take a look at NavEE. It's very flexible and easy to use. Well worth the price. ...


1

I personally always take the route of using segment conditionals to set my active state CSS class. It's easy to code and manage since it's handled in one template. <li><a {if segment_1 == 'about'}class="selected"{/if} href="">About Us</a></li>


1

Your best bet is to hold this URL via a global variable defined inside of your config file (as standard user-defined global variables will be scoped to each site). Or to get fancier, use Low Variables, which will may help you elsewhere in your site build as well.


1

This code tells Structure Nav to always start at root and to show 2 levels of the tree all the time: {exp:structure:nav start_from="/" max_depth="2"} Structure Nav Docs: http://www.buildwithstructure.com/tags/navigation/


1

I just resolved this, turns out it was a low variables/parse order issue. I needed to preparse segment_1 etc... on the main template. My code now looks like this {!--sidebar--} {exp:low_variables:single var="lv-sidebar" preparse:pre_seg_1="{segment_1}" preparse:pre_seg_2="{segment_2}" preparse:pre_seg_3="{segment_3}" preparse:...


1

I think it's because the sessions are handled differently in the most recent versions of EE. I fixed it on a couple of sites of mine just by recreating the links. If you're still having issues then I'd suggest removing the session hash from the URL. So http://url.de/backend/index.php?S=56ddd7c4744a94b131bcd8f0bdb6f61965476ed5&D=cp&C=...


1

Not tested, but this should work. We're checking to see if each fruit has parents, and if it doesn't, then we display it (and any child fruits). It would be helpful if the fieldtype had something like Playa's :total_parents and :total_children tags, but it doesn't (which is one of the many reasons I still use Playa). <ul> {if '{parents field="...


1

Be a bit mad to have duplicate content, messy and the trying to keep both in sync would be a nightmare. You also want to consider duplicate content in the eyes of Google. Your best bet would be to leave the content as is (only one copy), but have duplicate navigation. There are many ways to do this, one would be to have categories Section 1 and Section 2 ...


1

This seems to be a great role for NavEE. As you can see in my post (thanks for the link, BTW) I'm a fan of NavEE because it accomplishes much of the good stuff about Structure (easy nav menus) without abandoning the EE philosophy. You could have a NavEE fieldtype associated with those two channels whereby the client could create nav links, and NavEE's ...


Only top voted, non community-wiki answers of a minimum length are eligible