this bug's solution is to add a
after in line 17 of pm_pmlite.html

I installed this version, it looks nice! I've just some remarks about the cosmetics of the install script:

* The install pages are a bit tiny, I would like some more height to prevent scrolling

* Why are database settings divided in two screens? One page would look more organized, or are there checks in between?

* Add a line to the modules and extensions install pages, telling installing them can be done later also. Add tooltips with more detailed info about the individual modules/extensions. (newbe friendly)

Just curious: is it easy to make a custom made install script with other modules and extensions? So you could offer xoops packages loaded with modules for specific use like an intranet, sports-club, school, community website etc

the menu block seem to work fine in the alpha 2

Quote:

I am working on a PDO connection for xoops at the moment but when complete I will be getting back to working on the install script. The new install script is much different so please be patient. I probably have about 20-30 hours left to work on the PDO connection and then I will be getting back to the install script.

There is no point in changing anything with the install script until this is finished. I am trying to build it to be similar to xoops so that full theme building will work.

When I am a little closer with the install script and it is shown to be working it would be really nice if a theme builder could build a nice theme for it. But like I said... I will be working on it. My classes just started for the next semester so I will be a little slow with this. I am trying to get the PDO extention complete so I can turn it over to Trabis and let him do any final stuff to it to include it into 2.6 for Alpha 3 (Hopefully).

The install script will hopefully be ready long before we finish up with beta testing. I have gotten a long ways with it. The current setup for a basic install is one screen of settings and one screen of "results."

Also realize that the install script at the moment will allow you to install anything that is in the module directory. So if you want different modules just drop them into the modules directory prior to installation.

I do want to totally redo the install script from scratch to make it even easier but I don't have enough experience yet to accomplish that so a reworking of the current script is where I am at. The ideas I have for a new install script will require some preliminary work to be finished first(2 or 3 major changes to core features or new modules/extensions). So it will be 2.6.1 or 2.6.2 before some of that is accomplished depending on how much work my classes become.

Rodney

Quote:
Pity

Quote:

We have two Main Menu?

Quote:

Thank you for your return.
I can not use this solution because there are too many errors in the current code.

I modify the code to remove the problem and also solve the W3C validation.

Hi guys,

I'm doing some tests and... I'm really, really enjoying what I'm seeing... thank you, core team for the effort devoted to this version!!!

I've found some little problems...

When installing the system, I've unselected all modules and extensions... and after completing the system installation, I started the installation and tests of modules and extensions, however, when I try to install the extension User ranks , I got this messagem:Quote:
On admin of Page module, the Configuration Check alert that the extension 'xoosocialnetwork' isn't installed, but from what I observed here, this hasn't even exist in package

And to conclude, seems to me that the comments plugin is not working, at least it does not appear in the modules (Page or Publisher)

I'll try a new standard installation, to check if problems occurs

Quote:

Why aren't used in forms the jquery ui controls?

Input: (Radio, Checkbox) Select, etc.

Quote:

Not that I want to rush you But I don't think it's a good idea to present 2.6.0 without a complete install makeover. The script is the first impression newbie's get, and this can be part of making the decision to walk away from xoops and test another cms.