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

I am trying to figure out a way to add an item to structure which can directly link to a pdf document. Basically I use structure to output navigation on a site but there are a couple of items in the site nav that link directly to a document. I can’t figure out how to edit the link to point to a document folder on the root of the site.

Any thoughts?

Thanks.

I am trying to figure out a way to add an item to structure which can directly link to a pdf document. Basically I use structure to output navigation on a site but there are a couple of items in the site nav that link directly to a document. I can’t figure out how to edit the link to point to a document folder on the root of the site.

Well, this is more of a hack than anything else, but what if you put in some redirects (in a .htaccess file, for example) that go from the URLs to their corresponding PDFs?

Is there no way to edit the entire page uri?

Is there no way to edit the entire page uri?

AFAIK, the entire page URI is generated by “Structure” based upon an entry’s “parents”. So the only way to be able to edit the entire page URI would be to modify “Structure” to let you do that.

@benek super admins can do anything, so there’s nothing to set under settings besides the default templates once your weblogs are created. It will also say “No Structure Data” until you add top level pages through the publish menu.

@mitresdev I see your problem. RIght now, we don’t have plans to add features for nav_sub, so you’ll have to find a way around that. You could always use a different template just for that page and code the links in for that one only and not use the nav_sub tag. Glad you like the module, maybe we’ll get to the depth level down the road…

@Trinity Consulting You’d have to code the link to that PDF into that template and not use the dynamic tag or use a htaccess RewriteRule as @opuszine suggests. His would be a more elegant solution and still let you make use of the dynamic tag.

Hiya,

I’m considering moving away from Mark Huot’s Tome module to Structure. Reading through this thread scares me a bit since so many people seem to have had problems. Has anyone migrated from Tome to Structure?

The old Tome module was working well for me until recently… It now seems to be causing almost 800 queries per page view, which is unacceptable and slowing everytyhing down. I’ve also considered the module-less approach in Boyink’s tutorials (http://www.train-ee.com/courseware/static/), but those all seem to be slightly convoluted workarounds to me, especially since my main concern is to please my non-technical content authors. The built-in Pages module just doesn’t cut the mustard either so I’d like to give this a try…

James

I’ve had a few people reach out while experiencing a reordering “ERROR” upon dragging pages. If you’re developing in a sub directory the reordering doesn’t work properly. We’ll patch this in the next release, but in the meantime use this patch:

….in your structure.min.js in the function called “structure_saveMove” you must add “structure_settings.site_url +” before this ’’/index.php?ACT=’’ or it’s alway going to default to the root directory….

This was submitted by: Maurice Calhoun http://www.mauricecalhoun.com, Thanks Maurice!

Great module guys, thanks! Have you considered a parameter to reverse {exp:structure:titletrail}?

@damienh not at this point. Usability studies tend to show that people want the current page as the first words in the title. This helps when using the back button or looking through their browser history as the page they’re looking for comes up first instead of the site name. We’ve sort of adopted this convention and built the tag around that.

@rockthenroll I acknowledge this convention has it’s usability merits, personally I’ve used both but there are instances where grammatical significance is needed for the title. For example, looking at the page http://www.apple.com/macbookpro/features.html “Apple Macbook Pro Features” is a better title than Features Macbook Pro Apple.

Please consider a parameter of this sort in future revisions. Thanks again.

@damienh good example! We’ll put it on the list on consider it later when going through updates. Thanks!

I also seem to getting that error message a few people have mentioned when deleting entries from Listing weblogs on the EE Edit page:

Warning: extract() [function.extract]: First argument should be an array in .....system/modules/structure/nestedset/structure_nestedset_adapter_ee.php on line 29

Warning: Cannot modify header information - headers already sent by (output started at .....system/modules/structure/nestedset/structure_nestedset_adapter_ee.php:29) in .....system/core/core.functions.php on line 726

Doesn’t seem to affect functionality, but it is displaying everytime I delete.

Other than that loving the module - been using it on a number of sites over the last few weeks!

New version 1.0.3 released! Addresses several bugs (including @John Ryan’s above) and a few new parameters to tags. Get it at the top of the thread or here with the change log: http://www.ngenworks.com/software/ee/structure/#change-log

The 1.0.3 download shows as 1.0.2 when installed. Both the module and extension.