problem with admin username/password creation

Please post all install related problems here. Visit this forum first for troubleshooting.
aspat
Posts: 1
Joined: Thu 26. Jan 2006, 10:43

Post by aspat »

Hi - I have the same problem to - fresh install and fresh phpwcms database

Windows 2000 SP4
Apache/2.0.55
PHP/5.1.5
mysql 5.0.18
PHPMyAdmin 2.6.4-pl3
phpwcms dev 1.2.5

as mentioned earlier, the issue in step 2 seems to be a problem with the sql insert comamnd used to place the admin account details in to the "user" table

the insert comamnd only modifies certain fields and relies on the other fields being set to their default values as given in the schema for table "_user"

some of the default values appear to be invalid and so the insert fails and no admin account is created

also had a similiar issue trying to install the 1.1.4 rc version so i assume its some change made in the way mysql is running

one way i found around the setup issue was to modify the mysql global settings so as to remove STRICT_TRANS_TABLES which basically means that during a SQL INSERT if a value is invalid mysql will put the lowest valid value in

running the sql statement below in myphpadmin will dispaly the global setting
SELECT @@global.sql_mode

and this sql statment with set the "modes" of the global settingsl
SET GLOBAL sql_mode='modes'

in mysql 5.0.18 the default 'modes' value is
'STRICT_TRANS_TABLES,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

I changed the 'modes' value to
'NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION'

by making the above change I was able to run the phpwcms setup

with the 1.1.4 cr of phpwcms after running setup was able to login and phpwcms seemed to be working although not really used it in anger yet

with 1.25 dev version of phpwcms (setup with its own database) was able to login but then ran in to a this page can not be displayed

so i still appear to have an issue with the 1.2.5 dev version :)

to be honest not really happy making the global setting change in mysql as I belong to the old school where all values should be explicitly defined

if i am just being a pain trying to run latest version of mysql will people please let me know whats the latest version of mysql they have managed to use to run phpwcms 1.2.5 dev version and what global settings they have configured in mysql
User avatar
flip-flop
Moderator
Posts: 8178
Joined: Sat 21. May 2005, 21:25
Location: HAMM (Germany)
Contact:

Post by flip-flop »

Hi aspat,

why you don´t install the latest version of phpWcms? (V1.26DEV)
Take a look: http://www.phpwcms.de/forum/viewtopic.php?p=56208#56208

Gruß Knut
>> HowTo | DOCU | FAQ | TEMPLATES/DOCS << ( SITE )
User avatar
DeXXus
Posts: 2168
Joined: Fri 28. Nov 2003, 06:20
Location: USA - Florida

Post by DeXXus »

On Fri Jan 06, 2006 19:39
DeXXus wrote:... about working with BLOBs that aren't set to an "explicit" default? You can rest assured that if no DEFAULT value is specified ... MySQL automatically assigns one. :wink:
This behavior apparently was changed as of MySQL 5.0.2 (my apologies to beerka if his 5.0 was really 5.02 or greater :oops: ):

See here:
http://dev.mysql.com/doc/refman/5.0/en/ ... aults.html

BLOB and TEXT columns cannot be assigned a default value.

As of MySQL 5.0.2, if a column definition includes no explicit DEFAULT value, MySQL determines the default value as follows:

If the column can take NULL as a value, the column is defined with an explicit DEFAULT NULL clause. This is the same as before 5.0.2.

If the column cannot take NULL as the value, MySQL defines the column with no explicit DEFAULT clause. For data entry, if an INSERT or REPLACE statement includes no value for the column, MySQL handles the column according to the SQL mode in effect at the time:

If strict mode is not enabled, MySQL sets the column to the implicit default value for the column data type.

If strict mode is enabled, an error occurs for transactional tables and the statement is rolled back. For non-transactional tables, an error occurs, but if this happens for the second or subsequent row of a multiple-row statement, the preceding rows will have been inserted.
emKa
Posts: 8
Joined: Tue 23. Aug 2005, 02:18

Re: Solution?

Post by emKa »

toolman wrote:Hi,

i had the same problem with the installation as described.
The solution for me was the following:

Make sure to do a CHMOD 777 for the file setup.conf.inc
before starting the setup.php script!

After that, everything runs ok with the setup (hope so ;-)

Greeting
Ralf
...das war es! Habe nach einer frischen Installation und vor dem Setup die setup.conf.inc.php auf CHMOD 777 gesetzt und schon ging es. Der Admin-Account wurde eingerichtet und das Login funktionierte auch.

Vielen Dank
emKa
Post Reply