lots of games don't submit score..
anyway.. do the index / portal edit found in your original zip file..
look at the text files .. you'll see what to add and where..
but if your members are getting logged out after submitting score..(result not saving) because you said some members.
after vb4.1.1 or may be vb4.0.8 you MUST have remember me ticked when logging to the forum or the score will not save because it loges you out..
I posted this before somewhere a long time ago, but: I was debugging scoring problems and found that holdsession.php doesn't do what's intended because there's two problems with it: one is with the refresh html, there's an extra double quote after URL= so that the params aren't right.
The other problem is that the "lastactivity" time that's used to keep the session alive is updated using a shutdown query, and those don't get run at all unless exec_shut_down() is called (which is usually called by print_output() in vb scripts). I put exec_shut_down() at the end of my holdsession.php. (I haven't done anything with vB 4 versions so I don't know if this still applies).
There was also a problem with some code that apparently addresses a bug involving some version of IE and an "Error 005". I don't remember the details but I ended up hacking the code and changing $vs['start'] = $gametime; to $vs['start'] = $gametime - 1.0; around line 3484 of arcade.php.
I posted this before somewhere a long time ago, but: I was debugging scoring problems and found that holdsession.php doesn't do what's intended because there's two problems with it: one is with the refresh html, there's an extra double quote after URL= so that the params aren't right.
The other problem is that the "lastactivity" time that's used to keep the session alive is updated using a shutdown query, and those don't get run at all unless exec_shut_down() is called (which is usually called by print_output() in vb scripts). I put exec_shut_down() at the end of my holdsession.php. (I haven't done anything with vB 4 versions so I don't know if this still applies).
There was also a problem with some code that apparently addresses a bug involving some version of IE and an "Error 005". I don't remember the details but I ended up hacking the code and changing $vs['start'] = $gametime; to $vs['start'] = $gametime - 1.0; around line 3484 of arcade.php.
thanks for the info ..
here is the holdsession line
I see the line is still $vs['start'] = $gametime;
if that error never happened should it still be changed to $vs['start'] = $gametime - 1.0;
Sorry, I don't remember the details. I think it only happened with IE in certain circumstances, maybe only with certain games (but I do remember that I was able to get it to happen when I wanted). I guess if no one's ever complained then there's probably no reason to change it. It's a hack - something later is subtracted from the gametime (or the other way around) and if it's 0 it causes an error, so I made sure it was never 0. I don't even know if that was a reasonable way to fix it, for all I know I was just disabling a check that was put in there for a reason I don't understand.
Quote:
please explain a little more about exec_shut_down();
I am not sure if it's still needed
what was it doing with out it before.. thanks
To keep the session from timing out, init.php calls $vbulletin->session->do_lastvisit_update(). I guess for guests it works OK, but for logged in users it updates the session table with the current time, but it does it with db->shutdown_query(), which just queues it up to be run at shutdown (I don't know why - to speed up page loading maybe?). Anyway, it turns out that it's usually called by print_output() which isn't called in holdsession.php. I remember all that pretty well because I spent hours trying to figure out why the session was timing out even though holdsession.php was being requested. But like I said, that was 3.8 code so if you're working on version 4 it might not be true any more.
I suppose it's also possible I made a mistake somewhere alone the line...
I changed my database tables from MyISAM to InnoDB to correct an issue I was having. Now many (but not all) of my users aren't able to save their scores, and are presented with an error that another window is open.
I imagine that one or more of the tables shouldn't be InnoDB.