Software Support > controls.dat

Bear with me

<< < (5/8) > >>

SirPoonga:
Alright - try the login system.  I found a prebuilt one.  Took a bit to make it work with the site but it has enough security features.  I still have to integrate it better into the site at some point. But for now it will work.  Next weekend I will try to get the database up to mame 0.140.

http://controls.arcadecontrols.com

Howard_Casto:
Works for me.  One thing though.... when once the account is activated, even though it says you can log in with your username OR email only the user name worked for me. 

This is better anyway... more secure, but the text box needs changed so it doesn't confuse people.

SirPoonga:
Yeah, I have some tweaking to do.  The original register.php page required ALL of that info (phone, country, real name) so I had to figure out to modify that script.  Though I didn't touch ihe login.php file.  Let me look...

--- Code: ---if (strpos($user_email,'@') === false) {
    $user_cond = "user_name='$user_email'";
} else {
      $user_cond = "user_email='$user_email'";    
}

--- End code ---
See the problem.  ha ha.  it should be fixed now.

Also I noticed I made the main page login required.  Just removed that.  These scripts I downloaded seem to work well.  If it is a page that requires a login I just put a function at the beginning of the page and it will do the login process automatically if needed.  Accept it isn't smart enough to redirect to the page after logging in.  

Howard, I need to make sure I have you setup as an admin now that your user is created.  

At some point I am going to look at the scripts closely and integrate it into the main page.  So if you are not logged in there will be a username and password box in the left menu.  The registration and My Account Pages will get the same look and feel as the rest of the site.  But those are minor issues right now.

I should have the database updated to 0.140 soon.  The update process needs to be changed as I think we will be ready to accept child roms.  One of the reasons we don't accept child roms except for special cases is it makes it MUCH harder to update when a new mame comes out.  Case in point.  Here's the first few lines of mamediff I will be using to update the database..  The first column is the mame 106 romname and the second column is mame 140 romname.  so if both columns are filled it is a changed romname.  If just the first column then it is a deleted rom.  If just the second column then it is a new rom.

--- Code: ---mame106.xml mame140.xml
1942 1942a
1942a 1942b
1942b 1942
1943 1943u
3wonderu
64streej 64streetj
--- End code ---
So what you are seeing here is between 106 and 140 they switch which 1942 rom was the parent.  I update the romnames in the database according to this - so that means the 1942 controls will "move" to the child 1942a.  But then the last thing I do in the update script is any child that has control info, minus special cases, is moved to the parent.

At some point I will have to figure out a good way to update to allow for situations like this.  Then we can support entering in child roms.  I just need to think through it carefully.

SirPoonga:
Also, I did put in two levels of admin.  The super admin which is just me right now - allows me to deal with registered users.  And then a data admin which allows that user to review submitted entries.  This also means entries entered in by admins don't need to be reviewed (we assume an admin is a trusted person and knows how to enter the info).

So once we are updated to 0.140 we will need volunteers for data entry and admins for verifying entries.

Also once updated to 0.140 I will look at some of the unofficial controls.dat and think about integrating some of their data into the project.

Howard_Casto:
It all sounds good to me, let me know if you need me for anything. 

About child submissions:

I think the best way to do it would be to make a special "child" flag for when we make child-specific submissions.  That way if the child flag is checked (this should probably be done internally) the entry moves around with the renames... if not then the entry is always named after the parent rom.

Navigation

[0] Message Index

[#] Next page

[*] Previous page