Jump to content


- - - - -

Old forums completly messed up


  • Please log in to reply
1 reply to this topic

#1 Makaaveli

Makaaveli

    Post-aholic

  • Members
  • PipPipPipPipPipPipPip
  • 579 posts
  • Real Name:Anthony
  • IPB Version:v3.2.x

Posted 28 August 2010 - 03:39 PM

Right, I have an old forums, which is IPB 2.3.6. I decided to start a new 3.0 forums, closing my old 2.3 forums down (in offline mode). My host then decided to move me to another better/faster server. I had backed up my old forums and everything.

THe problem is, on the new server I can't access my old forums, it's as if it's stuck in offline mode and keeps giving me an ips error because of it.

http://thisisblasphemy.com/forum

Fatal error: Call to a member function board_offline() on a non-object in /home/thisisbl/public_html/forum/sources/ipsclass.php on line 5747

Now if i Log in to admin acp and try clicking any of the links, the forums screw up more and i get an IPS error, everywhere. In which case I have to re-import the old database so the ips error doesn't come again. Basically, the forums are completly screwed, because I took a backup of it in "offline" mode...

This is aparently the fix - http://www.techyforu...p?showtopic=245

But... I don't have access to the original forums in the old server, since my admin said all files on the old server got deleted. Is there any other way to fix this problem? These forums are really important , i have stuff in there that i really need :S

Edited by Makaaveli, 28 August 2010 - 03:41 PM.


#2 AndyF

AndyF

    Cogito ergo sum

  • Management
  • PipPipPipPipPipPipPipPipPipPip
  • 8,414 posts
  • Location:Derby, UK
  • Real Name:Andy
  • IPB Version:v3.2.x
Contributor

Posted 28 August 2010 - 05:25 PM

I've seen this before. The problem is although you can edit the database and switch it back on, you cannot update the caches. IPS have a tool to do this (and theres one for 2.1 around but that one is no use) , not sure if they will still do that as 2.3.x is not really supported now.

The alternative 'fix' is to upgrade this database to 3.1 , then you will be able to fix it that way.

If you really wanted to stay on 2.3.x, you will need an external cache rebuild tool, although you have some other issues with this backup by the sounds of it (other errors)

Do a test anyway, upload this database somewhere and then upload 3x and attempt to upgrade the 'broken' database to 3x to see what happens. Remember to 'test' with just a copy of it though.

View my tutorials

Please do NOT pm me with support related questions unless requested.
If you are in need of help or assistance, please post on the forum in the appropriate section!



A Look Back - 1.0.1 - 1.3.1 - 2.0.0 - 2.1.7 - 2.2.0 - 2.3.6




1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users