CMS Made Simple Forums

Hi,

I'm using Section Headers with pretty URLs in 1.9.2. I'm aiming for the following (URL-) structure: What I get is: Besides, if you call just /page/section-[number/ID] without the page you get: which is not ideal. This should IMO either be a redirect to the first child of a page section (301 Redirect) or a 404.

While the second issue is not that important to be solved, I see the first as a bug because I, for example, can't create URLs with the year as section-headers. It would give me /page/2009-1/sub-page, /page/2010-2/sub-page etc.

Or am I missing the option of defining the alias for a section header?

thanks,
Reto

Ah, I see. My very specific problem is, that the alias cannot be a number. Well, that's a pitty. Editing the alias for section headers would still be nice. And the second issue still exists, of course.

reto wrote: Besides, if you call just /page/section-[number/ID] without the page you get:

Code: Select all

string(51) "Smarty error: unable to read resource: "tpl_top:-1"" string(52) "Smarty error: unable to read resource: "tpl_head:-1"" string(52) "Smarty error: unable to read resource: "tpl_body:-1"

I'm having this same problem. I'm using CMSMS v1.9.3
Thanks in advance for any advice on this.

Sections cannot be linked at the moment. You may either substitute sections with real pages or manually link to the first child of the section.

I think this needs a fix, but didn't get a feedback so far.

The work around for making aliases for section headers is to start with content type content, make alias then choose section header content type...

I'm seeing this on a dual-language site I'm working on, but it is only intermittently that this occurs. I'm using the module Babel and English and Chinese. I've set up section headers for English and Chinese and it seems to work fine and dandy, except every once in awhile it will choke and spit out this code: If I navigate back to the domain itself, and click Chinese, it's fine. It seems to only happen when I'm flipping back and forth. I'll try that fix with the content you suggested and see if that solves it.