New Module: Structure - Uses entries to create a page hierarchy for static and listing pages
Development and Programming
@IschaGast anything that is multi-entry, like a news section or a blog needs to be added as a “listing” so that it doesn’t show up in the sitemap view. When selecting the weblog for a structural page, you would select something other than this “listing” weblog. Hope that makes sense. I think you need to read these instructions: http://www.ngenworks.com/software/ee/structure/#add-listing it will help get your head around the difference between regular and “listing” pages.
Thank you again, I think I misreaded that page because I had looked at it… but after reading it with a fresh mind I saw what I did wrong…
Hi - I thought I’d try using the structure module to help my clients populate the XML/Flash site I’ve built.
I often come up against the same problem - ie: Section/page with x number of sub pages. Normally I get round this by having one weblog whose entries are the sections, and then assign sub pages to these entries using a relationship field.
It’s all then output using an XML template and displayed in flash.
So… My question is - can I use the structure module to output child entries and their parents in my XML:
Kind of like this (where ‘projects’ is the parent weblog and ‘project_pages’ is the children weblog):
{exp:weblog:entries weblog="projects" }
<item bgimage="{bg_image}">
<title><![CDATA[{title}]]></title>
<!-- Children--> {some kind of loop for weblog="project_pages"}
<title><![CDATA[{title}]]></title>
<body><![CDATA[{main_text}]]></body>
</page>
{/end some kind of loop}
</item>
{/exp:weblog:entries}Any help received with thanks 😊
Marc
@exmonkey definitely possible, but you’d have to write custom code as the current tags are set to output a certain way. Some of the code is already there, sicne the nav_sub tag loops through and finds children. I’d start looking there.
Is there an ETA on allowing this to be turned on/off on a per weblog basis? I would be able to use this plugin full time for all my sites were it not for this minor gripe. As it stands now, I have to set other content (such as callouts and sidebar items) to a closed status in order for them to stay out of the Structure tab.
@Brandon C. we have this feature complete and are finishing up a few other items that are part of the same update. We’ll have some testing to do when that’s finished, so hopefully within the next few weeks at the most. Good solution on the status method!
Thanks for the update - that’s great to hear!
Just to follow up on my last post, it looks like even with setting the status to closed, new entries still go into the Structure tree. You then have to manually delete them, at which point they stay hidden. Do you know a way around this in the meantime?
Nope, just have to run with it that way for now. Next one is coming soon!
Testing with PHP 5.2+. Structure 1.0.3 works, but have this message on module settings page:
No permissible groups exist. A group must have these permissions before it will show here. Can access control panel Can access publish Can access edit Can access Structure
Am logged in as super-admin.
@russlipton You have to have another member group with access to the module and CP for them to show up there. Then you can assign permissions. Super admins default to having all privileges.
Can 1.0.4 use {site_url} for {exp:structure:nav_sub}? Current URLs don’t contain the domain name if install not root.
Example: http://localhost/index.php/services/a_service_we_offer/
I need: http://localhost/domain_name.com/index.php/services/web_digital_media/
@Jack McDade that should be included in 1.0.3 I’ll verify for the next release.
it’s currently using site_index, not site_url. I had to hack the module to give me the proper URL.
@Jack McDade got you. On our list!
Okay so Structure doesn’t play nice with search results. {auto_path} just gives me {site_url}/{url_title}. It doesn’t factor in the other URI segments. Is there a different tag to call or is this a limitation i didn’t factor in?
EDIT: Note to self – bug testing after midnight doesn’t always go so well. Problem solved with {page_url} replacing {auto_path}. Thank you and goodnight.
I just wrote a little extension that plays nice with Structure and thought someone might benefit from it too:
It hides system Hidden Templates (prefixed by “.”) from the dropdown in the Structure Tab of publish and edit. It also works in the Pages Module as well. We’re using it to keep the publish form clean for clients and to keep them from accidentally choosing say “includes/primary_nav” for a new page. We now are showing only a few templates like “site/two_column” and “site/three_column” which our clients really dig.
It requires the JQuery for Control Panel to be enabled. So far it plays well with a bunch of other extensions/modules, but let me know if you hit a snag.
See my thread if you’re interested: http://ellislab.com/forums/viewthread/102253/