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

I’m getting a an error when trying to change access permissions to add a member group to have access to Structure.

Wow, and just realized this error causes all Structure associated weblog info (structure/assets/unmanaged) to go back to unmanaged, losing all the listing associations too. Yikes.

@Peter Baker PHP 5.2+ is required

@Peter Baker PHP 5.2+ is required

Yeah, like I said, I got the error first on PHP 5.2.6.

@Peter Baker check your PMs

I’ve got to say, so far my test client’s loving working with Structure - great job, folks!

We’ve run into a small hiccup, though, involving records with very long titles. Specifically, there’s a conflict with the length of content accepted by the URL Title and Structure URI fields. When an item’s title is longer than 77 characters, including spaces (converted to hyphens), EE truncates, while Structure continues accepting characters (or rather, continues converting title characters to URI ones). As a result, content managed by Structure becomes inaccessible unless the content creator manually overrides the Structure URI field.

Ideally Structure would use whatever data appeared in the URL Title field to construct default Structure URI data (where the user hasn’t specifically input a URI), but I gather that is currently not the case.

Other than advising my client to create a custom URL title for long-titled records and copy&pasting;it into the Structure URI field, is there any advice you might have for dealing with this?

Thanks!

Once again sorry if this has been covered, but I’ve run into an issue with using this module and the built-in search functionality. The problem is that search results use the path settings in the weblog preferences. So technically the results will link to a page, but if you’re using url segments for any reason, then suddenly the pages break.

For example - the weblog that structure is using is named “page” and in the path settings for my ‘page’ weblog I’ve got the search results path set as /page/. I’ve got a page called small_grants, and that is a child of grants. So my normal (structure generated) url is www.website.com/grants/small_grants/ . If I search for and find that page, instead of linking to /grants/small_grants, it links to /page/small_grants - which while showing the correct page, breaks anything that uses the url segments - including the structure breadcrumb (and I’d assume main nav although I don’t use that tag). I’m also generating sidebars based on the first segment, so that breaks (I lose my subnav completely).

How are people handling search results links and structure? Am I missing something? What I really need is just a way to generate the structure URL for an entry - is there a way to do that? I was thinking I might use the parent title and start doing DB searches on that and build the URL, but we could potentially be down more than 2 levels so it wouldn’t work anyway I don’t believe?

Help? Thanks in advance 😊

@mkuplens can you use {page_uri} or {page_url} to access the pages instead?

@Brian M. we almost always use {page_uri} or {page_url} instead of the permlink tags within the results template. Through Structure, most of the path settings under weblog prefs don’t even matter.

@Brian M. we almost always use {page_uri} or {page_url} instead of the permlink tags within the results template. Through Structure, most of the path settings under weblog prefs don’t even matter.

Awesome! This is probably dumb, but what’s the difference between them?

@Brian M. {Page_url} is the full address like “http://your-site.com/whatever/something”, while {page_uri} is just “/whatever/something”

Thanks again Travis - best module ever built, hands-down.

[My first time posting in this thread so I must give thanks for this excellent module! Being able to create all my templates for different sections of the site in one Template group, and not having to worry about what they are called, is saving me so much headache surrounding the whole URL structuring thing!]

I think I may have found a bug, though I’m surprised that noone else has stumbled upon this yet (though I could have missed it in this mammouth thread!).

I set up the Structure module fine and it was working for me, but when my client/Administrator (who is in a different member group) added new listings, the page_uri was wrong. Instead of giving the URI ‘section/name-of-entry’, it gave the URI just as ‘name-of-entry’ so obviously the link didn’t work.

Turns out this was happening because I had set the Permissions in the Structure > Settings to NOT allow this member group to “View publish/edit Structure tab” (since the Structure URI gets auto-created from the Title I didn’t think they needed to see that). Now I have checked this box to allow them to view it, when they add a new entry now the URI path is correct.

Oh dear, now I have another bug/problem to report!

Summary: Listings weblog defaults to first available Weblog when editing Static page with an associated listing.

When I go to edit the static page which has a listing attached to it, the Weblog dropdown (under the Structure tab) for the listings shows NOT the weblog I had selected to be used for the associated listing. So if I don’t notice this and change it to the right one, it means that next time I go to add/edit a listing entry, the wrong weblog entry form appears. (and all sorts of screwy things happen to those entries, which has taken me a long time to fix, but I won’t bore you with that here!)

I have a question about setting up monthly archives within Structure. I’ll explain my setup thus far:

I have 3 “traditional” blogs on my site. I set up a template group called “blogs” with the following templates: index, article, blog1, blog2, blog3. I created a blog, managed by Structure, called “Blogs” which will have 4 entries:

Entry 1: this is the index page that shows the most recent entries from all 3 blogs. It uses the blogs/index template (url: www.domain.com/blogs/) Entry 2: this is the listing entry for blog1. It uses the blogs/blog1 template to list the most recent entries from blog1 (url: www.domain.com/blogs/blog1/) Entry 3: this is the listing entry for blog2. It uses the blogs/blog2 template to list the most recent entries from blog2 (url: www.domain.com/blogs/blog2/) Entry 4: this is the listing entry for blog3. It uses the blogs/blog3 template to list the most recent entries from blog3 (url: www.domain.com/blogs/blog3/)

The blogs/article template is used to display any single entry from blog1, blog2, or blog3.

I have a template called global/weblog-monthly-archives that embeds the following code into the sidebar of any of my blog listing or blog detail pages. (global is the template group that holds all my embeddable templates)

<h3>Monthly Archives</h3>
<ul>
   {exp:weblog:month_links weblog="{embed:the_weblog}"}
   <li><a href="http://{path=">{month}, {year}</a></li>
   {/exp:weblog:month_links}
</ul>

Note: the the_weblog, the_template_group variables are set in the template that calls global/weblog-monthly-archives (they are set in any of the following: blogs/article, blogs/blogs1, blogs/blogs2, blogs/blogs2)

Right now, when I click on a monthly archive link, e.g. www.domain.com/blogs/blog1/2009/03/ it takes me to a page, which I believe uses blogs/blog1 template (in this case). The problem right now is that is lists all of the blog entries (up to the limit which I set at 15), regardless of the month. So, for example, right now I have 10 entries (in the blog1 blog), 8 of which are from 03/2009 and 2 of which are from 04/2009. The archive page for 03/2009 is listing all 10, from both 03/2009 and 04/2009.

I don’t mind having the archives listed in the blogs/blogs1 template. Or I can create another template called archives so instead of having the following url:

www.domain.com/blogs/blog1/2009/03/

I would have:

www.domain.com/blogs/blog1/archives/2009/03/

Either way is fine as far as I’m concerned. However, I am unsure how to set this up in Structure. I’m sitting here figuring I am missing the painfully obvious, but could someone give me some guidance on how to set up the monthly archives in Structure so that it displays the entries only from the month selected?