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.


[Solved before I even posted] Sidepanel Title Issues

Login / Search

 [ Join | More ]
 Add topic 
Posted
Rating:
#67813 (In Topic #14444)
Avatar

Community saint

ocPortal 6.0.2

Greetings

Ok so I saw the message about how headers were changed, and that the !important tag is really important now and all that. I can't seem to find though the setting that changed the little standardbox title panels, so that I can fix them (or do I need to put in a new rule?)

Anyways, since a picture is worth a 1000 words, wheres 2000 words worth of description to show what I am refering to.
First the simply recolored theme for my Saga of Ablution page (will be builing a theme there soon-ish)


Now for the Clasic Legends theme, shown on the home page anod most of the site.


Anyways, I am wondering how to fix those side headers taht have gotten malformed in the update to 6.0.2. Eventally I would probably locate it, but here is hope that one of you much more intelligent than I people can speed up my process. Many thanks in advance!

BTW- This was tested and witnessed in Opera 11, rekonq, and Firefox 4.


Last edit: by mythus

Legends of Nor'Ova: A site powered by ocPortal; home of the Legends of Nor'Ova tabletop RPG wiki and community.

Like ocPortal? Want to thank Chris and gang somehow? Then help out in the chat room! It really needs your help! Just open it in a tab everytime you open your web browser, and when you hear a "ding", check it out!

"Those who want help should first be willing to give help."
Back to the top
 
Posted
Rating:
#67814
Avatar

This is exactly the issue described. Look for ".standardbox_title_panel {" in the global.css of your theme.


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#67815
Avatar

Community saint

Ah yes… how embarrassing as well. What I get for glazing off as I get towards the important stuff, it said the answer to the issue right at the bloody bottom of the news post.

Sorry about that Chris. As usual, you are already on top of it all.

Legends of Nor'Ova: A site powered by ocPortal; home of the Legends of Nor'Ova tabletop RPG wiki and community.

Like ocPortal? Want to thank Chris and gang somehow? Then help out in the chat room! It really needs your help! Just open it in a tab everytime you open your web browser, and when you hear a "ding", check it out!

"Those who want help should first be willing to give help."
Back to the top
 
Posted
Rating:
#67824
Avatar

Community saint

Chris Graham said

This is exactly the issue described. Look for ".standardbox_title_panel {" in the global.css of your theme.
Your's and ocPortal's BAD, Chris. This was TOO well hidden amongst the list of 'fixes' and NOT clear enough.

Sorry, but that's my take as I suffered the same 'nightmare' as mythus, went ahead and 'fixed' all my display issues by editing the appropriate CSS properties (the correct entry as it turned out), and THEN I stumbled across this thread.

Issue now sorted, BUT

I'll start new threads for a couple of other issues …




Take my advice. I'm not using it!

View my working ocPortal site (version 9.x.x) at Anglo-Indian Portal
Back to the top
 
Posted
Rating:
#67837
Avatar

Sorry about this. From a personal point of view, it's hard to find the time to tune these release announcements more carefully (12 hour work days are already pretty typical with my workload). You might want to consider holding back a little and letting someone else take their turn to feel any possible pain first if it's getting frustrating. I have now edited the post to add an additional note about the issue above it – I quite typically will go back to the release announcements and clarify them a bit as people experience any difficulties.

This isn't directly related to this particular experience, but I'm also aware it may seem like a bug fix merry-go-round. What it actually is is that as ocPortal becomes more stable and successful, people dig deeper to find bugs, like peeling off skins on an onion. We have two developers here in addition to myself working full time on ocPortal projects and lots of clients doing testing of their sites and new waves of users making sites, and that is leading to a big ramp up in the bug reports coming through; and of course with v6 just out and the more risk-adverse users now using it, additional testing is happening with the new code.

We're trying hard to not add functionality-orientated features, instead just fixing bugs and usability issues, to reach a level of great stability. Even most of v6 could be considered a bug fix in a sense, for performance issues and usability issues. I know it doesn't always seem like that though.

For a self-check I've just gone through the 6.0.2 fixes to classify them. I've not done this for any kind of PR purpose, I actually thought this was a good prompt for me to do this as it's not an exercise I've gone through before.

Of the fixes between 6.0.1 and 6.0.2…

Expand: Fixes to old functionality that had broken with changes since v5 (8 issue, 10.39% of issues resolved) Fixes to old functionality that had broken with changes since v5 (8 issue, 10.39% of issues resolved)

Expand: Fixes to issues in new v6 functionality (10 issue, 12.98% of issues resolved) Fixes to issues in new v6 functionality (10 issue, 12.98% of issues resolved)

Expand: Fixes to old issues in old functionality (58 issue, 75.32% of issues resolved) Fixes to old issues in old functionality (58 issue, 75.32% of issues resolved)


TOTAL: 77 issues resolved.


I think that's a fair reflection. We're not doing perfectly but it does show we're fixing much more than we're breaking :). The plan is to keep going with this approach, only implementing things that are solving bugs or usability/performance problems for the near future. When we then come to making a new major release we can leave it as 'bleeding edge' for a much longer length of time than we have in the past.


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#67842
Avatar

Community saint

Chris Graham said

This isn't directly related to this particular experience, but I'm also aware it may seem like a bug fix merry-go-round. What it actually is is that as ocPortal becomes more stable and successful, people dig deeper to find bugs, like peeling off skins on an onion.

I completely agree with that statement for the most part. Indeed many things are becoming much more stable plus the ability to find things deep within the system is becoming much easier. These are all great things and great accomplishments.

However: Some things that are being reported are not deeper level issues or whatever. For example, the paypal issue, while not at all ocPortal's fault, was more of a issue of things that used to work before but then got a bug later. Such an example though came not from ocPortal's change of code, but from Paypal's updating of it's authentication process. Having a small team it could indeed be difficult to have found such a bug, but that is what makes open source so great, you gut us to do that and report it!

An other example where this isn't true is with the sidepanel headings. While true this was changed to address usability and accessibility standards, and may not be seen as a bug per say, for many it is a bug. Especially for people using themes that were made by others.

While I strongly approve of continual improvement and accessibility, you gotta be careful here. Making changes that require fixes or remakes to themes is one thing, but having these changes take place as quickly as has been the case with ocPortal here lately will do one thing, it will drive people to not want to make themes for ocPortal, if anything out of sheer frustration and unknowing if the next release will come next week or next month or tomorrow and just what changes will need to be made to their themes they released two weeks ago under a release that is now two versions old.

Fletch:
I dunno… as I had read it, the fix was at the bottom in it's own code box. So it wasn't hidden by any means. Maybe it should had been addressed at the top of the change list, or maybe a big, bold text or whatever saying, "Changes to sideheadings are made, please refer to the bottom of this write up for more information" or whatever… *shrugs* but I really think in my case it was 99.9% my fault.

The one thing that I think might help is perhaps utilizing the hide tags in these write-ups. For example, the reason my eyes glazed over before I got to the important bits of info is because there was literally tons of changes and change logs in the write up. By the time I got halfway through I simply started glazing over the document and got tired of reading it. Perhaps if you were to break it up under hide tags such as  Changes, New Items, Fixes, but leave the big important must fix code completely visible, I wouldn't have glazed over it and Fletch wouldn't have seen it as hidden. Just an idea lol.

Legends of Nor'Ova: A site powered by ocPortal; home of the Legends of Nor'Ova tabletop RPG wiki and community.

Like ocPortal? Want to thank Chris and gang somehow? Then help out in the chat room! It really needs your help! Just open it in a tab everytime you open your web browser, and when you hear a "ding", check it out!

"Those who want help should first be willing to give help."
Back to the top
 
Posted
Rating:
#67843
Avatar

While I strongly approve of continual improvement and accessibility, you gotta be careful here. Making changes that require fixes or remakes to themes is one thing, but having these changes take place as quickly as has been the case with ocPortal here lately will do one thing, it will drive people to not want to make themes for ocPortal, if anything out of sheer frustration and unknowing if the next release will come next week or next month or tomorrow and just what changes will need to be made to their themes they released two weeks ago under a release that is now two versions old.

Definitely agreed. I was of two minds about it from the start, but as ocP6 is so new still I thought better fixed early. I know it's controversial, it probably would not go this way next time.

The one thing that I think might help is perhaps utilizing the hide tags in these write-ups. For example, the reason my eyes glazed over before I got to the important bits of info is because there was literally tons of changes and change logs in the write up. By the time I got halfway through I simply started glazing over the document and got tired of reading it. Perhaps if you were to break it up under hide tags such as  Changes, New Items, Fixes, but leave the big important must fix code completely visible, I wouldn't have glazed over it and Fletch wouldn't have seen it as hidden. Just an idea lol.

Nice idea :).



Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#67844
Avatar

Community saint

mythus said

While I strongly approve of continual improvement and accessibility, you gotta be careful here. Making changes that require fixes or remakes to themes is one thing, but having these changes take place as quickly as has been the case with ocPortal here lately will do one thing, it will drive people to not want to make themes for ocPortal, if anything out of sheer frustration and unknowing if the next release will come next week or next month or tomorrow and just what changes will need to be made to their themes they released two weeks ago under a release that is now two versions old.
And of course bugs in general that can drive people away. One of the last things I looked at before deciding to go with ocPortal was the stability. Looking at Confirmed bugs - ocPortal gave me the impression that it was a very stable product. I certainly didn't expect to see so many bug fixes in .0.0.1 patches and so quickly, let alone that I would be reporting so many bug in such a short time myself.

Once my site goes live I was already planning not do any upgrades for a long time (i.e. if it aint broke, don't fix it), but with the range of errors creeping in, that time between upgrades will almost certainly now be longer.

Do you have a Samsung Galaxy S / Galaxy S II ? If so, why not check out my ScreenFree FM Radio .
Back to the top
 
Posted
Rating:
#67845
Avatar

Yeah unfortunately big systems just tend to have bigger scope for bugs. But actually even the smaller third party systems we integrate with often have bugs that we need to patch into ocPortal and often we need to make the fixes ourselves (e.g. there have been maybe 8 bugs in just editarea, the syntax highlighting code editor we use). The bug catalogue isn't intentionally misleading, it's just there to organise carefully more serious fixes in functionality that might have recently broken for some reason or some kind of rare nasty problem that has a big impact.
This catalogue is an index of some confirmed bugs found with ocPortal (usually the most serious ones)


Become a fan of ocPortal on Facebook or add me as a friend. Add me on on Twitter.
Was I helpful?
  • If not, please let us know how we can do better (please try and propose any bigger ideas in such a way that they are fundable and scalable).
  • If so, please let others know about ocPortal whenever you see the opportunity.
  • If my reply is too Vulcan or expressed too much in business-strategy terms, and not particularly personal, I apologise. As a company & project maintainer, time is very limited to me, so usually when I write a reply I try and make it generic advice to all readers. I'm also naturally a joined-up thinker, so I always express my thoughts in combined business and technical terms. I recognise not everyone likes that, don't let my Vulcan-thinking stop you enjoying ocPortal on fun personal projects.
  • If my response can inspire a community tutorial, that's a great way of giving back to the project as a user.
Back to the top
 
Posted
Rating:
#67847
Avatar

Community saint

The 'criticism' was not meant to be harsh, just an expression of a personal frustration at not deciphering what I should have checked more closely.

Chris Graham said

The plan is to keep going with this approach, only implementing things that are solving bugs or usability/performance problems for the near future. When we then come to making a new major release we can leave it as 'bleeding edge' for a much longer length of time than we have in the past.

Your explanation was precise and to the point, and I have to say that, in my case at least, you are preaching to the converted!

Keep doing what you are doing - and I will try and put a sock in it.

 :$

Take my advice. I'm not using it!

View my working ocPortal site (version 9.x.x) at Anglo-Indian Portal
Back to the top
 
Posted
Rating:
#67858
Avatar

Community saint

*nods* I concur with Fletch.

You have no idea how appreciative I am of the awesome system you guys have put together. Truly. There isn't a system out there with the power, the versatility, the flexibility, and yes, even the stability of ocPortal. I know! I have used my fair share!

(not in any particular order)
Drupal (5 and 6, barely toyed with 7 - what a nightmare to put together a site with!)

Joomla (all but the current…. Loved it at first, easy to use, but began to hate it when faced with certain inflexibilities of it and loathed it when dealing with site security and bugs)

Dragonfly CMS (the old cpgnuke, thought it was pretty neat at first, but stayed stagnant and internal laziness + conflict drove me away)

the phpnukes (to many to list! each shortly after dragonfly, each getting frustrated with)

e107 (I loved this one for awhile, but security, stagnation, lack of support, and lack of progress with their cms were big downfalls)

mambo (briefly before trying joomla, don't remember much of it except that joomla was more stable)

I feel like there's another one that I am forgetting. The point is, if it wasn't for ocPortal being as awesome as it is, and the wonderful support you guys give, I'd still be with either Joomla (praying the site doesn't crash terribly and upgrades without too much headache) or e107. Heck I might even had settled on Drupal and lost many weeks of sleep still trying to get the site halfway to where it is right now.

Bugs, instability, and other such problems; these are issues that are going to plague any software, free or commercial. In the open source world we at least have the tools to make the fixes needed, even if we lack the know-how. In the ocPortal world we have the added bonus of support from the developers, developers who actually give a damn about what their userbase has to say!

Case in point: I complained about the inability to use the WYSIWYG editor in any browser except firefox (I don't have windows). What happened? They switched to a new editor that is cross-browser compliant! I complained about having to go through twenty (exaggeration used) pages to edit a theme…. they cut down on that drastically! And every issue I have had… every. single. one. has been addressed personally by Chris Graham himself, and several of the other ocportal users. I mean, where else can you get support like that? No where. Not with joomla (you'll get tons of user base people that might help yeah, but not as knowledgeable as the developers), not within a linux distro, not from Microsoft (and that's a commercial product, and just look at how buggy their stuff constantly is!).

The point is, stability, security, and flexibility are all important stuff to look for in choosing a CMS, but the most important aspect, the one that sold me on to ocPortal long ago, is support. ocPortal has that and has everyone else beat at that, and the bugs, however aggravating they may be, aren't show-stopper bugs and are quickly resolved by the developers. Remember, in an open source world, we are the product testers, and we are using this product for free, so we should feel the desire to report back all bugs, and be grateful we got developers who care enough to fix them instead of declare them as features.

The only thing that I wish for though, and I know, I am being nit-picky after preaching against it lol, is that there be either a.) a longer period of time where you don't have to make changes to themes to make them work with current versions, and/or b.) that upgrades somehow upgrade the theme in a sane manner (long shot, I know, but I can wish right lol).

Don't stopr working on ocPortal, releasing fixes and updates and new versions, just make them more theme-change proof and it's all good (most of your versions, admittedly, have been  so). Continue what you are doing Chris and ocPortal guys, and know that when ole' mythus starts complaining, it isn't that he is hating what you are doing, he is just upset that someone crossed over his recently manicured lawn!

Legends of Nor'Ova: A site powered by ocPortal; home of the Legends of Nor'Ova tabletop RPG wiki and community.

Like ocPortal? Want to thank Chris and gang somehow? Then help out in the chat room! It really needs your help! Just open it in a tab everytime you open your web browser, and when you hear a "ding", check it out!

"Those who want help should first be willing to give help."
Back to the top
 
There are too many online users to list.
Control functions:

Quick reply   Contract

Your name:
Your message: