Jump to content

Krillin

New Members
  • Content Count

    9
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Krillin

  • Rank
    Newbie
  1. Trust me. While I was waiting this afternoon I tried all sorts of options and they failed. I even tried swapping out 'argv' and 'argc' and that did not work either. So when I added the given array statement above the troubled line. I saw And I have not seen anything related to the savestate feature in a VERY long time now. I took a look in the /logdata/ folder and that hash for the files were present. So all is good once again. Thank you!
  2. I am currently rebuilding my player stats database from 2005 to today. It is going to take 4 days or so to complete this process with the new version vsp-core_v0.50. But my final word for now this is only testing with PHP 7.3.27. I still need to take a further leap to PHP 8.0.2 (at the time of this writing). But I am going to sit back and recover after a month of driving myself crazy as to why I could not come up with simple solution. You guys a thanked twice because there were two problems that were solved with one line of code needed to fix this issue. But I am saving 8.0.2 for another time,
  3. Kicken was on the right track! I was fooling around with the different statements within this function. What I ended up doing was taking his line and ADDED it above line #979. Saved it, copied it to test it. And to my amazement IT WORKED! The problem was solved by adding, not replacing. if (strcmp($V51d3ee44['argv'][$V865c0c0b], "-p")==0) { $V865c0c0b++; for ($V363b122c=$V865c0c0b;$V363b122c<$V51d3ee44['argc']-1;$V363b122c=$V363b122c+2) { $V0f14082c['parser-options']=array(); $V0f14082c['parser-options'][$V5
  4. This only got rid of the message. But now it is not passing the parserOptions into the program. It prints the options array and that array is empty so this is very unexpected. Any more ideas out there? Best Regards, Krillin
  5. Your "source" is based on a 15 year old version. I have been updating VSP since 2011 when I took on this web module myself in 2011. I am working with a later version of vsp-core_v0.47, I had them up to v0.49, but I failed to test them and they did not work when I updated my PHP 5 to PHP 7 as I was required to do so with Apache Web Server on windows server. I ended up using my 2014 version of v0.47 as my core as this worked and brought up the "help" screen. Now I am bringing this core to current v0.50 for PHP 7/8 in keeping with my version history. I did not know how where to begin to fix this
  6. I am trying this now. But I see an addition "+2" at the end of a variable in the line I am replacing, so this tells me it is modifying this function for a reason, but I will give it a try. I will let you know here in just a bit as I make the changes on my development machine and test on a production server. Thanks again, Krillin
  7. I went in to add the change posted above only to find it is already in the function on line #957. It is below the line: global $V0f14082c; //line 956 I do not think it needs to be stated again? Thanks again, Krillin
  8. Thank you for your reply, requinix! I think I need to clarify something here, right now, for the record. It is cute that you think I used the "source" link that you provided. But that is NOT my source. My source is from myrddin's website from back on 11/23/2005. The source you linked to above is based on the V0.45 which doesn't even have the SQL injection vulnerability fixes, and much more which is in vsp-core_v0.46. In 2011 I fixed these issues and have been fixing them since as myrddin, the creator / author, has been unreachable since 2008. The date from my copies of v0.45 of VSP is 3/2
  9. First off, I am NOT a programmer, but I have no problem diving into anything when it comes to web code. But for a few weeks I have been tracking down a few unknown issues and I do not know where to get help except here. I took over this project after not hearing back from the author since 2008. Normally I can fix issues, but this leap from PHP 5 to PHP 7/8 has got my head spinning. You would think after 10 years I would have a grasp on this by now, but I am not very efficient in PHP yet, but I will get there. While running vsp.php in PHP 7.3.27 I am getting two warnings, but this one is r
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.