Authorisation and edit issues

Hi,
there are two things, maybe connected, not sure:

1) I didn't have to set permissions to 777, I can edit everything immediately. After installation the content, cache and start folders were (and still are) 755. All the new pages I create are 777. All editable.

...which would be basically OK if:

2) If I set up a user and pass in config.inc.php it does not work, the correct data are not accepted and I can not enter the edit mode because of Authentication required.

Any help? Thanks.

hi, could you enable debug mode in the config.inc.php
$conf['log_level'] = 'debug';
and see what is being logged into log.txt ? (set log.txt to 777 before)

another possibility is that you should set username and password in user-config.inc.php , which overrides the values in config.inc.php

log.txt:
... modules loading .. loaded
... base_url: guessed http://...
... digest auth: none

setting user and pass in user-config did not work, the login window is jumping back (Authentication required if clicking Cancel)

are you still having these problems?

try our updated version (same download link) and set you name/password in config.inc.php

let me know!

yes, its still the same, even with the new version

are there any restrictions for the user/pass? (characters, length..?)

what hosting company are you using, or is it your own machine?
there was another report from one of our users with exactly the same problem.
we are looking into it, however it would be really helpful to see the log files from your server as well as the list of loaded apache modules, especially mod_auth, if that would be possible.

good news everyone!
authentication issues have been solved! there is a new HOTGLUE version available for download at http://hotglue.org/hotglue-latest.zip

you will have to edit config.inc.php and setup your username/password in appropriate fields. there is also a new variable - 'auth_method'. in case you had problems with authentication you shall leave it set to 'basic'.

apparently the problem was that some hosting providers have difficulties digesting the 'digest' method which we used by default. either 'reverse proxy' setup that eats up authentication data or apache with hardwired 'basic' mode. anyhow, 'digest' mode did not work there, that is why we now have a choice of auth_methods.

'digest' is generally more secure and if you can - we advise you to use it. otherwise 'basic' is safe bet for any kind of 'el-cheapo' hosting ;)