Maniaplanet Forum

Hey there,

For my snow-pack i got a script for the main-menu by guerro. Sadly I have a problem there.

So it's a really easy-built news-system what he made in 3mins xd
It's implemented in my Changelog-Page in the script part. On this page are three labels. One for the title, subtitle and body.
These 3 labels are only placeholders for size, formatting ans position. The script takes these labels and puts values from a xml at text into it. The changelog-xml is that one ( http://www.florenzius.de/changelog.xml )
So it puts the three labels into the placeholders. And it works fine. The only prob is, when i update my xml on my ftp with new content (or different text), it doesn't update directly... In the interface-designer-preview it's updated directly. In the tp not. Game restarting, updating tp, clearing cache or switching tp doesn't help. I already chatted with dommy and he said that I could add "False" to line 45 , so it doesn't add the text to cache, but it didn't help at all.
So after 60 or more minutes it worked somehow (but it was random).


Is the script slow at all or what could be the problem? Could some1 look over it? I need to have it until halloween ^^

Ask me via PM here for the script (i don't want to publish it here)

You can try to use different xml link each time so you avoid cached version of xml.
Example:

Ty for the answer.

That's the line which shall replace the#const line?

If I have to change the path everytime in the menuscript, i have to update the pack... So a live-updating Blog would be useless. The. I could change the Text everytime in the interface Designer

Did I understand correctly? xD

In your case it could be implemented like this:

Putting False as second param should slways disable cache, at least it does in my projects, like exchange.

Take a look at the source code of exchange manialink:
view-source:http://dominolink.aq.pl/manialinks/exchange.php

I don't know what could be the case but this looks to me like he is getting cached version of the file for some reason.
It could be that exchange xml is created dynamically while in this case this is fixed xml file.

Did you fix this problem?

Ah no, but it's no problem ^^