Hi,
I have a website in 3 languages using MLEcms, which seems to work great … except with the CGBlog module. On the English Blogs page (alias is 'en-activities'), I have:
In the main Content:
{CGBlog action='detail' detailtemplate='ENdetails' articleid='12'}
In the Sidebar as a table of contents:
{CGBlog detailpage='en-activities' detailtemplate='ENdetails'}
However, when I click on a different blog title in the sidebar, it displays the selected blog on the Home page instead of the English Blogs ('en-activities') page.
On a different website without MLEcms, all works fine, so I’m guessing this problem is CMSmle related, and probably has something to do with how the blog’s URL is created. In CGBlog’s Options settings, I have the following:
URL Template: {$postdate|cms_date_format:'%Y'}/{$postdate|cms_date_format:'%m'}/{$title}
Default detail page: none
Anyone have any ideas how to fix this?
Thanks,
Rainer
CMS Install Information:
CMS Version 1.11.10
CMSMailer 5.2.2
CMSPrinting 1.0.5
FileManager 1.4.4
MenuManager 1.8.6
MicroTiny 1.2.6
ModuleManager 1.5.5
News 2.14.2
Search 1.7.11
ThemeManager 1.1.8
CGExtensions 1.38.6
avplayer 1.3.2
CGSimpleSmarty 1.7.2
Gallery 1.6.1
Showtime 3.4
TinyMCE 2.9.12
FormBuilder 0.7.3
CGBlog 1.12.1
CGFeedback 1.6.5
FrontEndUsers 1.23.2
JM_Forum 1.0.0
JQueryTools 1.2.6
MleCMS 1.11.4
Captcha 0.4.6
(SOLVED sort of)Problem with CGBlog and MLEcms page redirect
(SOLVED sort of)Problem with CGBlog and MLEcms page redirect
Last edited by rab on Fri May 02, 2014 2:49 pm, edited 1 time in total.
Re: Problem with CGBlog and MLEcms page redirect
Are you using pretty URLs? If so I believe that this call won't work as expected:Check CGBlog help under Pretty URLS.
Code: Select all
{CGBlog detailpage='en-activities' detailtemplate='ENdetails'}
"There are 10 types of people in this world, those who understand binary... and those who don't."
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
Re: Problem with CGBlog and MLEcms page redirect
No, not using Pretty URLs.
- fearmydesign
- Power Poster
- Posts: 363
- Joined: Sun Feb 28, 2010 10:54 pm
Re: Problem with CGBlog and MLEcms page redirect
I'm having the same problem using {News} module...
I want a specific category to display on a specific detail page, but it keep ignoring my detailpage call below, and defaults to the "Detail View Settings" deafult page under options. JO Morg, any suggestions or workaround this? I am using Pretty URL's
{News category='Tutorials' detailpage="contact"}
I want a specific category to display on a specific detail page, but it keep ignoring my detailpage call below, and defaults to the "Detail View Settings" deafult page under options. JO Morg, any suggestions or workaround this? I am using Pretty URL's
{News category='Tutorials' detailpage="contact"}
Rod
"Be careful who you step on your way up; because you never know who you'll meet on your way down!" - or something like that.
"Be careful who you step on your way up; because you never know who you'll meet on your way down!" - or something like that.
Re: Problem with CGBlog and MLEcms page redirect
Honestly, no. The OT has MLEcms and the problem appears to be related to that module, although there is not enough info to help debug the issue.fearmydesign wrote:JO Morg, any suggestions or workaround this?
Do you also have MLEcms on your installation?
Although CGBlog is a fork of News (afaik) I'm not sure if their behaviour is similar in this case. It appears that a simple call such as {News category='Tutorials' detailpage="contact"} should work as expected even with pretty URL's.in CGBlog help wrote:Pretty URLS
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.
Not much help from me this time I'm afraid...
"There are 10 types of people in this world, those who understand binary... and those who don't."
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
* by the way: English is NOT my native language (sorry for any mistakes...).
Code of Condut | CMSMS Docs | Help Support CMSMS
My developer Page on the Forge
GeekMoot 2015 in Ghent, Belgium: I was there!
GeekMoot 2016 in Leicester, UK: I was there!
DevMoot 2023 in Cynwyd, Wales: I was there!
Re: (SOLVED sort of)Problem with CGBlog and MLEcms page redi
I copied all CGBlog articles over to the News module - now everything works just fine.