Leser in diesem Thema: 1 Anonyme(r)
Gast  
Re: Xoops and php4.4 uncompatible?? #7
Indeed, UXMichael is completely right! The functions and classes have to be rewritten.

But as I mentionend this beforehand - the Core Devs are fully aware of this.
UXMichael UXMichael
  • "myXOOPs"-Neuling
  • "myXOOPs"-Neuling
  • Registriert seit: 23.10.2005
  • Gruppe: Mitglieder
  • Beiträge: 53
  • Offline
  • Geschrieben von: 28.10.2005
Re: Xoops and php4.4 uncompatible?? #6
Its not a bug. In php4.4 was fixed some bugs from prior 4.4 so the messages are correct.
Its on xoops development to fix this.
Werbung  

Hier könnte auch Ihre Werbung stehen!
Kontaktieren Sie uns dazu und wir unterbreiten Ihnen ein Angebot.
Shine Shine
  • "myXOOPs"-Neuling
  • "myXOOPs"-Neuling
  • Registriert seit: 02.11.2002
  • Aus: Niederlande
  • Gruppe: Mitglieder
  • Beiträge: 91
  • Offline
  • Geschrieben von: 28.10.2005
Re: Xoops and php4.4 uncompatible?? #5
Hm, I hardly can imagine that I am almost the only one who has to work with php4.4 (since yesterday).
I am curious if other encouter the same msgs who had a php upgrade to this version during a running xoopswebsite.
Zitat:
..some notices ..

This is an understatement. The list of core notice msgs is veryyyyyyyyyy long. And I mean very looooong. Wau to long.
I read the article, but sorry to say I don't understand this technical talk.

Grtz., Shine
Gast  
Re: Xoops and php4.4 uncompatible?? #4
Hmmm, found an interesting article with a link to php.net about references.

I do know that the core devs are fully aware of this because they updated the xoops-server also to PHP 4.4 and got some notices and I think this will be fixed.

Here is the link to the article
Shine Shine
  • "myXOOPs"-Neuling
  • "myXOOPs"-Neuling
  • Registriert seit: 02.11.2002
  • Aus: Niederlande
  • Gruppe: Mitglieder
  • Beiträge: 91
  • Offline
  • Geschrieben von: 28.10.2005
Re: Xoops and php4.4 uncompatible?? #3
No, they are all Notice msgs.

I'll copy a tiny some of the long long list.
Since the site is closed, on the inlogscreen:
Notice [PHP]: Only variable references should be returned by reference in file include/functions.php line 493
Notice [PHP]: Only variables should be assigned by reference in file class/database/mysqldatabase.php line 239
Notice [PHP]: Only variable references should be returned by reference in file class/database/mysqldatabase.php line 386

After inlog:

Notice [PHP]: Only variable references should be returned by reference in file include/functions.php line 493
Notice [PHP]: Only variables should be assigned by reference in file class/database/mysqldatabase.php line 239
Notice [PHP]: Only variable references should be returned by reference in file class/database/mysqldatabase.php line 386
Notice [PHP]: Only variable references should be returned by reference in file kernel/config.php line 188
Notice [PHP]: Only variable references should be returned by reference in file kernel/configitem.php line 108
Notice [PHP]: Only variable references should be returned by reference in file class/module.textsanitizer.php line 260
Notice [PHP]: Only variable references should be returned by reference in file kernel/object.php line 289
Notice [PHP]: Only variable references should be returned by reference in file class/database/database.php line 128
Notice [PHP]: Only variable references should be returned by reference in file class/module.textsanitizer.php line 260
Notice [PHP]: Only variable references should be returned by reference in file kernel/object.php line 289
Notice [PHP]: Only variable references should be returned by reference in file kernel/configitem.php line 108
Notice [PHP]: Only variable references should be returned by reference in file kernel/configitem.php line 97
Notice [PHP]: Only variables should be assigned by reference in file class/database/mysqldatabase.php line 239
Notice [PHP]: Only variable references should be returned by reference in file class/database/mysqldatabase.php line 386
Notice [PHP]: Only variables should be assigned by reference in file class/module.textsanitizer.php line 112
Notice [PHP]: Only variables should be assigned by reference in file header.php line 136

And so on............pages long. Some repeatatly and all kinds of sorts. They ALL are related to the core.
If you feel like viewing my php-info, please let me know and I'll pm you the url to this file.

Grtz., Shine
Gast  
Re: Xoops and php4.4 uncompatible?? #2
I am not sure, but I read that these warning are caused by the way PHP4.4 was set up on the server.

So I assume that is not really a XOOPS-problem, but I have to investigate this again.

Error like this?

Zitat:
Warning [PHP]: preg_match: internal pcre_fullinfo() error -3
Shine Shine
  • "myXOOPs"-Neuling
  • "myXOOPs"-Neuling
  • Registriert seit: 02.11.2002
  • Aus: Niederlande
  • Gruppe: Mitglieder
  • Beiträge: 91
  • Offline
  • Geschrieben von: 28.10.2005
Xoops and php4.4 uncompatible?? #1
For some time I am running xoops 2.0.13.1 without any problems.
Today, after an Internetbreak of more then 24 hrs, I got surprised by a lot of core debug notices. The list is that long so it is absolutely undo-able to copy and paste the lists.
Surprised by it, I went searching and on the end I found out my hoster has done a php version upgrade to 4.4 just today. That way my conclusion is that this upgrade is problemcauser of it.

Is xoops 2.0.13.1 not php4.4 compatible?
What should I do to make these msgs disappear? Why does php4.4 upgrade cause so many core debug notices mesgs?

Grtz., Shine
Design by: XOOPS UI/UX Team