Default section and Front page not the same anymore

azw · 2007-02-04 07:34:35

Yes, separating these meanings/functions would be very helpful.

There’s no reason why we should be stuck with “default”. At the very least we should be able to change it’s name in the admin preferences, just as we can change the name of the location of image files, etc.

Mary · 2007-02-05 09:10:08

At the very least we should be able to change it’s name…

You can: see the top of the sections tab.

azw · 2008-02-06 10:03:42

I’m still concerned about this problem.

As I understand it (please correct me if I’m wrong), that feature at the top of the sections page just lets us change which page template is used. It doesn’t change the name of the home page or its URI.

Is there a way to de-link the home page, and the categories results page? (I have found an easy way to replace the search results with its own section. That’s excellent.)

The problem is that for most static sites, the home page can’t be reused for the “default” page which shows any search or category results. If Textpattern is going to be useful for creating all kinds of sites, this will be an essential feature.

I’d like to see an option in the sections tab that lets you choose a section for the extraneous (non-home page) default uses.

Similarly, it be great to have another option that let you choose which section was the blog-like “front page” (the one that will be used to display the listing of all articles in the way that the current default page does).

In the meanwhile is there a work-around using conditionals or something else? Maybe there’s a way to display just my specific home page content if the home page is accessed, and also to make that specific home page info disappear if the search or categories features are called?

colak · 2008-02-06 10:27:13

you can use glx_if

els · 2008-02-06 18:17:53

azw wrote:

Maybe there’s a way to display just my specific home page content if the home page is accessed, and also to make that specific home page info disappear if the search or categories features are called?

<txp:if_search>
   ... search results ...
<txp:else />
   <txp:if_category>
      ... category list ...
   <txp:else />
      ... front page ...
   </txp:if_category>
</txp:if_search>

tennapel · 2010-02-16 11:34:33

It would be very useful if any of the sections can be assigned as ‘default’. Now, you have to jump through hoops to generate a section-list as a navigation item on your website if you want to address one of the sections as the ‘home’ page and not use the homepage as an aggregator page.

The current default mechanism also makes it less flexible in the sense that you have to tinker with section-names in your templates or forms to make a section-based navigation item on your website for example this. For example, I want to designate ‘section_a’ as my default section

<ul id="nav">
<txp:if_section name="default">
    <li>
        <a href="<txp:site_url /><txp:section name="section_a" />/"><txp:section title="1" name="section_a" /></a>
    </li>
    <txp:section_list sections="section_a, section_b, section_c, section_d" break="">
        <li>
            <a href="<txp:site_url /><txp:section />/"><txp:section title="1" /></a>
        </li>
    </txp:section_list>
<txp:else />
    <txp:section_list sections="section_a, section_b, section_c, section_d" break="">
        <li>
            <a href="<txp:site_url /><txp:section />/"><txp:section title="1" /></a>
        </li>
    </txp:section_list>
</txp:if_section>
</ul>

I use the same template for all pages and use some rerouting in the template to pull in the same form for both the ‘default’ and the ‘section_a’ sections. Currently, this is the only way I know how to pull this off and it isn’t very uncommon for a website to explicitly define what the frontpage should be.

ps1: I am aware that you can use the ‘default’ as the ‘section_a’ page and do some renaming of the section display name in the section list with a few if_statements, but from a user perspective I find it hard to explain that an author has to assign the value ‘default’ in the sections dropdown while writing an article, to put it in ‘section_a’, that’s a very unfriendly workflow.

ps2: I am not suggestion to leave the default mechanism, since it has it use when the homepage is an aggregator page, I am suggestion to have an override mechanism.

Textpattern CMS

Textpattern CMS support forum

#16 2007-02-04 07:34:35

Re: Default section and Front page not the same anymore

#17 2007-02-05 09:10:08

Re: Default section and Front page not the same anymore

#18 2008-02-06 10:03:42

Re: Default section and Front page not the same anymore

#19 2008-02-06 10:27:13

Re: Default section and Front page not the same anymore

#20 2008-02-06 18:17:53

Re: Default section and Front page not the same anymore

#21 2010-02-16 11:34:33

Re: Default section and Front page not the same anymore

Board footer