problem after upgrade to knowlegderoot 1.0.3

[l2f]

Dear,

schema only, small file size

If you need the data: no problem at all, no sensitive data.

Regards

Yves

[admin]

Hi,

i take a look on the dump yesterday. But found no special problem.
Would be nice to take also a look on the full dump.
For that use a private way to give me the dump. You could also anonymize the dump. clear title, content and password hashes.

My problem is that i did not get the errors you have :/

Frank

[l2f]

Dear,

Here the full dump, thank you in advance for your help and time

Regards,

Yves

[l2f]

Dear,

I did a full tar of my setup (may be via a virtualbox, you will be able to reproduce the bug, if you are unable to do so, I will do a vm for you (I will try to convert my setup into a vm) and I will try to download into my google drive and share it with you.  We will find a solution anyway)

Please remove the .jpg extension to untar: crash file size. I will find a way to send you the file

directory: /usr/local/www/apache24/data/knowledgeroot
uname: FreeBSD milou.muhc.mcgill.ca 8.4-RELEASE-p7 FreeBSD 8.4-RELEASE-p7 #0: Sat Jan 11 01:06:55 UTC 2014     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386

permissions:
drwxr-xr-x  14 nobody  nobody   512B Feb 12 13:43 knowledgeroot

I run apache24 with the nobody account because Mantis refused to send e-mail if I run apache24 with "www" account

Regards,

Yves

[l2f]

Dear,

I sent it via your admin e-mail: link to my Google Drive.

Regards,

Yves

[l2f]

Dear,

My php.ini and php.conf

Regards,

Yves

[admin]

Hi,

thanks for all the stuff.
I will try to debug this this evening

Frank

[admin]

Hi,

ok with the php.ini i could recover the problem.
I am working on a solution for that.

Frank

[l2f]

Dear,

Great, take it easy I will be in vacation for the next week, I will be back the 25th of march

Regards,

Yves

[admin]

Hi,

i think i found the problem.
You are missing the table "access" in your database! So this makes the trouble.

So the question is how it could be lost.
Is it available in your old installation?
How did you dublicate the database to update to version 1.0.3?

Frank

[l2f]

Dear,

I double checked and if I remembered well, I did a fresh install of the version 1.0.3 and I loaded the dump from the version 0.9.8 into this fresh install.

So, today I did a fresh install without loading the data and adding any patches (better to start again from the starting point).

Regards,

Yves

[l2f]

Dear,

Screenshot of the new db (schema)

Regards,

Yves

[admin]

Hi,

so all looks fine now?!

To fix the error messages you should apply the patch.
And i will try to make a small bugfix release in the next days to fix that.

Frank

[l2f]

Dear,

I did not load the dump data from the old version yet.

So I will apply your patch and see if the errors will be corrected.

After I will load my dump.  Do you have a procdure for that ?

Regards

Yves

[admin]

Hi,

the upgrade path is to have a database running from version 0.9.9 and run the update.php in Version 1.0.
That will do the update on the database.

For your situation you could try to only insert data.
So in your dump should not drop table or something like that.

Frank