[SOLVED] Upgrade to 1.9.4.3: global content blocks disappear

The place to talk about things that are related to CMS Made simple, but don't fit anywhere else.
Post Reply
crb11
New Member
New Member
Posts: 8
Joined: Fri Feb 13, 2015 3:29 pm

[SOLVED] Upgrade to 1.9.4.3: global content blocks disappear

Post by crb11 »

Hello, I'm new to CMSMS and inherited a site running 1.6.5 which I'm trying to bring up to date. The current site is at http://www.klice.co.uk, with my current draft site at 96.0.147.21/public_html/index.php

I managed to upgrade to 1.7.1 then 1.8.2 apparently successfully, but when I take the next step to 1.9.4.3, where my global content blocks should be, I get messages along the lines of 'string(59) "Smarty error: unable to read resource: "globalcontent:news""'.

The admin panel claims I have no GCBs, but when I tried to add one in (to see what the correct syntax for referring to one was, and also to try and just copy them across from the old site - I only have six so this wouldn't be too bad) it wouldn't let me, reporting "There was an error inserting the Global Content Block"

I've checked the database, and the data for my GCBs is there in the htmlblobs table. The htmlblobs_seq is reading 8 (not 6) - it is incrementing on these failed insertions.

Something I didn't do at the 1.8.2 stage is deal with the deprecated {stylesheet} tags: I didn't realise I had any, and the site seemed to be working so I didn't go looking, but now I've investigated, I find my templates contain them, and they seem to be working in 1.9.4.3 fine despite not making the change.

I suspect something may have gone wrong with the database schema in the updates. Could someone give me a hand suggesting what I need to patch to get things working at this stage?

Many thanks,

Colin
Last edited by crb11 on Fri Feb 13, 2015 5:44 pm, edited 1 time in total.
crb11
New Member
New Member
Posts: 8
Joined: Fri Feb 13, 2015 3:29 pm

Re: Upgrade to 1.9.4.3: global content blocks disappear

Post by crb11 »

I dug around on the forums and think I've solved this one: it seems to be the same problem as reported as bug 5838. My htmlblobs table was missing the use_wysiwyg and description columns: adding them by hand fixes things. The report given there was that the account doing the upgrade didn't have full rights over my table - mine does, but willing to put it down to a glitch...
Post Reply

Return to “The Lounge”