Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

Blog Module /

Discuss the Blog Module.

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Archive widget doesn't work

Go to End

22 Posts   6393 Views


Community Member, 7 Posts

19 November 2009 at 9:48pm

Steve could you please give a more specific description about your problem. I can't quiet understand the page refreshing part.
I'm running blog module ver. 0.2 on one of my projects. I have a problem with RSS widget link not showing up on a page. Probably it is somekind of template or maybe even CSS problem. Otherwise everything seems to work.
Are you using Silverstripe 2.3.0 or above? As the blog module requires so.


Community Member, 224 Posts

20 November 2009 at 1:20am

I am running SilverStripe-v2.3.3. I am using blog-v0.2.1.

I think what was described here works - but see also this thread - it worked for me on the Archive issues talked about here...


Community Member, 98 Posts

25 November 2009 at 6:29am

If you want to avoid hacking the code in the Blog classes themselves, stick this in mysite/_config.php:

BlogHolder_Controller::$allowed_actions[] = '2009';

Web Designer Perth

Community Member, 49 Posts

7 April 2010 at 6:04pm

Perfect Tim.



Community Member, 4 Posts

6 May 2010 at 11:00pm

I have another problem with the Archive widget. I chose a monthly archive display for the widget, but if I click on any link of the archive widget I get to my 404-page.

I develop my site on a local drive, so the archive links want to link to "localhost/<ss-root>/news/2010/05/", where "news" is the changed title for "blog".

Tag cloud widget however is working just fine. Any ideas?

(I am using blog 0.3.0 and Silverstripe 2.4)


Community Member, 4 Posts

11 May 2010 at 12:32am

updating the blog module to the latest build fixed that problem. weird. :-)

Go to Top