I have just restored the database from a backup I had taken on Thursday 15th February.
This appears to have sorted out the start page issue. But i would be grateful if others with more knowledge of the system could take a look. I don't believe there has been any changes to tickets etc. But again if you know of any changes they may need to be reapplied. Now I must say sorry. It appears that last night when setting up the new Bloodhound environment I used the wrong database. I will try not to make the same mistake again. Cheers John On 18 February 2015 at 16:26, Ryan J Ollos <[email protected]> wrote: > On Tue, Feb 17, 2015 at 5:04 PM, Branko Čibej <[email protected]> wrote: > > > On 17.02.2015 20:22, Gary Martin wrote: > > > On 17/02/15 14:28, John Chambers wrote: > > > > > > Incidentally, I think I specified the wrong redirect in my last > > > message as we use products rather than product so that redirect should > > > be: > > > > > > https://issues.apache.org/bloodhound => > > > https://issues.apache.org/bhound/products/BLOODHOUND > > > > > > We can make the right redirects work without Infra involvement and > > without changing the root URL https://issues.apache.org/bloodhound so > > something horrible like .../bhound. > > > > Yeah, everything else sounds fine to me, but I also hope we can avoid > "bhound" in the URL. > > > > All it takes is to have a careful look at the current set of URLs used > > for BH stuff and then writing a number of rewrite rules that will catch > > only those URLs, but not any new .../bloodhound/product URLs. If that > > means we invent a virtual location, e.g., .../bloodhound/main to refer > > to the global environment, that's fine, IMO. Better than the current > > proposal in any case. > > > > -- Brane > > >
