CMS Made Simple Forums

Installing  0.10b local Windows

First Step Ok
Continue
Than this:
Fatal error: Class 'ModuleOperations' not found in C:\xampp\htdocs\cms\lib\classes\class.module.inc.php on line 29

Cannot test this version.

Do you have eAccelerator running?  There is something about it that's causing a problem that I'll look into tonight or this weekend.

Yes i have .

Next Error

Mysqli needs fom adodb the file  \datadict\datadict-generic.inc.php, that file is not in the download file

To use Mysqli the install.php must change:

from

$result = $db->Connect($_POST['host'].":".$_POST['port'],$_POST['username'],$_POST['password'],$_POST['database']);

to

$result = $db->Connect($_POST['host'],$_POST['username'],$_POST['password'],$_POST['database']);

Does that type of connect string work for mysql and pgsql as well?  (I assume they do)

Nevermind, I answered my own question on that one.  Thanks for the bug fixes!

Now without eaccelerator, but with changes in install.php and mysqli.

Install ok but wrong output:



[attachment deleted by admin]

I guess I better install php5 and see what happens.  Maybe that's an issue.

Found the problem with eAccelerator.  Moving the ModuleOperations class above the Module class in lib/classes/class.module.inc.php seems to fix it.  And, yes, it does make things a lot faster.  I'll release all these fixes in a beta2 sometime tomorrow.

The other error is that your initial.sql is not compatibel with mysqli .

What was the exact deal with that?  Was it a lowercase/uppercase issue?

This i have reported here:

http://forum.cmsmadesimple.org/index.ph ... ml#msg3780

You see , this problem is an old problem. 0.10b would be better if you read more in this forum.

...and it would be much easier to find bugs if they were reported in the bug tracking system instead of randomly on the forum.

Anyway, I fixed this last night.

Another error with mysqli:

In install.php sometimes tables are declared as follow:

$dbdict = NewDataDictionary($db);
$flds = "
content_id I KEY,
type C(25),
prop_name C(255) KEY,
param1 C(255),
param2 C(255),
param3 C(255),
content X,
create_date T,
modified_date T
";

The Value X comes as VARCHAR(255) must be LONGTEXT.

And here is the complete initial.sql:




[attachment deleted by admin]

Too many indexex on one field causes warnings so here where you are using content_alias twice:


Indizes: Dokumentation
Name Typ Kardinalität Aktion Feld
PRIMARY PRIMARY 5  Bearbeiten Löschen content_id
content_alias INDEX keine  Bearbeiten Löschen content_alias
active
content_alias_2 INDEX keine  Bearbeiten Löschen content_alias
Warning Es sollte nicht mehr als ein Index des Typs INDEX für die Spalte `content_alias` gesetzt sein

That's what I fixed.  The generic datadict makes them varchar(255).  Instead, I modifed the mysqli driver to use the mysql datadict and now it creates the tables correctly.

That's strange about the indexes.  You should be able to index it a bunch of different ways based on various queries.