hi,
i think the best would be appending to this topic since i am experiencing some problems with this template as well.
basics: i am using the most recent version of joomla 3 (which happens to be Joomla! 3.2.0 Stable [ Ember ] 6-November-2013 14:00 GMT) and the (what i think) most recent version of your oxygen template, at least i just updated it with the version from your downloadlink above even though the site (backend) still says version 2.0 from april 2012 but thats probably more a slip from the template-xml, i just checked the file i downloaded, same info there.
now for my problem about which i am not 100% sure if its a flaw in the template or rather an error cause by iso layer 8 (which would be me ^^) but see yourself:
when i use "featured articles" to display several articles in colums plus 1 leading article, everything is fine.
http://ev-luth-kg.spelle.net/30/
if i do the same using the category blog it looks like this:
http://ev-luth-kg.spelle.net/30/index.php/home-2
already checked, if i alter the div tag <div class="items-row cols-2 row-0 row-fluid clearfix"> manually (inside chrome for example) into <div class="items-row
cols-1 row-0 row-fluid clearfix"> everything looks fine.
bug? working as designed and just a user "abusing" your template in a way it was never meant to be used?
same thing happens at
http://ev-luth-kg.spelle.net/30/index.php/aktuelles
and (for example)
http://ev-luth-kg.spelle.net/30/index.php/termine/year.listevents/2013/11/20/- which is a jevent-page or
http://ev-luth-kg.spelle.net/30/index.php/gemeindebrief do look like i got a 2 cols layout instead of 1 column.
already tried the "trick" from the demo page for two column layout,
<div class="col-2"><div>First column of your content...</div></div>
<div class="col-2"><div>Second column of your content...</div></div>
<div class="clear"></div>
adapting it into "1 column layout" (putting "<div class="col-1">" into the article instead) but didn't work.
PLUS - to stay on topic of this thread: i CAN open articles to edit them, but "save" doesn't trigger anything - at least nothing that i'd notice. but thats more of a sidenote since most of the editiing happens through the backend anyways.