we have roller 4.0 http://blogs.mervpolis.com
will try to upgrade to 5.0 the old 5.0b, make several user cannot login and blog will update shortly F On Tue, Oct 12, 2010 at 8:11 PM, Dave <[email protected]> wrote: > On Sun, Oct 10, 2010 at 6:53 AM, Frans Thamura <[email protected]> wrote: >> just wanna to know. when will 5.0 released? > > Once all issues that we want to resolve are resolved and we have > enough feedback from the community then we'll vote it out. Personally, > I think we are very closed and should probably call for a release vote > on the next RC. > > For those out there waiting for 5.0: have you tried 5.0 and made sure > it works for you, provided feedback, reported bugs etc.? > > - Dave > > > >> On Fri, Oct 8, 2010 at 7:27 PM, Dave <[email protected]> wrote: >>> Congrats on working out the multi-domain setup! I was afraid you were >>> about to give up ;-) >>> >>> Yes, that is a known bug in RC2. A couple of paths that were supposed >>> to start with ${user.home} got hardcoded to '/home/dave'. The >>> workaround is to set properties to point to the directory in which you >>> want mediafile uploads stored: >>> >>> mediafiles.storage.dir= ... PATH TO MEDIA FILES DIR ... >>> search.index.dir= ... PATH TO SEARCH INDEX ... >>> >>> (I think you already fixed the search.index.dir one) >>> >>> I usually create a roller_data directory somewhere with subdirectories >>> for mediafiles and search-index. >>> >>> Hope that helps... >>> >>> - Dave >>> >>> >>> >>> On Fri, Oct 8, 2010 at 2:26 AM, Christopher Dodunski >>> <[email protected]> wrote: >>>> Hi Dave, >>>> >>>> Also, an error was reported when attempting to upload media and switch to >>>> custom theme... >>>> >>>> Unexpected Exception >>>> Status Code 500 >>>> Message org.apache.roller.weblogger.business.FileNotFoundException: >>>> Invalid path [/home/dave/roller_data/mediafiles/isaac], directory doesn't >>>> exist. >>>> Type >>>> Exception Roller has encountered and logged an unexpected exception. >>>> >>>> Is there a work around for this? >>>> >>>> Regards, >>>> >>>> Chris. >>>> >>>> >>>>> That is a known bug, which will be fixed in the next RC. You can work >>>>> around it by setting the 'search.index.dir=' to the place where you >>>>> want your search index created. >>>>> >>>>> Thanks, >>>>> Dave >>>> >>>> >>> >> >
