Loading...
 
Architecture / Installation

Architecture / Installation


Successfull install but no site

posts: 5

I have installed version 1.8, created the database and run the tiki-install.php script which completes succesfully. When I take the next step or go to a different PC and log in as admin (only user) instead of a site I get
Values:
Array ( )
$result is false
$result is empty

At various times I have had "HomePage" and "Files Gallery" in the Array Brackets. i have tried rerunning the install with different themes. the database config and data is exactkly as it should be.

posts: 1001 Canada

Hi Steve,
There should be an error above "Values:", do you mean there's really nothing else shown?

posts: 5

I think I've confused this by replying to the wrong message accidentally.

I did a cut and paste of the "view source" output, which looked exactly like the screen ie no tags or hidden bits.


posts: 5

No error message at all.
I have even hunted through the source to try and figure out where it is getting generated from but no joy i'm on MySQL 5 but the SQL database looks ok. the rest is beyond me.


posts: 5

I think I've confused this by replying to the wrong message accidentally.

I did a cut and paste of the "view source" output, which looked exactly like the screen ie no tags or hidden bits.


posts: 2881 United Kingdom

Whats your environment?

Mysql version:
PHP Version:
Apache:
IIS:
Linux:
Windows:

etc

posts: 5

interestingly enough i have just had the same screen from this site!

yesterday the site was logging me on automatically, but today it didn't so I typed the username, password and pressed enter.
All I got was the response already mentioned.
I hit the back button and typed in the username, password, clicked on the remember me and then on the login button and I am OK.
Unfortunately I don't get that original screen on my own site to see if there is a link.

To answer the environmental questions
The original build is based upon Apache2triad with modifications.

MySql v5.0.0-alpha-max-log client version 3.23.49

just found the following error in a log which is probably the cause:

PHP Warning: mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '-1' at line 1 in query:select `permName`,`type`,`level`,`permDesc` from `users_permissions` order by `permName` desc in C:\apache2\htdocs\tiki18\lib\tikidblib.php on line 125

So it probaly means that tikiwiki doesn't work au natrelle with mysql 5.
i shall look for line 125 and pray.

PHP is supposedly 4.3.4
Apache 2.0.48
windows 2K pro dorkstation


posts: 5

interestingly enough i have just had the same screen from this site!

yesterday the site was logging me on automatically, but today it didn't so I typed the username, password and pressed enter.
All I got was the response already mentioned.
I hit the back button and typed in the username, password, clicked on the remember me and then on the login button and I am OK.
Unfortunately I don't get that original screen on my own site to see if there is a link.

To answer the environmental questions
The original build is based upon Apache2triad with modifications.

MySql v5.0.0-alpha-max-log client version 3.23.49

just found the following error in a log which is probably the cause:

PHP Warning: mysql error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near '-1' at line 1 in query:select `permName`,`type`,`level`,`permDesc` from `users_permissions` order by `permName` desc in C:\apache2\htdocs\tiki18\lib\tikidblib.php on line 125

So it probaly means that tikiwiki doesn't work au natrelle with mysql 5.
i shall look for line 125 and pray.

PHP is supposedly 4.3.4
Apache 2.0.48
windows 2K pro dorkstation


posts: 1001 Canada

Actually Tiki is known to have never worked with MySQL 4.1+
Some patch trackers were submitted to SourceForge but not applied if you really need it.


posts: 5

If I understand your reply TikiWiki doesn't work with current or later versions of MySql.

Surely this is a major limitation to its future, which is why the problem never occured to me.

thanks and probably Bye as there is no point in me downgrading my database.