[XOOPS] Problem bei Installation (Linux + Lampp)

[Mark.G.]

Ich möchte gerne lokal das CMS XOOPS (2.4.4) testen, bekomme bei der Installation leider jede menge "Strict Standards" Fehler, die Installation bleibt dann auf der Seite 11/14 stehen.

System:
Linux (Ubuntu 10.04)
xampp (lampp 1.7.3a)

Vorgang:
Installiere Xampp (laut Anleitung):
keine Probleme

Ändere Passwörter (/opt/lampp/lampp security):
laut Xampp Homepage ist jetzt die MySQL Datenbank deaktiviert (obwohl sie gestartet wurde), sie lässt sich jedoch ohne Probleme aufrufen

Ändere Rechte des htdocs Ordners auf 777:
keine Probleme

Kopiere den Inhalt von XOOPS htdocs in den htdocs Ordner von Xampp:
keine Probleme

Ändere Rechte des htdocs Ordners auf 777(damit auch die neuen Files nicht nur root sind):
keine Probleme

rufe localhost auf:
XOOPS installation wizard wird Angezeigt jedoch sind folgende Fehler über der Seite

Strict Standards: Redefining already defined constructor for class MyTextSanitizerExtension in /opt/lampp/htdocs/class/module.textsanitizer.php  on line 56

Strict Standards: Redefining already defined constructor for class MyTextSanitizer in /opt/lampp/htdocs/class/module.textsanitizer.php on line 197

Nach der "Configuration save" (Seite 7) kommen folgende Fehler hinzu:

Strict Standards: Redefining already defined constructor for class XoopsLogger in /opt/lampp/htdocs/class/logger/xoopslogger.php  on line 70

Strict Standards: Non-static method XoopsDatabaseFactory::getDatabase() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/install/class/dbmanager.php on line 47

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/install/class/dbmanager.php on line 49

Nach den "Initial settings" (Seite 9) kommen folgende Fehler hinzu:

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /opt/lampp/htdocs/class/logger/xoopslogger.php on line 371

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /opt/lampp/htdocs/class/logger/xoopslogger.php on line 371

Nach der "Data Insertion" (Seite 10) kommen ganz neue Fehler und die alten sind weg:

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/include/common.php on line 43

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Non-static method XoopsLoad::loadCoreConfig() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 110

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/class/preload.php on line 26

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/class/preload.php on line 27

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Non-static method XoopsPreload::getInstance() should not be called statically in /opt/lampp/htdocs/include/common.php on line 44

Strict Standards: Non-static method XoopsCache::read() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/preload.php on line 83

Strict Standards: Non-static method XoopsCache::getInstance() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/cache/xoopscache.php on line 266

Strict Standards: Declaration of XoopsCacheFile::write() should be compatible with that of XoopsCacheEngine::write() in /opt/lampp/htdocs/class/cache/file.php on line 311

Strict Standards: Non-static method XoopsLoad::load() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/cache/file.php on line 113

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Redefining already defined constructor for class XoopsFile in /opt/lampp/htdocs/class/file/xoopsfile.php on line 46

Strict Standards: Non-static method XoopsFile::getHandler() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/cache/file.php on line 114

Strict Standards: Non-static method XoopsFile::load() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/file/xoopsfile.php on line 113

Strict Standards: Redefining already defined constructor for class XoopsFileHandler in /opt/lampp/htdocs/class/file/file.php on line 131

Strict Standards: Non-static method XoopsLoad::load() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/file/file.php on line 108

Strict Standards: Non-static method XoopsFile::getHandler() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/file/file.php on line 109

Strict Standards: Non-static method XoopsFile::load() should not be called statically, assuming $this from incompatible context in /opt/lampp/htdocs/class/file/xoopsfile.php on line 113

Strict Standards: Redefining already defined constructor for class XoopsFolderHandler in /opt/lampp/htdocs/class/file/folder.php on line 139

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/include/common.php on line 51

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/include/common.php on line 59

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Non-static method XoopsLoad::load() should not be called statically in /opt/lampp/htdocs/include/common.php on line 66

Strict Standards: Non-static method XoopsLoad::loadCore() should not be called statically in /opt/lampp/htdocs/class/xoopsload.php on line 90

Strict Standards: Redefining already defined constructor for class XoopsLogger in /opt/lampp/htdocs/class/logger/xoopslogger.php on line 70

Strict Standards: Non-static method XoopsLogger::getInstance() should not be called statically in /opt/lampp/htdocs/include/common.php on line 67

Ab da passiert dann nix mehr. Jemand eine Ahnung was da los sein kann?

 

[Suxxess]

Mach dich mal schlau welche PHP Version dein Script voraussetzt. PHP4 oder PHP5?
Unter Ubuntu könntest du auch einfach einen "normalen" Webserver + Mysql Webserver installieren.

Der Vorteil dabei ist dann halt du kannst dann selbst entscheiden ob du PHP 4 oder PHP 5 installierst.

 

[Mark.G.]

Laut phpinfo ist am Server PHP Version 5.3.1 und laut phpmyadmin MySQL 5.1+

Quelle: ( XAMPP Linux 1.7.3a Bemerkung)
http://www.apachefriends.org/de/xampp-linux.html

XOOPS verlangt:

PHP:
Any PHP version >= 4.3 (PHP 4.2.x may work but is not officially supported, PHP 5.0+ is strongly recommended)

Please note: XOOPS 2.4.x series is the LAST version of XOOPS tested on and supporting PHP4. Our next releases will be tested and certified exclusively on PHP5: Read more here

MySQL:
MySQL server 3.23+ (MySQL 5.0+ is strongly recommended)

Please note: XOOPS 2.4.x series is the LAST version of XOOPS tested on and supporting MySQL version lower than 5.0. Our next releases will be tested and certified exclusively on MySQL 5.0+:

Web server:
Any server supporting the required PHP version (Apache highly recommended)

Quelle: http://www.xoops.org/modules/news/article.php?storyid=5208

 

[chrissde]

Hallo!

Ich hatte das selbe Problem. Die Weiterleitung zu r12. Seite funktionierte nicht. Ich behalf mich indem ich die strict-Meldungen abstellte (error_reporting (E_ALL))
[E_STRICT ist nicht Teil von E_ALL)

Das selbe musste ich auch im Frontend machen (die Warnmeldungen sahen nicht nur unschön aus, sie verhindern auch das gültige setzen des DOCUMENT_TYPE)
(Ich habs in mainfile.php reingepackt, ganz oben), du kannst aber (Wenn du die Rechte dazu hast, was lokal wohl der Fall ist) auch die php.ini deines Servers anpassen.
(Dort sollte eine Zeile existieren die mit ERROR_REPORTING beginnt, einfach E_ALL|E_STRICT durch E_ALL ersetzen)

Gruß
chriss