GBX Data Fetcher module for Challenges, Maps, Replays, Packs

[Xymph]

A fix for resource leaking on PHP7 brings this module to v2.9 -- in the usual place.

[Xymph]

A minor but overdue addition of the TM² Lagoon lookback string brings the GBX Data Fetcher module to version 2.10.

[NoTimeToDrive]

Hey Xymph.

Just a small question.
I'm totally missed the update to 2.10
I have the v2.9: Fix resource leak on PHP7 version.
So I thought i was uptodate

Do I need to update the file in my TMUF server?
I read update is for lagoon only.

I am always a little anxious to replace files.
So if it is not needed for the TMUF.
Then i do nothing.
But if you think it's better to do.
I'll do it

Grt Ed

[Xymph]

Turns out that a few weeks after 2.10, I made an update to 2.11, but then forgot to publish it. So that's online now.

Updates are not mandatory, but the changes are small and don't affect usage on TMUF, so it'd be safe to upgrade anyway.

[NoTimeToDrive]

Hey Xymph.

Wow...so now 2.11.
Then i'm even more uptodate.
I'm gonna add the new files this weekend.
During the week server is to busy.
But glad you say it's save to add it.

Many many thanks for all the time you spend.
To keep this stuff up to date and running.

Thanks a lot

Grt Ed

[NoTimeToDrive]

Hey Xymph.

Yesterday I replace the new files.
You already say it don't affect usage on TMUF.
And al work fine indeed

but the changes are small and don't affect usage on TMUF, so it'd be safe to upgrade anyway.

Only after midnight I was shocked for a moment.
Just after the clock from 24 hour.
The dedi's didn't work anymore.
They don't show up
I quickly looked at other servers.
And I saw that the dedi's did not work there either
so I was reassured
But first I thought.....O boy..here we go

It take some 3 tracks so 25min..before dedi's return.

Thanks a lot

Grt Ed

[NoTimeToDrive]

Hey Xymph.

Maybe i'm wrong.
But I do think that 2.11 have some effects on TMUF.
After 4 weeks I went back to 2.9.

Xaseco crashed many times,
5 times in those 4 weeks.
I was hoping the error message to see in log file's.
But nothing there...
The message in cmd window from xaseco was something about remote (respons) stopped working.
just a single line..inside xaseco window.
Sadly I didn't make a printscreen from that error.
Becourse i thought i could see in log file.

I was fed up after the fifth time.
So I put 2.9 back 11 days ago.
No error so far anymore.
I wait some time before put it here.
Just to be sure if the problem was gone.

I try to find a missing , : ; or wat else inside 2.11
But only fond what you changed.
So i don't think the adjustment for lagoon isn't the problem.
I think nestLevel to inclDepth has created this?
But thats up to you.

Sadly i had removed 2.10..so can't test that one.

Greetings Ed

PS:The Dedi records keeping running this saturday night

[Xymph]

I presume you're running a Windoze server then. On Linux, errors and crash messages should be in aseco.log, even if not in logfile.txt.

Without message or more specific description, it's impossible to debug the problem, which may not even be due to GbxDataFetcher.

[NoTimeToDrive]

Hey Xymph

Yep you are right..run server on windows 7.
And I know..I had to write the error's on paper.
Next time better

Anyway...thanks for keeping an eye on this stuff
Server runs fine

Greetings Ed