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

Version 1.2.1 released with bug fixes for the above issues! Thanks for the help, everyone!

http://www.ngenworks.com/software/ee/structure/

I’m having a problem, and maybe this just isn’t the functionality… but is there a way to exclude certain items/pages from {exp:structure:nav_main}? Is that how the ‘exclude_status=’ string works?

If so how would I go about doing this, there arent any examples in the documentation.

@dreamworld yep, that’s exactly what it’s for. It connects to an entry’s status, so having exclude_status=”hidden” in your tag and then adding a custom status of “hidden” to your weblog’s status group would remove it from the nav. This is a great way to allow clients to add pages that aren’t “live” yet or are confirmation pages you don’t ever want shown in the subnav. PM me if you need more help!

In Structure 1.2 the items that are now in the “themes” folder has changed from previous versions. There aren’t any instructions on where this goes but it looks like you are supposed to put it directly inside the themes folder but the source code looks like it is meant to end up inside EE’s themes folder of whatever cp_theme is being used (and works if you drop it in there). So /themes/cp_themes/default(if this is what you are using)/”structure” goes here

@smartpill thanks! Wow, blew that one. Adding to the docs now. That directory goes inside your current theme under /themes/cp_themes

delet

Anyone know if Structure will work with LG Better Meta? http://leevigraham.com/cms-customisation/expressionengine/lg-better-meta/

delete

@dreamworld let’s keep new functionality thats not part of the core feature set in a new thread please, this will be confusing to people.

Travis, 1.6.1 fixed the reordering and entry_id missing issues we were having, which is great. But something that still seems to be happening, that was happening earlier on, but which we chalked up to the 5.2+ requirement (we’re on Engine Hosting; PHP 5.1.4):

On the Settings page, trying to change permission settings, to add a member group’s permissions, when hitting submit, we get a “server dropped connection” error, the page doesn’t load, and the settings don’t get saved. This was the same problem we were having earlier and asked you about, but I thought it was about the PHP version (even though we were getting an “Out of Memory” error on a MAMP dev box with 5.2.4 doing the same thing). I’m not sure if this is an Engine Host/MAMP problem or Structure.

Thanks, Pete

@Peter Baker check your PMs, we can’t replicate

Hi Travis - great plugin many thanks for sharing.

I had the same errors reported (error 1602)above and have upgraded to v1.2.1, which removes the error and all looks fine in the Control Panel.

But the site has now gone down, with the templates working, but not being able to pull any data using weblog:entries and the URL.

Nothing else was changed from the upgrade and I simply copied the files over the existing ones via FTP. Editing pages via Structure still displays the correct information under the Structure tab.

So I de-installed the module from the module tab, then re-installed it. Obviously this has wiped all the structure information and I’m having to rebuild.

Is there a correct process to upgrade without having to rebuild?

EDIT: Erm, actually it’s more terminal than that - it’s still not working, even after re-creating :(

Another EDIT & solution: All sorted now, tried re-installing v1.2, still the same, re-installed v1.2.1, still the same, then while re-building for the third time, noticed (in the Edit list) that the weblog entries had been changed from open to closed - hence why they weren’t appearing! This isn’t something I use and have the tab hidden, so it can’t be changed. For some reason after the initial update to 1.2.1 they were automatically changed?!?

@Twobelowzero Structure doesn’t change the status unless you delete a page, which just deletes the Structure reference and changes the entry to “Closed.” You can easily add that tab back to that weblog under Admin » Weblog Administration » Weblog Preferences and alter the statuses you need to. Not sure how they changed in the first place. Are you sure you assigned a Status Group to the weblog under Admin » Weblog Administration » Edit Groups? If no group is assigned it will default all entries to closed.

Travis, Spot on - For my content pages which I didn’t want turned off, I didn’t assign the weblog a status group.

Still unsure why the upgrade didn’t work, or more specifically, why the upgrade stopped the content from appearing - possibly the upgrade flipped the entries to “closed”…?

Trouble is I didn’t spot this until I’d uninstalled the module and re-installed while trying to fix it. From what you describe this probably would have caused the entries to change to “closed”, but it’s difficult to tell if it happened during the upgrade or there was another issue stopping the entries from being displayed…?

Thanks,

Peter