GrugInAus

What @soulsource said is likely the issue. The Linux file system is case-sensitive and sometimes the config directory has a capital C. I'd suggest checking that. This is a potential bug that @blackrack is aware of.

Fair call. I wasn't sure the water was part of the Proland port or something you added, but either way from reading your updates in this thread there has still been a huge amount of debugging and tweaking to get it all working with KSP so you deserve some of the credit. :-)

Shut Up!! That windy weather one looks unreal!! Blackrack - You are a god. /edit: Or technically "looks real", for those who want to be pedantic. :-P

Old posts viewed fine in the browser so its outputting correctly. I wouldn't assume that vBulletin did any conversion between formats and so I can only assume that the issue was the database table collation was wrong and that's what broke the conversion to IPS. Whatever the issue, given the data used to output correctly it should be possible to script something to either export it correctly, or convert the raw data to the correct format. I'm not sure why it is likely to be a "very tough operation"?

Ok, looks like the redirect is configured now... but old links still break if there is anything existing after the thread ID (which is just about every single KSP Forum link in existance on the web). @KasperVld You need to set your little script to trim anything after the thread ID ([0-9]+) or from the "-" onwards.

Kasper already said that he has a script to convert from the old ID's to the new ones suggesting that they must have logged the translation of ID's when created in the new BB.

Setting up an Apache/Nginx regex based redirect rule for a URL is simple. The /threads/ URI should be redirecting to the showthread.php?t= URI. Along those lines - I thought part of the point of this move was to move into this decade... which has the index.php? portion not been removed from the URI in exactly the same way as above. This is normal simple stuff. /Edit: If you are relying on your webhost to manage your Apache/Nginx configuration they should have advised you of these possibilities before the migration so that they were a complete non-issue. I wouldn't be even remotely happy with them.