5
To make this work, in the entry for Home under the structure tab, set the Structure Page URL to "/"
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
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)
answered Feb 10 '17 at 11:53
Mufi - Amici Infotech
2,1772 gold badges9 silver badges23 bronze badges
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:...
Only top voted, non community-wiki answers of a minimum length are eligible