Upgrade

My site I setup couple years ago is running version 9.0.33 and I'm working on upgrading it to the latest version.

First question, do all the directories and files need to run on web root, or can I make it more secure and run some off the web root?

I have done the update on database for utf-8 and it's ready for upgrade.

Second question, install the utf8 addon, where at or how?

I tried to do the generate upgrade on your site but didn't work for me so I downloaded the Omni-upgrader package.

Last question, do I just upgrade Omni-upgrader package on my server?

If I'm going to crash my site or upgrade I might as was do it now before I start chaning everything

Thanks

Hi Joe,

Quick answers…

Web root not required, fully flexible from any base URL.

utf-8 is the default now, no addon needed like was in v9.

Omni-upgrader correct, our compo.sr site doesn't have access to the ocPortal builds to generate upgrades, and the system has changed a little anyway.

Thanks for the quick reply Chris,

Wish me luck  

Good luck . Hope it goes better than things did for this guy:
 

Tagging on to this.
Was there some template changes made in R25?
.page_running_catalogues .panel_right {
display: none;
}

No longer works, while I can change the template to fix this. Are there any other tricks to hiding the sidebar opn certain pages, doesn't seem to be a native feature?

Hi,

I don't think that would have ever worked. Try doing "#panel_right" instead of ".panel_right".
You can also use Tempcode within (around) the panel's Comcode.
{+START,IF,{$NEQ,{$PAGE},whatever}}...{+END}
Empty panels will not show at all.

You can also customise the GLOBAL_HTML_WRAP.tpl template but that requires more care.

Yep, was meant to be a hash. Not being able to selectively disable the right sidebar via the settings is unfortunate, as I have found I needed to do some template and css changes to not only hide the blocks, but to expand the middle. This is proving to be a pain. Thankyou anyway.

If you use the Tempcode technique it will mean you won't need to do the expanding the middle thing, the default templates automatically adjust the spacing if a panel is blank. Plus you transfer less data.

We don't generally make things point and click when we think it's layering on too much of an assumption about the nature of things someone might want to do or the nature of the site - as it's possible people might want to hide the panel based on other criteria than the page (e.g. a visitor's usergroup), and a lot of sites won't have panels so we don't want to expose options that don't apply to those sites. That's the reasoning, I know sometimes it makes things harder, but in the longer run I think it makes for a more flexible and less-bloated system.

Used  and it worked a treat.
Thankyou

I been trying to upgrade my site 9.0.33 but nothing is working yet

I tried this latest Composr 10 RC28 and it didn't work, them I downloaded it to server, can't extract it.

I did a file integrity check, tried to delete obsolete files from the past and I get this message…

You don't have permission to access /upgrader.php on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Also tried file transfer and everything else on my upgrade page

My thoughts are, it seem there should be an easier way going from ocportal to composr, oh well it is what it is

Any ideas? I would appreciate

Thanks
Joe

Iddigger said

I been trying to upgrade my site 9.0.33 but nothing is working yet

I tried this latest Composr 10 RC28 and it didn't work, them I downloaded it to server, can't extract it.

I did a file integrity check, tried to delete obsolete files from the past and I get this message…

You don't have permission to access /upgrader.php on this server.

Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

Also tried file transfer and everything else on my upgrade page

My thoughts are, it seem there should be an easier way going from ocportal to composr, oh well it is what it is

Any ideas? I would appreciate

Thanks
Joe

From “Post #1385”, 15th Dec 2016

You need to use the omni-upgrader from

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

- that can be fed into the ocPortal upgrader to do an upgrade without any manual extraction.

An error like "You don't have permission to access /upgrader.php on this server." is usually caused by either too many, or insufficient, file permissions on the particular file (upgrader.php) in this case. For example, often if you set every user to have write permission, it won't run the file for security reasons. That's an Apache limitation.

The omni-upgrader process should avoid most complexities setting correct permissions etc for Apache like that.

Iddigger said

You need to use the omni-upgrader from

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

- that can be fed into the ocPortal upgrader to do an upgrade without any manual extraction.

An error like "You don't have permission to access /upgrader.php on this server." is usually caused by either too many, or insufficient, file permissions on the particular file (upgrader.php) in this case. For example, often if you set every user to have write permission, it won't run the file for security reasons. That's an Apache limitation.

The omni-upgrader process should avoid most complexities setting correct permissions etc for Apache like that.
[/Iddigger]

Already tried the

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

and it didn't work, also users don't have write permission.

Thanks Chris

Iddigger said

Iddigger said

You need to use the omni-upgrader from

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

- that can be fed into the ocPortal upgrader to do an upgrade without any manual extraction.

An error like "You don't have permission to access /upgrader.php on this server." is usually caused by either too many, or insufficient, file permissions on the particular file (upgrader.php) in this case. For example, often if you set every user to have write permission, it won't run the file for security reasons. That's an Apache limitation.

The omni-upgrader process should avoid most complexities setting correct permissions etc for Apache like that.
[/Iddigger]

Already tried the

Upgrading from ocPortal v8/v9 to Composr v10

How to upgrade from ocPortal to Composr

View

and it didn't work, also users don't have write permission.

Thanks Chris

From “Composr ebook”, 16th Dec 2016

Are you able to restore a backup, then report a bug on the exact failure you have with the omni-upgrader?

Thanks for checking Chris

I was so mad I wanted to delete the site and start over
I mellowed out now and still working on it, I'm manually deleting .htaccess bak files and some older ones.

I'll keep you informed on how it goes, the worst that can happen is I crash the site lol, not enough members to worry about anyway, most all spammers

I am determined to conquer it for now though

Thanks again Chris

Iddigger said

Thanks for checking Chris

I was so mad I wanted to delete the site and start over
I mellowed out now and still working on it, I'm manually deleting .htaccess bak files and some older ones.

I'll keep you informed on how it goes, the worst that can happen is I crash the site lol, not enough members to worry about anyway, most all spammers

I am determined to conquer it for now though

Thanks again Chris

From “Post #1399”, 18th Dec 2016

I understand. We'll ensure your site updates properly, just I need you to engage with the official process and report any issues - it may be a bug or at least some kind of server issue we need to automatically workaround somehow. Once a bug report is received and confirmed, I may just offer to do the upgrade for you if that seems prudent.

Hi Chris and thanks again

I guess I don't know what I'm expecting with this upgrade, I do see new files have been uploaded, I guess I was expecting changes to my site, still showing I'm running 9.0.33

I deleted all the files recommended by file integrity check, most of them were .htaccess bak files, they even when to my other directories and pages not related to ocPortal, I did the clear caches, check and fix missing perm and everything else.

I can't launch site in safe mode though…

Forbidden
You don't have permission to access /index.php on this server.
Additionally, a 403 Forbidden error was encountered while trying to use an ErrorDocument to handle the request.

I did call my server and they can't find any permission settings causing this or other problems. I disabled all users write permissions.

The site is running without any problems, I just thought I would see new changes and have to tweak things around again

Oh and yes before I started everything I did start with RC25.cms then the latest RC28.cms doing step below…

"You need to use the omni-upgrader from Upgrading from ocPortal v8/v9 to Composr v10 - Composr - that can be fed into the ocPortal upgrader to do an upgrade without any manual extraction"

I am missing this file…
site/pages/html_custom/EN/download_tree_made.htm
Not in any zips file though.

Thanks, Joe
P.S. I did check for errors on server and can't find any.

So you went through the "Transfer across new/updated files" step with the URL to the RC28.cms file, and it showed all the files extracting until it completed, but the site wasn't upgraded?

If you open a ticket with site access I'll take a closer look:

Add a new support ticket - Composr

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

View

Thanks Chris

I needed a break from this

I did a ocportal upgrade last night from 9.0.33 to 9.0.35 and I can see files being transfered and now its running 9.0.35. After this I tried the latest omni-upgrader, I did learn files do not transfer. I tried rc25, rc28, and rc29.

Should I change upgrader.php and uninstall.php with composr files? or not?

I know you offered to look into it Chris and I may still take your offer I still like to know how to fix things

Thanks, Joe

Oh well I love the support here Now I know what to do