roller-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Johnson (JIRA)" <nore...@atlassian.com>
Subject [Roller-JIRA] Resolved: (ROL-1536) Upgrading from Roller 1.0 doesn't fix root folder name
Date Sat, 08 Sep 2007 16:01:31 GMT

     [ http://opensource.atlassian.com/projects/roller/browse/ROL-1536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Johnson resolved ROL-1536.
--------------------------------

    Resolution: Fixed

Fixed by: http://svn.apache.org/viewvc?rev=573871&view=rev

> Upgrading from Roller 1.0 doesn't fix root folder name
> ------------------------------------------------------
>
>                 Key: ROL-1536
>                 URL: http://opensource.atlassian.com/projects/roller/browse/ROL-1536
>             Project: Roller
>          Issue Type: Bug
>         Environment: RHEL4, Tomcat 5.5, Java 1.5.0
>            Reporter: Eric L. Wittle
>            Assignee: David Johnson
>             Fix For: 3.1.1, 4.0
>
>
> After upgrading to roller 3.0, the template display of my bookmark folders/links was
imperfect. All of the folders and links were nested within an item named 'top'.
> I looked at the velocity macro showBookmarkLinksList, and it appeared to be special-casing
a folder named 'root'. When I created a new weblog, a folder named 'root' appeared in the
database. So expecting that this was sufficient evidence that the name of the root level folder
had changed at some point, I executed the following sql:
> update folder set name='root' where name='top';
> I restarted roller, and now magically my blogroll folders are no longer nested inside
a folder titled 'top'; each folder and/or bookmark within my root bookmark folder has its
own link. I believe this is the intended behavior.
> It seems like there are two possible solutions. One is to add 'top' to the special case
logic in the macro alongside 'root', the other would be to rename the root link in the upgrade
sql scripts.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://opensource.atlassian.com/projects/roller/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message