In vers. 21.05.11 we created user specific OpacMainUserBlock in news section. After web based upgrade on vers. 22.05 this user specific OpacMainUserBlock is displayed properly on Startpage, but its content cannot be changed because it cannot be reached as it is not displayed in the new "Additional contents (HTML-customisations)" part of the administration menue. If I create a new OpacMainUserBlock in the "Additional contents" part it will be displayed below that unchangable Text (and as it should be the same content: shown twice). If OpacMainUserBlock-Content is preserved during upgrade it should be accessibale through menue system.
I am not sure if we can fix that migration as this has been a while ago now, but maybe we can help with clearing up the situation: You can create a report like: select idnew, category, code, lang, location, branchcode from additional_contents; This should show you data similar to below: +-------+---------------------+---------------------+---------+-------------------+------------+ | idnew | category | code | lang | location | branchcode | +-------+---------------------+---------------------+---------+-------------------+------------+ | 1 | news | News_1 | default | staff_only | NULL | | 2 | news | News_2 | default | staff_only | NULL | | 4 | html_customizations | OpacMainUserBlock_3 | de-DE | OpacMainUserBlock | NULL | +-------+---------------------+---------------------+---------+-------------------+------------+ The html_customization is missing the default entry, which makes it disappear from the list. Note the idnew of the existing entry. Go to this link, replacing the id with your missing content one: /cgi-bin/koha/tools/additional-contents.pl?op=add_form&id=4&editmode=wysiwyg It should hopefully open the editor showing you the 'missing text'. Add something to default or move the content from a translation to there and save. Hope this helps!
thanks Katrin for your reply. We solved our problem by reinstalling the whole koha and importing our data into the new empty mysql db. just running the upgrade on the existing installation did NOT work. That was the reason to file the bug. I think the upgrade process does not adress the changed field structure from "news" to "html" properly. I wonder how other users worked around this.
(In reply to Hans Ulrich Frink from comment #2) > thanks Katrin for your reply. > We solved our problem by reinstalling the whole koha and importing our data > into the new empty mysql db. just running the upgrade on the existing > installation did NOT work. That was the reason to file the bug. I think the > upgrade process does not adress the changed field structure from "news" to > "html" properly. > I wonder how other users worked around this. In general it does address it, but we had some issues that have been fixed since. I am glad it works for you now, but usually that step should not be necessary. When you update, always keep an eye out for any error messages from the update script. Would also have been interesting to see what structure you ended up with. (INVALID is a compromise - I think won't be able to fix that for this old version now with the information we have, but it is a valid report. WORKSFORME or FIXED also didn't fit)