Yes, that's what I remember reading, and why the above userdata set line is checking. Where is the Javascript function though, I see no mention of it around that section of code..
See the "onsubmit" attribute on the login form.
Quote:
Originally Posted by DarkScythe
I did find this in the global file
PHP Code:
// you may define this if you don't want the password in the login box to be zapped onsubmit; good for integration
$show['nopasswordempty'] = defined('DISABLE_PASSWORD_CLEARING') ? 1 : 0; // this nees to be an int for the templates
Is this what I am looking for? I could also simply copied the hashed value directly over, but it would be plain MD5, which is a little iffy.. I don't think EE has any salting mechanism built in by default, so I normally hash passwords into SHA1, if I can, before putting it in there.
Disabling the client-side hash would be a bad idea IMO, as then the password would be sent plain text across the "interwebz" . You could always SHA1 your MD5 hash.
Quote:
Originally Posted by DarkScythe
vB also seems to have "datamanagers." What are these? From the manual it says they are useful for 'rapid integration of vBulletin-specific data structures and data constraints into [...] third-party applications.' I'm not entirely sure how to access this, or if it coincides with what I want to do..
Data managers allow you to insert data into vBulletin's system, with simple PHP function calls. See the articles section for some examples.
07-23-2008, 10:03 AM
. You could always SHA1 your MD5 hash.
Threaded Mode