This is just a shot in the dark!!

Would you happen to have uploaded a bunch of modules at the same time?

If you did, are any from GIJOE at Peak's, if so, then most of his modules require the ALTSYS module to be uploaded/installed , otherwise it will be blank where the module installs usually are.

Cheers,

http://www.simplemachines.org/community/index.php?topic=173730.0

Read up on it, there is a bridge in beta mode.

Félicitations Marc-André!!!

Note that the thread appears to mean an upgrade from 2.0.13.2 to 2.0.16, and the way the question is phrased also, not a clean install.

And since we're not as nice as the Joomla people, well...

The way you are doing it now is the best so far. Detailed notes for each site.


This would be a bomb of a module. Having the possibility from one main site to see the xoopsinfo module's info on other sites. This would make it easier to manage multiple XOOPS sites.

Sounds like you copied the mainfile.php from the 2.0.16 package over your existing mainfile.php. Therefore, that mainfile.php redirects to the install.

Hopefully, you have a backup of your initial install. Then put back the mainfile.php, upload the upgrade folder, and run the upgrade as per the instructions.

I've just uploaded a site from 2.0.13.2, without a hitch. THe instructions were perfect.

Cheers.

Nice of you to stop by for a visit. Cya.

Right there is no XOOPS installed and the upgrade folder is not populated with files, it would seem. Verify that all files are there and not corrupted uploads.

Quote:

Catz,

If you are referring to Giba's list, then it's not about being a core dev team. Whether you like it or not, you have been and still are an important part of this community. Just with the few helpful posts you write when needed and updates to your modules.

Cheers.

Quote:

Now, as much as I enjoy this banter, and since I won't be paid attention to anyway, I still want to say my peace about it. If you want to save some reading, the last 2 paragraphs are the important ones.

Xoops is presently under the control of one person, Skalpa. This being because he is the sole decision making person for the core programming, hence the direction of xoops.

The idea of a project manager is a great idea, unfortunately unfeasible, du to the reason stated above. Herko, was doing a mighty fine job as project manager. He had to step down since what he was saying in his capacities as project manager were then refuted by Skalpa, or modified, or whatever. Skalpa's vision was different than the then publicly visible XOOPS management position.

Understandably so, noone wishes to function in that environment, Herko had no say as to the direction of xoops(or informed in policy changes) and, rightfully so, stepped down.

Our unfortunate situation remains as a communication problem between the devs and the community. So be it.

Who honestly believes that nominating a person or committee will have an inkling of power in the decision process? We already had some people close to the projects heart and permitted some d*ckheads to cr*p on their house till they left.

If you want to do anything with the project, it is to start at the base. The Foundation is key, NOT the top of the pyramid. This top spot already being dominated by the lead dev. You want to be a part of the solutions, then start helping people out. Soon you'll get a good rep, then fuse with others doing the same thing and make a team of it. Then with time, and as your reputation increases, extend your influence to other aspects of the project.

Once 2.3 is out then it will be possible to increase the developer pool, hence increasing the dimensions of the project. Until it's out, this is Skalpa's baby, and daddy decides what the baby will be able to do and learn for now.

Cheers.

This is just getting fun!!