Seeing you are so close to releasing 1.1, I thought I would upgrade to Compo.sr from 9.0.28. I am on a shared server with Inmotion, and it does not appear that there are any issues on that side.

I've gone through the ocPortal ugrader, thinking that was the correct way as indicated on the

Download Composr

Open Source CMS with advanced social, interactive and dynamic features. Fully flexible, themeable and extendible: suitable for building powerful websites.

View

page. I would prefer not to do a fresh install by downloading the installer from that page, as I have done a lot of set up with the forum structure. Inmotion uses the Softaculous installer, however, there is no option visible for Compo.sr, just OCP.

Am I missing something that I should have done?

 

Hi,

Please see the instructions in here:

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

We'd accidentally allowed it to slip off the front page.

Chris Graham said

Hi,

Please see the instructions in here:

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

We'd accidentally allowed it to slip off the front page.

From “Post #889”, 12th Jul 2016

Thanks, tried that, it seemed to work, and then got this:

Screenshot 2016-07-31 at 2.35.01 AM.png

(Click to enlarge)

To me that looks like in another tab (or similar), the site was loaded or refreshed after upgrade started but before it finished.

We renamed info.php to _config.php in v10, and the new code automatically will rename it for you, but the upgrader extractor launched from v9 still relies on info.php being there until it's finished.

Actually thinking about this now, it could be CRON, or someone else hitting the site. That's definitely a big issue we didn't consider, so we'll fix that in the next RC by doing a copy of the file rather than a rename. Sorry for the inconvenience.

This is what the site shows now:

More, and different problems now. I did a clean install of OcPortal, with no additional customization at all. Then went to proceed to upgrade. Everything looked good, until I tried accessing the site. I got the following screen.

Did you do the database upgrade step (step 5)? I think you skipped over it to step 8.

Chris Graham said

Did you do the database upgrade step (step 5)? I think you skipped over it to step 8.

From “Post #922”, 25th Jul 2016

That may have been the problem, as all seems to be working now on RC14. Thanks for the replies! Once final is released and I can complete the site, I have a sneaking suspicion I will have to spread the word on Compo.sr

So many tools, so many options and amazing support.

Thanks .

A new f̶e̶a̶t̶u̶r̶e̶ er…. bug has appeared. Tried to update the time zone setting from the default UTC to Mountain (Denver) or Mountain (Edmonton etc.) and got the attached lengthy error message. I could not determine what the bolded [Column 'field_11' cannot be null] referred to.

Oh, rats.

There's a way to fix that in the system, but I wasn't aware it happened for v9 to v10 upgrades.

You need to edit the CPF #11 and it will correct itself. Admin Zone > Tools > Members > Custom Profile Fields > Edit Custom Profile Field… click Edit next to the one that say "Edit #11" on the edit tooltip.

Chris Graham said

Oh, rats.

There's a way to fix that in the system, but I wasn't aware it happened for v9 to v10 upgrades.

You need to edit the CPF #11 and it will correct itself. Admin Zone > Tools > Members > Custom Profile Fields > Edit Custom Profile Field… click Edit next to the one that say "Edit #11" on the edit tooltip.

From “Post #928”, 27th Jul 2016

EDIT:

The error occurs even if I try to edit the "Title" tab from blank to any string at all.

Not sure that is the one, as that seems to apply only to the Wiki. See screenshot:

Hi,

I just tested and can confirm the bug. There are few affected fields, I suggest just putting them all through an edit, then it can be okay.

I'll work on fixing the upgrade process, this is a legacy issue.

Chris, are there areas that need testing? I'm not ready to go live yet, so don't mind running a few things that others may not have tried yet. I'm a very old hat at HTML, but only have enough knowledge of CSS and PHP to be dangerous, so let me take a stab at more common functions that may put flies into the ointment.

I'll be guided by whatever suggestions you may have.

Hey,

That's very nice of you to offer .

We've fixed 100s, possibly 1000s of bugs over our longest testing period ever at this point, so we should be very close to release. But, things always creep up and surprise us.

Probably the best things to test is actually what I can't think of, the most obscure parts of the software.