Question [Solved] K 1.5.6, CB 1.2.1: CB plugin prevents access to forum (Frontend/Backend)

My comments in blue:

I first tried to re-intall 1.5.6 NO LUCK - I figured as much; your database sounded as though it was corrupted; I suspect you've lost a some table keys and/or indexes.

Then I tried to upgrade to 1.5.9 NO LUCK - admin component screen is just blank Similar comment as above.

So I tried this

1. BACKED up OLD Table (beofre i did anything even reinstall 1.5.6) Good move
2. REMOVED Data Base tables If your database tables were corrupted, this may have been a good idea or it may have been unnecessary; the upgrade might have fixed the problem, I don't know.
3. Delete by hand (FTP) admin component and component dirs Probably unnecessary. The upgrade would overwrite and replace whatever you had there.
4. Installed 1.5.9 (worked)
5. can get into my admin section and the live forums. Something good came from it.
6. I have my old backups how do I [put] back my config and my Forums and all the content that was there before?Well, here's the thing ...

Because you deleted the old tables you've got a bit of a problem. The upgrade (particularly going forward through K 1.5. makes a few changes to the database structure. I don't know, though, whether the upgrade installation process carries out an integrity check of your existing (i.e. K 1.5.6 tables) and repairs any errors that it finds ... but it probably doesn't.

Like I said (in reference to Matthew 3:11-12) it may take a keener mind and a better technician than me to restore your old data but I'm guessing that it should be possible because you've got a backup. Let's leave this for a little while. At least your system is up and running again. We'll try to mend the "sick and wounded" as best we can.

I have discussed your situation with "he whose sandals I am unworthy to take off", and this is what he suggested

It may be possible to recover your old data. It may be that your problem was caused in the first instance by a corrupted jos_fb_config table. It may also have been the result of a bad installation of JomSocial (I don't know if that is relevant) which has been known to cause the "white screen of anguish" in other Kunena installations.

One other way of tracking the source of your errors is to modify your php.ini file (if you have access to it) by adding the following statements: or place the following line into your .htaccess file: (Don't ask me to confirm if I got the syntax correct - I'm just the messenger, OK :blush: )

You can try to bring your system back as follows:

1. restore the backup copies that you've made of your jos_fb* tables
2. RENAME the jos_fb_config table
3. perform another K 1.5.9 install.

Re-installing K 1.5.9 will insert a new jos_fb_config table.

This may be all that is needed. It may not improve matters at all. However, "he whose sandals I am unworthy to take off" also said that users will only exacerbate the situation if they remove tables by hand.

The changes you make to the error logging will be captured in the Apache server logs for more detailed analysis of the situation.

I hope I have transmitted the message faithfully. "He whose sandals I am unworthy to take off" has had a rough day and needs his sleep.

Ok solved the WHOLE PROBLEM this is so strange..

I upgraded JOBS component the day before.. Tested it all out things worked.. then didnt' think much of it - as then i did have that mysql problem.. so i thought it was that..

Turns out that after doing some more DEBUGGING on Community builder - there was a plugin that was corrupting CM and Kunena..

Reinstalled the plug in for the JOBS - and vola it was fixed.

So what i did today. was

1. DELETE kunena 1.5.9
2. Delete all the TABLES
3. reintalled 1.5.6
4. empty all the TALBES
5. import my kunena back up i made from before
6. My forums back up and running great.
7. upgrade to 1.5.9

VOLA all becuase of a stupid plugin in Community builder..

:woohoo:

Thank you. Because you have supplied the information missing from your first message I am moving this topic to the Community Builder category. The genesis of this problem lies with the JOBS feature ( www.instantphp.com/ ) and the wrong plug-in for CB.

I am also locking this topic with an important message to anyone else tempted to follow your lead: Make regular backups of your data, keep Kunena up-to-date with the latest stable version, always thoroughly test new features on a test site before releasing into production ... and don't delete database tables by hand..