I was wondering if anyone has gotten the XLRStats webfront working. I tried and it didn't work:

 

http://xlrstats.nosmacktards.net

 

I don't have a cod8.php in my xlrstats/config folder so that could be the problem. I'm using the cod6.php instead. Any help from someone that has it working would be appreciated.

Well, I got mine working.

If you can't sort that out, I can upload my xlrstats installation and you just add your statsconfig.php

 

Edit: uploaded

http://sdrv.ms/QJqwMi

 

For "game" use "mw2" and for template you can use "cod8"

Well, I got mine working.

If you can't sort that out, I can upload my xlrstats installation and you just add your statsconfig.php

http://paulofonta.no-ip.org/xlrstats/

 

Do you have a cod8.php in your config folder or are you using cod6.php?

 

*edit* It looks like the stats might be working, as there's someone's stats on the page, but I'm getting these "Strict Standards: Resource ID#" errors... that's the problem.

yap, using cod6 (forgot that the php real name is censored here)

I was working on a cod8.php, but it's such a pain to add each weapon with each attachment, with each proeficiency, with each camo... that I left it for later.

 

GrossKopf":1xt3l8p6]*edit* It looks like the stats might be working, as there's someone's stats on the page, but I'm getting these "Strict Standards: Resource ID#" errors... that's the problem.

The stats are working since you started b3 with xlrstats plugin.

Now what you're missing is a proper webfront to display the information on the database.

Errors = bad php files

Now what you're missing is a proper webfront to display the information on the database.

Errors = bad php files

 

The problem appears to be that I have "strict" settings set on my php but I am unsure how to change that. That's why those errors are appearing, from what I can tell. I just don't know how to change that.

Seems that happens when php is run as an apache module.

Those settings are somewhere on httpd.conf and .htaccess (although I can't help you further, since I stopped using apache ages ago)

http://www.php.net/manual/en/configuration.changes.php

One thing I did that fixed a little bit of the problem was editing my php.ini file. I changed display_errors = On to display_errors = Off and the errors at the top of my XLRStats page went away. I still have the warnings/errors throughout the rest of the page.

 

I'm still trying to get rid of the rest of the errors. I'll keep this thread updated in case I find the fix, to help anyone else that might have this problem in the future.

GrossKopf":29jdp2q2]One thing I did that fixed a little bit of the problem was editing my php.ini file. I changed display_errors = On to display_errors = Off and the errors at the top of my XLRStats page went away. I still have the warnings/errors throughout the rest of the page.

 

I'm still trying to get rid of the rest of the errors. I'll keep this thread updated in case I find the fix, to help anyone else that might have this problem in the future.

You just changed the php error display but you didn't fix them, hiding them won't help.

You just changed the php error display but you didn't fix them, hiding them won't help.

 

I didn't write the XLRStats webfront so I can't fix the errors. They are apparently not important because they don't stop it from working. It's just annoying to see the errors about PHP being Strict.

Ok, I fixed the problem.

 

in php.ini:

 

error_reporting = E_ALL & ~E_NOTICE

Nice to see the solution

 

I was trying to level up to continue the webfront (need level 80 to get all weapons log output) but could only find softcore servers, and with my connection... when I think that I hit 5 bullets, I actually only fired 2, then I was killed already... only leveled 1 level in 3 or 4 matches

GrossKopf":2op3ozk6]Ok, I fixed the problem.

 

in php.ini:

 

error_reporting = E_ALL & ~E_NOTICE

As I said, that only hides the errors and show only the warnings, if there are any errors that have to be fixed, you won't know.

GrossKopf":1nw76zj0]http://xlrstats.nosmacktards.net

It's working without problems. Forget about the errors, since it doesn't affect the purpose of the webfront.

The webfront doesn't write into the database. It only retrieves and displays info. If it's displaying the required info, forget about annoying errors.

Anyway, the error is only with the php installation, since the same webfront installation never gave me errors. The "right" fix would be to reinstall php (and possibly the whole services package). But the wise fix is the one he did.

GrossKopf":3cfkrmcu]Ok, I fixed the problem.

 

in php.ini:

 

error_reporting = E_ALL & ~E_NOTICE

As I said, that only hides the errors and show only the warnings, if there are any errors that have to be fixed, you won't know.

 

As *I* said, I'm not the developer for the XLRStats webfront. I can't fix the errors. It's working just fine so those errors have no effect on the functioning of the webfront.

Anyway, the error is only with the php installation, since the same webfront installation never gave me errors. The "right" fix would be to reinstall php (and possibly the whole services package). But the wise fix is the one he did.

 

Through my searching to fix this problem, I found that the version of PHP I have (the newest one) defaults "Strict" reporting to on. Something about the setting changed between versions, which is why you probably didn't have that issue. your PHP is probably an older version.

 

There's nothing wrong with the PHP install or with XLRStats webfront. Again, from what I read, the messages I was getting is the results of "sloppy" code (not my words) or deprecated code that doesn't affect how the webfront actually works. It's something the XLRStats devs would have to fix and I don't think they're in any rush to worry about it.

Maybe they already updated the code, if that's the case.

Since it's been working quite fine, I didn't give myself the work of extracting iw4 code to update my xlrstats installation.

I was saving that to when I finish the webfront (let's see if I'll do it in this lifetime)