On 16 July 2012 19:01, Rob Weir <robw...@apache.org> wrote: > On Mon, Jul 16, 2012 at 1:13 PM, sebb <seb...@gmail.com> wrote: >> On 16 July 2012 17:26, Rob Weir <robw...@apache.org> wrote: >>> On Mon, Jul 16, 2012 at 12:06 PM, Barry Storah <barrysto...@yahoo.com> >>> wrote: >>>> Hi, >>>> >>>> I keep getting a message to "Register Your OpenOffice.org", it is not >>>> possible as I always get the message - Internet Explorer cannot display >>>> the webpage, or from OpenOffice welcome page - get more information "the >>>> webpage cannot be found". >>>> >>> >>> Hi Barry, >>> >>> It sounds like you are installing an old version of OpenOffice. The >>> current version is 3.4 and it does not have a registration screen. >>> You can download the latest version from >>> http://download.openoffice.org. >>> >>> If for some reason you need to install the older version, you will get >>> the behavior you reported. The registration went to a Sun/Oracle >>> website that no longer is up. You can safely ignore that error. >> >> Would it be possible to get the destination URL re-instated? > > The registration URL's for OOo 3.3 look like this: > > https://registration2.services.openoffice.org/RegistrationWeb/register/<GUID>?prduct=OpenOffice.org&locale=en&cid-926117 > > So we should be able to handle this entirely with ASF.
Good. > But I thought there was another version that went directly to an > Oracle domain. Maybe that was OOo 3.4 beta 1? Should catch that too. > The question is: what could we do if even a fraction of the 8 million > downloads of AOO 3.4.0 led to a registration? Suggest they join the > ooo-announce list? (Can ezmlm handle 100,000 subscribers?) Follow us > on Twitter? At the very least we can point them to the FAQ's and > support pages. I'm not suggesting that 3.4.0 be updated to include registration, merely that it would be helpful to direct users of 3.3 to the new version, and let them know that the registration step has not failed. > If there is some way we can help users by having them view a > post-install registration screen, then we might add the registration > step back in future versions. In the meantime, avoiding the error message for users of earlier versions would be a kindness to end users. For every one person who bothered to report the error, there are presumably many others who also encountered the error. > -Rob > >> Ideally this would redirect to an ASF page (easier to maintain), where >> the user could be informed that there is a new version. >> Alternatively, the target page could do the same, with a link to the >> ASF for further information. >> >>> Regards, >>> >>> -Rob >>> >>> >>>> Regards, >>>> Barry Storah
