CMS Made Simple Forums

Code: Select all

<section class="main items">
  {CGBlog category="Portfolio" summarytemplate="PortfolioSummary" detailtemplate="PortfolioDetail" }           
</section>
        
<section class="main ArchBlogPostItems">
 {CGBlog category="Articles" summarytemplate="BlogSummary" detailtemplate="BlogDetail" }    
</section>

Code: Select all

Pretty URLS are ideal for websites where search engine optimization is a real concern. It provides a shorter, friendlier URL that search engines will treat better, and that are easier to share. However they come at a cost. Particularly, many of the parameters specified in the call to CGBlog, that should be passed down to another view via a link cannot be passed on a pretty url.

For example, when pretty urls are not enabled it is possible to call the browsecat action like this: {CGBlog action=browsecat summarytemplate=somesummary detailtemplate=somedetail detailpage=mydetailpage pagelimit=25 sortby=cgblog_extra sortorder=asc}. Now when the browsecat action generates its display, including links to summary views for each category, it should pass the summarytemplate,detailtemplate,detailpage,paglimit,sortby, and sortorder parameters along on the URL For the resulting summary view to use. However, it is not possible to pass these parameters on a pretty URL, and to keep them "pretty"

To that end, it is possible to provide default values for most of these parameters via the CGBlog admin console. This however, limits the flexibility of the module in some ways. Another possibility is to use the {cge_module_hint} tag to provide behavioral hints to the module on destination pages.

Code: Select all

{cge_module_hint module=CGBlog detailtemplate=sports}