Reorder Blog Plugin Sidebar


(Chet) #1

URL: https://www.chetjcollins.com/blog/

I’ve decided, after much experimenting, to use the standard RW blog plugin. I’ve been blogging since 2013 and have over 700 posts. I’m using the Writer theme by NCD.

On the sidebar, I’m a bit frustrated on two pieces.

  1. In RW6, the months displayed the 3 letter abbreviation (Mar for March, etc), but that changed in RW7, with the archives only displaying the full month name. Of course, that makes the list much longer which equals more scrolling. Is there any way to force RW to display that 3 letter abbreviation in the Archives?

  2. The default order for the RW blog plugin sidebar is Categories, Archives, Tags. Is there any way to rearrange that order?

Thanks in advance for the helps and ideas!


#2

To your question number 2, I have been able to change the order in the sidebar by using some javascript. For example, to move the RSS link above categories paste in Page Inspector > HTML > JavaScript:

<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js"></script>
<script type="text/javascript">
var $j = jQuery.noConflict();
$j(function() {
$j("#blog-categories").before($j("#blog-rss-feeds")).css({'padding-top': '0px'});
});
</script>

To move the tag cloud use #blog-tag-cloud instead of #blog-rss-feeds, or to move the archives use #blog-archives. So this moves an element in relation to another element.


(Chet) #3

Thanks for the idea. It seems that particular script interferes with the theme’s nav.

Is this ordering done by RW itself or is it a theme option? If the theme determines the order, then perhaps I could mod the theme, but I wouldn’t want to do that if it was a program-level decision.


#4

I don’t have the Writer theme so I can’t test myself. As such, this script should work with the Rapidweaver default blog plugin. It’s not theme dependent but as you noticed it could conflict.


#5

Have you tried without the padding-top value .css({‘padding-top’: ‘0px’});? Any help?


(Chet) #6

No luck w/o the CSS. :confused: