I did a regular 2.4.5 to 2.5.5 upgrade, too.
The problem is related to the following step of the official upgrade guide:
Quote:
and the upgrade package does not contain all the templates files.

This advise should be ONLY for people doing the "full upgrade".

If you use the "upgrade files", they contain only files that are different. If you delete all the original files, then obviously you'll be missing all of those that were not different from the 2.5.5 version, as obviously, they were not included in the upgrade package.

Quote:

I'm agree with you, but the upgrade instruction contains the following notes:

Quote:

and it was the cause for our blank blocks

Link to the page: XOOPS 2.5.5 Final Released

Sorry for the misunderstanding!

I've updated the text to make it clear there that this is for Full Update.

Sorry Mamba, but in my opinion the upgrade guide is still not correct (or maybe the upgrade package does not cointain all the required files).

I try to better explain the situation and I will start from "the beginning" just to be sure that my feeling will be eplained correctly.

It is possible to install xoops 2.5.5 in 3 different ways:
1. fresh installation (using the latest xoops package)
2. installation from previous xoops version, that can be split in:
2.1 installation from xoops version 2.5.0
2.2 installation from versions older than 2.5.0

We made a full upgrade from xoops version 2.4.5 (step "2.2" mentioned above) and we got the "blank blocks issue" because some templates file were missing in the following directories:
/modules/sytem/templates/
/modules/sytem/templates/blocks/

At this stage, we can have two alternatives to explain the issue:
1. the upgrading package for xoops versions olders than 2.5.0 does not contain all the templates files
2. the following step of the official upgrade guide:
Quote:
is wrong, and it should be removed.

I agree with what Shiroku said. There is obviously a problem here. I agree that it is nice to get rid of "old unnecessary files", but it seems that not all of them are unnecessary.

And it is not even a custom module that has problems, it is the system module blocks that are not working properly.

I believe this should be investigated more, if not for a fix for the current release, than definitely for the next upgrade cycle that will come with XOOPS 2.6.