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

So, to be sure, this module is or is not MSM friendly?

I’ve been testing Structure out on an MSM site and tried setting up a dummy new site. What happens is that the structure page showing the hierarchy of all entries is only applied to the initial site. The structure tab still appears when creating/editing entries in the new site, but you can only access/create entries in the new site via the default EE publish/edit tabs, which means that it kinda becomes just the same as the normal pages module for other sites in the MSM.

OK, that makes sense. So, the AJAX request has the wrong path to the system?

@mdupre the AJX request is saving the page data after moving it. Do you have MSM installed on the site you’re having the issue on? The module is currently untested with MSM so that may be the root of the issue.

@Tyssen once your site hierarchy is in place you can add and access all entries through the Structure interface - that’s it’s main draw. I’m not sure what’s going wrong with your install. You may need to resave all the old entries to get them to show up within Structure. This module is really meant to use when you begin development and is a different way to build, not so much an addition,

@mdupre the AJX request is saving the page data after moving it. Do you have MSM installed on the site you’re having the issue on? The module is currently untested with MSM so that may be the root of the issue.

MSM is installed. The response I get is 404 from the request. If I change the path to the correct system it should work shouldn’t it?

@Tyssen once your site hierarchy is in place you can add and access all entries through the Structure interface - that’s it’s main draw. I’m not sure what’s going wrong with your install. You may need to resave all the old entries to get them to show up within Structure. This module is really meant to use when you begin development and is a different way to build, not so much an addition,

Sorry, I described what was happening incorrectly. Setting up a new site and duplicating entries/templates does show the Structure tab with the site hierarchy the same as the default site, but the View Page links all point to the root of the site (ie no unique page URIs as they are for the default site) and when clicking on a page name to edit it or the Add page link gives an ‘You are not authorized to post in this section’ error. I can only access the entries through the usual Edit tab.

Also when creating the new site, MSM asks you which entries you want to move/duplicate - I only specified a certain weblog when creating the new site, but the Structure tab for the new site is populated with all the entries from the default site.

This module is really meant to use when you begin development and is a different way to build, not so much an addition

Yep, that’s what I’m doing - starting from scratch with a new site.

@mdupre that’s probably it. I’m not sure on the path change as its untested and I’m not familiar with MSM. If you can, do a single test install without MSM so we can see if it’s your environment or not. Then we have a free environment to test in if it pops up again and less variables to worry about it being caused by.

@Tyssen but you’re using or created the site with MSM if I understand correctly. Once again, untested, but I’m looking into when we can work on a version that’s MSM compatible and tested.

Yes, that’s right. I installed EE, installed MSM, did some basic config stuff, then installed Structure and began building the default site.

@Tyssen Sorry to keep repeating, but it’s not tested with MSM. I haven’t even used MSM so I can’t speak to what could cause the problem, but it sounds lie that’s it. If you want to try a test install without MSM let me know the results so we can narrow the issue. PM me if you have more questions and your install.

@Tyssen Sorry to keep repeating, but it’s not tested with MSM.

Yes, I understand that. I’m just trying to provide more info to help clarify the issue that the posters mentioning MSM issues might be experiencing.

The module works fine with MSM installed, but only for the first site - the default one - that you set up. It’s only when you add additional sites that the same functionality doesn’t get carried across to the new site.

I could try setting up a new site without MSM and Structure, but it would be the same as what I’ve already got - it works fine on the first/default site.

@mdupre that’s probably it. I’m not sure on the path change as its untested and I’m not familiar with MSM. If you can, do a single test install without MSM so we can see if it’s your environment or not. Then we have a free environment to test in if it pops up again and less variables to worry about it being caused by.

OK, I was way off base and not thinking properly. As it turns out the index.php had been renamed! The index.php is properly named now and the Structure Module control panel seems to be working properly with MSM.

The templates still need to be created but we will keep you updated on the progress.

@Tyssen sorry! I got you, wasn’t reading correctly I guess. SO it’s confirmed we need to release a MSM update 😊 Stay tuned we’re talking about next updates and features internally soon and will try to get some timeframes. Updates aren’t a priority until another few weeks most likely. Thanks for the help!

@mdupre Def keep me updated if you can get another MSM site working, but it seems like Tyssen above has confirmed it chokes…Thanks!

The pages module is much less userfriendly than structure, however it’s very handy if I can limit structure to just my static pages weblog. I’ve come up with a quick and dirty hack, it could be done much better by making the weblog_id configurable and so on..

Basically, structure only works on entries that have been submitted after structure has been installed. So structure won’t effect other entries if no structure records are added for that entry. The easiest way to prevent this is in the ext.structure_ext.php.

1. At the top of the class add a new var with the weblog_id you want to use (all others are ignored): var $weblog_id = 6; I’ve done my check so that if I change the welog_id to false all is normal again.

2. Add a check (if($weblog_id == $this->weblog_id OR $this->weblog_id == false){ … } ) in following functions:

   • add_publish_tab (dont show tab)
   • add_publish_tab_block (dont show form)
   • publish_submit_end (don’t add new structure record) - use $data[‘weblog_id’] instead of $weblog_id
   • publish_tab_block_validate (don’t validate the removed form) - use $data[‘weblog_id’] instead of $weblog_id

Cool solution frenzal! That should help people out until a feature can be released. Team work!

@rockthenroll

I havn’t tried your module yet, but it’s exactly what I need! Do you have any example sites up that are using this module so I can see a working example of the site structure in action?

Keep up the good work. This is great news!