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

@jmobley 1) Did you enable the extension? 2) Do you have enough memory? Try adding this to your htaccess file: php_value memory_limit 16M (or more for the MB value)

Answers:

1) – yes…that produces a blank screen as well. So both attempting to enable the module and the extension blanks out & makes white screen. 2) - I tried adding this to my .htaccess, but that brought whole site down w/ a 500 Internal Server Error

@jmobley You must not have enough memory, contact your host and see what they can do about it.

I just found a bit of oddness with Structure that I think might be a bit of a bug.

So I was cutting and pasting some content from a client into some weblog entries. After I posted the weblog entries, I noticed on some the comment form would appear and some would not. Weird.

After messing with the comment form a million ways, I started looking around elsewhere.

I realized that on the pieces without the comment form, there was an extra space at the end of the title. It got included when I pasted them into the form. EE deletes that space when making urls but Structure turns that into an underscore. Once I changed the Structure URL to not have the underscore at the end, everything was fine.

It’s definitely an operator error to put an extra space in there at the end, but EE compensates for dumb-dumbs like me by knocking it off before making a url. Structure should be similarly dumb-dumb proof.

@toddajackson Very odd. Is this within Structure managed templates? I’ll need to get inside to see what you’re talking about a bit more.

@toddajackson Very odd. Is this within Structure managed templates? I’ll need to get inside to see what you’re talking about a bit more.

I believe so. The post was set up as a “listing” for a static content page. I just tested it again and if I add an extra space, EE deletes that space, but Structure does not and it creates a discrepancy that makes the Comment Form not appear on the page.

If I take away the space from the Structure URL the Comment Form appears on the listing page. Perhaps there’s a parameter I’m missing on the Comment Form that would prevent this, but since it seems like it’s fixed by changing the Structure URL to match the URL_title, I’m thinking there’s the rub.

Todd

@toddajackson So can you just remove the spaces then?

Oh yeah, remove the space at the end in the Structure tab and bam it works.

But I’m concerned a client won’t do that or will miss that. If EE strips out the last space and Structure doesn’t, I can see unending frustration in someone else’s future. (Not mine, cuz I know now)

Of course, I think I saw back in this thread that you use EE’s template system rather than structure when working with comment forms. So maybe that’s the solution here… just prevent it from coming up.

Todd

@toddajackson I’ll add removing spaces to our list for a future version. It’s edge case, but you’re right could be frustrating.

Hi rockthenroll, Had some success with modifying structure to fit the MSM/language needs but there’s still this last bit which is a bit confusing

/foo/sub_page/ will display the sub_page entry right? But say you want to use a prefix to this, like /en/foo/sub_page/ to pull the exact same page, is there something in the get_data method you have to change(even though it mostly seems to have to do with the admin)? Or where does the {exp:weblog}-tag pulling the entry-data and structure actually work together?

Cheers, Chris

Travis,

I would love some more info about the release of Structure 2.0. According to your twitter it should be close, but are we days, weeks or months from there? Another hint would really be appreciated as I’m using Structure for a project with launch in early december. And the possibilty to use different field groups would really make a difference here.

Thanks!

@rollingoptics Structure 2 is only days away, probably late this week. As far as “different field groups” I’m not sure what you mean as field groups don’t have anything to do with Structure…

Cool, that’s great news!

And what I meant was the same chichilatte was asking about a few pages back, and you replied that it will be included in Structure 2:

Is there no way Structure can ask you what *kind* of page you want to create when you click “Add page”? Adding a page with the exact same fieldgroup as its parent is, well, kind of useless, right?

Not sure if I get both of you wrong, but I guess I’ll just wait for the upcoming version and see what’s in it, now that I know it is close.

Thanks for your quick reply!

Ahh sorry I misunderstood! Yes, that is in version 2 and is pretty sweet if I say so myself. It’s smart enough to know if there is more than one available weblog to add a page to and defaults to the only available one if there is only one. It of course filters the listing weblogs out as well, so you don’t have content issues. Can’t wait to release this!

I’m experiencing a problem with the url_title matching the Structure Page URL. I’ve noticed that if there’s a period in an entry title EE will include that period in the URL title, but Structure will remove it. Also, if a title is very long EE will truncate it but Structure will not truncate it. These discrepancies cause permanlinks in the templates to not direct the user to the correct single entry pages. Is there a way around this, or a fix available?