Version 9 has now been released. This version is the gold release of the next version of ocPortal. Upgrading is not necessary.To upgrade follow the steps in your website's http://mybaseurl/upgrader.php script. You will need to copy the URL of the attached TAR file (created via the form below) during step 3.
Please make sure you take a backup before uploading your new files!
Your upgrade to version 9
You can generate an upgrader from any version of ocPortal to any other version. If you access this upgrade post via the version information box on your Admin Zone front page then we'll automatically know what version you're running.
If you'd prefer though you can enter in your version number right here:
If you'd prefer though you can enter in your version number right here:
ocPortal version 9 is now released.
Version 9 includes a major redesign of the default theme (1000s of changes). Compatibility with version 8 themes has been dropped, as well as compatibility for Microsoft Internet Explorer 6 and Microsoft Internet Explorer 7.
We have used the rare situation of dropping compatibility as an opportunity to improve design standards, increase consistency, leverage new technologies, and make themeing easier.
Theme improvements
Standards and semantics:- Enabled HTML5 as standard and broadened our implementation.
- Streamlined data transfer sizes (by disabling some features not commonly used, by default).
- Improved our code validation technology to better support HTML5 and CSS3.
- The HTML semantics have been greatly improved. Pieces of grammatical presentation used for layout have been removed, such as line breaks, brackets, hard-spaces, 'raquo' and 'middot'. Now these styles are placed via CSS, allowing greater control.
Code/layout structure:
- Standard boxes are now achieved directly via CSS, rather than a complex abstraction within ocPortal.
- HEADER.tpl, FOOTER.tpl, and GLOBAL.tpl have been removed and replaced with a simpler GLOBAL_HTML_WRAP.tpl template. In addition, many referenced variables that used to be parameters to these templates, are now Tempcode symbols, meaning you have more flexibility to move stuff around however you want it.
- Templating and CSS applied to overlays, popups, and iframes, has been simplified, so the themer can better understand where particular styles will be applied.
- All HTML wrapper templates (global, overlays, popups, iframes) now share the same HTML header, meaning you only need to add things like jQuery or Google fonts once and they'll also work in frames.
- The panel width setting has been removed, and now this is handled via regular CSS. This allows greater flexibility and simplicity.
- The member and stats bars in OCF are now blocks. These blocks are put in via panel_top and panel_bottom and by default now exist on multiple 'social' pages in the system. The horizontal menu across the top of the forum is now editable by default, and links to all these 'social' (aka community) pages. The forum zone menu link is now titled 'Social'. In essence we have broken down walls between OCF and other parts of the system, and simplified navigation around these areas.
- Our default left-panel menus are now simpler, as we have taken social pages out of them due to the above change. We have also moved 'Rules' to the footer.
- Tidied up the concept of content boxes (i.e. how a box previewing some content should look).
- There is a new catalogue display mode, grids of boxes.
- Internal Javascript naming standards have been introduced.
Themeing usability:
- Much more code commenting in key theme files (now that we automatically minimise CSS, and have Tempcode comments, we can do this without worry of increasing output size).
- Many templates have been renamed, and many parameters renamed, for greater simplicity and consistency, both within ocPortal, and in relation to better use of industry-standard terminology. Some examples:
- the catalogue templates have been renamed to clarify which are used for what.
- 'results browser' is now 'pagination'.
- 'tree' is now 'breadcrumbs'.
- 'link' is now 'URL' (to indicate the difference between an actual URL, and an <a> tag).
- Added example usages of jQuery and Google Fonts, to make sure people understand we are embracing these things even if ocPortal isn't requiring them by default.
CSS:
- The CSS has been completely overhauled - almost all of it has been touched in some way.
- The CSS class names, and file structure are now far more logical and therefore far easier to understand.
- Some styles that did the same thing have been merged.
- Some stuff is taken out of global.css and adminzone.css and side_blocks.css and removed into separate addon-specific CSS files.
- The forms CSS is taken out of global.css and put into forms.css.
- Theme Wizard colours are now defined in a table at the top of global.css, making it easier to manage your complete site colour scheme from one place.
- The number of colours has been reduced, as similar ones have been merged.
- The colours have been given more logical names and clear definitions, so you can understand exactly how they work.
- The Theme Wizard can now be talked-to via OcCLE, which is incredibly useful if you want to extend the accurate result of Theme Wizard equations into your own theme changes.
- We have embraced the concept of 'margin collapsing' in a big way. Rather than trying to explicitly define the spacing between each box, through hard-line breaks or explicit top/bottom margins, we now surround all boxy-elements with a margin and let CSS margin collapsing automatically set them apart at sensible distances. This is a very major change to how we go about things, and a big improvement.
- Almost everything is now spaced using 'em' units rather than pixels. This means that spacing is more accurate, automatic, and consistent. For example, most boxes are spaced with a '1em' margin – if the font size for the surrounding element was reduced, the margin would reduce in proportion.
- We have a very handy new Tempcode symbol called 'BETA_CSS_PROPERTY', that can automatically add vendor prefixes to CSS properties. This is used extensively. Through maintenance of the symbol we can fix late-changes to specifications and ensure things keep working right. For example, IE10 was announced just last night to implement an updated version of the CSS gradients standard, and all other browsers only support the standard of the previous draft – through this symbol we can now support both the draft and the standard, smoothing things out through the transition period, but with no need to give it any consideration to it at all in the CSS files. It also allows the themer to clearly see what CSS is standard, and what is making use of upcoming functionality, or functionality that ocPortal is kludging to work on IE8 (e.g. opacity).
Design:
- Up to now the Theme Wizard has worked mostly by blending saturations of the seed colour. We have now injected some use of colour theory into it, and as a result mathematically correct complement colours are used in a few places.
- CSS3 has been used to add flourish to many existing styles. A lot of use of gradients, curved borders, and transitions, has been added.
- The default start and panel pages feature a new 'deboxification' method that may be deployed anywhere at the webmasters discretion. By wrapping a CSS class around some elements you can trigger them to be rendered without boxes (i.e. no borders, gradients, boxed-title). Instead, they are rendered in more of a newspaper format that is less cluttered and draws the eye towards the content.
- The welcome zone is back on by default, and the default welcome zone features a modern marketing callout and animated content scroller. It's not quite the old splash page that rightly went out of fashion, but it's more of a decluttered and powerful marketing landing page.
- The forum styling used on ocPortal.com is now standard in ocPortal.
- We have been through all the screen previews defined for ocPortal (i.e. every template, every style) and made sure each really looks amazing (and of course, this allowed us to easily ensure all our sweeping changes hadn't broken stuff).
- CEDI is now named Wiki+.
- Improved gallery display a lot, so that if thumbnails have inconsistent styles it doesn't break the grid layout.
- Improved all content view screens to have a more attractive, tidy, and consistent way of displaying meta-data (such as who submitted the content, and the submission date).
- All kinds of new design styles have been added. We'll let you discover them yourself, but it's really cool how nicer some things look, and how consistent these new styles are.
Very little across over a thousand templates and many CSS files is untouched by these changes. Changes are broad and deep, detailed, and consistent. It really brings quality up a few levels.
Compatibility
Some compatibility has been dropped:- Theme compatibility is broken, so all themes will need to be rebuilt. We recognise this is a biggie, which is why we've tried to hard to make this a one-off and to really make it worth it.
- The old syntaxes for the Comcode 'page' tag have been removed.
- The Comcode 'box' tag no longer accepts a height; the dimensions parameter is replaced with a width parameter which accepts CSS units.
- The old 'internal_table' Comcode tag is dropped (history lesson: ocPortal was originally developed before good CSS layouts were possible, so standard boxes used to be tables, which are sized outwards while CSS is sized inwards – we are finally removing the last subtle references to this in our underlying architecture design).
- The 'side_stored_menu' block now accepts a 'title' parameter instead of a 'caption' parameter (for consistency with other block parameter names).
- The side_zone_jump block has been removed.
- To be more touch-friendly, the default menu type is now 'embossed' rather than 'tree'.
- Otherwise, compatibility with v8 is pretty good – we have not done major database changes or changed the internal structuring greatly.
Compatibility with Microsoft Internet Explorer 6 (IE6) and Microsoft Internet Explorer 7 (IE7) has been entirely and irreversibly dropped. This is a change that has allowed us to make substantial improvements without taking months working-around IE bugs or implementing stuff using old time consuming, inflexible, techniques. IE8 and IE9 (and soon, IE10) are essentially a clean start for IE, far more stable and supporting newer standards, and we are leveraging it for all it's worth. We have essentially just done a rendering technology leap of 12 years. Most of the theme changes we have made are due to new engineering decisions that improved technology has allowed us to make.
Some of our visual techniques will not work on all browsers, however these techniques are optional. For example, we make use of CSS curved borders (IE9+), CSS transitions (IE10+), CSS transformations (IE10+), and CSS gradients (IE10+).
Use of modern CSS techniques have allowed us to achieve better display, with less code. Less-prescriptive HTML that relies on modern CSS capability allows themers the flexibility to make sweeping changes without having to modify many templates.
The banner code option has been removed because HTML banner code may now be added within regular banner entries. This is both simpler and much more powerful, but you'll need to re-add your banner.
Other features
This release is definitely not just theme improvements. It also has:- New anti-spam system:
- Blocklists: DNS:BL, RBLs, stopforumspam – advanced configuration to say exactly what checks and thresholds take place.
- Black holes defined on forms to detect spam-bots.
- Support for linking in Project Honeypot honeypots, in a way likely to prevent spammers auto-detecting the honeypot.
- Internal support for temporary IP bans.
- An OcCLE command for checking against blocklists.
- New content filtering system:
- A highly flexible filtering systems, supporting many different modes of operation and great richness in filter definition.
- New mini-language for defining filters: ocSelect.
- Filter block, for easily building up content filtering forms for most major content types in ocPortal.
- Merged category browsing option (per-content-type), where browsing subcategories works as a filter metaphor rather than as an exploration metaphor).
- More sophisticated calendar recurrence support (e.g. every third Tuesday of the month).
- Automated detection of out-dated non-bundled addons and bulk upgrading
- A trick to improve browser caching of Javascript and CSS files, so outdated files are not incorrectly cached.
- Better catalogue CSV import (e.g. control of how duplicate records are handled).
- A hint about if either Safe Mode or Fatalistic Mode are active is provided, for usability reasons.
- Member directory search by email address (admins-only).
- Integrated OCF signup into the purchase wizard (so you can, for example, purchase a subscription account without having to join separately first).
- Listing inside the upgrader of what files belong to non-bundled addons (rather than just labelling everything external as simply alien)
- Support for adding direct-HTML/PHP banners (as advertising affiliates will often provide raw HTML for you to use, but many site admins prefer to continue to work through the banner system rather than template editing)
- Improved backup generation/restoration, memory limits no longer provide a problem for backup size (CGI/safe-mode server timeout during generation is still a problem for some servers though, so we continue to recommend using third-party backup if possible)
- New OcCLE commands:
- phpinfo (useful if the PHP-info addon is not installed, or the Admin Zone is not accessible for some reason)
- db_search (useful for finding where data is stored in the database)
- directory_sizes (to find out how much disk space is being used, and where)
- mysql_table_sizes (to find out how much database space is being used, and where)
- New/updated non-bundled addons
- "Member directory boxes" addon for advanced member directory search with a year-book layout
- New "Related members" addon (allow members to define themselves to be in a shared family, with other family members shown on a member profile tab similar to friends)
- Static site exporter (use CMS tools for authoring then export your site to static HTML, if you don't need dynamic features and want the site to run really fast without needing a database; all forms get routed through an e-mailer script)
- New backup tool for developers to generate a TAR backup in real-time as a direct download, with basic directory and time filtering support
- Many code cleanups and small improvements to existing functionality





Edited
Comments
The non-bundled addons aren't out yet, but should be out tomorrow.
(Except of course the theme compatibility break)
All reported bugs are now fixed, listed in the usual place:
9 - ocPortal.com
These are the two issues found so far that everyone will wish to patch:
Upgraded to 9 - Hate it.
Patty Lynch
patty@lldrepsonly.biz
Use that to restore your site to its original 8.x.x state.
You should have read the 'negative' comments about upgrading to 9.0.0 in this thread. It would have rung alarm bells!
If you didn't use the ocPortal backup system, read to the end.
You should be able to restore things to an acceptable level, even if it takes a bit of time. Ultimately, it is worth it - nay, essential - since you don't have a site that you had or want!
Good Luck!
Thanks for your help!
Stick to 8.x.x until you decide you wish to change the layout completely, THEN take a stab at upgrading. Build a 'clone' site (comprehensive instructions by temp1024 at - View topic: How to clone your ocPortal site - ocPortal.com) and work on that, (one bite of the elephant at a time), and you will slowly realise how, where and what you need to change to achieve your objective.
I know I am slowly going through this painful process, but on a more enthusiastic note, I am also seriously toying with the idea of a completely 'new' design.
Here's to your success …
Despite all of the warnings, I decided to take the hard route. Yes, I am just that stubborn.
Yes, the work was hard. I had to replace certain files that got left out of the upgrade for some reason, and had to slowly rebuild my theme from scratch. But over all… It just wasn't as bad as I was fearing it would be ™.
For most sites, the best route for an upgrade if they must have one would be to do the cloning method. I chose to do the hard way because hey, someone had to. My site is now up and running well, and everything looks fine (after 100+ questions in the Developing Forum, sorry about that Chris).
If I could make one suggestion Chris, remove the theme upgrader for upgrading to v9. Instead put in big bold letters YOUR THEME WILL NOT WORK IN v9!!!!!! That sould catch all of those who just refuse to believe your warnings of doom!
Over all, a good release. But please, lets wait a while before the next major breaking release lol.
As you rightly point out, this is a one-time MAJOR change to anything we are currently running in versions <8.x.x, and sites and themes will need to be rebuilt - from the ground up.
For that reason alone I don't think I will be rushing to upgrade to v9.x.x any time soon. Perhaps the solution would be to build a new site based on version 9, but I don't have the heart to 'start all over again'.
Also, you might want to consider removing my site as an 'example' build from the ocP Home page as it will no longer be a relevant example. If I manage to resurrect the site with a version 9 build and theme, I will re-submit for your perusal.
I 'upgraded' the sacrificial 'clone' site, and I wasn't disappointed.
It got HOSED!
Now it's back to temp's instructions on how to clone a site, so that I can resurrect the clone, although I don't see the need for it any longer now that I know that v9 isn't going to play nice!
I suspect there will be a plethora of 'established' ocPortal sites stagnating at version 8.x.x for some time to come.
v9 is a great base for new users.
I imagine v10 will be quite a while, so some existing users may wish to jump over v9 and go straight to v10 when it does come, which probably include the other side to compat breaks – server-side stuff (e.g. raising the minimum PHP version, heavily reorganising the filesystem, and so on).
Yeah, OK!
Some users might not be aware they are using a theme. Really, anyone who has chosen a colour during the Setup Wizard, has a custom theme, which won't be compatible after the upgrade.
You can delete and recreate the theme from the Admin Zone, which will be fully working and accessible.
Admin Zone > Style > Themes, then choose to edit the theme and delete it.
Then you'll find the option to make a new theme on Admin Zone > Style > Themes also.
v9 and themes
On a theme-by-theme basis we can upgrade and license them via our normal support system though. We'd need to charge a few support hours per theme to do the conversion – we're saying we'll do this at a loss to share the upgrade cost, although exactly how that will work out isn't decided yet.
We also are maintaining version 8 with bug fixes for the time being, there's no reason to upgrade if you don't wish to. As mentioned elsewhere in this thread, I expect some users will choose to leapfrog v9 at the point where they're ready for a new reinvestment/upgrade cycle in their sites.
The full story is that we invested heavily to make them due to a high demand for professional ocPortal themes. After they were released people stopped giving any feedback on themes at all, and we didn't make any sales. I think ultimately people wanted to see a large number of themes, but for free or possibly just as a demonstration of what can be achieved. Normally we'd get some kind of feedback, even if to say the price was wrong, I just expect people realised the price was fair but most users didn't have budgets, or if they did probably didn't want to use a theme. I'm sure there would have been one or two exceptions but the cost of just maintaining such a large collection of sophisticated themes would be many times more than we'd recoup in sales.
I think the main take-away from the experience for me is to survey-survey-survey on people's actual intentions rather than just implementing feedback unquestionably. A big lesson for me there.
v9 and the theme
On my end, credits were spent in this process, if the next version is soon, I could possibly wait. There is content that is in need of publishing, and I am not exactly sure when my classes start again (although I should find out on Thursday), when they do, there will be fervent publishing.
Otherwise, if you could take a look at how the site looks now (post-upgrade), it would be great to have a firmer idea of what it would take to get back what has been lost.
I can roll it back at some point to the 13th which was the last date before the upgrade, but, I may not have much time to decide as I'm not totally familiar with SG's restore process and data discharge schedule.
Will the v10 upgrade lead to these issues as from 8 to 9? With the editing done to this to date, it doesn't seem practical to restart this project, will there be a big gain in v10?
As usual, your efforts and skills are appreciated.
As detailed in the release announcement, the themeing changes exist on a level somewhere between a reorganisation and a complete rewrite. So it's not so much a matter of upgrading the themes, it'd be a case of rewriting large chunks of them, perhaps 6 hours per theme if we work really fast and efficiently. v10 wouldn't change this, but I expect by the time that comes (quite a long time I imagine, but this hasn't been determined) users would have gone through a redesign cycle on their sites anyway.
If you upgraded without realising I would suggest restoring the backup. As discussed above, people aren't required to upgrade and we're maintaining v8 with bug fixes. v8 is a great release and it's not being abandoned.
I'm afraid I'm not sure I follow so please clarify for me. Is SG the webhost, and you are relying on the backups taken by the web host, and are not sure how their restoration process would go?
I know it's not helpful for me to say at this point, but our advice is to always make your own backups and to test them – personally I wouldn't trust a web host's own backup system unless I had instant access to the backups and had verified their integrity.
Best regards,
Chris
So I wonder if I should bother with 9. Is it going to be a major improvement over 8?
My biggest issue with OCP so far is simply speed, it seems so much slower than anything else I have used.
I find that, for me, v9 feels a bit faster than v8.
ocPortal is a huge behemoth of a program. There are a lot of database calls and such that your speed with ocPortal is more or less going to be dependent upon your host. However, the improvements and changes to how templates and themeing and whatnot work in v9 seem, for me, to make it run a little faster and smoother.
The question if making the change to v9 yet is a good idea or not can only really be answered by you. Do you really want or need the themeing improvements and standarizations put into v9, or is v8 doing well enough for you now as it is? I note that you still have some things not working in v8, and there is no guarentee such things would work in v9. But for the most part, the largest change in v9 is templating. That might give you a preformance boost… but is it worth the headache to make the change?
For me, it was. For you? That is really just something you are going to have to think about. But at least there is no rush to do so and you can continue to use v8 as long as you like. It is, after all, your site
Ooh, burn!
I'm sure he must have meant Windows 2000
Historically speaking, Windows Me is more notorious with being a horrible platform that was quickly dropped by Microsoft.
I can't see how ocPortal 9 fits that description. If anything, it is more akin to KDE4.0 - 4.2, being that it was a huge changing of the engines and such used, themeing and what not overhauled, and such upgrades caused pains for many despite the fact that if taken as a whole as seperate from KDE 3.5 series, it was really an ok system.
And, it became so much more with 4.9 being quite a stellar release.
The trouble with that analogy is that not many know about KDE to relate to it. As hard as I try though, I just can't find an acceptable Windows analogy to fit…
Show 8 more replies