Hi everyone!
First of all, thanks very much to the dev-team for putting that much work into the project. It's nice to see it on track again.
I switched from SMF 1.x to 2.0 at RC2-level and upgraded/updated my way through the various RCs, even managed to salvage the modifications I use, although they are no more supported officially.
However, when I switched to RC4 and RC5 I saw that the news-section in the admin center that shows off the latest SMF-news, was no longer up to date. As if the reference-URL was wrong.
I hoped this would change with SMF 2.0 final, but it didn't. It still references "SMF 2.0 RC3 Public released" as the newest news and says my 2.0 was the wrong version number ;).
My question is, what can I do to set this right? This way I have to check for updates manually while they light up usually when I go to the admin center.
As you can see in the screenshots, all files were updated accordingly.
Any help would be highly appreciated.
Thanks in advance, best regards!
VSG
Those are updated on a schedualed task AFAIK, so you might need to either manually run the tasks, or wait a day or two (depending on your settings) :)
Thanks for that really fast answer. How can I refresh that manually?
These news have been so for months, since my switch to RC3 ... so I don't know whether an update server-side will make a difference.
Best regards,
VSG
You can try
Admin -> Maintenance -> Scheduled Tasks
Select to run now "Fetch Simple Machines Files"
Tried that - didn't change the admin center news.
When I refresh just that webpage, I can see behind the "Current SMF version:" two question marks - so the script IS updating live from a website. Once it updated, I can see the RC3 shown as newest again.
Just which location is it gathering the info from?
Did running that task cause any errors to your error log?
It sounds to me like it probably tries to update it ok, but fails to save the results for some reason.
Yes, there is an entry:
File http://www.simplemachines.org/smf/current-version.js?version=SMF+2.0 could not be downloaded.
If I call it in a browser, it does work however.
Then it could be that your server setup is stopping the file download - Do you have access to your server's error log?
If you have, did the task leave any errors there?
I'm afraid not - I'm with a big hoster here and they are kind of restrictive when it gets to things like logs.
Could it be that the CHMOD is set incorrectly after the update? Where is the file saved to? Or is the information stored in the database?
Now I have to admit I'm not sure myself - I'd have to look that up, but just now I don't have the tools or time to start digging in to code.
I'll get to that later unless someone else gets you an answer faster ;)
Thanks in advance. I'm heading for work as well ... :)
It would seem to me, that the Admin Info file data is loaded from Simplemachines.org (like you already found out) and saved to the forum database, so a chmod error can't be the cause. I'd guess your server doesn't allow some part of this function
http://support.simplemachines.org/function_db/index.php?action=view_function;id=586
I just upgraded from 1.1.14 to 2.0 and running that scheduled task updated my version numbers.
Thanks for looking it up. I found the entry in the database ... but deleting it, doesn't help. It won't get reloaded when I hit the scheduled tasks.
What I don't understand here is: it had to work someday. Otherwise the entries for 2.0 RC3 that are present wouldn't be there. So what changed that it doesn't work anymore?
Perhaps some file wasn't updated correctly. Or some database-change during the upgrade-process wasn't applied?
I'm at a loss.
Best regards,
VSG
I'm not sure of what could have changed, but I do believe the problem lies in the function to actually load the data - not in the way it is saved to database.
So do you know if your server config changed in this time?
I don't know for sure, but I would presume so. They did a lot of software-upgrades. Maybe some functions that were available before then were disabled (due to security reasons) after the update.
Hm ... I guess there's no workaround then?
Thanks for your help.
Best regards!
VSG
same issue here..
Does your host have mod_security installed, with some restrictive settings, by any chance? It may be worth asking them why that URL doesn't seem to get processed, telling them the exact URL mentioned a few posts above.