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

That is a shame…after all we have Pages Module it would be nice to see is spiced up out-of-the-box. I finally got to test drive Structure a bit more and really nice work! Please do keep this module going! 😊 Thank you.

Thanks for the swift reply r’t’r I certainly understand the complexity it adds to your project, and it might be a minor request, but surprisingly one i come across all the time. (Not complaining, as i now plan to go down the “navigator” menu generator path)

But with title being important to SEO (my titles always end up in H1 tags, for example), the titles do tend to become quite intensive (maybe adding company name, or field of expertise, etc), where as a lot of primary menus are kept short - home, about, portfolio, contact, etc. However, i can also see the other side in that if the titles are important for SEO, then the links are very much so too.

For secondary menus, the using of titles for menu items logic makes perfect sense, and i would 100% use it that way.

Anyhow - getting to my point, what do others do in relation to structure (which i do think is great by the way) and primary menu’s, etc? Advice appreciated. And i’ll be sure to check out the next generation of Structure if it is being dropped soon. N

has anyone tried to successfully uninstall this module? it has cause me no end of problems… Uninstalling it from modules section of the site, causes publish and edit pages to fail with SQL error… Removing the module folder causes white screen on modules page, etc…

Any tips here please?

Ignore above… i have resolved… I am guessing the problem was something to do with the order of disabling the module, extension and enabling pages… But it seems to be running without a glitch now… SO probably something i did… Thanks anyway.

@nevsie I see your point and how that could be handy. I’ll put some thought into it for a future release. Maybe in the future we could add a new tag that grabs a certain custom field using a parameter. Example: titletagname field=”your_title_custom_field” Would that do what your thinking?

hmmm, let me think on this one… i mean perfect world for the user would be to be on the structure tab, “menu value override” or similar… but i know this would be a pain to store it, etc… I think linking to a custom field would cause confusion for the average user, and be a little fiddly if using it across lots of fields… hmmm, i’ll think on this and get back to you. N

Hi, we’re trying to use Structure on one of our sites. However, the nav_sub tag is behaving strangely. What happens is we’ll use the tag like this, in our templates:

{exp:structure:nav_sub start_from="foo/bar"}

And the HTML it generates is like this:

<ul id="nav_sub"><li class="sub_level_0"><a href="http://index.php/foo/bar/alpha/">Alpha</a></li>
<li class="sub_level_0"><a href="http://index.php/foo/bar/beta/">Beta</a></li>
<li class="sub_level_0"><a href="http://index.php/foo/bar/gamma/">Gamma</a></li>
</ul>

You see? The problem is that it gives the full path from the site root, but does it without a leading slash, so that the browser interprets the links like this:

http://www.domain.org/index.php/foo/bar/index.php/foo/bar/alpha/

Which is, of course, no page on the site. I suspect it’s probably a configuration issue or something, but I have no idea where to look. Have any of you encountered such an issue? Any tips?

@Doug E try ading a slah in front like start_from=”/foo/bar” Also, do you have your site URL and index.php input correctly under Admin » System Preferences?

Adding a leading slash, as in start_from=’/foo/bar’, does nothing. Adding a leading slash in front of “index.php” in the “Name of your site’s index page” field under Admin >> System Preferences >> General Preferences “fixes” the problem, but it seems like a strange fix, since I’m pretty sure EE has only “index.php” in that field by default and on another test server Structure behaves as expected without adding that leading slash.

Anyhow, I suppose we have the problem “solved” for now, but it would be nice if we had a better understanding of why this is happening.

@Doug E try ading a slah in front like start_from=”/foo/bar” Also, do you have your site URL and index.php input correctly under Admin » System Preferences?

@nevsie I see your point and how that could be handy. I’ll put some thought into it for a future release. Maybe in the future we could add a new tag that grabs a certain custom field using a parameter. Example: titletagname field=”your_title_custom_field” Would that do what your thinking?

That’s funny—I was just wondering how to do this. I’m using Structure for the first time on a new project and need this very function. The page titles are far too long to be used as menu titles. I thought about creating a custom field with a “short title” that could be used for this, but then saw no way to pass this through to nav_main.

Not having this function pretty much makes the main navigation function unusable for this project. I understand that accommodating this would add some complexity, but just wanted to drop in to add my “vote” that this addition would be appreciated!

How do I upgrade from 1.3.1 to 2.0 without messing up anything?

Just seen the 2.0 release, congrats… i think adding a “menu text overide” option to the structure tab for each entry would be the right choice, no matter how complex for a paid extension… Something on: B. Multiple Content Types (http://buildwithstructure.com/) just under URL would be suitable i think…

Is version 1.3.1 still downloadable? I want to upgrade my old version to this version first before I maybe upgrade to version 2.0.

@nevsie I see your point and how that could be handy. I’ll put some thought into it for a future release. Maybe in the future we could add a new tag that grabs a certain custom field using a parameter. Example: titletagname field=”your_title_custom_field” Would that do what your thinking?

That’d be perfect! Personally, I switch between a bespoke CMS I’d built in CodeIgniter and using ExpressionEngine (depending on the project requirements) and in my bespoke one, I have two fields: Page Title and Nav Title, with Page Title being a required field (and therefore, akin to the Title field in weblog entries in EE). This allows users to have a more verbose title for pages that isn’t used for navigation elements; if present, the Nav Title field is also used to generate the URL Title for the page.