This is an update for ocPortal users.
It is a fact of life that some users are still on ocPortal (the previous iteration of our product), although Composr CMS v10 has been out for years. This is far from ideal, and we'd advise to not be in this situation, but we do understand users don't necessarily have any budget to update sites on someone else's schedule.
We have not officially updated ocPortal in some time, and the most recent PHP version supported is PHP 7.1. Unofficially we have patched it to support up to PHP 7.4.
We have just made a patcher micro project to help users who have become stuck, when their webhosts upgrade PHP to a version ocPortal cannot run on, and thus the ocPortal upgrader is itself broken.
See:
https://github.com/chrisgraham/ocPortal/releases/tag/patcher
Alternatively, see this project that allows building a custom self-extractable upgrader archive:
Composr ecosystem / Make Composr Upgrader · GitLab
And, if you are able to roll back the PHP version to 7.1, you can upgrade to our unofficial ocPortal version from what is released here:
https://github.com/chrisgraham/ocPortal/releases/tag/9.0.42
Further ocPortal upgrades
Note that ocPortal will never be updated to support PHP 8.Professional services
Note that ocProducts has regrettably not (as a general rule) been able to offer our own upgrade services to update ocPortal sites to Composr on behalf of users. This is because our resources are limited, and we need to put them towards work that involves developing the product, particularly Composr v11. Upgrading sites between major releases can involve a lot of time, and diverting our limited resources away from v11 to putting users on v10 would just be painful for us and the users who have for a long time been anticipating v11 getting finished.We have always encouraged seeking the services of providers beyond ocProducts, and don't want to have any kind of monopoly in this ecosystem. Providers may advertise their services within the community (
Comments
This is the code i get when i put in the new code you gave me into the global2.php file:
Fatal error: Call to undefined function safe_ini_set() in /home1/martenas/public_html/sources/global2.php on line 184
NVM! Problem solved!
Im a real novice here. But i had a pretty sizable following as a cartoonist, and wanted to give the whole membership website a go. I stumbled upon OC portal in 2014. Over 6 years later and its done me real solid. I have really enjoyed the product/experience, even though i regret not educating myself more with the inner workings of the actual software integration, and updating to Composr when it came out. Everything was fine, but then about a month ago, my website just went down. All i could see was the installer.
Did some poking around, and as it turned out, my Web Hosting service updated me to PHP 7.4
And that didn't play well with my members section (OC portals software) so i got them to roll it back to a PHP where it would work. Somehow that number was 5.6.3
The site atleast appears the same as before, and looks to run fine except a few glitches;
For starters, i get this…
Deprecated: iconv_set_encoding() [ref.iconv.php]: Use of iconv.output_encoding is deprecated in /home1/martenas/public_html/sources/global2.php on line 2124
Deprecated: iconv_set_encoding() [ref.iconv.php]: Use of iconv.internal_encoding is deprecated in /home1/martenas/public_html/sources/global2.php on line 2125
…at the top of the screen.
Im also unable to do any sort of updating, content management, or site editing due to the fact that i get this error everytime i try to go in the admin zone:
PHP WARNING [2] Cannot modify header information - headers already sent by (output started at /home1/martenas/public_html/sources/global2.php:2124) in sources/site.php on line 208 (version: 9.0.11, PHP version: 5.6.30, URL: /adminzone/index.php?page=start&keep_no_swfupload=1&keep_session=241999584)
So im not sure if this has to do with the fact that the PHP is such a low number, or that it was changed a couple of times by a rep via my web hosting. Or just some other thing that i have missed.
Here is my website: http://otakusquid.info/index.php?keep_no_swfupload=1&
Be warned… my fans have a really weird eclectic taste in art and cartoons, and i sorta fall into the vein of crumb, bisley, and that dude who did ren & stimpy (post nickelodeon). Oh, and lots of anime squids.
Attached is a page that shows what PHP i am using, as well as what the page looks like when i get the error. If you need anything else, please let me know, as this site reliably gave me a decent chunk of income for me & the fam to live off of.
Sincerely,PM2K
Upgrading from ocPortal v8/v9 to Composr v10
How to upgrade from ocPortal to Composr
View
There's a box near the top that mentions what to try for older Composr versions.
The omni-upgrader is linked in this article. This is a special upgrade file to upgrade ocPortal to Composr.
It does make me nervous, so definitely take a full backup before trying this.
One last question; should i, and am i in a decent position to simply upgrade to Composr at this point?
or do i need to patch to be compatible with new PH first?
Currently running ocPortal 9.0.11 on the inherit PHP setting.
Thanks Chris.
The way the diff works is it shows lines in red to remove and lines in green to insert. But don't worry about that now that you have it working.
Wish I had more time to get in to detail with each individual user, but alas I don't.
Beleive it or not, i managend to figure this out. Atleast so i can get in there, do some backups, and update to Composr.
I dont know if this sounds like a bad idea, or just plain wrong…
But I simply deleted the lines of code in my file manager;
in /home1/martenas/public_html/sources/global2.php on line 2124
&
in /home1/martenas/public_html/sources/global2.php on line 2125
Via The error code given at the top of the screen, and it worked! I could finally get into the admin area! Couldnt belive it!
Im not sure if that was wise, or if it will cause problems down the line, but atleast i was able to get into teh admin zone for now, and do some much needed backups. Now, i am looking into updating to Composr.
You are a proper gent!
pm2k
Secondly, i do admit… i feel like the grasshopper in the story with the ants. You gave us warning of winter, and i just trotted along, not really preparing for winter. I did try and update the software when you said you'd release Composr. But i failed to back up my files (for some reason it wasn't working), and simply gave up.
I honestly almost gave up on doing art for a living, but many people wanted me to continue my lifes passion. This software helped me do just that. But i have neglected to learning how to code & didnt keep up with the times. So i am stuck with the poor decisions i have made.
Enough beating myself up though.
So i tried entering the code you linked, and it doesn't seem to work for me. Though i could have done something completely wrong on my end (being the novice that i am). But i tried simply copying the code in green(omitting the lines in red), and it didn't take. So i took all the code from the link and put it in my global2.php file, and it gave me a blank page. So i uploaded my back up again, and i brought the site back to its current state (with no admin access due to PHP error)
Should i give it a go again? Something i did wrong?
What are some other choice that i may possibly have? Is there anything i can do from the installer or updater screens? Can i revert back to a working state somehow? Or can i update to Composr from the updater page? Everything else works on the website fine. Just cant get into the admin screen without getting the aforementioned PHP errors.
I know you are a busy man. And i doubt you have much time.
But as i ponder my options, including possibly using membership gimmicks from my webhosting… i just sorta feel that i would let go of so much potential i saw in the software to begin with.
So hoping you can help with that.
pm2k
This was the fix:
https://github.com/chrisgraham/ocPortal/commit/0151791078439505a4260b150e3e0795693bbe94#diff-251c3e6887dcd88ed73f4a46b97ef38207f816a047b9c742229413e5c0e51edc
See if you can manually apply the changes there to sources/global2.php. Or if you're not sure, you could try replacing the whole file (but backup that file first!).
TBH This is pretty much a cautionary tale in not keeping up with patches or new releases. It's completely understandable, I've done the same myself with stuff I don't feel like upgrading. But the consequence is being seriously left in the dirt, things breaking and it getting much more complex to upgrade in the future.