XOOPS / XoopsCore

Core Framework for next version of XOOPS CMS: 2.6.0
https://xoops.org
138 stars 81 forks source link

Installation problems... #630

Open hyperclock opened 3 years ago

hyperclock commented 3 years ago

I treied to install and failed. On both my development, as well as, my public server failed during installation. I get to "..._/install/pagesiteinit.php" and then recieve this error msg.:

Uncaught exception: Class 'Xoops\Core\Cache\CacheManager' not found array(0) { } 
geekwright commented 3 years ago

I'll look in to this, later today hopefully. The last time I did an install there appeared to be several "bit-rot" issues.

geekwright commented 3 years ago

I do not get that error. The CacheManager is called on once to set up the default cache. It should be available through the autoloader built by composer. You did do the composer update before starting the install?

There are numerous problems with PHP8 and MySQL8, so those will not work yet. That was expected. Stabilizing on current builds will be the first order of business.

I've been working my way up versions from PHP 7.1, looking for any issues that break install. An environment with PHP 7.3.25 and mysql 5.7.32 is working. There are some warning messages, but so far nothing seriously broken. I'll get to 7.4 later.

If you can provide some environment data, that might help figuring out what is going on.

hyperclock commented 3 years ago

I'm using Debian 10 on both my Dever and Desktop. The Server at OVH, the Desktop is at home.

Both are using the same configs: latest ISPConfig, mysql : Ver 15.1 Distrib 10.3.27-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2 & PHP 7.3.27

I also have 5.6 and 7.4 setup, but I have the test site set with php7.3

I followed the README instructions, moving composer.phar.dist and composer install & update. Could the *.phar file be conflicting with my version of composer - Composer version 1.10.20? .

geekwright commented 3 years ago

The only time I use that .phar is to do a ./composer.phar selfupdate -- It comes in handy sometimes to not have to start from scratch. If you have composer already installed, go with that.

Your versions look good, nothing but a few warnings in a few spots.

Getting to that error message is the result of these steps:

The first 2 steps had the autoloader or would have failed. How did it disappear? Is the xoops_lib tree broken?

The autoloader should find it in xoops_lib/Xoops/Core/Cache/CacheManager.php Even it xoops_lib is called something else or moved around, the navigation inside the autoloader is all relative to that directory. As long as everything is in that directory in the same relative positions, it should find it.

I am at a loss. I'll keep thinking.

hyperclock commented 3 years ago

I got it to install. The only difference is that I didn't rename xoops_lib and xoops_data. I all three intall attemps before, I did rename those folders. They are placed outside of the webroot.

Thanx for the info and help. Now I can start getting some themes ready.