New Module: Structure - Uses entries to create a page hierarchy for static and listing pages

Excuse me if this has been answered, but I couldn’t find it elsewhere on this thread - does Structure work with the ExpressionEngine Core version?

Thanks! - Andrew

When I view a URL that does not exist, EE is serving up the index template and displaying the content from every page managed by structure.

I’m using {exp:weblog:entries}{/exp:weblog:entries} to show the information and it works perfectly when requesting a valid page.

But when viewing a URL that does not exist, it seems to pull out all weblogs associated with structure.

Am i doing something wrong here?

Thanks

Hi All,

Loving structure but one thing i can’t seem to do is output a full list of all parents and children, i want to do this to use a dropdown menu on the navigation, i have tried the site_map tag, but this doesn’t support the selected page, but is the basis of what i need.

Before i go implementing this is there a way of doing what i need already?

General note: I know this thread is gnarly and quite often simple to solve issues are too buried within the posts. To help with this, the next version of the site will have a knowledge base section with often asked questions or needed methods.

@rewdy In the next version, we’re working towards unifying the feature set of each tag. Incremental updates will add smaller features after that. As far as one master tag, it’s something I’ve considered and will be addressed later. It’s definitely a good idea, but it’s a lot to rewrite and tackle being such a huge part of the module. Combining them also poses many interesting issues in making sure it works in all or most cases. Definitely on the list, but as they work now they get the job done and we’ll be working to improve their behavior to match what everyone needs until a complete overhaul it undertaken. Some kind o flooping wrapper tag is an interesting idea. Thanks for your thoughtful feedback! Keep it coming!

@Rob Leeper Some sort of if_children method will be in the next version, but until then use segment checking to remove the nav_sub tag on needed pages.

@Andrew Waegel It does work with core, but there’s a note in the very first post about that. Of course we all support license buying though! Help keep EE going!

@AJ Reading You need to assign your 404 template under Templates » Global Template Preferences. To show a specific entry there, use entry_id on the weblog tag.

@Matthew Lanham We’re finalizing the feature set, but a tag for every page will most likely be included in 2.0 - currently there is not a tag to do that, but if you can hardcode the top level, you cna use nav_sub with the start_from and show_depth parameters to output all children for each section.

As always, PM or email me if you need more help!

First let me start by saying that you’ve read my mind. I have been looking for an easy way to turn EE into a true CMS instead of a blogging tool.

For those of you, like me, who are not professional developers, I’d like to share an article that I stumbled upon that may help in getting a grasp of how structure does what it does in setting up relationships. It may also be useful in developing some custom plug-ins or php to tweak it to your specific needs. Heirachical Data. It explores the “adjacency list model” (how ee does categories) and the “nested set model” (used by structure). This article gives examples of queries to extract specific relationships from a table for both models.

Can stand alone edit forms be created for structure entries? I can’t get it happening since structure seems to prevent you getting entry data via a exp:weblog:entry tag with an entry_id parameter.

Any thoughts on having {exp:structure:parent_title} take a parent level? In many cases I don’t want the parent title as much as I want the “section” title. It would be great if this would take a level 1,2,3,4…etc… from the top of the tree structure as an optional param.

A few good idea. I’ll make sure it gets on the list with Travis 😊 BTW, I’m now on the Structure Dev team, so you may see me in this thread more often from here on out.

I think this would be a great addition and something that I’d love to see; allow us to define the segment that’s the parent. For example, I have the following structure on a site I’m working on:

/news-and-events/latest-news/this-is-a-news-item

When I’m at

/news-and-events/latest-news

The parent_title function works as I’d hoped: by telling me that I’m within the News and Events section. But when I view a news item, it sees the parent as latest-news, and so the title becomes “Latest News” which might be a bit confusing for the user.

Any ideas if this would be an option to include in the future?

@Craig Allen Currently, no

@Phil Norton Something like that is in the works

@Matthews issue Travis,

so there is no way right now of displaying sub_nav (level 0) and sub_nav (level 1) at the same page?

great module nice work.

@Interfacer start_from and show_depth should help you out, give it a try.

Does that need to run segments?

(btw that was the fastest response in forum ever - NY rocks)

@Interfacer It can use segments, but doesn’t have to, especially if you’re looking to ALWAYS output the same thing. The best thing to do is install and try it!

Found a bug with the sql query in mod.structure.php that calculates the entry count for pagination. This yields the incorrect count when using the category parameter with the nested exp:weblog:entries tag

Line 1274:

$sql = "SELECT COUNT(entries.entry_id) AS c" .

Change to:

$sql = "SELECT COUNT(DISTINCT(entries.entry_id)) AS c" .

I’ve just begun using Stucture for 4 separate weblogs on my site where each of the weblogs is managed by a separate group manager. Is there a way for me to limit the control panel view so that each manager can only see the weblog that they are in charge of?

For instance (see pic) I only want the East Area manager to see the East Area weblog, and want the West Area, Extended Area, and Extranet weblogs to be invisible.

Is there a simple way to achieve this? Will I need to go into the ‘structure_admin.tpl.php’ file, in /system/modules/structure/ and hack it?

thanks for any help or advice.

brian