86
On a demo server, I upgraded XOOPS from 2.3.2b to 2.3.3. The 2.3.2b-to-2.3.3 upgrade package included the System module, which was updated; and the pm and profile modules (which remained inactive). Upgrade instructiions included in the release_notes file were followed.
Then I spent much more time than expected (the entire afternoon!) figuring out why the site looked different and why the header image was missing. Well, the upgrade package was missing some files in themes/default folder:
xo-banner_bg.png
xoops-logo.png
xoops-logo.psd
which were in the full release. But despite that location, the code was looking for the xoops-logo.png at the root level; so, I copied it there and the header looked okay at last.
Favicon use had changed to the themes/default/icons/favicon.png file, and so had overridden the favicon at the root level.
I also found no mention that the default theme had been dramatically changed. In particular, the typography was redesigned in the themes/default/style.css file, along with additional styling: the font sizing scheme in em's versus %'s, color scheme, and a large new section for the system_siteclosed page, which was part of the new themes/default/modules/suystem folder.
Validator Bugs
/xoops/class/pagenav.php
$ret .= '
';
Changed to
$ret .= '
';
xoops/themes/default/style.css
#xo-pagenav {
#xo-pagenav a {
#xo-pagenav a:hover {
Changed to
.xo-pagenav {
.xo-pagenav a {
.xo-pagenav a:hover {