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

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.

Sounds like you guys are thinking about it from the wrong angle. Just use the title field as your short title, which appears in the navigation, and add a new custom field such as page_title or long_title that will serve as the headers in your pages.

understand where you are coming from and what you suggest certainly is a suitable workaround. But what i was suggesting was not that it is not possible, but more what would make life easier and logical. Having two title fields could and would throw off many of my clients!

Whereas having it in the seperate tab of structure would be a cleaner simpler solution.

By comparison, it is similar to LG BETA META, i purchase this to make use of the clean seperate tab, and functional output. I could quite easily just add fields to the bottom of every weblog/channel to cover my META needs, but i don’t!

I guess what i am getting at is not about making it work, but making it work well and conveniently for me/my clients. (although i admit i have spoilt brat syndrome!!! 😉)

@Sean: Googe has them cached: http://74.125.113.132/search?q=cache:A269ZgVhtXsJ:buildwithstructure.com/+buildwithstructure&cd=1&hl=en&ct=clnk&gl=us

And I understand where you are coming from. I’ve done the meta fields at the bottom of each page, and the separate page_title field, and used the description to explain what each field does in the form. My client’s haven’t had an issue with that thus far, and some have actually found it beneficial to have 2 different title fields (one for the nav, and one for the page header). To each their own.

Sounds like you guys are thinking about it from the wrong angle. Just use the title field as your short title, which appears in the navigation, and add a new custom field such as page_title or long_title that will serve as the headers in your pages.

Yeah, I thought about implementing it that way. But I wanted to stick my head in here to see if I was missing something related to Structure before changing my templates and field groups, since it seemed like this would be a common issue. It sounds like I’m going to have to do just what you suggest, though.

First of all, as many have noticed, Structure 2.0 is out! http://buildwithstructure.com

There’s a new knowledge base that will be growing very soon and the add-on is officially a commercial version now. There are loads of new requested features and bug fixes that can all be seen here: http://buildwithstructure.com/changelog

Eventually, I’ll request this thread be closed to be taken over through official support, but I want to keep it active for at least a few weeks to support those eon 1.3.1. I’m always available by email and IM if needed. travis [at] rockthenroll [dot-com] or rockthenroll on AIM.

RE: Menu text I see who this could be useful and will be considering it for future versions. For now, the title can drive your menus and a custom field can be your extra text. Thanks for the input!

RE: Upgrades 1.3.1 is no longer available. Structure is now a paid module to help support our time and development. I don’t want to pull the rug from under anyone, but the move to commercial has been announced quite some time ago.

@Sean the docs are mostly the same and I will continue to help people as much as possible with 1.3.1, but paid upgrades are suggested to support development.

@nevsie If properly labeled and trained a custom field will work perfectly. If you need extra instruction power, check out Masuga’s awesome Dulee Noted extension http://masugadesign.com/the-lab/scripts/dulee-noted/

Thanks everyone!

Any chance the -1 bug has been fixed in v2? 1.3.1 didn’t do it…

Good move going commercial - I’d much rather pay and know you will be around than take the chance. Great work on the module!

@rockthenroll Yeah certainly agree it can work and work effectively that way. After all that is pretty much the basis for EE completely. I was just expressing something that would be helpful for me on a current project, that others might like too, or might be a handy feature request for yourself.

But as many others have pointed out this is just my preference, and the processes and methods i like, many others would not agree. And in my case perhaps a different solution might be suitable - which is why i am currently using Navigator. But i definitely like structure and it has a place for me within the near future.

@Brian M. Yes, it’s fixed.

@nevsie Cool!

New thread for Structure 2.0 related matters: http://ellislab.com/forums/viewthread/134500/

This thread will remain dedicated to 1.3.1 for the time being.

double posted.. please delete.

I updated this for DROP DOWNS for the newest structure & thought I’d share my code. In mod_stucture.php….

Yes, Travis added drop downs in 2.0 version!!! http://buildwithstructure.com/tags/nav_full/

I’m going to update right away.

is the old version still available?

Is it possible to use it effectively with multi-language site?

I’ve been thinking of using status groups for separating different languages output.

Has anyone tried that - if so what are the limitations? If not, are there any other approaches towards this?

Thanks for help!