Author Topic: problem after upgrade to knowlegderoot 1.0.3  (Read 10553 times)

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
problem after upgrade to knowlegderoot 1.0.3
« on: February 12, 2014, 05:54:22 PM »
Dear,

I run: FreeBSD milou.muhc.mcgill.ca 8.4-RELEASE-p4 FreeBSD 8.4-RELEASE-p4 #0: Mon Sep  9 23:00:58 UTC 2013     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  i386

upgrade knowlegderoot to 1.0.3 from 0.9.8.6

apache: apache24-2.4.4_1
php: php5-5.4.16
mysql: mysql-server-5.1.70
php-mysql: php5-mysql-5.4.16
I had installed also php5-mysqli-5.4.16

I followed the upgrade doc and I ran the update.php script and I modified my php.ini and restarted apache24
error_reporting =  = E_ALL & ~E_DEPRECATED

I have still the following error:

Code: [Select]
Strict Standards: Declaration of db::connect() should be compatible with db_core::connect() in /usr/local/www/apache24/data/knowledgeroot/include/class-mysql.php on line 160
And

Code: [Select]
Warning: Invalid argument supplied for foreach() in /usr/local/www/apache24/data/knowledgeroot/include/class-knowledgeroot-extension.php on line 51
And

Code: [Select]
Notice: Undefined index: symlink in /usr/local/www/apache24/data/knowledgeroot/include/class-tree.php on line 259
In fact I have a full page of errors, warnings and notices, take a look to my screenshots

Thank you in advance for your help

l2f

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #1 on: February 12, 2014, 07:00:56 PM »
Hi,

please try it with:
error_reporting = E_ALL & ~E_DEPRECATED & ~E_NOTICE
in your php.ini.

regards,
Frank

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #2 on: February 12, 2014, 07:52:00 PM »
Dear,

I did it and I got the 3 following errors (great deal only 3 errors remainings ):

Code: [Select]
Strict Standards: Declaration of db::connect() should be compatible with db_core::connect() in /usr/local/www/apache24/data/knowledgeroot/include/init.php on line 70

Strict Standards: Declaration of db::query() should be compatible with db_core::query() in /usr/local/www/apache24/data/knowledgeroot/include/init.php on line 70

Warning: Invalid argument supplied for foreach() in /usr/local/www/apache24/data/knowledgeroot/include/class-knowledgeroot-extension.php on line 51

I tested the navigation and everything seems to work great (see the sreenshot).

Thank you for your help

l2f

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #3 on: February 12, 2014, 11:25:13 PM »
Hi,

i will check that in my environment and will try to give you a patch or i will make a short bugfixrelease.

Frank

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #4 on: February 13, 2014, 09:38:45 PM »
Hi,

i have tried to fix the problems.
You could use the attached files for testing.
Remove the suffix ".txt" at saving time ;)
And save the files in your knowledgeoroot/include folder.

I am waiting for your feedback.
Frank

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #5 on: February 13, 2014, 11:52:40 PM »
Dear,

Thanks a lot, busy day at work, will try tomorrow (friday) the patch.  As I see you can produce some patch, I have some errors on the admin interface too, if you can look at them if you have time( if ok, tomorrow, I will send them with a screenshot).

Thank you in advance for your precious help and time.

Regards,

l2f

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #6 on: February 14, 2014, 09:11:05 AM »
Hi,

no problem.

Let me know the problems.
I will try to fix them and i think i will create a official small bugfix release after that.

regards,
Frank

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #7 on: February 14, 2014, 04:40:15 PM »
Dear,

Great.

Code: [Select]
Strict Standards: Declaration of db::connect() should be compatible with db_core::connect() in /usr/local/www/apache24/data/knowledgeroot/include/init_admin.php on line 79

Strict Standards: Declaration of db::query() should be compatible with db_core::query() in /usr/local/www/apache24/data/knowledgeroot/include/init_admin.php on line 79

Regards,

l2f

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #8 on: February 14, 2014, 04:55:35 PM »
Dear,

I applied the patch for class-db-core and class-knowlegderoot-extension and it works great on the admin interface: no more errors :)

Good work :)

I had to change some permission on somes directories and files:
Code: [Select]
chmod -R 775 extension/libsecure/htmlpurifier/HTMLPurifier/DefinitionCache/Serializer/HTML
Code: [Select]
chmod 775 extension/libsecure/htmlpurifier/HTMLPurifier/DefinitionCache/Serializer.php
I don't know if there is a security hole with those changes ?

but I have the following errors from the main page:
Code: [Select]
Warning: mysql_fetch_assoc() expects parameter 1 to be resource, boolean given in /usr/local/www/apache24/data/knowledgeroot/include/class-mysql.php on line 113
See the screenshot

Regards,

l2f

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #9 on: February 14, 2014, 05:56:32 PM »
Dear,

Ooops missing information on the new version with the patch provided: see the screenshot

old version: knowlegderoot-5
new version without patch: knowlegderoot-7
new version with the patch provided: knowlegderoot-6

The admin interface is ok: screenshot knowlegderoot-8

Regards,

l2f

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #10 on: February 18, 2014, 05:02:00 PM »
Hi,

sorry for late reply.

Does the errors are only shown on the login page or on every page?

Frank

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #11 on: February 18, 2014, 08:03:12 PM »
Dear,

No problem, I was finally able to run the old version on the new server, so I have an alternate solution.

On a unpatch version of 1.0.3 only on the top, see the screenshots
9-unpatch: after login
10-unpatch: before login (logout)
11-unpatch: at login prompt

Regards,

l2f

« Last Edit: February 18, 2014, 08:07:08 PM by l2f »

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #12 on: February 19, 2014, 04:07:17 PM »
Hi,

thanks for the info.
But with my patch for version 1.0.3 does an error exists or is all solved?

Frank

Offline l2f

  • User
  • *
  • Posts: 22
    • View Profile
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #13 on: February 21, 2014, 06:07:37 PM »
Dear,

- For the admintration page with your patch = no more errors :)
see screenshot: knowlegderoot-8.gif

- For the knowlegderoot pages with your patch = 3 more errors but no content displayed ?! :-o
see screenshot: knowlegderoot-6.gif

- For the knowlegderoot pages without your patch = errors but content displayed :)
see screenshots: knowlegderoot-7.gif, knowlegderoot-9.gif, knowlegderoot-10.gif and knowlegderoot-11.gif


Regards,

l2f

Offline admin

  • Administrator
  • User
  • *****
  • Posts: 688
    • View Profile
    • http://www.lordlamer.de
Re: problem after upgrade to knowlegderoot 1.0.3
« Reply #14 on: March 11, 2014, 10:13:42 AM »
Hi,

is it possible that i could get a full dump from your database?
Or only a dump with the structure and without data?

It seems that this is a update problem.

Frank