1. Removing the pagination links (next/prev) from archive.php:27 was trivial:

   <div id="archive-posts">
       <?php arras_render_posts( null, arras_get_option('archive_display') ) ?>     
   
       <?php if(function_exists('wp_pagenavi')) wp_pagenavi(); else { ?>
           <div>
               <div><?php next_posts_link( __('Older Entries', 'arras') ) ?></div>
               <div><?php previous_posts_link( __('Newer Entries', 'arras') ) ?></div>
           </div>
       <?php } ?>
       </div><!-- #archive-posts -->

2. arras_render_posts() (library/template.php:157) uses the WP’s loop query, which has posts_per_page set to 10 globally, and it seems by the time Arras’s archive.php is invoked it’s too late — the query was already processed and cannot be modified?

   function arras_render_posts( $args = null, /*...*/ ) {
       /*...*/
       if ( ! $args ) {  
           $query = $wp_query;
       } else {
           $query = new WP_Query( $args );
       }

3. A workaround would be to pass a new query instead of null. But how to keep the WP query’s other parameters, and modify just posts_per_page (or posts_per_archive_page)? And, for efficiency, how to avoid running another query by modifying WP’s?
4. Or, an ugly hack around this, was to run another query, thus replacing the global $wp_query:

   query_posts($query_string . '&posts_per_archive_page=-1');  
   arras_render_posts( null, /*...*/);

5. But really, this is definitely not the place to hardcode this option.

The navigation menu in our theme Lavender is in the sidebar, and in order to keep it above the fold, at least initially, we want to collapse the nested levels using an accordion effect.

Requirements

1. Hierarchical menu
2. Only leaves are links
3. Link to pages, categories, or anything?
4. jQuery (WP’s?)

Searching for a WP plugin…

1. Super Slider: MooTools based.
2. BySlideMenu:  MooTools, horizontal, images.
3. Accordion Image Menu: MooTools, images, with “lightbox” effect.
4. Tabbed Widgets: jQuery UI. Messed with it for quite a while — unintuitive. Makes “tabs” of other widgets in the widget area, but…

… Nevermind

Can’t find a simple, usable plugin.I mean, there’s Accordion Menu, which only works with the Pages widget (hardcoded to li.widget_pages), limited to three levels, and the code looks convoluted. Foo?

But this ought to be trivial to hack with jQuery:

1. Add a listener on clicks to list items;
2. Collapse everything initially (ie, on document ready);
3. Toggle visibility when clicked;
4. Use WP’s jQuery; make sure it’s inserted when the menu is rendered.

Implementation

The DOM we expect:

li#nav_menu-3.widget_nav_menu
   .menu-navigation-container
      ul#menu-navigation.menu
         li#menu-item-14.menu-item
            a "Foo"
            ul.sub-menu
               li#menu-item-10.menu-item
                  a "Bar"

Algorithm for the event handler is now apparent: if the clicked anchor is followed by an unordered list sibling, toggle that UL’s visibility:

function() {
	var sub = jQuery(this).next("ul");
	if (!sub.length)
		return true; //??? Is it necessary?
	if (sub.is(":hidden"))
		sub.slideDown();
	else
		sub.slideUp();
	return false;
}

Now apply this handler to anchors in the menu:

jQuery('ul#menu-navigation > li.menu-item > a').click(…);

and run all this on document ready.

Oh, and collapse them initially:

jQuery('ul#menu-navigation > li.menu-item > ul.sub-menu').hide();

Stupid (useless) error message, ugly (complicated, inconsistent) code, horrible (noisy, and worse) programming language, and… why does it take forever to fix this silly problem? Countless threads, frustrated users, over years. Why? How does this happen? What should be done to prevent/improve this?

Notes towards…