Blog Modules Issues

Topics: Standard packages
May 26, 2011 at 10:49 PM

So bacially im pretty new to Composite C1, i have been using it for about 2months developing my own portfolio website. One of the reason i chose Composite was its simiplicity to use and develop websites, but i have been having a few problems...

So im having a few issues with my blog that i have running on my website. The issues i am having are:

1. When i click on an item in the tag cloud sometime its filters blog posts by that word and sometimes it doesnt, very random and sometimes it will work and then other times it will not, even though the URL has changed.
2. This also happens when i click on the title of the blog posting when i want to read the full article. sometimes it will click through and then sometimes it will stay on the same page.

I find it quite diffuclt to describe my problem in text but have a go on my website...(Few positioning errors in IE 9 ) but firefox is your best bet

http://www.richardgdavies.co.uk/blog.aspx


Would be great if someone could bring the error to light

Thanks Richard
Coordinator
May 27, 2011 at 10:32 AM

Hi Richard

For now, edit /Renderers/Page.aspx and remove line

<%@ OutputCache Duration="60" VaryByParam="*" VaryByCustom="C1Page" %>

 

It is strange that we haven't had this problem before, can you say one what IIS version you're running on, and on what version of Composite C1 ?

May 27, 2011 at 11:18 AM

Thanks for replying so soon, removing that line has seemed to work which is great, i havent tried adding another post yet but will soon. Could it be the way i have set the blog up itself? I have followed the instructions on the Composite C1 website but may have missed something out, I am not really that sure? But for now...

The version of Composite C1 i am using is 2.1.1 and Nuild No. 2.1.4113.99

I am also using IIS 7.5 provided by a shared hosting provider

I hope this can help you.

Coordinator
May 30, 2011 at 1:11 PM

>> I have followed the instructions on the Composite C1 website but may have missed something out, I am not really that sure?

I haven't reproduced this problem locally, but it looks like a caching problem. 

Requests like

http://www.richardgdavies.co.uk/Blog.aspx/2011/05

http://www.richardgdavies.co.uk/Blog.aspx/Web%20Design

Were producing the same cache key (http://www.richardgdavies.co.uk/Blog.aspx/). So i would take 1 minute for cache to expire, so you can see another page, which would also be cached for a minute.

 

Anyway, the related code has been rewritten recently, and in the next release this problem should not appear.