Custom sort order?

Or, alternately, we might preface with a different character instead of the tilde.. for example – we might use a bullet char ” ? ” instead – would that work?

I just tried “? “ – which didn’t work.
I also tried “ ~“ (with a leading space), and also “ ~” – unfortunately neither idea worked.
The leading space is automatically deleted, and the “&nbsp:” appears at the bottom of the list as an “&”.

• This reply was modified 6 years, 3 months ago by algerpixel.
• This reply was modified 6 years, 3 months ago by algerpixel.
• This reply was modified 6 years, 3 months ago by algerpixel.

Hmmm… interesting

Try this. About line 585 find:

foreach( $groups as $letter => $tags ) {

and add above it:

$groups = array('~' => $groups['~']) + $groups;

like so:

$groups = array('~' => $groups['~']) + $groups;
foreach( $groups as $letter => $tags ) { 

note: this is specifically looking for the ~ and this does not change the order of the show_navigation (you’re not using it anyway)

@tugbucket,

Thanks, that worked.
However, I am concerned that should I download any future updates to the plugin, this code will be overwritten.

I am using a child theme however – do you know how to properly place a copy of the mctagmap_functions.php into a child theme – so these mods will not be lost?

I know how to do this with files living at the theme root, but as this is outside the theme I am not certain how (or even if) this can be done.

Any thoughts?

@algerpixel

First off, thank you for reading the instructions and providing code and screenshots ??

I finally got around to adding the option to store the multi-column-tag-map folder in the child theme. So you can now do: /yourChildTheme/multi-column-tag-map/mctagmap_function.php and edit away.

For the record though, you could modify the mctagmap_function.php in the parent and when updating the parent, it would still be there unless the theme developer did something crazy where on update, wipe the theme and re-download it rather than update.

But as this addition didn’t really take a lot of work to incorporate into the code, I did just that.

See v15.0.2 and the new options of force_first and force_first_nav for an explanation.

Wonderful! Thanks for doing this.
The child theme addition works perfectly; and although I have not yet tested the “force_first” or “force_first_nav” params I really appreciate your prompt attention to such details. This is a great plugin – there’s actually nothing else quite like it.