Upgrading from ocPortal v8/v9 to Composr v10

Upgrading from ocPortal v8/v9 to Composr v10

7th February 2016, 10:19 pm

How to upgrade from ocPortal to Composr CMS.

ocFilter is now Selectcode and ocSelect is now Filtercode? I have a suspicion that these have been muddled up.
No, that's correct. In ocPortal we didn't invent these at once, so the names that ended up being used were sub-optimal, we've fixed it now.
On first look it seemed like they had been victims of the old switcheroo, but if they were named wrong originally then it makes sense yeah :)
Dear Admin,

      I think that i did some mistakes in importing database. I have downloaded my sql in the server then uninstalling OCPortal. I didn't read this guidence before.

    Now, i have backed up data base sql but in latin1 format.  I try  to import but the database can not be used because different type with Composr database (utf8). So, how  can i importing or converting database from db ocportal 9 to composr in this condition?

Thanks.

Hi,

We acknowledge that the latin1 to utf8 jump makes things awkward.
You may want to just defer the change. Make a lang_custom/EN/global.ini file that specifies iso-8859-1 (i.e. latin1 in MySQL terms) as the instructions suggest.
Just try the upgrader, I have this error now:
Fatal error: Call to undefined function has_solemnly_declared() in /home/diablus/public_html/portal/sources/tempcode.php on line 730
Hi, what version are you upgrading from, and how deep did you get through upgrading? It suggests not all files extracted somehow (particularly, sources/zones.php).
Well my trial upgrade didn't go so well. So many broken things, missing image files, missing cedi/wiki tree/child pages, etc…. that I'm not even sure where to begin fixing things. Good thing this was not done on my live site but on a clone of it.

I guess I'll retry it again later after more bugs have been worked out? Here's hoping that I'll even be able to upgrade my site - there is a quite a bit of custom work in it after all.
Sorry to hear that.

Missing image files, I'm guessing maybe menu icons? It might be that because the paths to the theme images have changed you'll need to re-associate these.

The Wiki+ tree feature is no longer there, but can be replicated via the new Sitemap functionality. You'd create a page with a menu block like:

Code

[block param="site:wiki:browse:1" type="sitemap" silent_failure="0" cache="0"]menu[/block]
(actually I was just testing it now and it didn't work right, but I've fixed it for the next release).
The nice thing about the Sitemap is it's one unified system that's very flexible, as opposed to v9 having lots of separate systems doing similar things.

"child pages" - not sure what that issue would be, if there's a bug please report.
I'll have to try that in a bit with the site tree. Question about that though, is there a button or whatever to easily make child pages in a wiki? Likes you could with the cedi tree? If there is, that is missing from my upgraded test. 

Btw that's what I meant concerning child pages, the cold pages of a wiki page. Right now where it would show the tree lists of child pages on my wiki home page it just shows a number. 

There are other issues to, like complaining about misusing front page symbols and the like. Lots of little things to track down.
"is there a button or whatever to easily make child pages in a wiki? Likes you could with the cedi tree?" - I don't believe anything's changed, we never had a button in v9 did we? Unless I'm missing something it was always done via the edit tree button, typing in the list of pages underneath the one you're at. EDIT: Maybe we're talking about the same button, it should still be there.

"Right now where it would show the tree lists of child pages on my wiki home page it just shows a number. " - could it be a themeing issue? A lot of templates have changed, we haven't been able to maintain compatibility with v9 themes to that level I'm afraid. Particularly what it could be is that what were previously separate templates are now merged together in a few cases.
That is what I mean, the edit tree button is missing. Not sure why it's missing.

Not sure if it's a theme issue or not, maybe it is? My theme is simply CSS edits of the default theme, for the most part, with a script that was ran to replace button images with CSS buttons. But yes, no easy upgrade for me…

Chris Graham said

Hi, what version are you upgrading from, and how deep did you get through upgrading? It suggests not all files extracted somehow (particularly, sources/zones.php).

Hi

I finish the install, and I am upgrading from Oc Portal 9 (latest version available before the composr switch.

Thansk
Is upgrading from 9.0.22 no longer supported? Just tried to go through the upgrade process and everything is failing. The generator claims unsupported or unrecognized version. So I have no idea what to use for the update URL in the upgrader. There are no instructions with regard to the actual upgrade process in the instructions about upgrading from 9 to 10.

I competed step 7 but that is where the instructions stop. I assume the next step (8) would be to go to the upgrader, but I have no URL to give it.
Upgrading from ocPortal 9xx to current Composr version. Followed the instructions above:
Prior to upgrading
utf-8

Modified the mysql database as suggested and received the following error after dropping the tables and importing the modified sql file…

Error

SQL query:

ALTER TABLE `ocl4_chat_rooms`
  ADD PRIMARY KEY (`id`),
  ADD KEY `room_name` (`room_name`),
  ADD KEY `is_im` (`is_im`,`room_name`),
  ADD KEY `first_public` (`is_im`,`id`),
  ADD KEY `allow_list` (`allow_list`(30))

MySQL said: Documentation
#1071 - Specified key was too long; max key length is 1000 bytes

None of the keys were created. How can I fix this please?

Also, as a point of information the tables listed for modification here: Composr Tutorial: Localisation and internationalisation - Composr are different from the list of tables above.
Hi,

Sorry about that. Somehow this slipped through our testing.
I have updated the instructions with some possibilities. I recommend moving over to InnoDB, which is one of those possibilities. A Commandr/OcCLE command is given which is for guiding Composr's performance.

Attachment
1 guest and 0 members have just viewed this.
Control functions:

Statistics

Users online:

amit.nigam, mytracker, Philip, Manu, Vaiva

Forum statistics:
  • 1,079 topics, 5,217 posts, 6,064 members
  • Our newest member is fubs
Birthdays:
Back to Top