first time login to 3.0.0 RC is not possible

What is the behavior ?
No OK button ? No effect on OK Button click ? Error message ?
Did you get any Javascript error ?
Did you get any error reported in the log file ?

the password is showed in URL (GET method ?)

Do you mean in the url field of the brower ? And not coded ?
It is very strange, as password is only sent through Ajax (so no visibile in the browser) and only encoded ...

I should choose 'Change Password' to make it upgraded to 3.0.0 RC

Then you got the "Database update" message ? Before of after redirection to password change screen ?

navigation right button for toolbar is in wrong position

I can see it on your print screen. In fact, it is in right position, but buttons should not be seen on rightmost side...

Browser : Safari 6.0.2
OS: MacOS 10.8.2

This is it :woohoo: The bug is here B) Move to Linux ! 👿
(sorry, I could not resist) :blush:

I never produced this issues your're facing.
I tested on Chrome, IE (8 & 9) and FireFox, without issue.
I'll try Safari for windows (sorry, I don't have a Mac 😉 )

Very strange. :huh:
I could not reproduce your issues. :silly:

No password display.
Toolbar button correctly placed.

Did you try to refresh your browser cache ?

What is the behavior ?
No OK button ? No effect on OK Button click ? Error message ?
Did you get any Javascript error ?
Did you get any error reported in the log file ?

There is OK button but after ENTER its kept me back to login page and no error message, i dont get javascript error and no error_log

Do you mean in the url field of the brower ? And not coded ?
It is very strange, as password is only sent through Ajax (so no visibile in the browser) and only encoded ...

In URL field of the browser and not coded totally naked :woohoo:

Then you got the "Database update" message ? Before of after redirection to password change screen ?

Yes I got 'database update' message after changing password and after changed password i forgot is redirect to dashboard or get me back to login screen.

I can see it on your print screen. In fact, it is in right position, but buttons should not be seen on rightmost side...

yes it is

This is it :woohoo: The bug is here B) Move to Linux ! 👿
(sorry, I could not resist) :blush:

Haha I'm opened on macos+safari but the server it self is linux+apache, I will try to open on my linux box

I never produced this issues your're facing.
I tested on Chrome, IE (8 & 9) and FireFox, without issue.
I'll try Safari for windows (sorry, I don't have a Mac 😉 )

that should be same as long as safari.

Thank you

Very strange. :huh:
I could not reproduce your issues. :silly:

No password display.
Toolbar button correctly placed.

Did you try to refresh your browser cache ?

That shouldnt be browser cache problem as I was open the page after sometimes the caches was cleaned

I think I've got a similar issue, but not exactly the same:

- unzipped V3.0.0 (in a new directory-is it an error?)
- gone through configuration screen
- clicked on "continue" and driven directly to login screen - no upgrade at all of database.

Now, I got a connection error and the log file says:

2012-11-16 17:59:53 ** ERROR ** Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'projectorria.user' doesn't exist
2012-11-16 17:59:53 ** ERROR ** For query : desc user
2012-11-16 17:59:53 ** ERROR ** Strack trace :
2012-11-16 17:59:53 ** ERROR ** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1689]
2012-11-16 17:59:53 ** ERROR ** #1 SqlElement->getFormatList called at [/opt/projectorria/model/persistence/SqlElement.php:1491]
2012-11-16 17:59:53 ** ERROR ** #2 SqlElement->getDataType called at [/opt/projectorria/model/persistence/SqlElement.php:1108]
2012-11-16 17:59:53 ** ERROR ** #3 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:35]
2012-11-16 17:59:53 ** ERROR ** Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'projectorria.user' doesn't exist
2012-11-16 17:59:53 ** ERROR ** For query : select * from user where user.name='bernard' and user.isUser = '1'
2012-11-16 17:59:53 ** ERROR ** Strack trace :
2012-11-16 17:59:53 ** ERROR ** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1133]
2012-11-16 17:59:53 ** ERROR ** #1 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:35]
2012-11-16 17:59:53 ===== TRACE ===== Login error for user 'bernard'

It seems you upgraded database, and now try to use it with old version of code.
In V3.0.0, table "user" has been renamed to "resource".

The message you get is "table user not found".

When you deploy new version, you must overwrite old code with new one, so you need to unzip in the existing folder.

Mmmhhh... I can't understand how this may happen: I don't have any code that old.

I had done a tar.gz of the previous version (2.6.3). If I untar it in place, I get the same type of error!

tail projector_20121118.log
2012-11-18 16:40:37 ** ERROR ** Strack trace :
2012-11-18 16:40:37 ** ERROR ** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1103]
2012-11-18 16:40:37 ** ERROR ** #1 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:30]
2012-11-18 16:40:37 ===== TRACE ===== Login error for user 'bernard'
2012-11-18 16:40:37 ** ERROR ** Exception-[42S02] SQLSTATE[42S02]: Base table or view not found: 1146 Table 'projectorria.user' doesn't exist
2012-11-18 16:40:37 ** ERROR ** For query : select * from user where user.name ='bernard' and user.isUser = '1'
2012-11-18 16:40:37 ** ERROR ** Strack trace :
2012-11-18 16:40:37 ** ERROR ** #0 Sql->query called at [/opt/projectorria/model/persistence/SqlElement.php:1103]
2012-11-18 16:40:37 ** ERROR ** #1 SqlElement->getSqlElementsFromCriteria called at [/opt/projectorria/tool/loginCheck.php:30]
2012-11-18 16:40:37 ===== TRACE ===== Login error for user 'bernard'

What can I do?

Well, I think I begin to understand: The upgrade of table must hav begun but never properly ended and I'm stucked with a new base structure and a code which 'think' it hasn't been done.
I _must_ tweak to find out where... Can you help me?

It really looks like you are using V3.0.0 code, with database migrated to V3.0.0 but version stored in database set to V2.6.3.
This can happen if you migrate to V3.0.0, and there use it again with old code : dbVersion will be reversed to old version, although the database is in V3.0.0 format.

Can you :
- set debug level to 3 (instead of 2) in parameters.php file and try again
- check paramerterValue in table parameter where parameterCode='dbVersion'
Thanks.

I finally found out a workaround but it does not satisfy me: I had to rename the resource table into user, then give a _full write access_ to the entire directory tree to have the migration done.

It's a *serious security hole* to have to do that. I wouldn't never have to do that. I admit the product has to write logs and reports but if he can't write to a specific file during the migration, I have to be notified and the migration has to be rollbacked or a new run must go straightforward.

Can you retrieve the log file including the migration step and post it here ?

Hi,
Previouly, most of the parameters were stored in the parameters.php file, and new parameters added by each version were also written in the parameters.php file.
So application needs to be able to write this file.
There is a control on first configuration, but there is not control on migration to new version, so if you changed access rights to files, issue may occur. And you will find error only in the log file.

V3.0.0 completely refactors parameters storage. They are now moved to the database, except dababase access parameters 😉 and log files parameters.
So V3.0.0 needs to be able to write in parameters.php file (to remove parameters).
But now, new versions will not need this anymore. So you can reapply security access restrictions to your directories.