You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@roller.apache.org by Dave Johnson <da...@rollerweblogger.org> on 2005/11/14 05:32:58 UTC
Time for Roller 2.0 RC2?
Thanks to our testers, over the weekend we've found and fixed these:
* removed session-factory name argument from Hibernate configuration
file
* restored missing create-user page
* restored missing weblog maintenance page
* added cache flush to save of bookmarks
* fixed array-index out of bounds problem when no default blogroll
defined
Are we ready for a new RC, or is there some other evil lurking?
- Dave
Re: Time for Roller 2.0 RC2?
Posted by Anil Gangolli <an...@busybuddha.org>.
Henri Yandell wrote:
>Spent the end of the evening working on Roller. Installation went
>fine. We QA'd the New Registration page. Nothing huge, just spelling
>mistakes and the confusing default of 'Front Page' for the site short
>name (let me know if my change to 'Roller' was presumptuous).
>
>Carrie and I are testing out a lightweight QA process. Before she
>spent the last year taking care of our baby, Carrie was a
>web-editor/QA tester. So we're looking into coming up with something
>that feels right in terms of light, open-source style agility.
>
>Not sure it's as lightweight as we'd want; took an hour to do 1 page
>:) But that included fixing it etc.
>
>---
>
>When I try to invite someone to my blog, I get:
>
> User successfully invited
>ERROR: Notification email(s) not sent, Roller's mail session not
>properly configured
>
>Three issues here:
>
>1) I can't find anything detailing how to set that up in the wiki
>install doc, or the install faq.
>
>
Yes. It needs more explanation. There is only a comment in the sample
context xml files.
>2) The machine is running smtp on localhost, so I would have thought
>it should have worked by default
>
>
The mail/session resource needs to be set up in the context.
>3) The successfully invited bit means it won't let me invite them
>again. ie) it saw the error but didn't rollback the invitation.
>
>
Yes it should not commit until after the send succeeds. There's still a
chance that the mail get to the first relay and encounter some problem.
There should be a way to resend the invitation.
>Hen
>
>On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>
>
>>Thanks to our testers, over the weekend we've found and fixed these:
>>
>>* removed session-factory name argument from Hibernate configuration
>>file
>>* restored missing create-user page
>>* restored missing weblog maintenance page
>>* added cache flush to save of bookmarks
>>* fixed array-index out of bounds problem when no default blogroll
>>defined
>>
>>Are we ready for a new RC, or is there some other evil lurking?
>>
>>- Dave
>>
>>
>>
>>
>
>
>
>
Re: Time for Roller 2.0 RC2?
Posted by Henri Yandell <fl...@gmail.com>.
Spent the end of the evening working on Roller. Installation went
fine. We QA'd the New Registration page. Nothing huge, just spelling
mistakes and the confusing default of 'Front Page' for the site short
name (let me know if my change to 'Roller' was presumptuous).
Carrie and I are testing out a lightweight QA process. Before she
spent the last year taking care of our baby, Carrie was a
web-editor/QA tester. So we're looking into coming up with something
that feels right in terms of light, open-source style agility.
Not sure it's as lightweight as we'd want; took an hour to do 1 page
:) But that included fixing it etc.
---
When I try to invite someone to my blog, I get:
User successfully invited
ERROR: Notification email(s) not sent, Roller's mail session not
properly configured
Three issues here:
1) I can't find anything detailing how to set that up in the wiki
install doc, or the install faq.
2) The machine is running smtp on localhost, so I would have thought
it should have worked by default
3) The successfully invited bit means it won't let me invite them
again. ie) it saw the error but didn't rollback the invitation.
Hen
On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> Thanks to our testers, over the weekend we've found and fixed these:
>
> * removed session-factory name argument from Hibernate configuration
> file
> * restored missing create-user page
> * restored missing weblog maintenance page
> * added cache flush to save of bookmarks
> * fixed array-index out of bounds problem when no default blogroll
> defined
>
> Are we ready for a new RC, or is there some other evil lurking?
>
> - Dave
>
>
Re: Time for Roller 2.0 RC2?
Posted by Dave Johnson <da...@rollerweblogger.org>.
Thanks for the reminder. I'll do that right after I upload the release
whose name and number shall not be spoken.
- Dave
On Nov 15, 2005, at 3:30 PM, Allen Gilliland wrote:
> I want send another reminder about doing this merge. I know for a
> fact that the ThemeEditorAction.java in the 1.x branch has code that
> isn't in the ThemeEditorAction in the 2.x trunk.
>
> -- Allen
>
>
> On Mon, 2005-11-14 at 14:18, Allen Gilliland wrote:
>> can we also do a full merge of the 1.3 branch into the 2.0. luckily
>> i just noticed that one of the final changes that i made in the 1.3
>> branch hasn't actually been merged into 2.0.
>>
>> -- Allen
>>
>>
>> On Mon, 2005-11-14 at 10:10, Dave Johnson wrote:
>>> On Nov 14, 2005, at 12:42 PM, Allen Gilliland wrote:
>>>
>>>> This is a point of debate actually.
>>>
>>> I don't debate this one anymore. I agree with Allen and Matt that
>>> pages
>>> should have the tabs.
>>>
>>>
>>>> We can probably handle this one in Roller 2.1 since it would
>>>> require a
>>>> reasonable amount of work to put all these pages back into the tab
>>>> structure.
>>>
>>> Yeah, I think it's too late to fix this for 2.1.
>>>
>>> - Dave
>>>
>>>
>>>>
>>>> -- Allen
>>>>
>>>>
>>>> On Sun, 2005-11-13 at 21:07, Matt Raible wrote:
>>>>> Is the menu (tabs) supposed to always show up for users. I noticed
>>>>> that it doesn't show up when editing categories, nor bookmarks.
>>>>>
>>>>> Matt
>>>>>
>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>> When trying to upgrade from 1.3 to 2.0 using the
>>>>>> 130-to-200-migration.sql script, I got an error:
>>>>>>
>>>>>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index';
>>>>>> check
>>>>>> that column/key exists
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>>> I should mention my prod and test environments:
>>>>>>>
>>>>>>> Production on Linux:
>>>>>>>
>>>>>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>>>>> Tomcat 5.0.28
>>>>>>> JDK 5
>>>>>>>
>>>>>>> Testing on OS X:
>>>>>>>
>>>>>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>>>>> Tomcat 5.5.9
>>>>>>> JDK 5
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as
>>>>>>>> 2.0
>>>>>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only
>>>>>>>> found
>>>>>>>> one issue.
>>>>>>>>
>>>>>>>> On raibledesigns.com, if you scroll to the bottom of the page,
>>>>>>>> there
>>>>>>>> will be a link on the left side that allows you to navigate to
>>>>>>>> the
>>>>>>>> previous entry. It seems like it's a bug in 1.2 that I can only
>>>>>>>> navigate to the single previous entry, rather than a list of
>>>>>>>> entries.
>>>>>>>> In 1.3, there is no link at all. Did this functionality get
>>>>>>>> removed
>>>>>>>> in 1.3?
>>>>>>>>
>>>>>>>> Also, comparing my raibledesigns.com blog to my jroller.com
>>>>>>>> blog, I
>>>>>>>> noticed there are no navigation links to go to next/prev/main
>>>>>>>> when
>>>>>>>> viewing a single entry.
>>>>>>>>
>>>>>>>> I was able to fix this by adding in "#showNextPreviousLinks()"
>>>>>>>> to
>>>>>>>> my
>>>>>>>> theme. However, my main page is _sunsets and is not displayed
>>>>>>>> as a
>>>>>>>> menu item - but it does show up as the name to navigate back to
>>>>>>>> from
>>>>>>>> the #showNextPreviousLinks() macro.
>>>>>>>>
>>>>>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in
>>>>>>>> less
>>>>>>>> than an hour.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org>
>>>>>>>> wrote:
>>>>>>>>> Thanks to our testers, over the weekend we've found and fixed
>>>>>>>>> these:
>>>>>>>>>
>>>>>>>>> * removed session-factory name argument from Hibernate
>>>>>>>>> configuration
>>>>>>>>> file
>>>>>>>>> * restored missing create-user page
>>>>>>>>> * restored missing weblog maintenance page
>>>>>>>>> * added cache flush to save of bookmarks
>>>>>>>>> * fixed array-index out of bounds problem when no default
>>>>>>>>> blogroll
>>>>>>>>> defined
>>>>>>>>>
>>>>>>>>> Are we ready for a new RC, or is there some other evil lurking?
>>>>>>>>>
>>>>>>>>> - Dave
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>
>>>
>>
>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
I want send another reminder about doing this merge. I know for a fact that the ThemeEditorAction.java in the 1.x branch has code that isn't in the ThemeEditorAction in the 2.x trunk.
-- Allen
On Mon, 2005-11-14 at 14:18, Allen Gilliland wrote:
> can we also do a full merge of the 1.3 branch into the 2.0. luckily i just noticed that one of the final changes that i made in the 1.3 branch hasn't actually been merged into 2.0.
>
> -- Allen
>
>
> On Mon, 2005-11-14 at 10:10, Dave Johnson wrote:
> > On Nov 14, 2005, at 12:42 PM, Allen Gilliland wrote:
> >
> > > This is a point of debate actually.
> >
> > I don't debate this one anymore. I agree with Allen and Matt that pages
> > should have the tabs.
> >
> >
> > > We can probably handle this one in Roller 2.1 since it would require a
> > > reasonable amount of work to put all these pages back into the tab
> > > structure.
> >
> > Yeah, I think it's too late to fix this for 2.1.
> >
> > - Dave
> >
> >
> > >
> > > -- Allen
> > >
> > >
> > > On Sun, 2005-11-13 at 21:07, Matt Raible wrote:
> > >> Is the menu (tabs) supposed to always show up for users. I noticed
> > >> that it doesn't show up when editing categories, nor bookmarks.
> > >>
> > >> Matt
> > >>
> > >> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > >>> When trying to upgrade from 1.3 to 2.0 using the
> > >>> 130-to-200-migration.sql script, I got an error:
> > >>>
> > >>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> > >>> that column/key exists
> > >>>
> > >>> Any ideas?
> > >>>
> > >>> Matt
> > >>>
> > >>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > >>>> I should mention my prod and test environments:
> > >>>>
> > >>>> Production on Linux:
> > >>>>
> > >>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> > >>>> Tomcat 5.0.28
> > >>>> JDK 5
> > >>>>
> > >>>> Testing on OS X:
> > >>>>
> > >>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> > >>>> Tomcat 5.5.9
> > >>>> JDK 5
> > >>>>
> > >>>> Matt
> > >>>>
> > >>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > >>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> > >>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
> > >>>>> one issue.
> > >>>>>
> > >>>>> On raibledesigns.com, if you scroll to the bottom of the page,
> > >>>>> there
> > >>>>> will be a link on the left side that allows you to navigate to the
> > >>>>> previous entry. It seems like it's a bug in 1.2 that I can only
> > >>>>> navigate to the single previous entry, rather than a list of
> > >>>>> entries.
> > >>>>> In 1.3, there is no link at all. Did this functionality get
> > >>>>> removed
> > >>>>> in 1.3?
> > >>>>>
> > >>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> > >>>>> noticed there are no navigation links to go to next/prev/main when
> > >>>>> viewing a single entry.
> > >>>>>
> > >>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to
> > >>>>> my
> > >>>>> theme. However, my main page is _sunsets and is not displayed as a
> > >>>>> menu item - but it does show up as the name to navigate back to
> > >>>>> from
> > >>>>> the #showNextPreviousLinks() macro.
> > >>>>>
> > >>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> > >>>>> than an hour.
> > >>>>>
> > >>>>> Matt
> > >>>>>
> > >>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > >>>>>> Thanks to our testers, over the weekend we've found and fixed
> > >>>>>> these:
> > >>>>>>
> > >>>>>> * removed session-factory name argument from Hibernate
> > >>>>>> configuration
> > >>>>>> file
> > >>>>>> * restored missing create-user page
> > >>>>>> * restored missing weblog maintenance page
> > >>>>>> * added cache flush to save of bookmarks
> > >>>>>> * fixed array-index out of bounds problem when no default blogroll
> > >>>>>> defined
> > >>>>>>
> > >>>>>> Are we ready for a new RC, or is there some other evil lurking?
> > >>>>>>
> > >>>>>> - Dave
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
can we also do a full merge of the 1.3 branch into the 2.0. luckily i just noticed that one of the final changes that i made in the 1.3 branch hasn't actually been merged into 2.0.
-- Allen
On Mon, 2005-11-14 at 10:10, Dave Johnson wrote:
> On Nov 14, 2005, at 12:42 PM, Allen Gilliland wrote:
>
> > This is a point of debate actually.
>
> I don't debate this one anymore. I agree with Allen and Matt that pages
> should have the tabs.
>
>
> > We can probably handle this one in Roller 2.1 since it would require a
> > reasonable amount of work to put all these pages back into the tab
> > structure.
>
> Yeah, I think it's too late to fix this for 2.1.
>
> - Dave
>
>
> >
> > -- Allen
> >
> >
> > On Sun, 2005-11-13 at 21:07, Matt Raible wrote:
> >> Is the menu (tabs) supposed to always show up for users. I noticed
> >> that it doesn't show up when editing categories, nor bookmarks.
> >>
> >> Matt
> >>
> >> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>> When trying to upgrade from 1.3 to 2.0 using the
> >>> 130-to-200-migration.sql script, I got an error:
> >>>
> >>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> >>> that column/key exists
> >>>
> >>> Any ideas?
> >>>
> >>> Matt
> >>>
> >>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>>> I should mention my prod and test environments:
> >>>>
> >>>> Production on Linux:
> >>>>
> >>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> >>>> Tomcat 5.0.28
> >>>> JDK 5
> >>>>
> >>>> Testing on OS X:
> >>>>
> >>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> >>>> Tomcat 5.5.9
> >>>> JDK 5
> >>>>
> >>>> Matt
> >>>>
> >>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> >>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
> >>>>> one issue.
> >>>>>
> >>>>> On raibledesigns.com, if you scroll to the bottom of the page,
> >>>>> there
> >>>>> will be a link on the left side that allows you to navigate to the
> >>>>> previous entry. It seems like it's a bug in 1.2 that I can only
> >>>>> navigate to the single previous entry, rather than a list of
> >>>>> entries.
> >>>>> In 1.3, there is no link at all. Did this functionality get
> >>>>> removed
> >>>>> in 1.3?
> >>>>>
> >>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> >>>>> noticed there are no navigation links to go to next/prev/main when
> >>>>> viewing a single entry.
> >>>>>
> >>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to
> >>>>> my
> >>>>> theme. However, my main page is _sunsets and is not displayed as a
> >>>>> menu item - but it does show up as the name to navigate back to
> >>>>> from
> >>>>> the #showNextPreviousLinks() macro.
> >>>>>
> >>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> >>>>> than an hour.
> >>>>>
> >>>>> Matt
> >>>>>
> >>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> >>>>>> Thanks to our testers, over the weekend we've found and fixed
> >>>>>> these:
> >>>>>>
> >>>>>> * removed session-factory name argument from Hibernate
> >>>>>> configuration
> >>>>>> file
> >>>>>> * restored missing create-user page
> >>>>>> * restored missing weblog maintenance page
> >>>>>> * added cache flush to save of bookmarks
> >>>>>> * fixed array-index out of bounds problem when no default blogroll
> >>>>>> defined
> >>>>>>
> >>>>>> Are we ready for a new RC, or is there some other evil lurking?
> >>>>>>
> >>>>>> - Dave
> >>>>>>
> >>>>>>
> >>>>>
> >>>>
> >>>
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Dave Johnson <da...@rollerweblogger.org>.
On Nov 14, 2005, at 12:42 PM, Allen Gilliland wrote:
> This is a point of debate actually.
I don't debate this one anymore. I agree with Allen and Matt that pages
should have the tabs.
> We can probably handle this one in Roller 2.1 since it would require a
> reasonable amount of work to put all these pages back into the tab
> structure.
Yeah, I think it's too late to fix this for 2.1.
- Dave
>
> -- Allen
>
>
> On Sun, 2005-11-13 at 21:07, Matt Raible wrote:
>> Is the menu (tabs) supposed to always show up for users. I noticed
>> that it doesn't show up when editing categories, nor bookmarks.
>>
>> Matt
>>
>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>> When trying to upgrade from 1.3 to 2.0 using the
>>> 130-to-200-migration.sql script, I got an error:
>>>
>>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
>>> that column/key exists
>>>
>>> Any ideas?
>>>
>>> Matt
>>>
>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>> I should mention my prod and test environments:
>>>>
>>>> Production on Linux:
>>>>
>>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>> Tomcat 5.0.28
>>>> JDK 5
>>>>
>>>> Testing on OS X:
>>>>
>>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>> Tomcat 5.5.9
>>>> JDK 5
>>>>
>>>> Matt
>>>>
>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
>>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
>>>>> one issue.
>>>>>
>>>>> On raibledesigns.com, if you scroll to the bottom of the page,
>>>>> there
>>>>> will be a link on the left side that allows you to navigate to the
>>>>> previous entry. It seems like it's a bug in 1.2 that I can only
>>>>> navigate to the single previous entry, rather than a list of
>>>>> entries.
>>>>> In 1.3, there is no link at all. Did this functionality get
>>>>> removed
>>>>> in 1.3?
>>>>>
>>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
>>>>> noticed there are no navigation links to go to next/prev/main when
>>>>> viewing a single entry.
>>>>>
>>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to
>>>>> my
>>>>> theme. However, my main page is _sunsets and is not displayed as a
>>>>> menu item - but it does show up as the name to navigate back to
>>>>> from
>>>>> the #showNextPreviousLinks() macro.
>>>>>
>>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
>>>>> than an hour.
>>>>>
>>>>> Matt
>>>>>
>>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>>>>>> Thanks to our testers, over the weekend we've found and fixed
>>>>>> these:
>>>>>>
>>>>>> * removed session-factory name argument from Hibernate
>>>>>> configuration
>>>>>> file
>>>>>> * restored missing create-user page
>>>>>> * restored missing weblog maintenance page
>>>>>> * added cache flush to save of bookmarks
>>>>>> * fixed array-index out of bounds problem when no default blogroll
>>>>>> defined
>>>>>>
>>>>>> Are we ready for a new RC, or is there some other evil lurking?
>>>>>>
>>>>>> - Dave
>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
This is a point of debate actually.
There are a number of pages throughout the editor UI where a specific page does not show the tabs. I don't remember all of them, but I know the invite user and edit template pages are examples.
Personally, I think this is a UI mistake and that we should be consitent by including all editor pages within the tab structure. During our testing/fixing of 2.0 at Sun we ultimately ran out of time to deal with this and it was left alone. I don't think it will cause much harm, but I do believe that it is more appropriate for these pages to have tabs like all the other pages.
We can probably handle this one in Roller 2.1 since it would require a reasonable amount of work to put all these pages back into the tab structure.
-- Allen
On Sun, 2005-11-13 at 21:07, Matt Raible wrote:
> Is the menu (tabs) supposed to always show up for users. I noticed
> that it doesn't show up when editing categories, nor bookmarks.
>
> Matt
>
> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > When trying to upgrade from 1.3 to 2.0 using the
> > 130-to-200-migration.sql script, I got an error:
> >
> > ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> > that column/key exists
> >
> > Any ideas?
> >
> > Matt
> >
> > On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > > I should mention my prod and test environments:
> > >
> > > Production on Linux:
> > >
> > > MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> > > Tomcat 5.0.28
> > > JDK 5
> > >
> > > Testing on OS X:
> > >
> > > MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> > > Tomcat 5.5.9
> > > JDK 5
> > >
> > > Matt
> > >
> > > On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > > > I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> > > > tonight. I'm just finishing up the 1.3 upgrade and I've only found
> > > > one issue.
> > > >
> > > > On raibledesigns.com, if you scroll to the bottom of the page, there
> > > > will be a link on the left side that allows you to navigate to the
> > > > previous entry. It seems like it's a bug in 1.2 that I can only
> > > > navigate to the single previous entry, rather than a list of entries.
> > > > In 1.3, there is no link at all. Did this functionality get removed
> > > > in 1.3?
> > > >
> > > > Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> > > > noticed there are no navigation links to go to next/prev/main when
> > > > viewing a single entry.
> > > >
> > > > I was able to fix this by adding in "#showNextPreviousLinks()" to my
> > > > theme. However, my main page is _sunsets and is not displayed as a
> > > > menu item - but it does show up as the name to navigate back to from
> > > > the #showNextPreviousLinks() macro.
> > > >
> > > > On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> > > > than an hour.
> > > >
> > > > Matt
> > > >
> > > > On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > > > > Thanks to our testers, over the weekend we've found and fixed these:
> > > > >
> > > > > * removed session-factory name argument from Hibernate configuration
> > > > > file
> > > > > * restored missing create-user page
> > > > > * restored missing weblog maintenance page
> > > > > * added cache flush to save of bookmarks
> > > > > * fixed array-index out of bounds problem when no default blogroll
> > > > > defined
> > > > >
> > > > > Are we ready for a new RC, or is there some other evil lurking?
> > > > >
> > > > > - Dave
> > > > >
> > > > >
> > > >
> > >
> >
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
Is the menu (tabs) supposed to always show up for users. I noticed
that it doesn't show up when editing categories, nor bookmarks.
Matt
On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> When trying to upgrade from 1.3 to 2.0 using the
> 130-to-200-migration.sql script, I got an error:
>
> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> that column/key exists
>
> Any ideas?
>
> Matt
>
> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > I should mention my prod and test environments:
> >
> > Production on Linux:
> >
> > MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> > Tomcat 5.0.28
> > JDK 5
> >
> > Testing on OS X:
> >
> > MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> > Tomcat 5.5.9
> > JDK 5
> >
> > Matt
> >
> > On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > > I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> > > tonight. I'm just finishing up the 1.3 upgrade and I've only found
> > > one issue.
> > >
> > > On raibledesigns.com, if you scroll to the bottom of the page, there
> > > will be a link on the left side that allows you to navigate to the
> > > previous entry. It seems like it's a bug in 1.2 that I can only
> > > navigate to the single previous entry, rather than a list of entries.
> > > In 1.3, there is no link at all. Did this functionality get removed
> > > in 1.3?
> > >
> > > Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> > > noticed there are no navigation links to go to next/prev/main when
> > > viewing a single entry.
> > >
> > > I was able to fix this by adding in "#showNextPreviousLinks()" to my
> > > theme. However, my main page is _sunsets and is not displayed as a
> > > menu item - but it does show up as the name to navigate back to from
> > > the #showNextPreviousLinks() macro.
> > >
> > > On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> > > than an hour.
> > >
> > > Matt
> > >
> > > On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > > > Thanks to our testers, over the weekend we've found and fixed these:
> > > >
> > > > * removed session-factory name argument from Hibernate configuration
> > > > file
> > > > * restored missing create-user page
> > > > * restored missing weblog maintenance page
> > > > * added cache flush to save of bookmarks
> > > > * fixed array-index out of bounds problem when no default blogroll
> > > > defined
> > > >
> > > > Are we ready for a new RC, or is there some other evil lurking?
> > > >
> > > > - Dave
> > > >
> > > >
> > >
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
On Tue, 2005-11-15 at 11:43, Matt Raible wrote:
> On 11/15/05, Allen Gilliland <Al...@sun.com> wrote:
> > After looking at the RequestFilter more carefully, is there any reason we even need that filter anymore?
> >
> > >From the code it appears this filter does 3 things ...
> >
> > 1. pre-emptively create a RollerRequest object
> > 2. create a login cookie for users that want it
> > 3. set the update time in the request !?
> >
> > I think we can easily scratch 1 & 3 off as items that should be done by whatever servlet or struts action is handling the request. We shouldn't need to do that work ahead of time.
> >
> > Then if we move #2 somewhere else we should be fine. I also think that step 2 will probably be going away when we switch to Acegi security.
>
> Yes, most of the logic in this class is removed by the Acegi
> integration. I can upgrade my patch to Acegi 0.9.0 if there's enough
> interest.
definitely. i would definitely still like to see Acegi as part of Roller 2.1. perhaps after you update the patch then we can take a little bit more time to test and then do a vote.
-- Allen
>
> Matt
>
> >
> > Anyone opposed to the removal of the RequestFilter? This would be a Roller 2.1 change.
> >
> > -- Allen
> >
> >
> > On Tue, 2005-11-15 at 04:39, Matthew P. Schmidt wrote:
> > > The request filter may not be dispatched for forwards. We had to do
> > > that for some filters.
> > >
> > > -Matt
> > >
> > > Allen Gilliland wrote:
> > >
> > > >
> > > >
> > > > Dave Johnson wrote:
> > > >
> > > >>
> > > >> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
> > > >>
> > > >>> Just a followup, it could be that the frontpage lists old entries
> > > >>> because it can only find one user with a handle and so is only
> > > >>> listing those users. If you hit it in the next hour or so,
> > > >>> http://rr.javalobby.org:20900 should be up for testing. It also
> > > >>> appears that hitting the site from 'links' on linux redirects
> > > >>> properly, while firefox does not. As I said, a hard redirect to
> > > >>> main.do is probably not a good thing and unless I changed Jroller
> > > >>> from the default, I don't think 1.2 did that :)
> > > >>>
> > > >>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
> > > >>>> and also ran into some of the indices problems. Easily resolved,
> > > >>>> but there are other issues.
> > > >>>>
> > > >>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
> > > >>>> to main.jsp like it used to. We'd like to not have a hard redirect
> > > >>>> to main.do as that would screw with our page ranks and indexing
> > > >>>> with the various search engines.
> > > >>>> 2) If I do go to /, I get the following error:
> > > >>>
> > > >>>
> > > >>
> > > >> The main pages need the RequestFilter and since your front page has
> > > >> no *.do extension, you'll have to map /* to the RequestFilter. That's
> > > >> sub-optimal because some pages don't need the overhead of the request
> > > >> filter (e.g. the RSS feeds).
> > > >>
> > > >> We want the main pages to go in the page cache, so we map planet.do
> > > >> and main.do to the PageCacheFilter. Since you arrive at the front
> > > >> page without main.do in your URL, you won't get any of the normal
> > > >> caching.
> > > >>
> > > >> I don't have a good solution for this problem and we've been running
> > > >> with the redirect and the *.do URLs for over six months now, so I'm
> > > >> against changing it for 2.0. Perhaps it could be addressed in the
> > > >> cache rewrite coming in 2.1.
> > > >
> > > >
> > > >
> > > > So, it definitely looks like the RequestFilter should be changed to be
> > > > the last filter in line. It should certainly be behind the caches
> > > > since we are trying not to hit the db when we are using cached pages.
> > > > I can try testing this in my dev environment tomorrow.
> > > >
> > > > I had also noticed that when you hit the front page via "/" rather
> > > > than "/main.do" it doesn't seem to get cached. We currently use a jsp
> > > > forward to servlet dispatch the request from /index.jsp -> /main.do
> > > > and I would think that would go through the filters, but for some
> > > > reason it isn't :/ I'll have to play with this a bit to see if there
> > > > is a reason why, otherwise the only other alternative is the alter the
> > > > filter mappings.
> > > >
> > > > -- Allen
> > > >
> > > >>
> > > >>
> > > >>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
> > > >>>>
> > > >>>> 4) The hot blogs list has all blogs listed with a /page as the
> > > >>>> url, no handle. It appears that none of the blogs have a handle
> > > >>>> after the upgrade. There also doesn't appear to be anything in the
> > > >>>> upgrade script that generates them.
> > > >>>
> > > >>>
> > > >>
> > > >> This is troubling. Has anybody else run into this problem of the
> > > >> upgrade script not creating handles?
> > > >>
> > > >>
> > > >>>> 5) If I login as one of the users, it doesn't think I have any
> > > >>>> weblogs, when I clearly did before.
> > > >>>
> > > >>>
> > > >>
> > > >> And not creating weblog-user relationships?
> > > >>
> > > >> That looks like an upgrade problem too, but it's going to be
> > > >> difficult to diagnose if we can't reproduce. You do have a customized
> > > >> Roller 1.2 installation. How close was your old database to the stock
> > > >> Roller 1.2?
> > > >>
> > > >> - Dave
> > > >>
> >
> >
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
On 11/15/05, Allen Gilliland <Al...@sun.com> wrote:
> After looking at the RequestFilter more carefully, is there any reason we even need that filter anymore?
>
> >From the code it appears this filter does 3 things ...
>
> 1. pre-emptively create a RollerRequest object
> 2. create a login cookie for users that want it
> 3. set the update time in the request !?
>
> I think we can easily scratch 1 & 3 off as items that should be done by whatever servlet or struts action is handling the request. We shouldn't need to do that work ahead of time.
>
> Then if we move #2 somewhere else we should be fine. I also think that step 2 will probably be going away when we switch to Acegi security.
Yes, most of the logic in this class is removed by the Acegi
integration. I can upgrade my patch to Acegi 0.9.0 if there's enough
interest.
Matt
>
> Anyone opposed to the removal of the RequestFilter? This would be a Roller 2.1 change.
>
> -- Allen
>
>
> On Tue, 2005-11-15 at 04:39, Matthew P. Schmidt wrote:
> > The request filter may not be dispatched for forwards. We had to do
> > that for some filters.
> >
> > -Matt
> >
> > Allen Gilliland wrote:
> >
> > >
> > >
> > > Dave Johnson wrote:
> > >
> > >>
> > >> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
> > >>
> > >>> Just a followup, it could be that the frontpage lists old entries
> > >>> because it can only find one user with a handle and so is only
> > >>> listing those users. If you hit it in the next hour or so,
> > >>> http://rr.javalobby.org:20900 should be up for testing. It also
> > >>> appears that hitting the site from 'links' on linux redirects
> > >>> properly, while firefox does not. As I said, a hard redirect to
> > >>> main.do is probably not a good thing and unless I changed Jroller
> > >>> from the default, I don't think 1.2 did that :)
> > >>>
> > >>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
> > >>>> and also ran into some of the indices problems. Easily resolved,
> > >>>> but there are other issues.
> > >>>>
> > >>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
> > >>>> to main.jsp like it used to. We'd like to not have a hard redirect
> > >>>> to main.do as that would screw with our page ranks and indexing
> > >>>> with the various search engines.
> > >>>> 2) If I do go to /, I get the following error:
> > >>>
> > >>>
> > >>
> > >> The main pages need the RequestFilter and since your front page has
> > >> no *.do extension, you'll have to map /* to the RequestFilter. That's
> > >> sub-optimal because some pages don't need the overhead of the request
> > >> filter (e.g. the RSS feeds).
> > >>
> > >> We want the main pages to go in the page cache, so we map planet.do
> > >> and main.do to the PageCacheFilter. Since you arrive at the front
> > >> page without main.do in your URL, you won't get any of the normal
> > >> caching.
> > >>
> > >> I don't have a good solution for this problem and we've been running
> > >> with the redirect and the *.do URLs for over six months now, so I'm
> > >> against changing it for 2.0. Perhaps it could be addressed in the
> > >> cache rewrite coming in 2.1.
> > >
> > >
> > >
> > > So, it definitely looks like the RequestFilter should be changed to be
> > > the last filter in line. It should certainly be behind the caches
> > > since we are trying not to hit the db when we are using cached pages.
> > > I can try testing this in my dev environment tomorrow.
> > >
> > > I had also noticed that when you hit the front page via "/" rather
> > > than "/main.do" it doesn't seem to get cached. We currently use a jsp
> > > forward to servlet dispatch the request from /index.jsp -> /main.do
> > > and I would think that would go through the filters, but for some
> > > reason it isn't :/ I'll have to play with this a bit to see if there
> > > is a reason why, otherwise the only other alternative is the alter the
> > > filter mappings.
> > >
> > > -- Allen
> > >
> > >>
> > >>
> > >>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
> > >>>>
> > >>>> 4) The hot blogs list has all blogs listed with a /page as the
> > >>>> url, no handle. It appears that none of the blogs have a handle
> > >>>> after the upgrade. There also doesn't appear to be anything in the
> > >>>> upgrade script that generates them.
> > >>>
> > >>>
> > >>
> > >> This is troubling. Has anybody else run into this problem of the
> > >> upgrade script not creating handles?
> > >>
> > >>
> > >>>> 5) If I login as one of the users, it doesn't think I have any
> > >>>> weblogs, when I clearly did before.
> > >>>
> > >>>
> > >>
> > >> And not creating weblog-user relationships?
> > >>
> > >> That looks like an upgrade problem too, but it's going to be
> > >> difficult to diagnose if we can't reproduce. You do have a customized
> > >> Roller 1.2 installation. How close was your old database to the stock
> > >> Roller 1.2?
> > >>
> > >> - Dave
> > >>
>
>
Re: Time for Roller 2.0 RC2?
Posted by Matthew Schmidt <ma...@javalobby.org>.
This was indeed the case. I added the following to anything that was
mapped to .do. The frontpage comes up properly now.
<dispatcher>REQUEST</dispatcher>
<dispatcher>FORWARD</dispatcher>
-Matt
Matthew P. Schmidt wrote:
> The request filter may not be dispatched for forwards. We had to do
> that for some filters.
>
> -Matt
>
> Allen Gilliland wrote:
>
>>
>>
>> Dave Johnson wrote:
>>
>>>
>>> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>>>
>>>> Just a followup, it could be that the frontpage lists old entries
>>>> because it can only find one user with a handle and so is only
>>>> listing those users. If you hit it in the next hour or so,
>>>> http://rr.javalobby.org:20900 should be up for testing. It also
>>>> appears that hitting the site from 'links' on linux redirects
>>>> properly, while firefox does not. As I said, a hard redirect to
>>>> main.do is probably not a good thing and unless I changed Jroller
>>>> from the default, I don't think 1.2 did that :)
>>>>
>>>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>>>> and also ran into some of the indices problems. Easily resolved,
>>>>> but there are other issues.
>>>>>
>>>>> 1) Just visiting / doesn't appear to redirect to main.do or
>>>>> forward to main.jsp like it used to. We'd like to not have a hard
>>>>> redirect to main.do as that would screw with our page ranks and
>>>>> indexing with the various search engines.
>>>>> 2) If I do go to /, I get the following error:
>>>>
>>>>
>>>
>>> The main pages need the RequestFilter and since your front page has
>>> no *.do extension, you'll have to map /* to the RequestFilter.
>>> That's sub-optimal because some pages don't need the overhead of the
>>> request filter (e.g. the RSS feeds).
>>>
>>> We want the main pages to go in the page cache, so we map planet.do
>>> and main.do to the PageCacheFilter. Since you arrive at the front
>>> page without main.do in your URL, you won't get any of the normal
>>> caching.
>>>
>>> I don't have a good solution for this problem and we've been running
>>> with the redirect and the *.do URLs for over six months now, so I'm
>>> against changing it for 2.0. Perhaps it could be addressed in the
>>> cache rewrite coming in 2.1.
>>
>>
>>
>> So, it definitely looks like the RequestFilter should be changed to
>> be the last filter in line. It should certainly be behind the caches
>> since we are trying not to hit the db when we are using cached
>> pages. I can try testing this in my dev environment tomorrow.
>>
>> I had also noticed that when you hit the front page via "/" rather
>> than "/main.do" it doesn't seem to get cached. We currently use a
>> jsp forward to servlet dispatch the request from /index.jsp ->
>> /main.do and I would think that would go through the filters, but for
>> some reason it isn't :/ I'll have to play with this a bit to see if
>> there is a reason why, otherwise the only other alternative is the
>> alter the filter mappings.
>>
>> -- Allen
>>
>>>
>>>
>>>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>>>
>>>>> 4) The hot blogs list has all blogs listed with a /page as the
>>>>> url, no handle. It appears that none of the blogs have a handle
>>>>> after the upgrade. There also doesn't appear to be anything in
>>>>> the upgrade script that generates them.
>>>>
>>>>
>>>
>>> This is troubling. Has anybody else run into this problem of the
>>> upgrade script not creating handles?
>>>
>>>
>>>>> 5) If I login as one of the users, it doesn't think I have any
>>>>> weblogs, when I clearly did before.
>>>>
>>>>
>>>
>>> And not creating weblog-user relationships?
>>>
>>> That looks like an upgrade problem too, but it's going to be
>>> difficult to diagnose if we can't reproduce. You do have a
>>> customized Roller 1.2 installation. How close was your old database
>>> to the stock Roller 1.2?
>>>
>>> - Dave
>>>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
After looking at the RequestFilter more carefully, is there any reason we even need that filter anymore?
>>From the code it appears this filter does 3 things ...
1. pre-emptively create a RollerRequest object
2. create a login cookie for users that want it
3. set the update time in the request !?
I think we can easily scratch 1 & 3 off as items that should be done by whatever servlet or struts action is handling the request. We shouldn't need to do that work ahead of time.
Then if we move #2 somewhere else we should be fine. I also think that step 2 will probably be going away when we switch to Acegi security.
Anyone opposed to the removal of the RequestFilter? This would be a Roller 2.1 change.
-- Allen
On Tue, 2005-11-15 at 04:39, Matthew P. Schmidt wrote:
> The request filter may not be dispatched for forwards. We had to do
> that for some filters.
>
> -Matt
>
> Allen Gilliland wrote:
>
> >
> >
> > Dave Johnson wrote:
> >
> >>
> >> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
> >>
> >>> Just a followup, it could be that the frontpage lists old entries
> >>> because it can only find one user with a handle and so is only
> >>> listing those users. If you hit it in the next hour or so,
> >>> http://rr.javalobby.org:20900 should be up for testing. It also
> >>> appears that hitting the site from 'links' on linux redirects
> >>> properly, while firefox does not. As I said, a hard redirect to
> >>> main.do is probably not a good thing and unless I changed Jroller
> >>> from the default, I don't think 1.2 did that :)
> >>>
> >>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
> >>>> and also ran into some of the indices problems. Easily resolved,
> >>>> but there are other issues.
> >>>>
> >>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
> >>>> to main.jsp like it used to. We'd like to not have a hard redirect
> >>>> to main.do as that would screw with our page ranks and indexing
> >>>> with the various search engines.
> >>>> 2) If I do go to /, I get the following error:
> >>>
> >>>
> >>
> >> The main pages need the RequestFilter and since your front page has
> >> no *.do extension, you'll have to map /* to the RequestFilter. That's
> >> sub-optimal because some pages don't need the overhead of the request
> >> filter (e.g. the RSS feeds).
> >>
> >> We want the main pages to go in the page cache, so we map planet.do
> >> and main.do to the PageCacheFilter. Since you arrive at the front
> >> page without main.do in your URL, you won't get any of the normal
> >> caching.
> >>
> >> I don't have a good solution for this problem and we've been running
> >> with the redirect and the *.do URLs for over six months now, so I'm
> >> against changing it for 2.0. Perhaps it could be addressed in the
> >> cache rewrite coming in 2.1.
> >
> >
> >
> > So, it definitely looks like the RequestFilter should be changed to be
> > the last filter in line. It should certainly be behind the caches
> > since we are trying not to hit the db when we are using cached pages.
> > I can try testing this in my dev environment tomorrow.
> >
> > I had also noticed that when you hit the front page via "/" rather
> > than "/main.do" it doesn't seem to get cached. We currently use a jsp
> > forward to servlet dispatch the request from /index.jsp -> /main.do
> > and I would think that would go through the filters, but for some
> > reason it isn't :/ I'll have to play with this a bit to see if there
> > is a reason why, otherwise the only other alternative is the alter the
> > filter mappings.
> >
> > -- Allen
> >
> >>
> >>
> >>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
> >>>>
> >>>> 4) The hot blogs list has all blogs listed with a /page as the
> >>>> url, no handle. It appears that none of the blogs have a handle
> >>>> after the upgrade. There also doesn't appear to be anything in the
> >>>> upgrade script that generates them.
> >>>
> >>>
> >>
> >> This is troubling. Has anybody else run into this problem of the
> >> upgrade script not creating handles?
> >>
> >>
> >>>> 5) If I login as one of the users, it doesn't think I have any
> >>>> weblogs, when I clearly did before.
> >>>
> >>>
> >>
> >> And not creating weblog-user relationships?
> >>
> >> That looks like an upgrade problem too, but it's going to be
> >> difficult to diagnose if we can't reproduce. You do have a customized
> >> Roller 1.2 installation. How close was your old database to the stock
> >> Roller 1.2?
> >>
> >> - Dave
> >>
Re: Time for Roller 2.0 RC2?
Posted by "Matthew P. Schmidt" <ma...@javalobby.org>.
The request filter may not be dispatched for forwards. We had to do
that for some filters.
-Matt
Allen Gilliland wrote:
>
>
> Dave Johnson wrote:
>
>>
>> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>>
>>> Just a followup, it could be that the frontpage lists old entries
>>> because it can only find one user with a handle and so is only
>>> listing those users. If you hit it in the next hour or so,
>>> http://rr.javalobby.org:20900 should be up for testing. It also
>>> appears that hitting the site from 'links' on linux redirects
>>> properly, while firefox does not. As I said, a hard redirect to
>>> main.do is probably not a good thing and unless I changed Jroller
>>> from the default, I don't think 1.2 did that :)
>>>
>>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>>> and also ran into some of the indices problems. Easily resolved,
>>>> but there are other issues.
>>>>
>>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
>>>> to main.jsp like it used to. We'd like to not have a hard redirect
>>>> to main.do as that would screw with our page ranks and indexing
>>>> with the various search engines.
>>>> 2) If I do go to /, I get the following error:
>>>
>>>
>>
>> The main pages need the RequestFilter and since your front page has
>> no *.do extension, you'll have to map /* to the RequestFilter. That's
>> sub-optimal because some pages don't need the overhead of the request
>> filter (e.g. the RSS feeds).
>>
>> We want the main pages to go in the page cache, so we map planet.do
>> and main.do to the PageCacheFilter. Since you arrive at the front
>> page without main.do in your URL, you won't get any of the normal
>> caching.
>>
>> I don't have a good solution for this problem and we've been running
>> with the redirect and the *.do URLs for over six months now, so I'm
>> against changing it for 2.0. Perhaps it could be addressed in the
>> cache rewrite coming in 2.1.
>
>
>
> So, it definitely looks like the RequestFilter should be changed to be
> the last filter in line. It should certainly be behind the caches
> since we are trying not to hit the db when we are using cached pages.
> I can try testing this in my dev environment tomorrow.
>
> I had also noticed that when you hit the front page via "/" rather
> than "/main.do" it doesn't seem to get cached. We currently use a jsp
> forward to servlet dispatch the request from /index.jsp -> /main.do
> and I would think that would go through the filters, but for some
> reason it isn't :/ I'll have to play with this a bit to see if there
> is a reason why, otherwise the only other alternative is the alter the
> filter mappings.
>
> -- Allen
>
>>
>>
>>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>>
>>>> 4) The hot blogs list has all blogs listed with a /page as the
>>>> url, no handle. It appears that none of the blogs have a handle
>>>> after the upgrade. There also doesn't appear to be anything in the
>>>> upgrade script that generates them.
>>>
>>>
>>
>> This is troubling. Has anybody else run into this problem of the
>> upgrade script not creating handles?
>>
>>
>>>> 5) If I login as one of the users, it doesn't think I have any
>>>> weblogs, when I clearly did before.
>>>
>>>
>>
>> And not creating weblog-user relationships?
>>
>> That looks like an upgrade problem too, but it's going to be
>> difficult to diagnose if we can't reproduce. You do have a customized
>> Roller 1.2 installation. How close was your old database to the stock
>> Roller 1.2?
>>
>> - Dave
>>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
Dave Johnson wrote:
>
> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>
>> Just a followup, it could be that the frontpage lists old entries
>> because it can only find one user with a handle and so is only
>> listing those users. If you hit it in the next hour or so,
>> http://rr.javalobby.org:20900 should be up for testing. It also
>> appears that hitting the site from 'links' on linux redirects
>> properly, while firefox does not. As I said, a hard redirect to
>> main.do is probably not a good thing and unless I changed Jroller
>> from the default, I don't think 1.2 did that :)
>>
>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>> and also ran into some of the indices problems. Easily resolved,
>>> but there are other issues.
>>>
>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
>>> to main.jsp like it used to. We'd like to not have a hard redirect
>>> to main.do as that would screw with our page ranks and indexing with
>>> the various search engines.
>>> 2) If I do go to /, I get the following error:
>>
>
> The main pages need the RequestFilter and since your front page has no
> *.do extension, you'll have to map /* to the RequestFilter. That's
> sub-optimal because some pages don't need the overhead of the request
> filter (e.g. the RSS feeds).
>
> We want the main pages to go in the page cache, so we map planet.do
> and main.do to the PageCacheFilter. Since you arrive at the front page
> without main.do in your URL, you won't get any of the normal caching.
>
> I don't have a good solution for this problem and we've been running
> with the redirect and the *.do URLs for over six months now, so I'm
> against changing it for 2.0. Perhaps it could be addressed in the
> cache rewrite coming in 2.1.
So, it definitely looks like the RequestFilter should be changed to be
the last filter in line. It should certainly be behind the caches since
we are trying not to hit the db when we are using cached pages. I can
try testing this in my dev environment tomorrow.
I had also noticed that when you hit the front page via "/" rather than
"/main.do" it doesn't seem to get cached. We currently use a jsp
forward to servlet dispatch the request from /index.jsp -> /main.do and
I would think that would go through the filters, but for some reason it
isn't :/ I'll have to play with this a bit to see if there is a reason
why, otherwise the only other alternative is the alter the filter mappings.
-- Allen
>
>
>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>
>>> 4) The hot blogs list has all blogs listed with a /page as the url,
>>> no handle. It appears that none of the blogs have a handle after
>>> the upgrade. There also doesn't appear to be anything in the
>>> upgrade script that generates them.
>>
>
> This is troubling. Has anybody else run into this problem of the
> upgrade script not creating handles?
>
>
>>> 5) If I login as one of the users, it doesn't think I have any
>>> weblogs, when I clearly did before.
>>
>
> And not creating weblog-user relationships?
>
> That looks like an upgrade problem too, but it's going to be difficult
> to diagnose if we can't reproduce. You do have a customized Roller 1.2
> installation. How close was your old database to the stock Roller 1.2?
>
> - Dave
>
Re: Time for Roller 2.0 RC2?
Posted by Matthew Schmidt <ma...@javalobby.org>.
Hi guys. I just ran the upgrade script (SQL) on a fairly recent copy of
our database and it took all of 10 seconds. If your task is taking 4.5
days, then I think perhaps there must be something wrong with the task
and the way its using the connections. It does appear that the entries
all have the PUBLISHED or DRAFT settings and all websites have handles.
-Matt
Matthew P. Schmidt wrote:
> Allen,
> Yes, we attempted this with the actual database. No way to
> successfully test this without it :) Our users do things to break
> stuff that I would never have imagined :) I don't remember seeing a
> "Doing upgrade to 200" in the logs , but I'll run it again today.
> Where is that task located in the source tree? 4.5 days seems a bit
> excessive ;) Thanks for the script, I'll let you know how it goes.
>
> -Matt
>
> Allen Gilliland wrote:
>
>> Matthew,
>>
>> I am assuming you did this upgrade on the jRoller system db? or is
>> this on a test system with only a few blogs?
>>
>> The upgrade sql script doesn't actually come with any sql that
>> migrates the necessary data from a 1.3 db into the new tables and
>> columns for a 2.0 db. That part of the upgrade process is actually
>> handled in the application via the UpgradeDatabase process after you
>> deploy the 2.0 app. You should have seen messaging in your log files
>> that said "Doing upgrade to 200...", etc. If that didn't happen then
>> that would definitely be strange, but it's possible that you somehow
>> ended up on a funky upgrade path.
>>
>> I would first check for that 2.0 upgrade messaging and see if it is
>> actually there. If not, then you may want to do the upgrade to 1.3
>> separately and make sure that seems to be working, then try upgrading
>> to 2.0. The upgrade to 1.3 should be very quick.
>>
>> Now, assuming you are working on your large jRoller db, the
>> application upgrade process would take you roughly 4.5 days by my
>> last test case. Yes, I said 4.5 DAYS. That's because the part of
>> the upgrade handled by the app is iterating through each weblog in
>> your db and one-by-one it's updating the necessary data and inserting
>> some new data. When I tested this on our 1600 blog db it took me ~20
>> hrs.
>>
>> To get around this I created the attached mysql scripts which does
>> the data migration part that you seem to be missing. Hopefully that
>> helps.
>>
>> -- Allen
>>
>>
>> Matthew P. Schmidt wrote:
>>
>>> I'll try mapping the request filter to /index.jsp and see what
>>> happens. That might be enough to get it jumpstarted. As for the
>>> database, I think it was pretty close to stock. We may have added a
>>> new indices or two in the last two weeks and other than the four
>>> missing indices, it seemed to drop everything just fine and run the
>>> upgrade script. I don't see anything in the mysql upgrade script
>>> that generates those handles or creates the relationships. Am I
>>> missing something?
>>>
>>> -Matt
>>>
>>> Dave Johnson wrote:
>>>
>>>>
>>>> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>>>>
>>>>> Just a followup, it could be that the frontpage lists old entries
>>>>> because it can only find one user with a handle and so is only
>>>>> listing those users. If you hit it in the next hour or so,
>>>>> http://rr.javalobby.org:20900 should be up for testing. It also
>>>>> appears that hitting the site from 'links' on linux redirects
>>>>> properly, while firefox does not. As I said, a hard redirect to
>>>>> main.do is probably not a good thing and unless I changed Jroller
>>>>> from the default, I don't think 1.2 did that :)
>>>>>
>>>>>> Hey guys. We're in the process of trying to migrate to Roller
>>>>>> 2.0 and also ran into some of the indices problems. Easily
>>>>>> resolved, but there are other issues.
>>>>>>
>>>>>> 1) Just visiting / doesn't appear to redirect to main.do or
>>>>>> forward to main.jsp like it used to. We'd like to not have a
>>>>>> hard redirect to main.do as that would screw with our page ranks
>>>>>> and indexing with the various search engines.
>>>>>> 2) If I do go to /, I get the following error:
>>>>>
>>>>>
>>>>>
>>>>
>>>> The main pages need the RequestFilter and since your front page has
>>>> no *.do extension, you'll have to map /* to the RequestFilter.
>>>> That's sub-optimal because some pages don't need the overhead of
>>>> the request filter (e.g. the RSS feeds).
>>>>
>>>> We want the main pages to go in the page cache, so we map planet.do
>>>> and main.do to the PageCacheFilter. Since you arrive at the front
>>>> page without main.do in your URL, you won't get any of the normal
>>>> caching.
>>>>
>>>> I don't have a good solution for this problem and we've been
>>>> running with the redirect and the *.do URLs for over six months
>>>> now, so I'm against changing it for 2.0. Perhaps it could be
>>>> addressed in the cache rewrite coming in 2.1.
>>>>
>>>>
>>>>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>>>>
>>>>>> 4) The hot blogs list has all blogs listed with a /page as the
>>>>>> url, no handle. It appears that none of the blogs have a handle
>>>>>> after the upgrade. There also doesn't appear to be anything in
>>>>>> the upgrade script that generates them.
>>>>>
>>>>>
>>>>>
>>>>
>>>> This is troubling. Has anybody else run into this problem of the
>>>> upgrade script not creating handles?
>>>>
>>>>
>>>>>> 5) If I login as one of the users, it doesn't think I have any
>>>>>> weblogs, when I clearly did before.
>>>>>
>>>>>
>>>>>
>>>>
>>>> And not creating weblog-user relationships?
>>>>
>>>> That looks like an upgrade problem too, but it's going to be
>>>> difficult to diagnose if we can't reproduce. You do have a
>>>> customized Roller 1.2 installation. How close was your old database
>>>> to the stock Roller 1.2?
>>>>
>>>> - Dave
>>>>
>> ------------------------------------------------------------------------
>>
>> -- this should only be run once to update the data set from 1.3 to 2.0
>> -- subsequent uses of this script on a 2.0 database may cause problems
>>
>> -- fix people who changed their root category
>> update website,weblogcategory set website.defaultcatid =
>> weblogcategory.id where weblogcategory.websiteid=website.id and
>> weblogcategory.name = 'root';
>>
>> -- set website handles using old usernames
>> UPDATE website,rolleruser SET website.handle = rolleruser.username
>> WHERE website.userid = rolleruser.id AND website.handle = '';
>>
>> -- set weblog entry creator and publish state for PUBLISHED entries
>> UPDATE website,rolleruser,weblogentry SET
>> weblogentry.userid=rolleruser.id, weblogentry.status='PUBLISHED'
>> WHERE website.userid=rolleruser.id AND
>> website.id=weblogentry.websiteid AND weblogentry.userid = '' AND
>> weblogentry.publishentry = 1;
>>
>> -- set weblog entry creator and publish state for DRAFT entries
>> UPDATE website,rolleruser,weblogentry SET
>> weblogentry.userid=rolleruser.id, weblogentry.status='DRAFT' WHERE
>> website.userid=rolleruser.id AND website.id=weblogentry.websiteid AND
>> weblogentry.userid = '' AND weblogentry.publishentry = 0;
>>
>> -- insert new permissions masks for all existing weblogs
>> INSERT into roller_user_permissions(id, website_id, user_id,
>> permission_mask, pending) SELECT concat(website.id,
>> 'p'),website.id,rolleruser.id,3,0 FROM website,rolleruser WHERE
>> website.userid=rolleruser.id;
>>
>> -- set roller db version to 2.0
>> UPDATE roller_properties SET value = '200' WHERE name =
>> 'roller.database.version';
>>
>>
Re: Time for Roller 2.0 RC2?
Posted by "Matthew P. Schmidt" <ma...@javalobby.org>.
Allen,
Yes, we attempted this with the actual database. No way to
successfully test this without it :) Our users do things to break stuff
that I would never have imagined :) I don't remember seeing a "Doing
upgrade to 200" in the logs , but I'll run it again today. Where is
that task located in the source tree? 4.5 days seems a bit excessive
;) Thanks for the script, I'll let you know how it goes.
-Matt
Allen Gilliland wrote:
> Matthew,
>
> I am assuming you did this upgrade on the jRoller system db? or is
> this on a test system with only a few blogs?
>
> The upgrade sql script doesn't actually come with any sql that
> migrates the necessary data from a 1.3 db into the new tables and
> columns for a 2.0 db. That part of the upgrade process is actually
> handled in the application via the UpgradeDatabase process after you
> deploy the 2.0 app. You should have seen messaging in your log files
> that said "Doing upgrade to 200...", etc. If that didn't happen then
> that would definitely be strange, but it's possible that you somehow
> ended up on a funky upgrade path.
>
> I would first check for that 2.0 upgrade messaging and see if it is
> actually there. If not, then you may want to do the upgrade to 1.3
> separately and make sure that seems to be working, then try upgrading
> to 2.0. The upgrade to 1.3 should be very quick.
>
> Now, assuming you are working on your large jRoller db, the
> application upgrade process would take you roughly 4.5 days by my last
> test case. Yes, I said 4.5 DAYS. That's because the part of the
> upgrade handled by the app is iterating through each weblog in your db
> and one-by-one it's updating the necessary data and inserting some new
> data. When I tested this on our 1600 blog db it took me ~20 hrs.
>
> To get around this I created the attached mysql scripts which does the
> data migration part that you seem to be missing. Hopefully that helps.
>
> -- Allen
>
>
> Matthew P. Schmidt wrote:
>
>> I'll try mapping the request filter to /index.jsp and see what
>> happens. That might be enough to get it jumpstarted. As for the
>> database, I think it was pretty close to stock. We may have added a
>> new indices or two in the last two weeks and other than the four
>> missing indices, it seemed to drop everything just fine and run the
>> upgrade script. I don't see anything in the mysql upgrade script
>> that generates those handles or creates the relationships. Am I
>> missing something?
>>
>> -Matt
>>
>> Dave Johnson wrote:
>>
>>>
>>> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>>>
>>>> Just a followup, it could be that the frontpage lists old entries
>>>> because it can only find one user with a handle and so is only
>>>> listing those users. If you hit it in the next hour or so,
>>>> http://rr.javalobby.org:20900 should be up for testing. It also
>>>> appears that hitting the site from 'links' on linux redirects
>>>> properly, while firefox does not. As I said, a hard redirect to
>>>> main.do is probably not a good thing and unless I changed Jroller
>>>> from the default, I don't think 1.2 did that :)
>>>>
>>>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>>>> and also ran into some of the indices problems. Easily resolved,
>>>>> but there are other issues.
>>>>>
>>>>> 1) Just visiting / doesn't appear to redirect to main.do or
>>>>> forward to main.jsp like it used to. We'd like to not have a hard
>>>>> redirect to main.do as that would screw with our page ranks and
>>>>> indexing with the various search engines.
>>>>> 2) If I do go to /, I get the following error:
>>>>
>>>>
>>>>
>>>
>>> The main pages need the RequestFilter and since your front page has
>>> no *.do extension, you'll have to map /* to the RequestFilter.
>>> That's sub-optimal because some pages don't need the overhead of the
>>> request filter (e.g. the RSS feeds).
>>>
>>> We want the main pages to go in the page cache, so we map planet.do
>>> and main.do to the PageCacheFilter. Since you arrive at the front
>>> page without main.do in your URL, you won't get any of the normal
>>> caching.
>>>
>>> I don't have a good solution for this problem and we've been running
>>> with the redirect and the *.do URLs for over six months now, so I'm
>>> against changing it for 2.0. Perhaps it could be addressed in the
>>> cache rewrite coming in 2.1.
>>>
>>>
>>>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>>>
>>>>> 4) The hot blogs list has all blogs listed with a /page as the
>>>>> url, no handle. It appears that none of the blogs have a handle
>>>>> after the upgrade. There also doesn't appear to be anything in
>>>>> the upgrade script that generates them.
>>>>
>>>>
>>>>
>>>
>>> This is troubling. Has anybody else run into this problem of the
>>> upgrade script not creating handles?
>>>
>>>
>>>>> 5) If I login as one of the users, it doesn't think I have any
>>>>> weblogs, when I clearly did before.
>>>>
>>>>
>>>>
>>>
>>> And not creating weblog-user relationships?
>>>
>>> That looks like an upgrade problem too, but it's going to be
>>> difficult to diagnose if we can't reproduce. You do have a
>>> customized Roller 1.2 installation. How close was your old database
>>> to the stock Roller 1.2?
>>>
>>> - Dave
>>>
>------------------------------------------------------------------------
>
>-- this should only be run once to update the data set from 1.3 to 2.0
>-- subsequent uses of this script on a 2.0 database may cause problems
>
>-- fix people who changed their root category
>update website,weblogcategory set website.defaultcatid = weblogcategory.id where weblogcategory.websiteid=website.id and weblogcategory.name = 'root';
>
>-- set website handles using old usernames
>UPDATE website,rolleruser SET website.handle = rolleruser.username WHERE website.userid = rolleruser.id AND website.handle = '';
>
>-- set weblog entry creator and publish state for PUBLISHED entries
>UPDATE website,rolleruser,weblogentry SET weblogentry.userid=rolleruser.id, weblogentry.status='PUBLISHED' WHERE website.userid=rolleruser.id AND website.id=weblogentry.websiteid AND weblogentry.userid = '' AND weblogentry.publishentry = 1;
>
>-- set weblog entry creator and publish state for DRAFT entries
>UPDATE website,rolleruser,weblogentry SET weblogentry.userid=rolleruser.id, weblogentry.status='DRAFT' WHERE website.userid=rolleruser.id AND website.id=weblogentry.websiteid AND weblogentry.userid = '' AND weblogentry.publishentry = 0;
>
>-- insert new permissions masks for all existing weblogs
>INSERT into roller_user_permissions(id, website_id, user_id, permission_mask, pending) SELECT concat(website.id, 'p'),website.id,rolleruser.id,3,0 FROM website,rolleruser WHERE website.userid=rolleruser.id;
>
>-- set roller db version to 2.0
>UPDATE roller_properties SET value = '200' WHERE name = 'roller.database.version';
>
>
Re: Time for Roller 2.0 RC2?
Posted by Allen Gilliland <Al...@Sun.COM>.
Matthew,
I am assuming you did this upgrade on the jRoller system db? or is this
on a test system with only a few blogs?
The upgrade sql script doesn't actually come with any sql that migrates
the necessary data from a 1.3 db into the new tables and columns for a
2.0 db. That part of the upgrade process is actually handled in the
application via the UpgradeDatabase process after you deploy the 2.0
app. You should have seen messaging in your log files that said "Doing
upgrade to 200...", etc. If that didn't happen then that would
definitely be strange, but it's possible that you somehow ended up on a
funky upgrade path.
I would first check for that 2.0 upgrade messaging and see if it is
actually there. If not, then you may want to do the upgrade to 1.3
separately and make sure that seems to be working, then try upgrading to
2.0. The upgrade to 1.3 should be very quick.
Now, assuming you are working on your large jRoller db, the application
upgrade process would take you roughly 4.5 days by my last test case.
Yes, I said 4.5 DAYS. That's because the part of the upgrade handled by
the app is iterating through each weblog in your db and one-by-one it's
updating the necessary data and inserting some new data. When I tested
this on our 1600 blog db it took me ~20 hrs.
To get around this I created the attached mysql scripts which does the
data migration part that you seem to be missing. Hopefully that helps.
-- Allen
Matthew P. Schmidt wrote:
> I'll try mapping the request filter to /index.jsp and see what
> happens. That might be enough to get it jumpstarted. As for the
> database, I think it was pretty close to stock. We may have added a
> new indices or two in the last two weeks and other than the four
> missing indices, it seemed to drop everything just fine and run the
> upgrade script. I don't see anything in the mysql upgrade script that
> generates those handles or creates the relationships. Am I missing
> something?
>
> -Matt
>
> Dave Johnson wrote:
>
>>
>> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>>
>>> Just a followup, it could be that the frontpage lists old entries
>>> because it can only find one user with a handle and so is only
>>> listing those users. If you hit it in the next hour or so,
>>> http://rr.javalobby.org:20900 should be up for testing. It also
>>> appears that hitting the site from 'links' on linux redirects
>>> properly, while firefox does not. As I said, a hard redirect to
>>> main.do is probably not a good thing and unless I changed Jroller
>>> from the default, I don't think 1.2 did that :)
>>>
>>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>>> and also ran into some of the indices problems. Easily resolved,
>>>> but there are other issues.
>>>>
>>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
>>>> to main.jsp like it used to. We'd like to not have a hard redirect
>>>> to main.do as that would screw with our page ranks and indexing
>>>> with the various search engines.
>>>> 2) If I do go to /, I get the following error:
>>>
>>>
>>
>> The main pages need the RequestFilter and since your front page has
>> no *.do extension, you'll have to map /* to the RequestFilter. That's
>> sub-optimal because some pages don't need the overhead of the request
>> filter (e.g. the RSS feeds).
>>
>> We want the main pages to go in the page cache, so we map planet.do
>> and main.do to the PageCacheFilter. Since you arrive at the front
>> page without main.do in your URL, you won't get any of the normal
>> caching.
>>
>> I don't have a good solution for this problem and we've been running
>> with the redirect and the *.do URLs for over six months now, so I'm
>> against changing it for 2.0. Perhaps it could be addressed in the
>> cache rewrite coming in 2.1.
>>
>>
>>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>>
>>>> 4) The hot blogs list has all blogs listed with a /page as the
>>>> url, no handle. It appears that none of the blogs have a handle
>>>> after the upgrade. There also doesn't appear to be anything in the
>>>> upgrade script that generates them.
>>>
>>>
>>
>> This is troubling. Has anybody else run into this problem of the
>> upgrade script not creating handles?
>>
>>
>>>> 5) If I login as one of the users, it doesn't think I have any
>>>> weblogs, when I clearly did before.
>>>
>>>
>>
>> And not creating weblog-user relationships?
>>
>> That looks like an upgrade problem too, but it's going to be
>> difficult to diagnose if we can't reproduce. You do have a customized
>> Roller 1.2 installation. How close was your old database to the stock
>> Roller 1.2?
>>
>> - Dave
>>
Re: Time for Roller 2.0 RC2?
Posted by "Matthew P. Schmidt" <ma...@javalobby.org>.
I'll try mapping the request filter to /index.jsp and see what happens.
That might be enough to get it jumpstarted. As for the database, I
think it was pretty close to stock. We may have added a new indices or
two in the last two weeks and other than the four missing indices, it
seemed to drop everything just fine and run the upgrade script. I don't
see anything in the mysql upgrade script that generates those handles or
creates the relationships. Am I missing something?
-Matt
Dave Johnson wrote:
>
> On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
>
>> Just a followup, it could be that the frontpage lists old entries
>> because it can only find one user with a handle and so is only
>> listing those users. If you hit it in the next hour or so,
>> http://rr.javalobby.org:20900 should be up for testing. It also
>> appears that hitting the site from 'links' on linux redirects
>> properly, while firefox does not. As I said, a hard redirect to
>> main.do is probably not a good thing and unless I changed Jroller
>> from the default, I don't think 1.2 did that :)
>>
>>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>>> and also ran into some of the indices problems. Easily resolved,
>>> but there are other issues.
>>>
>>> 1) Just visiting / doesn't appear to redirect to main.do or forward
>>> to main.jsp like it used to. We'd like to not have a hard redirect
>>> to main.do as that would screw with our page ranks and indexing with
>>> the various search engines.
>>> 2) If I do go to /, I get the following error:
>>
>
> The main pages need the RequestFilter and since your front page has no
> *.do extension, you'll have to map /* to the RequestFilter. That's
> sub-optimal because some pages don't need the overhead of the request
> filter (e.g. the RSS feeds).
>
> We want the main pages to go in the page cache, so we map planet.do
> and main.do to the PageCacheFilter. Since you arrive at the front page
> without main.do in your URL, you won't get any of the normal caching.
>
> I don't have a good solution for this problem and we've been running
> with the redirect and the *.do URLs for over six months now, so I'm
> against changing it for 2.0. Perhaps it could be addressed in the
> cache rewrite coming in 2.1.
>
>
>>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>>
>>> 4) The hot blogs list has all blogs listed with a /page as the url,
>>> no handle. It appears that none of the blogs have a handle after
>>> the upgrade. There also doesn't appear to be anything in the
>>> upgrade script that generates them.
>>
>
> This is troubling. Has anybody else run into this problem of the
> upgrade script not creating handles?
>
>
>>> 5) If I login as one of the users, it doesn't think I have any
>>> weblogs, when I clearly did before.
>>
>
> And not creating weblog-user relationships?
>
> That looks like an upgrade problem too, but it's going to be difficult
> to diagnose if we can't reproduce. You do have a customized Roller 1.2
> installation. How close was your old database to the stock Roller 1.2?
>
> - Dave
>
Re: Time for Roller 2.0 RC2?
Posted by Dave Johnson <da...@rollerweblogger.org>.
On Nov 14, 2005, at 11:10 AM, Matthew Schmidt wrote:
> Just a followup, it could be that the frontpage lists old entries
> because it can only find one user with a handle and so is only listing
> those users. If you hit it in the next hour or so,
> http://rr.javalobby.org:20900 should be up for testing. It also
> appears that hitting the site from 'links' on linux redirects
> properly, while firefox does not. As I said, a hard redirect to
> main.do is probably not a good thing and unless I changed Jroller from
> the default, I don't think 1.2 did that :)
>
>> Hey guys. We're in the process of trying to migrate to Roller 2.0
>> and also ran into some of the indices problems. Easily resolved, but
>> there are other issues.
>>
>> 1) Just visiting / doesn't appear to redirect to main.do or forward
>> to main.jsp like it used to. We'd like to not have a hard redirect
>> to main.do as that would screw with our page ranks and indexing with
>> the various search engines.
>> 2) If I do go to /, I get the following error:
The main pages need the RequestFilter and since your front page has no
*.do extension, you'll have to map /* to the RequestFilter. That's
sub-optimal because some pages don't need the overhead of the request
filter (e.g. the RSS feeds).
We want the main pages to go in the page cache, so we map planet.do and
main.do to the PageCacheFilter. Since you arrive at the front page
without main.do in your URL, you won't get any of the normal caching.
I don't have a good solution for this problem and we've been running
with the redirect and the *.do URLs for over six months now, so I'm
against changing it for 2.0. Perhaps it could be addressed in the cache
rewrite coming in 2.1.
>> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>>
>> 4) The hot blogs list has all blogs listed with a /page as the url,
>> no handle. It appears that none of the blogs have a handle after the
>> upgrade. There also doesn't appear to be anything in the upgrade
>> script that generates them.
This is troubling. Has anybody else run into this problem of the
upgrade script not creating handles?
>> 5) If I login as one of the users, it doesn't think I have any
>> weblogs, when I clearly did before.
And not creating weblog-user relationships?
That looks like an upgrade problem too, but it's going to be difficult
to diagnose if we can't reproduce. You do have a customized Roller 1.2
installation. How close was your old database to the stock Roller 1.2?
- Dave
Re: Time for Roller 2.0 RC2?
Posted by Matthew Schmidt <ma...@javalobby.org>.
Just a followup, it could be that the frontpage lists old entries
because it can only find one user with a handle and so is only listing
those users. If you hit it in the next hour or so,
http://rr.javalobby.org:20900 should be up for testing. It also appears
that hitting the site from 'links' on linux redirects properly, while
firefox does not. As I said, a hard redirect to main.do is probably not
a good thing and unless I changed Jroller from the default, I don't
think 1.2 did that :)
-Matt
Matthew Schmidt wrote:
> Hey guys. We're in the process of trying to migrate to Roller 2.0 and
> also ran into some of the indices problems. Easily resolved, but
> there are other issues.
>
> 1) Just visiting / doesn't appear to redirect to main.do or forward to
> main.jsp like it used to. We'd like to not have a hard redirect to
> main.do as that would screw with our page ranks and indexing with the
> various search engines.
> 2) If I do go to /, I get the following error:
>
> javax.servlet.jsp.JspException: Exception;
> TEMPLATE_CLASSPATH=/menu-tabbed.vm;
> exception=org.roller.RollerPermissionsException: Only global admin or
> system
> user can save properties
> at
> org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:101)
> at org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
> at
> _jsp._theme._tiles_22dfrontpage__jsp._jspService(theme/tiles-frontpage.jsp:45)
>
>
>
> 3) Hitting main.do gives me a bunch of old entries, back to 2003.
>
> 4) The hot blogs list has all blogs listed with a /page as the url,
> no handle. It appears that none of the blogs have a handle after the
> upgrade. There also doesn't appear to be anything in the upgrade
> script that generates them.
> 5) If I login as one of the users, it doesn't think I have any
> weblogs, when I clearly did before.
>
> 6) In roller.properties, you may want to allow system property
> expansion for the planet cache directory.
>
> Thanks guys, looking forward to trying out the new release my our data.
>
> -Matt
>
> Matt Raible wrote:
>> On 11/14/05, Anil Gangolli <an...@busybuddha.org> wrote:
>>
>>> I retested my upgrade and I didn't see these errors. Is it possible
>>> that you had arrived at your 1.3 database schema via a development
>>> build
>>> of the schema that didn't include all of the indices?
>>>
>>> This happened to me on two different indices.
>>>
>>> ERROR 1091 (42000): Can't DROP 'pingqueueentry_pingtargetid_index';
>>> check that column/key exists
>>> ERROR 1091 (42000): Can't DROP 'pingqueueentry_websiteid_index'; check
>>> that column/key exists
>>>
>>> I tracked my errors back to the fact that I had arrived at my 1.3
>>> schema
>>> via a 1.2 dev schema, not actually the 1.2 release schema; late in the
>>> game in 1.2, some additional indices were added. I think this
>>> happened
>>> just before 1.0 or 1.1 as well. Anyway, the 1.3 to 2.0 upgrade didn't
>>> find these when dropping them, but they are indeed present if built
>>> from
>>> the official released versions.
>>>
>>
>> It's entirely possible (and highly likely) that my current 1.2 schema
>> is from development, rather than a release. These indices must have
>> been added in 1.2 (or prior) b/c I did upgrade 1.2 to 1.3 and then to
>> 2.0.
>>
>> No worries, I'll just remember to comment out these indices when
>> running the upgrade script.
>>
>> Matt
>>
>>
>>> --a.
>>>
>>>
>>> Anil Gangolli wrote:
>>>
>>>
>>>> Typically DDL (schema modifying commands) are not transactional.
>>>> There is no way to commit versus roll them back. So yes, it is
>>>> especially important that they work properly with no errors. If
>>>> errors are skipped during sourcing (which I think is the default in
>>>> MySQL) and if objects being dropped already do not exist, that should
>>>> be ok. However, this might cause problems with other databases.
>>>>
>>>> Matt Raible wrote:
>>>>
>>>>
>>>>> I ended up having to comment out 4 of the indexes b/c they didn't
>>>>> exist in my database. Here's the list from the MySQL
>>>>> 130-to-200-migration script.
>>>>>
>>>>> --alter table webpage drop index webpage_id_index;
>>>>> --alter table website drop index website_id_index;
>>>>> --alter table folderassoc drop index folderassoc_relation_index;
>>>>> --alter table weblogentry drop index weblogentry_pinnedtomain_index;
>>>>>
>>>>> I think it's important that we remove these (or add an "if exists")
>>>>> b/c the migration scripts seems to leave the database in an unknown
>>>>> state when this fails (rather than rolling back all the changes).
>>>>>
>>>>> Matt
>>>>>
>>>>>
>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> When trying to upgrade from 1.3 to 2.0 using the
>>>>>> 130-to-200-migration.sql script, I got an error:
>>>>>>
>>>>>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
>>>>>> that column/key exists
>>>>>>
>>>>>> Any ideas?
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I should mention my prod and test environments:
>>>>>>>
>>>>>>> Production on Linux:
>>>>>>>
>>>>>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>>>>> Tomcat 5.0.28
>>>>>>> JDK 5
>>>>>>>
>>>>>>> Testing on OS X:
>>>>>>>
>>>>>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>>>>> Tomcat 5.5.9
>>>>>>> JDK 5
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
>>>>>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only
>>>>>>>> found
>>>>>>>> one issue.
>>>>>>>>
>>>>>>>> On raibledesigns.com, if you scroll to the bottom of the page,
>>>>>>>> there
>>>>>>>> will be a link on the left side that allows you to navigate to the
>>>>>>>> previous entry. It seems like it's a bug in 1.2 that I can only
>>>>>>>> navigate to the single previous entry, rather than a list of
>>>>>>>> entries.
>>>>>>>> In 1.3, there is no link at all. Did this functionality get
>>>>>>>> removed
>>>>>>>> in 1.3?
>>>>>>>>
>>>>>>>> Also, comparing my raibledesigns.com blog to my jroller.com
>>>>>>>> blog, I
>>>>>>>> noticed there are no navigation links to go to next/prev/main when
>>>>>>>> viewing a single entry.
>>>>>>>>
>>>>>>>> I was able to fix this by adding in "#showNextPreviousLinks()"
>>>>>>>> to my
>>>>>>>> theme. However, my main page is _sunsets and is not displayed
>>>>>>>> as a
>>>>>>>> menu item - but it does show up as the name to navigate back to
>>>>>>>> from
>>>>>>>> the #showNextPreviousLinks() macro.
>>>>>>>>
>>>>>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in
>>>>>>>> less
>>>>>>>> than an hour.
>>>>>>>>
>>>>>>>> Matt
>>>>>>>>
>>>>>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>> Thanks to our testers, over the weekend we've found and fixed
>>>>>>>>> these:
>>>>>>>>>
>>>>>>>>> * removed session-factory name argument from Hibernate
>>>>>>>>> configuration
>>>>>>>>> file
>>>>>>>>> * restored missing create-user page
>>>>>>>>> * restored missing weblog maintenance page
>>>>>>>>> * added cache flush to save of bookmarks
>>>>>>>>> * fixed array-index out of bounds problem when no default
>>>>>>>>> blogroll
>>>>>>>>> defined
>>>>>>>>>
>>>>>>>>> Are we ready for a new RC, or is there some other evil lurking?
>>>>>>>>>
>>>>>>>>> - Dave
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>
Re: Time for Roller 2.0 RC2?
Posted by Matthew Schmidt <ma...@javalobby.org>.
Hey guys. We're in the process of trying to migrate to Roller 2.0 and
also ran into some of the indices problems. Easily resolved, but there
are other issues.
1) Just visiting / doesn't appear to redirect to main.do or forward to
main.jsp like it used to. We'd like to not have a hard redirect to
main.do as that would screw with our page ranks and indexing with the
various search engines.
2) If I do go to /, I get the following error:
javax.servlet.jsp.JspException: Exception; TEMPLATE_CLASSPATH=/menu-tabbed.vm;
exception=org.roller.RollerPermissionsException: Only global admin or system
user can save properties
at org.roller.presentation.tags.VelocityTag.doEndTag(VelocityTag.java:101)
at org.roller.presentation.tags.HybridTag.doEndTag(HybridTag.java:64)
at _jsp._theme._tiles_22dfrontpage__jsp._jspService(theme/tiles-frontpage.jsp:45)
3) Hitting main.do gives me a bunch of old entries, back to 2003.
4) The hot blogs list has all blogs listed with a /page as the url, no
handle. It appears that none of the blogs have a handle after the
upgrade. There also doesn't appear to be anything in the upgrade script
that generates them.
5) If I login as one of the users, it doesn't think I have any weblogs,
when I clearly did before.
6) In roller.properties, you may want to allow system property expansion
for the planet cache directory.
Thanks guys, looking forward to trying out the new release my our data.
-Matt
Matt Raible wrote:
> On 11/14/05, Anil Gangolli <an...@busybuddha.org> wrote:
>
>> I retested my upgrade and I didn't see these errors. Is it possible
>> that you had arrived at your 1.3 database schema via a development build
>> of the schema that didn't include all of the indices?
>>
>> This happened to me on two different indices.
>>
>> ERROR 1091 (42000): Can't DROP 'pingqueueentry_pingtargetid_index';
>> check that column/key exists
>> ERROR 1091 (42000): Can't DROP 'pingqueueentry_websiteid_index'; check
>> that column/key exists
>>
>> I tracked my errors back to the fact that I had arrived at my 1.3 schema
>> via a 1.2 dev schema, not actually the 1.2 release schema; late in the
>> game in 1.2, some additional indices were added. I think this happened
>> just before 1.0 or 1.1 as well. Anyway, the 1.3 to 2.0 upgrade didn't
>> find these when dropping them, but they are indeed present if built from
>> the official released versions.
>>
>
> It's entirely possible (and highly likely) that my current 1.2 schema
> is from development, rather than a release. These indices must have
> been added in 1.2 (or prior) b/c I did upgrade 1.2 to 1.3 and then to
> 2.0.
>
> No worries, I'll just remember to comment out these indices when
> running the upgrade script.
>
> Matt
>
>
>> --a.
>>
>>
>> Anil Gangolli wrote:
>>
>>
>>> Typically DDL (schema modifying commands) are not transactional.
>>> There is no way to commit versus roll them back. So yes, it is
>>> especially important that they work properly with no errors. If
>>> errors are skipped during sourcing (which I think is the default in
>>> MySQL) and if objects being dropped already do not exist, that should
>>> be ok. However, this might cause problems with other databases.
>>>
>>> Matt Raible wrote:
>>>
>>>
>>>> I ended up having to comment out 4 of the indexes b/c they didn't
>>>> exist in my database. Here's the list from the MySQL
>>>> 130-to-200-migration script.
>>>>
>>>> --alter table webpage drop index webpage_id_index;
>>>> --alter table website drop index website_id_index;
>>>> --alter table folderassoc drop index folderassoc_relation_index;
>>>> --alter table weblogentry drop index weblogentry_pinnedtomain_index;
>>>>
>>>> I think it's important that we remove these (or add an "if exists")
>>>> b/c the migration scripts seems to leave the database in an unknown
>>>> state when this fails (rather than rolling back all the changes).
>>>>
>>>> Matt
>>>>
>>>>
>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>
>>>>
>>>>
>>>>> When trying to upgrade from 1.3 to 2.0 using the
>>>>> 130-to-200-migration.sql script, I got an error:
>>>>>
>>>>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
>>>>> that column/key exists
>>>>>
>>>>> Any ideas?
>>>>>
>>>>> Matt
>>>>>
>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>
>>>>>
>>>>>
>>>>>> I should mention my prod and test environments:
>>>>>>
>>>>>> Production on Linux:
>>>>>>
>>>>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>>>> Tomcat 5.0.28
>>>>>> JDK 5
>>>>>>
>>>>>> Testing on OS X:
>>>>>>
>>>>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>>>> Tomcat 5.5.9
>>>>>> JDK 5
>>>>>>
>>>>>> Matt
>>>>>>
>>>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>>>
>>>>>>
>>>>>>
>>>>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
>>>>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
>>>>>>> one issue.
>>>>>>>
>>>>>>> On raibledesigns.com, if you scroll to the bottom of the page, there
>>>>>>> will be a link on the left side that allows you to navigate to the
>>>>>>> previous entry. It seems like it's a bug in 1.2 that I can only
>>>>>>> navigate to the single previous entry, rather than a list of entries.
>>>>>>> In 1.3, there is no link at all. Did this functionality get removed
>>>>>>> in 1.3?
>>>>>>>
>>>>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
>>>>>>> noticed there are no navigation links to go to next/prev/main when
>>>>>>> viewing a single entry.
>>>>>>>
>>>>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to my
>>>>>>> theme. However, my main page is _sunsets and is not displayed as a
>>>>>>> menu item - but it does show up as the name to navigate back to from
>>>>>>> the #showNextPreviousLinks() macro.
>>>>>>>
>>>>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
>>>>>>> than an hour.
>>>>>>>
>>>>>>> Matt
>>>>>>>
>>>>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>> Thanks to our testers, over the weekend we've found and fixed these:
>>>>>>>>
>>>>>>>> * removed session-factory name argument from Hibernate configuration
>>>>>>>> file
>>>>>>>> * restored missing create-user page
>>>>>>>> * restored missing weblog maintenance page
>>>>>>>> * added cache flush to save of bookmarks
>>>>>>>> * fixed array-index out of bounds problem when no default blogroll
>>>>>>>> defined
>>>>>>>>
>>>>>>>> Are we ready for a new RC, or is there some other evil lurking?
>>>>>>>>
>>>>>>>> - Dave
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>
>>>>
>>>>
>>>
>>
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
On 11/14/05, Anil Gangolli <an...@busybuddha.org> wrote:
> I retested my upgrade and I didn't see these errors. Is it possible
> that you had arrived at your 1.3 database schema via a development build
> of the schema that didn't include all of the indices?
>
> This happened to me on two different indices.
>
> ERROR 1091 (42000): Can't DROP 'pingqueueentry_pingtargetid_index';
> check that column/key exists
> ERROR 1091 (42000): Can't DROP 'pingqueueentry_websiteid_index'; check
> that column/key exists
>
> I tracked my errors back to the fact that I had arrived at my 1.3 schema
> via a 1.2 dev schema, not actually the 1.2 release schema; late in the
> game in 1.2, some additional indices were added. I think this happened
> just before 1.0 or 1.1 as well. Anyway, the 1.3 to 2.0 upgrade didn't
> find these when dropping them, but they are indeed present if built from
> the official released versions.
It's entirely possible (and highly likely) that my current 1.2 schema
is from development, rather than a release. These indices must have
been added in 1.2 (or prior) b/c I did upgrade 1.2 to 1.3 and then to
2.0.
No worries, I'll just remember to comment out these indices when
running the upgrade script.
Matt
> --a.
>
>
> Anil Gangolli wrote:
>
> >
> > Typically DDL (schema modifying commands) are not transactional.
> > There is no way to commit versus roll them back. So yes, it is
> > especially important that they work properly with no errors. If
> > errors are skipped during sourcing (which I think is the default in
> > MySQL) and if objects being dropped already do not exist, that should
> > be ok. However, this might cause problems with other databases.
> >
> > Matt Raible wrote:
> >
> >> I ended up having to comment out 4 of the indexes b/c they didn't
> >> exist in my database. Here's the list from the MySQL
> >> 130-to-200-migration script.
> >>
> >> --alter table webpage drop index webpage_id_index;
> >> --alter table website drop index website_id_index;
> >> --alter table folderassoc drop index folderassoc_relation_index;
> >> --alter table weblogentry drop index weblogentry_pinnedtomain_index;
> >>
> >> I think it's important that we remove these (or add an "if exists")
> >> b/c the migration scripts seems to leave the database in an unknown
> >> state when this fails (rather than rolling back all the changes).
> >>
> >> Matt
> >>
> >>
> >> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>
> >>
> >>> When trying to upgrade from 1.3 to 2.0 using the
> >>> 130-to-200-migration.sql script, I got an error:
> >>>
> >>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> >>> that column/key exists
> >>>
> >>> Any ideas?
> >>>
> >>> Matt
> >>>
> >>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>>
> >>>
> >>>> I should mention my prod and test environments:
> >>>>
> >>>> Production on Linux:
> >>>>
> >>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> >>>> Tomcat 5.0.28
> >>>> JDK 5
> >>>>
> >>>> Testing on OS X:
> >>>>
> >>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> >>>> Tomcat 5.5.9
> >>>> JDK 5
> >>>>
> >>>> Matt
> >>>>
> >>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> >>>>
> >>>>
> >>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> >>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
> >>>>> one issue.
> >>>>>
> >>>>> On raibledesigns.com, if you scroll to the bottom of the page, there
> >>>>> will be a link on the left side that allows you to navigate to the
> >>>>> previous entry. It seems like it's a bug in 1.2 that I can only
> >>>>> navigate to the single previous entry, rather than a list of entries.
> >>>>> In 1.3, there is no link at all. Did this functionality get removed
> >>>>> in 1.3?
> >>>>>
> >>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> >>>>> noticed there are no navigation links to go to next/prev/main when
> >>>>> viewing a single entry.
> >>>>>
> >>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to my
> >>>>> theme. However, my main page is _sunsets and is not displayed as a
> >>>>> menu item - but it does show up as the name to navigate back to from
> >>>>> the #showNextPreviousLinks() macro.
> >>>>>
> >>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> >>>>> than an hour.
> >>>>>
> >>>>> Matt
> >>>>>
> >>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> >>>>>
> >>>>>
> >>>>>> Thanks to our testers, over the weekend we've found and fixed these:
> >>>>>>
> >>>>>> * removed session-factory name argument from Hibernate configuration
> >>>>>> file
> >>>>>> * restored missing create-user page
> >>>>>> * restored missing weblog maintenance page
> >>>>>> * added cache flush to save of bookmarks
> >>>>>> * fixed array-index out of bounds problem when no default blogroll
> >>>>>> defined
> >>>>>>
> >>>>>> Are we ready for a new RC, or is there some other evil lurking?
> >>>>>>
> >>>>>> - Dave
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>
> >>
> >>
> >>
> >
> >
>
>
Re: Time for Roller 2.0 RC2?
Posted by Anil Gangolli <an...@busybuddha.org>.
I retested my upgrade and I didn't see these errors. Is it possible
that you had arrived at your 1.3 database schema via a development build
of the schema that didn't include all of the indices?
This happened to me on two different indices.
ERROR 1091 (42000): Can't DROP 'pingqueueentry_pingtargetid_index';
check that column/key exists
ERROR 1091 (42000): Can't DROP 'pingqueueentry_websiteid_index'; check
that column/key exists
I tracked my errors back to the fact that I had arrived at my 1.3 schema
via a 1.2 dev schema, not actually the 1.2 release schema; late in the
game in 1.2, some additional indices were added. I think this happened
just before 1.0 or 1.1 as well. Anyway, the 1.3 to 2.0 upgrade didn't
find these when dropping them, but they are indeed present if built from
the official released versions.
--a.
Anil Gangolli wrote:
>
> Typically DDL (schema modifying commands) are not transactional.
> There is no way to commit versus roll them back. So yes, it is
> especially important that they work properly with no errors. If
> errors are skipped during sourcing (which I think is the default in
> MySQL) and if objects being dropped already do not exist, that should
> be ok. However, this might cause problems with other databases.
>
> Matt Raible wrote:
>
>> I ended up having to comment out 4 of the indexes b/c they didn't
>> exist in my database. Here's the list from the MySQL
>> 130-to-200-migration script.
>>
>> --alter table webpage drop index webpage_id_index;
>> --alter table website drop index website_id_index;
>> --alter table folderassoc drop index folderassoc_relation_index;
>> --alter table weblogentry drop index weblogentry_pinnedtomain_index;
>>
>> I think it's important that we remove these (or add an "if exists")
>> b/c the migration scripts seems to leave the database in an unknown
>> state when this fails (rather than rolling back all the changes).
>>
>> Matt
>>
>>
>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>
>>
>>> When trying to upgrade from 1.3 to 2.0 using the
>>> 130-to-200-migration.sql script, I got an error:
>>>
>>> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
>>> that column/key exists
>>>
>>> Any ideas?
>>>
>>> Matt
>>>
>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>
>>>
>>>> I should mention my prod and test environments:
>>>>
>>>> Production on Linux:
>>>>
>>>> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>> Tomcat 5.0.28
>>>> JDK 5
>>>>
>>>> Testing on OS X:
>>>>
>>>> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>> Tomcat 5.5.9
>>>> JDK 5
>>>>
>>>> Matt
>>>>
>>>> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>>
>>>>
>>>>> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
>>>>> tonight. I'm just finishing up the 1.3 upgrade and I've only found
>>>>> one issue.
>>>>>
>>>>> On raibledesigns.com, if you scroll to the bottom of the page, there
>>>>> will be a link on the left side that allows you to navigate to the
>>>>> previous entry. It seems like it's a bug in 1.2 that I can only
>>>>> navigate to the single previous entry, rather than a list of entries.
>>>>> In 1.3, there is no link at all. Did this functionality get removed
>>>>> in 1.3?
>>>>>
>>>>> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
>>>>> noticed there are no navigation links to go to next/prev/main when
>>>>> viewing a single entry.
>>>>>
>>>>> I was able to fix this by adding in "#showNextPreviousLinks()" to my
>>>>> theme. However, my main page is _sunsets and is not displayed as a
>>>>> menu item - but it does show up as the name to navigate back to from
>>>>> the #showNextPreviousLinks() macro.
>>>>>
>>>>> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
>>>>> than an hour.
>>>>>
>>>>> Matt
>>>>>
>>>>> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>>>>>
>>>>>
>>>>>> Thanks to our testers, over the weekend we've found and fixed these:
>>>>>>
>>>>>> * removed session-factory name argument from Hibernate configuration
>>>>>> file
>>>>>> * restored missing create-user page
>>>>>> * restored missing weblog maintenance page
>>>>>> * added cache flush to save of bookmarks
>>>>>> * fixed array-index out of bounds problem when no default blogroll
>>>>>> defined
>>>>>>
>>>>>> Are we ready for a new RC, or is there some other evil lurking?
>>>>>>
>>>>>> - Dave
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>
>>
>>
>>
>
>
Re: Time for Roller 2.0 RC2?
Posted by Anil Gangolli <an...@busybuddha.org>.
Typically DDL (schema modifying commands) are not transactional. There
is no way to commit versus roll them back. So yes, it is especially
important that they work properly with no errors. If errors are skipped
during sourcing (which I think is the default in MySQL) and if objects
being dropped already do not exist, that should be ok. However, this
might cause problems with other databases.
Matt Raible wrote:
>I ended up having to comment out 4 of the indexes b/c they didn't
>exist in my database. Here's the list from the MySQL
>130-to-200-migration script.
>
>--alter table webpage drop index webpage_id_index;
>--alter table website drop index website_id_index;
>--alter table folderassoc drop index folderassoc_relation_index;
>--alter table weblogentry drop index weblogentry_pinnedtomain_index;
>
>I think it's important that we remove these (or add an "if exists")
>b/c the migration scripts seems to leave the database in an unknown
>state when this fails (rather than rolling back all the changes).
>
>Matt
>
>
>On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>
>
>>When trying to upgrade from 1.3 to 2.0 using the
>>130-to-200-migration.sql script, I got an error:
>>
>>ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
>>that column/key exists
>>
>>Any ideas?
>>
>>Matt
>>
>>On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>
>>
>>>I should mention my prod and test environments:
>>>
>>>Production on Linux:
>>>
>>>MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
>>>Tomcat 5.0.28
>>>JDK 5
>>>
>>>Testing on OS X:
>>>
>>>MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
>>>Tomcat 5.5.9
>>>JDK 5
>>>
>>>Matt
>>>
>>>On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
>>>
>>>
>>>>I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
>>>>tonight. I'm just finishing up the 1.3 upgrade and I've only found
>>>>one issue.
>>>>
>>>>On raibledesigns.com, if you scroll to the bottom of the page, there
>>>>will be a link on the left side that allows you to navigate to the
>>>>previous entry. It seems like it's a bug in 1.2 that I can only
>>>>navigate to the single previous entry, rather than a list of entries.
>>>>In 1.3, there is no link at all. Did this functionality get removed
>>>>in 1.3?
>>>>
>>>>Also, comparing my raibledesigns.com blog to my jroller.com blog, I
>>>>noticed there are no navigation links to go to next/prev/main when
>>>>viewing a single entry.
>>>>
>>>>I was able to fix this by adding in "#showNextPreviousLinks()" to my
>>>>theme. However, my main page is _sunsets and is not displayed as a
>>>>menu item - but it does show up as the name to navigate back to from
>>>>the #showNextPreviousLinks() macro.
>>>>
>>>>On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
>>>>than an hour.
>>>>
>>>>Matt
>>>>
>>>>On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
>>>>
>>>>
>>>>>Thanks to our testers, over the weekend we've found and fixed these:
>>>>>
>>>>>* removed session-factory name argument from Hibernate configuration
>>>>>file
>>>>>* restored missing create-user page
>>>>>* restored missing weblog maintenance page
>>>>>* added cache flush to save of bookmarks
>>>>>* fixed array-index out of bounds problem when no default blogroll
>>>>>defined
>>>>>
>>>>>Are we ready for a new RC, or is there some other evil lurking?
>>>>>
>>>>>- Dave
>>>>>
>>>>>
>>>>>
>>>>>
>
>
>
>
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
I ended up having to comment out 4 of the indexes b/c they didn't
exist in my database. Here's the list from the MySQL
130-to-200-migration script.
--alter table webpage drop index webpage_id_index;
--alter table website drop index website_id_index;
--alter table folderassoc drop index folderassoc_relation_index;
--alter table weblogentry drop index weblogentry_pinnedtomain_index;
I think it's important that we remove these (or add an "if exists")
b/c the migration scripts seems to leave the database in an unknown
state when this fails (rather than rolling back all the changes).
Matt
On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> When trying to upgrade from 1.3 to 2.0 using the
> 130-to-200-migration.sql script, I got an error:
>
> ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
> that column/key exists
>
> Any ideas?
>
> Matt
>
> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > I should mention my prod and test environments:
> >
> > Production on Linux:
> >
> > MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> > Tomcat 5.0.28
> > JDK 5
> >
> > Testing on OS X:
> >
> > MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> > Tomcat 5.5.9
> > JDK 5
> >
> > Matt
> >
> > On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > > I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> > > tonight. I'm just finishing up the 1.3 upgrade and I've only found
> > > one issue.
> > >
> > > On raibledesigns.com, if you scroll to the bottom of the page, there
> > > will be a link on the left side that allows you to navigate to the
> > > previous entry. It seems like it's a bug in 1.2 that I can only
> > > navigate to the single previous entry, rather than a list of entries.
> > > In 1.3, there is no link at all. Did this functionality get removed
> > > in 1.3?
> > >
> > > Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> > > noticed there are no navigation links to go to next/prev/main when
> > > viewing a single entry.
> > >
> > > I was able to fix this by adding in "#showNextPreviousLinks()" to my
> > > theme. However, my main page is _sunsets and is not displayed as a
> > > menu item - but it does show up as the name to navigate back to from
> > > the #showNextPreviousLinks() macro.
> > >
> > > On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> > > than an hour.
> > >
> > > Matt
> > >
> > > On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > > > Thanks to our testers, over the weekend we've found and fixed these:
> > > >
> > > > * removed session-factory name argument from Hibernate configuration
> > > > file
> > > > * restored missing create-user page
> > > > * restored missing weblog maintenance page
> > > > * added cache flush to save of bookmarks
> > > > * fixed array-index out of bounds problem when no default blogroll
> > > > defined
> > > >
> > > > Are we ready for a new RC, or is there some other evil lurking?
> > > >
> > > > - Dave
> > > >
> > > >
> > >
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
When trying to upgrade from 1.3 to 2.0 using the
130-to-200-migration.sql script, I got an error:
ERROR 1091 (42000) at line 111: Can't DROP 'webpage_id_index'; check
that column/key exists
Any ideas?
Matt
On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> I should mention my prod and test environments:
>
> Production on Linux:
>
> MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
> Tomcat 5.0.28
> JDK 5
>
> Testing on OS X:
>
> MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
> Tomcat 5.5.9
> JDK 5
>
> Matt
>
> On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> > I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> > tonight. I'm just finishing up the 1.3 upgrade and I've only found
> > one issue.
> >
> > On raibledesigns.com, if you scroll to the bottom of the page, there
> > will be a link on the left side that allows you to navigate to the
> > previous entry. It seems like it's a bug in 1.2 that I can only
> > navigate to the single previous entry, rather than a list of entries.
> > In 1.3, there is no link at all. Did this functionality get removed
> > in 1.3?
> >
> > Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> > noticed there are no navigation links to go to next/prev/main when
> > viewing a single entry.
> >
> > I was able to fix this by adding in "#showNextPreviousLinks()" to my
> > theme. However, my main page is _sunsets and is not displayed as a
> > menu item - but it does show up as the name to navigate back to from
> > the #showNextPreviousLinks() macro.
> >
> > On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> > than an hour.
> >
> > Matt
> >
> > On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > > Thanks to our testers, over the weekend we've found and fixed these:
> > >
> > > * removed session-factory name argument from Hibernate configuration
> > > file
> > > * restored missing create-user page
> > > * restored missing weblog maintenance page
> > > * added cache flush to save of bookmarks
> > > * fixed array-index out of bounds problem when no default blogroll
> > > defined
> > >
> > > Are we ready for a new RC, or is there some other evil lurking?
> > >
> > > - Dave
> > >
> > >
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
I should mention my prod and test environments:
Production on Linux:
MySQL 3.23.56-Max-log with mysql-connector-java-3.1.10-bin.jar
Tomcat 5.0.28
JDK 5
Testing on OS X:
MySQL 5.0.15 with mysql-connector-java-3.1.7-bin.jar
Tomcat 5.5.9
JDK 5
Matt
On 11/13/05, Matt Raible <mr...@gmail.com> wrote:
> I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
> tonight. I'm just finishing up the 1.3 upgrade and I've only found
> one issue.
>
> On raibledesigns.com, if you scroll to the bottom of the page, there
> will be a link on the left side that allows you to navigate to the
> previous entry. It seems like it's a bug in 1.2 that I can only
> navigate to the single previous entry, rather than a list of entries.
> In 1.3, there is no link at all. Did this functionality get removed
> in 1.3?
>
> Also, comparing my raibledesigns.com blog to my jroller.com blog, I
> noticed there are no navigation links to go to next/prev/main when
> viewing a single entry.
>
> I was able to fix this by adding in "#showNextPreviousLinks()" to my
> theme. However, my main page is _sunsets and is not displayed as a
> menu item - but it does show up as the name to navigate back to from
> the #showNextPreviousLinks() macro.
>
> On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
> than an hour.
>
> Matt
>
> On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> > Thanks to our testers, over the weekend we've found and fixed these:
> >
> > * removed session-factory name argument from Hibernate configuration
> > file
> > * restored missing create-user page
> > * restored missing weblog maintenance page
> > * added cache flush to save of bookmarks
> > * fixed array-index out of bounds problem when no default blogroll
> > defined
> >
> > Are we ready for a new RC, or is there some other evil lurking?
> >
> > - Dave
> >
> >
>
Re: Time for Roller 2.0 RC2?
Posted by Matt Raible <mr...@gmail.com>.
I'm testing an upgrade of my site from 1.2 to 1.3, as well as 2.0
tonight. I'm just finishing up the 1.3 upgrade and I've only found
one issue.
On raibledesigns.com, if you scroll to the bottom of the page, there
will be a link on the left side that allows you to navigate to the
previous entry. It seems like it's a bug in 1.2 that I can only
navigate to the single previous entry, rather than a list of entries.
In 1.3, there is no link at all. Did this functionality get removed
in 1.3?
Also, comparing my raibledesigns.com blog to my jroller.com blog, I
noticed there are no navigation links to go to next/prev/main when
viewing a single entry.
I was able to fix this by adding in "#showNextPreviousLinks()" to my
theme. However, my main page is _sunsets and is not displayed as a
menu item - but it does show up as the name to navigate back to from
the #showNextPreviousLinks() macro.
On to 1.3 to 2.0, then 1.2 to 2.0. Should have the results in less
than an hour.
Matt
On 11/13/05, Dave Johnson <da...@rollerweblogger.org> wrote:
> Thanks to our testers, over the weekend we've found and fixed these:
>
> * removed session-factory name argument from Hibernate configuration
> file
> * restored missing create-user page
> * restored missing weblog maintenance page
> * added cache flush to save of bookmarks
> * fixed array-index out of bounds problem when no default blogroll
> defined
>
> Are we ready for a new RC, or is there some other evil lurking?
>
> - Dave
>
>