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

Moving forward with Composr

ocPortal has been relaunched as Composr CMS, which is now in beta. ocPortal 9 will be superseded by Composr 10.

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


ocPortal 7.1.6 released - Comments

Login / Search

 [ Join | More ]
 

ocPortal 7.1.6 released

Posted 21 March 2012, 7:14 PM

7.1.6 released. Read the full article for a list of changes, and upgrade information.

Read more


Avatar
Hello,

When I saw this listed fix…

"Fixed major layout bug with forms on Google Chrome"

…I thought it meant we could once again see the names of form fields in screens where you add News, Images, etc. For some reason these names disappeared some time back. However, I'm not seeing this issue fixed even though I made sure the caches were emptied in the site and in my Chrome browser after the upgrade.
Avatar
Yes, this is it.

It needs applying to themes manually too. In global.css:

Code


body .accessibility_hidden { /* {$,Contents should be made visible (or interpreted) for accessibly representation but hidden for normal visual display} */
   /* Shift it out of the viewport */
   position: absolute;
   top: -256000px;
   left: 0;
}
becomes:

Code


body .accessibility_hidden { /* {$,Contents should be made visible (or interpreted) for accessibly representation but hidden for normal visual display} */
   /* Shift it out of the viewport */
   position: absolute;
   top: -256000px;
   left: 0;
   display: block; /* stops browser bugs where it interacts with the layout flow incorrectly */
}

i.e. the display:block bit needs adding.

I'm pretty annoyed with Google causing this bug in an automatic update then completely ignoring the test case I reported to them months ago. Generally I really love Google Chrome, but I don't love organisations that ignore bug reports in their key products.
Avatar
Okay, thanks Chris for explaining these things so quickly



Avatar
I have a lot of 'custom' code changes.   Would upgrading either lose those changes, or potentially not really upgrade the system because a part of code that is upgraded is in a 'custom' file?
Avatar
It's important that you apply the patch we posted in the recent security announcement, otherwise if things are fine I wouldn't worry (apart from the Google Chrome bug Rishi discusses above).

If you've been properly saving customised changes into the proper *_custom dirs they won't be overwritten and it's unlikely there'll be a conflict.

Regardless, the upgrade TAR can be extracted manually (i.e. going through the changes by hand) so long as you know what you're doing.
Avatar
Where is that security announce neither searching nor browsing can I find it although I will no doubt stumble across it the minute I dispatch this.

Bob

EDIT: as expected, I just found it: ocPortal security update - ocPortal.com



Avatar
Upgrade went perfectly smooth including running the the theme upgrader.

Thank you! :)

Avatar
Well, there's a surprise I wan't expecting.

Were their any/many TPL changes, Brian?

Bob

Avatar
I honestly never looked to see, I just hit go lol

But my main theme does have a custom header and global template and it looks to have had no problem with it.

I also upgraded this theme which has no template edits that I can recall but does have extensive css changes and it upgraded with no problems too.

Avatar
No theme changes to deal with.

Avatar
Thanks, Brian and Chris.

Avatar
no problems found. smooth upgrading.

Harry

Avatar
Yes, this should be an extremely stable release, as it consists only of bug fixes done in v8 carefully back-ported.

Avatar
I found a problem :( My favorite tool by far, contectual css editor gives an error. I tried it on a few different sites and themes and this is the error I get.

Expand: error error

Avatar
Sorry for the new bug, fix is here:

Fix to CSS editor - ocPortal.com
Avatar
Just saw this, thank you Chris. :)



Avatar
correct, but only to the global.css at my place other css files give no problem

update: found another one news.css

Avatar
I went to copy over the upgrader file with ftp like I usually do, but this time it's telling me it cannot connect to the FTP server. It gives the same message whether I enter the host name as the actual domain name or as IP address. (I was able to connect to our FTP server through Interarchy, so I know I have the correct login info.)

We did upgrade the server for all our websites recently, and it requires SFTP to be used. I wonder if that's an issue here on ocPortal
Avatar
Yes, PHP has no support for SFTP. However, if the server has a good configuration (suExec) it won't need an FTP connection at all to transfer files so you may be able to just leave the FTP stuff blank.


Avatar
Okay, our new server must have good configuration because I left the FTP stuff blank and this time it worked, thanks!

Avatar
Hello,

I'm not sure if it's a bug introduced with this 7.1.6 upgrade, but I just discovered that that system is no longer able to automatically create a thumbnail when I upload a video to the site. However it still automatically generates thumbnails when added youtube videos or uploading images.
Avatar
You'll need FFMPEG on the server, and correctly pointed to by the 'FFMPEG path' option. Also PHP will need to be able to call up system command, and sometimes PHP configurations prevent this.
Avatar
oops, we didn't realize that ffmpeg was not installed on our new server by default



There are too many online users to list.
Control functions:

Quick reply   Expand