The online racing simulator
hm... link Table Styles

[B]Notice[/B]: Undefined variable: styledef in [B]/home/marko/public_html/lfs/hottracker/sdk/model/styles.php[/B] on line [B]88[/B]

Below get notices if i use or do something

Link Show all LFS World Teams. If I press button Reload all works but if i checked Show team members (slow performance) then lots of some notices:
[B]Notice[/B]: Undefined index: Members in [B]/home/username/public_html/lfs/hottracker/sdk/model/lfswteams.php[/B] on line [B]50[/B]

Link Groups
Add new group
[B]Notice[/B]: Undefined offset: 0 in [B]/home/username/public_html/lfs/hottracker/sdk/model/hottrackerdb.php[/B] on line [B]750[/B]

Maybe this wa last notice but i'am not sure Now i test little more.

One security mistake. What happend if user lost password?
Now: Administrator reset password and tell him because only hi see this password. No e-mail now.
Future: Administrator reset password and automatically send e-mail to user. Administrator don't see this password. OR, link Forgot Password for user. My opinion.

First must remove old Notices
Okram - Damn, good beta testers are hard to come by, nice job!
HP - Great work keeping on top of this.
Ok, the notices are hopefully gone now (but I believe there are still some more hidden in the code ... just waiting for Okrom to reveal them ).

Concerning the password reset, Okram, you're absolutely right. I also wasn't satisfied with the current solution, but regarded it as not important enough to change it.

Now, any user can reset his password by himself. Since there is no identification check, the user has to provide the email address in order to reset the password. If he doesn't know his email anymore, he can't do anything. When resetting the password, an email will be sent.

I still allow the super user to reset the password for a user (automatic email generation still to implement at this point).

In order for the email to be a valid identifier (just as the username) it has now to be unique in the tracker user database!

Other than that:
  • A slight change of the control center layout (two columns of menu items now)
  • Super user now can leave a note in the control center (either visible to all visitors, to registered users only or to no one at all).
I still have to update the documentation as well ...

Regards,

Timo
Ok, uploaded an updated documentation and ZIP.

And if the super user now decides to reset the password of a registered user, he will not see the password anymore - instead an automatically created email will be genereted and sent to the user.

I think that's it for today. I hope there will not be so much issues anymore because I'm kind of burned-out at the moment. I need a break.

However, if there are still some smaller issues, I will fix them and remove the BETA tag a few days from now.
Two image link is broken Hot Tracker v2.0 beta and German Gamers Club

[URL]http://http//mydomain/~username/lfs/hottracker/images/logo.png[/URL]
[URL]http://http//mydomain/~username/lfs/hottracker/images/ggc.png[/URL]

Logout, Login and Register link is broken right corner of top and eMail send wrong link if you have forgotten your password
http://http//mydomain/~username/lfs/hottracker/sdk/model/logout.php
http://http//mydomain/~username/lfs/hottracker/controlcenter.php?loginform
http://http//mydomain/~username/lfs/hottracker/sdk/model/register.php

Click Groups, add new group and notice
[B]Notice[/B]: Undefined offset: 0 in [B]/home/username/public_html/lfs/hottracker/sdk/model/hottrackerdb.php[/B] on line [B]775[/B]

This not bug but i see this Ingame Racer Names and Racers per Group. If users added then Preview (Racer field in Racers per Group) works fine if user is team member. But if not, then before name is space. Move mouse over name in table.

[U] Okram[/U]
[U]TEST Okram[/U]

The broken links are all based on the constant LINKBASE in config.php, i.e. they are for example

<?php 
$link 
LINKBASE "/sdk/model/register.php
?>


So if they are broken, you have most likely set up you LINKBASE constant wrong. I suppose in your case you need to set

<?php 
@define(LINKBASE"http://mydomain/~username/lfs/hottracker");
?>

in config.php (do not forget the ":" between http and //).

Concerning the space in the Ingame Racer Names: When you add a new racer, the tracker suggests a pattern for an ingame name. By default, this suggestion is

<?php 
^^n
?>


where ^t is replaced by a team tag and ^n by the LFS Nickname and   is the HTML command for a non-breaking space.

So if you add a racer which has no team, you should really change this pattern to

<?php 
^n
?>


or any explicit name (including LFS color codes).

The notice will have to be fixed of course. EDIT: <== Fixed.
Ups, my mistake. Fast copy & paste It seems that now, I guess all of the notices found. No more notices
Yeah! :headbang:

(There are still some, I'm sure, they just have to be found ...)

I hope you can enjoy the tracker now.
Since there hasn't been any feedback since a while now, I assume there are no critical bugs anymore. I hope the tracker now works also with PHP4, but I'm not sure about that.

Anyway, I uploaded the latest version and removed the BETA tag.

I wish you all a happy easter.
hi i´m having problems with the tracker

i install it all the stuff

http://www.lfscr.com/hottracker/controlcenter.php

but when i loggin as a "super" appears all in white




and when i log out, dont work, and still login

andy idea...?
Attached images
trackerpro.jpg
Well, at least you are able to login as "super". So the MySQL setup seems to be fine.

When I try this link:

http://www.lfscr.com/hottracker/controlcenter.php?loginform

I can see the grey background. The same holds for the registration page.

I have no idea yet what it could be.

Please check
  • data directory allows write access (chmod 777)
  • Maybe delete your cookies and re-login.
i delete cache/cookies in Firefox


and the DATA is with CHMOD: 777




the files in the /data/ are in: 755 CHMOD

andy idea?
Attached images
trackkerPRO1.jpg
1) the grey:

2) the login with: "super" and appears in white all

3) when i try to logout, dont work, and still in LOGIN

4) when i click in: CLICK HERE for redirect, appears in the same whit page and said: (super:logout), like 2)
Attached images
trackPro2.jpg
trackPro3.jpg
trackpro4.jpg
Problem seems to be solved now. It seems the tracker still does not work properly with PHP4, switching to PHP5 solved the issue.

Looking at your installation there are still some broken links to images.

This is due to an incorrect setup of config.php. There is a parameter where you have to enter the base-URL for your tracker installation. In your case that is something like http://www.lfscr.com/hottracker (maybe you have to add a '/' at the end also, take a look in the documentation please).
Bone from Bavarian Racing discovered a bug related to character encoding.

When creating a new racer with a name containing UTF-8 2-Byte characters (like "ü" for example), the name on the DB was written in non-UTF-8 format (i.e. "ü" as 2-Characters, not one 2-Byte character).

The same problem occured when creating ingame tags or names containing such special characters (like ä, ö, ü, or Alt-0149: •).

The reason was a missing explicit MySQL statement that all data transfer between PHP and MySQL should be done in UTF-8.

This is now fixed, new version uploaded, see first post.

Thanks to Bone!
Horse, congrats for Hottracker.

When i update selected racers results in no data found on PBs, WR...

The only configuration needed is in the config.php file?

Where I come to adjust data only for my servers?

Every change of page slow 5 seconds...ex: LFS Color Replacement Configuration

Regards.
Thank you.

Let me try to figure out your questions ...

Basically, you only need to adjust the config.php (it is well-documented, also in the PDF-document).

Make sure you use PHP 5.x as there are still some issues with PHP 4.x.

Make sure, the data directory allows writing access (chmod 777).

I'm not exactly sure what you mean with the other questions. When the single racer update sais "no data" this might be due to "no data" being found on LFS World (e.g. the racer does not exist or he has no HLs on LFSW for example).

Other than that don't forget that there is a tar-pitting for LFS World Access. That means, if you do not have PREMIUM-Access, you will only be allowed to read data from LFS World only every 5 seconds.

That changing the page is so slow might be due to a slow server or a misconfigured config.php. What are your settings?
You might have some server setup issues. When trying to load the tracker test page, I get some warnings:
Quote :
Warning: file_get_contents() [function.file-get-contents]: URL file-access is disabled in the server configuration in /home/lfsbr/public_html/hottracker/templates/trackertest.php on line 96

Warning: file_get_contents(http://www.lfsbr.com/hottracke ... amp;track=&multiple=1) [function.file-get-contents]: failed to open stream: no suitable wrapper could be found in /home/lfsbr/public_html/hottracker/templates/trackertest.php on line 96

Other than that I think it's the connection to the MySQL DB that takes so long. The only page that loads faster is the Tracker Test page (which does NOT check the user currently, thus has no access to the DB unless you explicitely request the tracker list).

Check your server settings please.
It is indeed the file_get_contents() function call that is causing the issue. His current server configuration does not allow the use of file_get_contents() access urls. There is a setting within the main php.ini file that prosides over the whole webserver that allows for the use of the file functions URLs. The setting is called allow_url_fopen and it must be set to TRUE. It should be noted that this setting can only be changed in the main php.ini file, and any local changes to this setting will be ignored. It should also be noted that the first warning caused the second warning, and once you fix the first warning the second warning will go away.
Quote from jscorrea :Look here Dygear:

http://lfsbr.com/phpinfo.php

Thanks!

Ok, I submit one other item of fact but as I'm quite unsure how a compile time option would effect the reporting of the php.ini file I don't have any evidence to support this theory. (just instinct)

There is a compile time option --allow-URL-wrappers or something like that, that if set to false will turn the value off irrespective of the setting in the php.ini file. I'm not sure if you have This compile time option set if it would still report as true when set as such in the php.ini file even tho the value is compiled to off and thus is unaffected by php.ini.

So even tho it's showing as on, it might be compiled to off (as the code path is not there anymore) and thus can't be turned on. You can't turn on what's not there.
So maybe I should implement this ...

Anyway, the file_get_contents is just in the demo page. One can also use include instead I think.

Maybe I will need your help, Dygear, since some users get the error message (header already sent ...) when I try to set COOKIEs. The strange thing is, that I cannot reproduce it. I have two different trackers on two different servers and I never had that problem.

But others have ... I cannot figure it out.
Headers are sent before any output, including error messages. For an error message to be displayed in a browser the php script must first send the header of the page to conform to the HTTP standard. By default, error messages do not wait for the end of code execution and thus any output will be flushed to the screen and as such any headers that have been set are sent to the browser. For this reason, if your page throws an error before you call your last header() function in your program, the warning will show that the headers have already been sent. A solution to this problem is to suppress errors, but log them to a file, for this I recommend you implement the php native function set_error_handler().

COOKIEs are nothing more the a string in a header, thus if you have already sent the output to the browser, you can no longer set a cookie. It should also be noted that the ob_start() and ob_get/end_flush() should correct this issue if your having issues with headers being sent before they should. (Because, don't forget, a cookie is nothing more then a special header statement.)

FGED GREDG RDFGDR GSFDG