The news archive page and news for a date page where using natural sorting for
the dates, which properly handles dates with an additional alphabetic character
at the end (used when we have several news for the same day). However the
recent news code was using a numeric sort, which resulted in those dates not
being properly handled and the order being the reverse of what we want.
According to the Debian website for the ScummVM
package [https://packages.debian.org/sid/scummvm],
the current version available in the "sid" repository
is 1.8.1.
According to the Debian website for the ScummVM
package [https://packages.debian.org/sid/scummvm],
the current version available in the "sid" repository
is 1.8.0.
According to the Debian website for the ScummVM
package [https://packages.debian.org/sid/scummvm],
the current version available in the "sid" repository
is 1.7.0 and not 1.6.0 as stated on the ScummVM
downloads website.
Now by default we're looking into local FS.
There are 3 potential places for files: frs/scummvm/, frs/scummvm-tools/
and downloads/. They're now governed by 'type' attribute to url.
As mentioned in f3c2203e2f,
the language switching was always 1 behind. As in, the
language would be the last language you selected.
The first problem is that some of the smarty config variables
were being set after the call to _smarty->config_load(). Since
the smarty instance is cached, it was using the last set of variables.
I don't know why the production web site isn't throwing errors. My
personal set up wouldn't load until I could set _smarty->compile_dir
the first time. Perhaps the language update was done on the fly, so
smarty was still cached.
The next potential problem is persistence with $_SESSION.
The session is never initialized with session_start(). However,
the production php.ini may have session auto start enabled.