I went hunting for a plugin I’d seen that allowed custom buttons, and discovered that the standard installation of WordPress actually has a keyboard command that toggles some extra goodies off and on. Obviously, mine have all been off!

Turns out, you can Show/Hide the Advanced Editor Toolbar in the standard Wordpress installation and unlock a dozen or so extra buttons, including “Paste as Plain Text” and “Paste from Word”. When the Advanced Editor Toolbar is enabled, there is a toggle button available to turn it off. However, when it is off, you must use Alt-V (IE) or Shift-Alt-V (Firefox) to toggle the advanced buttons back “on”.

Adding Buttons is something I haven’t delved into yet. I need to play with this new toy first. But I learned from the Codex that under “Rich Editor Filters” in the Plugin_API/Hooks page, you can see a simple means of adding your own buttons to TinyMCE in WordPress.

http://codex.wordpress.org/Plugin_API/Filter_Reference#Rich_Text_Editor_Filters

Advanced Editing Plugins

If the Advanced Editing Toolbar buttons are not sufficient, perhaps you’re looking for a plugin to extend the functionality of the TinyMCE editor, or to add custom code snippets. Here are two you can try:

Custom TinyMCE Buttons (for WordPress 2.1)

Advanced TinyMCE Editor (for Wordpress 2.2)

It was the former that I recalled having seen, which started me on this quest, and the latter which I discovered in the process, and informed me of the advanced toggle option. Surprised that I had never heard of it in two years of hanging out on the WordPress forums, I personally added the information to the Codex. I also added links to these two amazing plugins, which I’m sure will come in handy for others.

This manifests itself in an unexpected (and probably unwanted) bullet before your list title (or a lone bullet alongside your first Page link, if you used the title_li=0 argument), and often by making the “bullet” for all subsequent Page links appear as something other than a bullet (in mine, it looks like this: >> ) because it’s reading them as sub-nested list items. What a mess!

Maybe this is convenient if you only use wp_list_pages inside of an existing ordered or unordered list, but I generally don’t….so I have been fighting this strange bullet problem for quite some time.

It may be possible for you to style away this problem by adding CSS classes for .pagenav and .page_item, but if that’s not working for you, then you might want to edit the function itself. Editing the core of WordPress isn’t generally recommended, but sometimes it becomes necessary.

Here are instructions for WordPress 2.1.3. Other versions are probably similar. Don’t forget to make a back up before you do this!!!

You’ll be changing this file:

/wp-includes/post_functions.php.

Locate “function wp_list_pages” (line 265 in my 2.1.3)

Look for the “if” statement and remove the opening and closing LI tags in the two lines that begin with ?output= (one of them includes class=pagenav), so it reads as follows:


if ( !empty($pages) ) {
    if ( $r['title_li'] )
      $output .= '' . $r['title_li'] . '<ul>';
 
    global $wp_query;
    if ( is_page() )
      $current_page = $wp_query->get_queried_object_id();
    $output .= walk_page_tree($pages, $r['depth'], $current_page, $r);
 
    if ( $r['title_li'] )
      $output .= '</ul>';
  }


When looking at the whole function, you’ll see you can also remove the page_item class for the inner nested LIs if you want, but you can also just not define that class in CSS and it won’t do anything.

The following instructions explain what to do, provided you are working with an Author Template file (author.php) per the instructions in the WordPress codex.

Your author.php file should begin looking something like this:

<?php get_header(); ?>
   <div id="content" class="narrowcolumn">
   
      <!-- This sets the $curauth variable -->
<?php
if(isset($_GET['author_name'])) :
$curauth = get_userdatabylogin($author_name);
else :
$curauth = get_userdata(intval($author));
endif;
?>

You have called the header, and you’ve set the $curauth variable. This is EXTREMELY important. Without the $curauth variable, the rest of these instructions will produce nothing.

Now, let’s say you have used Cimy User Extra Fields to create a field for the user’s favorite color, named (appropriately) “FAV_COLOR”. You want the author’s profile to display the author’s favorite color, which is “red”.

Once you have declared the $currauth variable, you can use it to retrieve the author’s ID, which is what the get_cimyFieldValue function needs to call (and display) the author’s favorite color outside the loop.

<?php $value = get_cimyFieldValue($curauth->ID, 'FAV_COLOR'); ?>
 
<?php echo $value; ?>

Note that $curath->ID replaces get_the_author_ID, because get_the_author_ID can only be used inside the Loop.

On the other hand, $curauth->ID can only be used in this example because the $curauth variable has been declared at the beginning of the file, and is now available for use in the rest of the template.

Once again, let me reiterate that you MUST have a working author.php file (with the $curauth variable declared at the outset) in order for this to function correctly.

Many thanks to Marco Cimmino developing Cimy User Extra Fields, and for his prompt and helpful support!!

• The very first thing I do is go to Users –> Authors & Users (default tab) and click “edit” for my new admin profile….and CHANGE THE PASSWORD. I will never remember the random one WordPress gives me. (If you installed WordPress with Fantastico, you chose your own password, so you can skip this step.)
• Next, I set privacy settings in Options –> Privacy. If I have a lot of set up to do and don’t want visitors yet, I will opt for a private blog for now. This prevents WordPress from pinging Update Services every time I make a test post.
• Another important step before you start posting is your Permalinks options (Options –> Permalinks). I prefer “pretty permalinks” and so do search engines. They look nicer, are more memorable to users, and can tell the search engines more about the content of your site than a link with ?p=4 in it. Be sure you have a file in your root (top level) WordPress directory (same place as index.php) named .htaccess (it can be completely blank, but it must exist) which is CHMOD 666, so that WordPress can update the file for you.
• If this site will allow comments, I enable the Akismet plugin to prevent comment spam. You’d be amazed at how fast spammers find new installations of WordPress and start spamming them.

Once these preliminary set up steps are completed, I install the theme, start adding plugins and making test posts. The plugins usually lead to theme modifications, so now the real fun begins.

You might indeed want search engines to find your blog — after you get it set up completely. But not knowing the real meaning of this option, you say “yes” to search engines, and unbeknownst to you, WordPress is now going to notify Ping-O-Matic every single time you make a post to your blog! Yes, even your test posts and that silly “Hello World!” post (if you edit or update it).

Personally, my first assumption would be that the question about search engines would insert or leave out robots.txt tags, create or modify the robots.txt file, or something of that nature — since the robots.txt file and tags are directly related to search engines, and keeping them out or letting them in.

As a new blogger, or even moreso as someone setting up a content management system, the concept behind Ping-O-Matic (and update services in general) may be completely unknown. And furthermore, it has nothing to do (at least not directly) with search engines. So asking this question, in this manner, at set up is misleading to say the least.

This question should read “Do you want to automatically inform Ping-O-Matic of new posts to your blog? (If you choose YES, your site may be indexed immediately, even your test posts. You can change this option later in Options –> Privacy.)” since that is exactly what your answer to the question will determine. It should also tell you (or present a link to find out more) about pinging, and the actual results of setting this option to YES.

If you don’t want your new blog (and any test posts you make) immediately crawled by Yahoo! and other search engines, then say NO to this option during set up, or turn it off as soon as you get into Admin for the first time, before you blog about anything…or even update (edit) the Hello World! test post.