WordPress updates

Each time you login to your WordPress site you should check for updates and install them if there are any.

In general there are two types of updates. WordPress updates which include WordPress its self along with theme updates. The second type of updates and the ones you will see most often are plugin updates. WordPress will notify you when updates are available for both of these categories of updates when you log into the Dashboard of your site.

WordPress notifies you that updates are available by putting a red dot with the number of updates to be installed next to the Updates menu item which is in the Dashboard menu. Also WordPress notifies you when plugin updates are available by putting a red dot with the number of updates to be installed next to the Plugins menu item.

Wordpress updates

Each time you log in your WordPress site and updates are available to be installed you should follow the steps below to install the updates. Because Plugin updates are the most common updates you will see I will start with those.

  1. Plugin updates.
    1. Log in to the Dashboard of your site.
    2. If there is a read dot with a number of available updates go to Plugins> Installed plugins>
      1. Then towards the top of the Plugins page click on Update available. The page will change to show you only the available updates.
        1. Then select the checkbox at the top of the table of available updates next to the title plugin to select all of the available plugins.
        2. Next from the Bulk Actions dropdown list select the Update item.
          1. NOTE Be very careful to only select the Update item because if you select the wrong item you could Deactivate or worse Delete your plugins.
        3. Click the apply button and wait while WordPress downloads and installs the plugin updates for you. WordPress will show you the progress by updating the screen for you.
    3. When all plugin updates are installed you can continue with what you were doing.
  1. WordPress and WordPress theme updates.
    1. Log in to the Dashboard of your site.
    2. If there is a read dot with a number of available updates go to Dashboard> Updates>
      1. There are three sections where updates could be available on this screen.
        1. WordPress
          1. When a new version of WordPress is available you can chose from install now or download. Chose install now
        2. Plugins
          1. When there are plugins available to be updated you will see a list of available plugins. Select the ones you want to update (usually all) and click the install plugins button.
        3. Themes
          1. When a new version of your WordPress theme is available select the checkbox next to your theme and click the update theme button
    3. When everythig is up to date you can continue with what you were doing.

I hope this is helpful.

How to change the ‘Enter title here’ text in WordPress dynamically.

I am using the Pods Framework to developing a Content Management System (CMS) for a client. With Pods Framework plugin installed in WordPress, it’s possible to create Custom Content Types and Custom Fields. Usually this involves writing the PHP that you need by hand. With Pods, you can create all of the Custom Content Types and Custom Fields that you need from within the Pods plugin.

While developing the CMS I ran into a small issue. WordPress automatically displays ‘Enter title here’ text in the title field of any Post or Custom Content Types. When you create a new Post or Custom Content Type Pods does not correct this text to suit the Custom Content Type. Which is fine when the new Post is a Post. However lets say you are creating a CMS for a site storing customer information and the title field is being used for the Customers name then the ‘Enter title here’ is less useful and could be confusing to some.

Enter title hereI searched the internet looking for a solution to this problem. There were several approaches but where they all fell down was that they relied on a if/then statement for each Post, Page, or Custom Content Type. Which in its self is not a problem however every time you add a new Custom Content Type you have to add a new if/then statement. What I wanted was the replacement text to be created dynamically so that the function worked in all cases. So I wrote a function that will do exactly that.

Add New Customer HereThe best part is all you have to do is copy the text below and past it in to the functions.php file of your child theme and it is done. From then on the ‘Enter title here’ text will be dynamically replaced through WordPress with something like ‘Add New Customer Here’

Functions.php
function change_default_title( $title ){
     global $post;
     $enter_title_text = esc_html( get_admin_page_title() ).’ Here’;
     return $enter_title_text;
}
 
add_filter( ‘enter_title_here’, ‘change_default_title’ );

Have your Jetpack and use Better WP Security too

Jetpack header logoRecently I started using Jetpack for amongst other things the Publicize feature. Publicize
automatically share your site’s posts on a range of social media networks when you publish a new post. The time this saves makes Jetpack a worth while plugin on its own. Not to mention all of the other features you get when you install Jetpack.

Jetpack PublicizeAfter I installed and configured Jetpack to connect to wordpress.com and Publicize to my social media sites I published a Post and sure enough a post was sent to my social media sites. The next post which was after an update of Jetpack was not so successful. The post on my blog was fine but no publicization of my article to my social media sites. So commenced the reading, reading, reading, reading, reading, reading…

Then I came across the Jetpack Troubleshooting Tips page which states;

Jetpack Troubleshooting Tips
3. Check your XMLRPC file. You can do this by going to your web site URL and adding “/xmlrpc.php” to the end (without the quotes). When it loads in your browser, you should see “XML-RPC server accepts POST requests only.” on a line by itself.

If you see this message, but it is not on a line by itself, a theme or plugin is displaying extra characters when it shouldn’t. See points 1 and 2 above for debugging steps.If you get an 404 Error Not Found message, contact your web host. They may have security in place that is blocking XMLRPC.

4. Check the Known Issues list and make sure you aren’t using a plugin or theme listed there.

I ran the test for my self. I simply went to my home page and added “/xmlrpc.php” to the end of the URL in the address bar of my browser window (without the quotes) and sure enough I got a 404 error page, not the “XML-RPC server accepts POST requests only.” on a line by itself. So I clicked the Known Issues list link and the words Better WP Security immediately jumped off the page because I have the Better WP Security plugin installed. The Known Issues page states;

Known Issues
Known Issues
WordFence, Better WP Security, Login Security Solution

These plugins block access to your site’s XML-RPC file. This file is used by Jetpack to connect to WordPress.com, and must be accessible at all times. You will consequently need to deactivate these plugins to be able to use Jetpack.

My first thought was “I am not going to deactivate a plugin that provides the amount of security that Better WP Security provides with out first running some tests”. I then went over to my wordpress dashboard and the Better WP Security plugin and had a good look around. I had not had a look at the Better WP Security plugin for a while and did not remember all of its features.

Better WP Security - Various Security TweaksQuite quickly I found what I was looking for on the Tweaks screen which ststes;

Remove EditURI header
Remove EditURI header

Removes the RSD (Really Simple Discovery) header. If you don’t integrate your blog with external XML-RPC services such as Flickr then the “RSD” function is pretty much useless to you.

Warning: This feature is known to cause conflicts with some 3rd party application and services that may want to interact with WordPress.

Better WP Security Header TweaksI uncheck the checkbox and clicked Save Changes. Then I ran the “/xmlrpc.php” test again. This time it was successful I got “XML-RPC server accepts POST requests only.” on a line by itself.

Now to test if my posts are once again being published on social media networks I will post this Article but if it does not work I will continue searching for the answer and post it here as an addition to this post.

Update wordpress – WP Maintenance Mode – Internal Server Error – solution

The problem

After updating your WordPress and/or WP Maintenance Mode plugin your site is running normally for a period of time eg between 6 and 18 hours. Then at some random time all that any visitor is able to see is an Internal Server Error message. To anyone trying to get to your site, your site appears to be broken. For more information open the section on Server Side Errors in my article, Where to find Apache response codes and how to determine their meaning.

Internal server error, Update wordpress, WordPress, WP Maintenance Mode, Maintenance Mode, Maintenance, Mode, Internal Server Error, site, broken site, Plugins, Plugin, Support

Corrupt .htaccess file and Internal Server Error

Ok So you are working on your wordpress site. Making changes and updating your site when all of a sudden you get…

Internal Server Error

Internal Server Error

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.
Apache/2.2.18 (Ubuntu) Server at www.yoursite.com Port 80

Before the panic sets in go to your .htaccess file and check that all is as it should be. For example when this happened to me last time this is what my file looked like.

Corrupt .htaccess

# BEGIN # BEGIN Wo<IfModul<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ – [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfM# END W
# END WordPress

notice the first and second last lines

# BEGIN # BEGIN Wo<IfModul<IfModule mod_rewrite.c>

</IfM# END W

well this means that during the last save your .htaccess file has become corrupt. There are a plethora of reasons why the .htaccess can become corrupt for example the .htaccess above was corrupted when my internet connection dropped out for a few seconds while the file was being written.

So how to fix this problem. You could try correcting the problem lines. If you know what the correct lines should look like. If you don’t know what the corrupted lines should look like you can delete the corrupted .htaccess file all together. Then in the wordpress dashboard open either a post or a page and save it, you don’t even need to make any changes and your .htaccess file will be re written. Simple huh?

Ultimate TinyMCE Switching between the visual and html editor

As seen on the wordpress forum…

Posted by allanit

Hi

When I switch between the visual and html editor the layout of the code in html editor goes to one line of code. If I switch back to the visual editor and then back to the html editor the layout is corrected.

Posted by Josh

I haven’t heard of this issue before. You might want to try the typical plugin routine to make sure it is not a plugin conflict.

Posted by allanit

Hi Josh

Turning off all the other plugins made this problem intermittent 🙁 Sorry I know this makes it worse.

AllanIT

Posted by Josh

Lol… yes, it does 😉

Let’s see…

Other than the options you have set for the buttons group one and the buttons group 2… go ahead and make sure all other options are NOT selected. This includes the options in the admin settings and the miscellaneous features.

Perhaps one of those options in the settings panel is interfering??

Posted by allanit

Hi Josh

I finally found time today to address the problem at the beginning of this thread. But something in the last two updates has fixed the problem in the Pages editor but not in the Posts editor.

AllanIT

Posted by josh

Hello Allan,

Okay. Let’s knock this out!

Can you post a link to a screenshot of the two instances you describe. One of the code in the pages… and another of the code in the posts.

Let me visually see what’s going on, and it should help.

Thanks.

Posted by allanit

Hi Josh
Here is the link to the two screen shots.

An image of the WordPress HTML editor displaying incorrectly.

An image of the WordPress HTML editor displaying correctly.

A beginners guide to writing SEO compliant keyword rich articles.

Over the past several months I have been reading as many articles on Search Engine Optimisation (SEO) as I could get my hands on. There are many differing opinions out there on the best way to achieve good SEO. I am going to share my most important findings in this article.

Writing rich content will improve your SEO.

The most important SEO strategy that I found was either not in most of the articles or, in a list of 10 things to improve your SEO was at number 6 to 8 and barely rated a mention. Very few articles cover any aspect of writing the content of your post or page so that it is SEO compliant and keyword rich. Without good content the rest of the SEO is useless or leads to people taking up bad practices to attempt to achieve their desired SEO outcome.

Write for human readers.

When writing the content for your web pages or blog posts, just cover one or two related subjects in an article. Too many topics will confuse your readers. Keep your writing to the point and try not to stray off on some tangent. Write your page or post for a human reader and not for what you think a search engine is looking for in SEO because you will probably be wrong. Try to present your concepts simply so that you will appeal to a larger readership. You never know who is reading your work.

Many of the articles I read spoke about the importance of making your articles keyword rich on the one hand and how, if you are stuffing your pages and posts with too many keywords, your page ranking (PR) would likely fall on the other. My advice would be to forget about search engine optimisation altogether while you are writing your articles.

Write your post or page for the content, as thought you need to pass on information to someone who is on the other side of the planet and their only way of communicating with you is through the information you put on your website. Which in most cases is the truth.

Hone and polish your work.

Whether you are writing content for a page or a post, always write in a wordprocessor and run both spellchecker and grammar checker on your work regularly. Not all grammar checker suggestions will be relevant, however  grammar checker can help you to polish your article. Don’t be in a rush to write and post your article. Spend a bit of time honing your content so that it is informative. Remember, you want to provide the other person enough information to get your point across. Also, don’t make your article so long that no one would ever finish it. Give your article a good clear conclusion. Don’t just trail off leaving your reader feeling like they have missed the point.

When you have an article that you are happy with read it out aloud to yourself. You will be surprised at how many minor mistakes you will pick up when you are reading your posts aloud. Then ask someone whose opinion you trust to proof-read your article, not just to read your writing but to read it with a critical eye, and to make suggestions that will improve your work.  Consider their suggestions carefully and include any changes that improve your article.

Editing for human readability.

After you have finished your article and edited it several times, go over your work again. This time you are looking for words like “it, they, those” that you can change to more descriptive words. Change pronouns for nouns wherever you are able to and you will be on the way to improving your SEO. Be sure that the changes you make are improving the human readability of your work and not just for the sake of adding better keywords to your article. Search engines will know the difference. Never add keywords that are not relevant to your article just because you think they will improve your SEO.

Setting up a wordpress installation ready for the inevitable upgrade.

All websites have to be updated from time to time. If you read the documentation they tell you to install wordpress in the root directory, which is fine if you are never going to change anything. On the other hand you should be planning for the future.

Start off by creating a folder in the root directory of your hosting package. The name of the directory is irrelevant so choose something that suits you. One word of warning, most will tell you to use something like wordpress. I, on the other hand, would use something else because you can only use it once. Choose something that when you update you can use the next one in the sequence. EG: “January”, “February” or “wordpress_2012”, “wordpress_2013”.

This directory is where you are going to install your wordpress. By setting up your wordpress in this way, in the future when you want to reconfigure your site, all you will have to do is create another folder (the next in the sequence) and install a separate wordpress in the new folder. While you are working on your site or new site you will be able to access it with the following url  http://yoursite.com.au/yourfolder/wp-login.php. Of course you will replace yoursite.com.au with the url of your site and yourfolder with either of the folders your sites are in, depending which on which site you want to login to.

When you are ready to go live with your new site you will only have to change one line in the existing index.php in your root directory and update the .htaccess file and your new site will be live.

Below are the full instructions how to set up your site in this way.

1.    Download and install the latest version of WordPress in a new directory on your web host plan. Eg: “yourfolder_2012”

2.    Add or edit your robots.txt file in your root directory and block access to your new folder because while you are in the setup phase you don’t want search engines to crawl your site.

a.    Add the following to your robots.txt file with each item on its own line.

i.    User-agent: *

ii.    Disallow: /yourfolder/

3.     Log in to your dashboard and install the Maintenance Mode plugin

a.    Search for “maintenance mode” in the plugin installer in your new wordpress site

i.    WordPress> Plugins> Add New>

ii.    Configure the maintenance mode plugin to block access to your new site.

b.    Go to Maintenance Mode settings

i.    Plugins> WP Maintenance Mode> Settings>

ii.    Change Plugin Activate to “true”

iii.    You can set any of the other features you want at the same time.

4.    Each time you want to add content to your new site you will be able to go to

a.    http://yoursite.com.au and click the link and login on the next screen or go directly to

b.    http://yoursite.com.au/yourfolder/wp-login.php and login.

5.    Add your content and code to your site

a.    Test your site, make sure every thing is working the way you want it to.

i.    When everything is working, and not before, move on to the next section.

ii.    Remember test, test, test and test again.

[Plugin: Ultimate TinyMCE] Table layout breaks with image. As on wordpress forum

From AllanIT

Hi Guys

This is a bit complicated to explain so I will tell you the steps to create the problem and see if others can recreate it and help to fix it.

1. Create a page
2. In Ultimate TinyMCE create a table 8 colums by 20 rows
3. Select colum 6 and 7 in row 4 down to row 10 so you have a box 2 colums by 7 rows
4. Then from the tables dropdown menu select merge cells.
5. Place an image 300w x 600h in the merge cells.
6. Then in row 4 select colum 1 to 4 and merge the cells
7. Repeat step 6. For rows 6, 8 and 10.
8. In row 4 colum 1 which now spans 4 colums put one word eg TinyMCE and give the merged cells a background color.
9. Then in rows 6, 8 and 10 add a paragraph of text so that in total you have more text than the image is high.
10. Then save the page and view the page in a browser.

If you get the same problem in the browser row 4 will match the height of the image. Strange huh? Any one know how to stop this from happening?

AllanIT

 

From Josh Lobe

Okay, I tried to replicate this… and aside from feeling like I was playing a tetris video game… I was unable to see what you are describing.

Perhaps you can link to a screenshot where I can see what you mean?

Update Services – ping lists.

In my travels around the web I have found several ping lists that others use to notify of new posts on their blog. So I have been compiling a list that could be useful for others it includes the recommended ping list for WordPress.

Another must have ping tool you should have in your arsenal is to register with http://feedshark.brainbliss.com/ which will send out pings, RSS and podcasts.

Click the show button on the ping list below then select the entire list and copy it. Then got to your Dashboard > Setting > writing and scroll to the bottom of the page where you will find a description for Update Services. In the box below that description past the list then click the save changes button. Then the next time you post an article WordPress will automatically ping all of the address in the list.

Wordpress writing settings, wordpress, ping lists, site, trafic,

Ping List
http://www.a2b.cc/setloc/bp.a2b
http://1470.net/api/ping
http://a2b.cc/setloc/bp.a2b
http://api.feedster.com/ping
http://api.moreover.com/ping
http://api.moreover.com/RPC2
http://api.my.yahoo.co.jp/RPC2
http://api.my.yahoo.com/ping
http://api.my.yahoo.com/RPC2
http://api.my.yahoo.com/rss/ping
http://audiorpc.weblogs.com/RPC2
http://bblog.com/ping.php
http://bitacoles.net/notificacio.php
http://bitacoles.net/ping.php
http://bitacoras.net/ping
http://blo.gs/ping.php
http://blog.goo.ne.jp
http://blog.goo.ne.jp/XMLRPC
http://blogbot.dk/io/xml-rpc.php
http://blogdb.jp
http://blogdb.jp/xmlrpc
http://blogdigger.com/RPC2
http://blogmatcher.com/u.php
http://blogoole.com/ping/
http://blogoon.net/ping/
http://blogpeople.net/ping
http://blogroots.com/tb_populi.blog?id=1
http://blogsearch.google.ae/ping/RPC2
http://blogsearch.google.at/ping/RPC2
http://blogsearch.google.be/ping/RPC2
http://blogsearch.google.bg/ping/RPC2
http://blogsearch.google.ca/ping/RPC2
http://blogsearch.google.ch/ping/RPC2
http://blogsearch.google.cl/ping/RPC2
http://blogsearch.google.co.cr/ping/RPC2
http://blogsearch.google.co.hu/ping/RPC2
http://blogsearch.google.co.id/ping/RPC2
http://blogsearch.google.co.il/ping/RPC2
http://blogsearch.google.co.in/ping/RPC2
http://blogsearch.google.co.it/ping/RPC2
http://blogsearch.google.co.jp/ping/RPC2
http://blogsearch.google.co.ma/ping/RPC2
http://blogsearch.google.co.nz/ping/RPC2
http://blogsearch.google.co.th/ping/RPC2
http://blogsearch.google.co.uk/ping/RPC2
http://blogsearch.google.co.ve/ping/RPC2
http://blogsearch.google.co.za/ping/RPC2
http://blogsearch.google.com.ar/ping/RPC2
http://blogsearch.google.com.au/ping/RPC2
http://blogsearch.google.com.br/ping/RPC2
http://blogsearch.google.com.co/ping/RPC2
http://blogsearch.google.com.do/ping/RPC2
http://blogsearch.google.com.mx/ping/RPC2
http://blogsearch.google.com.my/ping/RPC2
http://blogsearch.google.com.pe/ping/RPC2
http://blogsearch.google.com.sa/ping/RPC2
http://blogsearch.google.com.sg/ping/RPC2
http://blogsearch.google.com.tr/ping/RPC2
http://blogsearch.google.com.tw/ping/RPC2
http://blogsearch.google.com.ua/ping/RPC2
http://blogsearch.google.com.uy/ping/RPC2
http://blogsearch.google.com.vn/ping/RPC2
http://blogsearch.google.com/ping/RPC2
http://blogsearch.google.es/ping/RPC2
http://blogsearch.google.fr/ping/RPC2
http://blogsearch.google.gr/ping/RPC2
http://blogsearch.google.hr/ping/RPC2
http://blogsearch.google.ie/ping/RPC2
http://blogsearch.google.in/ping/RPC2
http://blogsearch.google.it/ping/RPC2
http://blogsearch.google.jp/ping/RPC2
http://blogsearch.google.lt/ping/RPC2
http://blogsearch.google.nl/ping/RPC2
http://blogsearch.google.pl/ping/RPC2
http://blogsearch.google.pt/ping/RPC2
http://blogsearch.google.ro/ping/RPC2
http://blogsearch.google.ru/ping/RPC2
http://blogsearch.google.se/ping/RPC2
http://blogsearch.google.sk/ping/RPC2
http://blogsearch.google.tw/ping/RPC2
http://blogsearch.google.us/ping/RPC2
http://blogshares.com/rpc.php
http://blogsnow.com/ping
http://blogstreet.com/xrbin/xmlrpc.cgi
http://blogupdate.org/ping/
http://bulkfeeds.net
http://bulkfeeds.net/rpc
http://bulkfeeds.net/rpc
http://catapings.com/ping.php
http://coreblog.org/ping
http://effbot.org/rpc/ping.cgi
http://feedsky.com/api/RPC2
http://fgiasson.com/pings/ping.php
http://geourl.org/ping
http://hamo-search.com/ping.php
http://holycowdude.com/rpc/ping/
http://imblogs.net/ping/
http://ipings.com
http://lasermemory.com/lsrpc/
http://mod-pubsub.org
http://mod-pubsub.org/kn_apps/blogchatt
http://mod-pubsub.org/knapps/blogchatt
http://mod-pubsub.org/ping.php
http://newsblog.jungleboots.org/ping.php
http://newsisfree.com/RPCCloud
http://packetmonster.net/xmlrpc.php
http://ping.amagle.com
http://ping.bitacoras.com
http://ping.blo.gs/
http://ping.blogg.de/
http://ping.bloggers.jp/rpc
http://ping.blogoon.net/
http://ping.blogs.yandex.ru/RPC2
http://ping.cocolog-nifty.com/xmlrpc
http://ping.exblog.jp/xmlrpc
http://ping.fakapster.com/rpc
http://ping.fc2.com/
http://ping.feedburner.com
http://ping.feeds.yahoo.com/RPC2/
http://ping.kutsulog.net/
http://ping.myblog.jp
http://ping.namaan.net/rpc
http://ping.rootblog.com/rpc.php
http://ping.snap.com/ping/RPC2
http://ping.syndic8.com/xmlrpc.php
http://ping.weblogalot.com/rpc.php
http://ping.weblogs.se
http://ping.wordblog.de/
http://pinger.blogflux.com/rpc
http://pingoat.com/
http://pingoat.com/goat/RPC2
http://pingqueue.com/rpc/
http://popdex.com/addsite.php
http://r.hatena.ne.jp/rpc
http://rcs.datashed.net
http://rcs.datashed.net/RPC2
http://rpc.blogbuzzmachine.com/RPC2
http://rpc.bloggerei.de/ping/
http://rpc.blogrolling.com/pinger/
http://rpc.britblog.com/
http://rpc.icerocket.com:10080
http://rpc.newsgator.com/
http://rpc.pingomatic.com/
http://rpc.reader.livedoor.com/ping
http://rpc.tailrank.com/feedburner/RPC2
http://rpc.technorati.com/rpc/ping
http://rpc.twingly.com
http://rpc.weblogs.com/RPC2
http://rpc.wpkeys.com
http://services.newsgator.com/ngws/xmlrpcping.aspx
http://signup.alerts.msn.com/alerts-PREP/submitPingExtended.doz
http://snipsnap.org/RPC2
http://syndic8.com/xmlrpc.php
http://thingamablog.sourceforge.net/ping.php
http://topicexchange.com
http://topicexchange.com/RPC2
http://trackback.bakeinu.jp/bakeping.php
http://wasalive.com/ping/
http://weblogues.com/ping/
http://weblogues.com/RPC/
http://www.a2b.cc
http://www.a2b.cc/setloc/bp.a2b
http://www.bitacoles.net/ping.php
http://www.blogdigger.com/RPC2
http://www.bloglines.com/ping
http://www.blogoole.com/ping/
http://www.blogoon.net/ping
http://www.blogpeople.net
http://www.blogpeople.net/servlet/weblogUpdates
http://www.blogroots.com
http://www.blogroots.com/tb_populi.blog?id=1
http://www.blogroots.com/tbpopuli.blog?id=1
http://www.blogsdominicanos.com/ping/
http://www.blogshares.com/rpc.php
http://www.blogsnow.com/ping
http://www.blogstreet.com/xrbin/xmlrpc.cgi
http://www.catapings.com/ping.php
http://www.feedsky.com/api/RPC2
http://www.feedsubmitter.com
http://www.holycowdude.com/rpc/ping/
http://www.imblogs.net/ping/
http://www.lasermemory.com
http://www.lasermemory.com/lsrpc
http://www.mod-pubsub.org/kn_apps/blogchatter/ping.php
http://www.mod-pubsub.org/knapps/blogchatter/ping.php
http://www.mod-pubsub.org/ping.php
http://www.newsisfree.com/RPCCloud
http://www.newsisfree.com/xmlrpctest.php
http://www.octora.com/add_rss.php
http://www.pingerati.net
http://www.pingmyblog.com
http://www.popdex.com
http://www.popdex.com/addsite.php
http://www.snipsnap.org
http://www.snipsnap.org/RPC2
http://www.wasalive.com/ping/
http://www.weblogalot.com/ping
http://www.weblogues.com
http://www.weblogues.com/RPC
http://www.xianguo.com/xmlrpc/ping.php
http://www.zhuaxia.com/rpc/server.php
http://xmlrpc.blogg.de
http://xping.pubsub.com/ping
http://zhuaxia.com/rpc/server.php
http://zing.zingfast.com

 

Be warned however if you ping to often on one day you could be marked as spam.

Good luck bloging
AllanIT