HTML Logo by World Wide Web Consortium ( Click to learn more about our commitment to accessibility and standards.

Moving forward with Composr

ocPortal has been relaunched as Composr CMS. ocPortal 9 is superseded by Composr 10.

Head over to for our new site, and to our migration roadmap. Existing ocPortal member accounts have been mirrored.

Deployment Timeline

Login / Search

 [ Join | More ]
 Add topic 
#49044 (In Topic #10697)

Fan in action

Some Questions - Seeking Advise

OK I have a site that I am going to convert to OCP. Still testing but with the new fix I will be able to bring over my users, forums, and posts in the conversion. I have a couple of other areas to convert.

I am going to test the conversion, then back it out to do some architecture decisions.

Anyway I am trying to figure out a deployment order. Once I have tested all the conversions I was thinking it would go like this.

1. Theme - Design/Implimentation
2. Architecture setup (manual) for manual conversion areas
3. Import Users only
4. Import manual conversion pieces
5. Address architecture importation issues
6. Import forums et al

Now one of the things I am thinking about is shutting down features a week prior to the final move on the new site. For example shutting down new user registration. Thoughts on this.

Also I am wondering when I reinitialize a site, what do I lose? Most of my architecture decisions are related to Zone and Category usage, as well as custom pages, panels, and comcode. When I rerun the install process how much of this do I lose?


"L'enfer c'est Les Autres." -Jean Paul Sartre
Back to the top


Are you importing users first so that you can get the other things bound to them sorted before having to disable and move your old forums?

If so, you'll likely want to disable new registrations on your old site. Oh wait, just read further and you're planning this – so yes, it makes sense.

I've never tested finishing an import with a big gap. Please take backups of the import_* tables after importing users just in case anything goes wonky - you'll need this data if there is a problem (and if there is I'll help - it's just we'll need that data).

It wasn't really designed that the install is rerun after a site is installed, but if you're technical you can do it. No guarantees though. It shouldn't hurt your zones, Comcode pages (including panels), any custom PHP code, and language files, and themes (as long as you place theme images manually - not through ocPortal). Anything in the database will get lost though - so any content entries, members, etc.

Become a fan of Composr on Facebook or add me as a friend. Add me on on Twitter. Support me on Patreon
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about Composr whenever you see the opportunity or support me on Patreon.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying Composr on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
There are too many online users to list.
Control functions:

Quick reply   Contract

Your name:
Your message: