WordPressHelp » moving http://wordpresshelp.org Making WordPress Even Easier to Use! Fri, 21 Jan 2011 03:45:35 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 DoFollow-NoFollow? http://wordpresshelp.org/2009/04/13/dofollow-nofollow/ http://wordpresshelp.org/2009/04/13/dofollow-nofollow/#comments Mon, 13 Apr 2009 14:25:02 +0000 admin http://wordpresshelp.org/?p=98 Yet Another Related Posts Plugin.]]>

In order to better understand the relative merits of from NoFollow to DoFollow, I have begun a test on this .

Basically I am using two new (for me) plugins.

The basic notion is that Lucia’s LinkLove allows for an automatic reset of the default NoFollow for comments to DoFollow, after pre-determined number (determined by me) of approved comments have been added by a given user to this site. The NoFollow Reciprocity module sets and/all comments to NoFollow if the receiveing site has their site set to NoFollow.

Hopefully this test will demonstrate an uptick in this site’s ratings and traffic without a significant additional burden in SPAM.  I’ll post the results of my test, as they become obvious.  If you have ideas of other plugins that I should add to this mix, please let me know.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

]]> http://wordpresshelp.org/2009/04/13/dofollow-nofollow/feed/ 1 Web Standards Checklist http://wordpresshelp.org/2008/03/02/web-standards-checklist/ http://wordpresshelp.org/2008/03/02/web-standards-checklist/#comments Sun, 02 Mar 2008 18:10:25 +0000 http://wordpresshelp.org/2008/03/02/web-standards-checklist/ Yet Another Related Posts Plugin.]]>

From the original article by:
Russ Weakley
13-August-04

– more than just ‘ table-free sites ‘

The term web standards can mean different things to different people. For some, it is ‘ table-free sites ‘, for others it is ‘ using valid code ‘. However, web standards are much broader than that. A built to web standards should adhere to standards (HTML, XHTML, XML, CSS, XSLT, DOM, MathML, SVG etc) and pursue best practices (valid code, accessible code, semantically correct code, user-friendly URLs etc).

In other words, a site built to web standards should ideally be lean, clean, -based, accessible, usable and search engine friendly .

About the checklist

This is not an uber-checklist. There are probably many items that could be added. More importantly, it should not be seen as a list of items that must be addressed on every site that you develop. It is simply a Guide that can be used:

  • to show the breadth of web standards
  • as a handy tool for developers during the production phase of websites
  • as an aid for developers who are interested in towards web standards

The checklist

  1. Quality of code
    1. Does the site use a correct Doctype?
    2. Does the site use a Character set?
    3. Does the site use Valid (X)HTML?
    4. Does the site use Valid CSS?
    5. Does the site use any CSS hacks?
    6. Does the site use unnecessary classes or ids?
    7. Is the code well structured?
    8. Does the site have any broken links?
    9. How does the site perform in terms of speed/page size?
    10. Does the site have JavaScript errors?
  2. Degree of separation between content and presentation
    1. Does the site use CSS for all presentation aspects (fonts, colour, padding, borders etc)?
    2. Are all decorative images in the CSS, or do they appear in the (X)HTML?
  3. Accessibility for users
    1. Are “alt” attributes used for all descriptive images?
    2. Does the site use relative units rather than absolute units for text size?
    3. Do any aspects of the layout break if font size is increased?
    4. Does the site use visible skip menus?
    5. Does the site use accessible forms?
    6. Does the site use accessible tables?
    7. Is there sufficient colour brightness/contrasts?
    8. Is colour alone used for critical information?
    9. Is there delayed responsiveness for dropdown menus (for users with reduced motor skills)?
    10. Are all links descriptive (for blind users)?
  4. Accessibility for devices
    1. Does the site work acceptably across modern and older browsers?
    2. Is the content accessible with CSS switched off or not supported?
    3. Is the content accessible with images switched off or not supported?
    4. Does the site work in text browsers such as Lynx?
    5. Does the site work well when printed?
    6. Does the site work well in Hand Held devices?
    7. Does the site include detailed metadata?
    8. Does the site work well in a range of browser window sizes?
  5. Basic Usability
    1. Is there a clear visual hierarchy?
    2. Are heading levels easy to distinguish?
    3. Is the site’s navigation easy to understand?
    4. Is the site’s navigation consistent?
    5. Does the site use consistent and appropriate language?
    6. Does the site have a sitemap page and contact page? Are they easy to find?
    7. For large sites, is there a search tool?
    8. Is there a link to the home page on every page in the site?
    9. Are links underlined?
    10. Are visited links clearly defined?
  6. Site management
    1. Does the site have a meaningful and helpful 404 error page that works from any depth in the site?
    2. Does the site use friendly URLs?
    3. Do your URLs work without “www”?
    4. Does the site have a favicon?

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

]]> http://wordpresshelp.org/2008/03/02/web-standards-checklist/feed/ 0 How to move a WordPress site http://wordpresshelp.org/2008/02/11/how-to-move-a-wordpress-site/ http://wordpresshelp.org/2008/02/11/how-to-move-a-wordpress-site/#comments Mon, 11 Feb 2008 10:43:57 +0000 http://wordpresshelp.org/?p=14 Yet Another Related Posts Plugin.]]>

This applies to the within your own webspace, or if you want to move it to another host server. I have read a few versions of how to this and many details have been missed that are important.

Notes

  1. When moving a site you have to consider if you have ever modified (hacked) any core files in

  2. If you have and you want to maintain the functionality you must copy these over to the new installation

  3. WordPress stores all user data in the wp-content folder and sub-directories and its database. This means all plugins, , images and other added fies will be in wp-content folder. NOTE. Some plugins DO put files elsewhere. Be aware!

  4. If your file mods/ hacks are in the wp-content folder then carry on as below.

  5. If you have hacked/modified files anywhere else, these must be copied over separately.

  6. If you have no special mods/hacks, simple ignore the above.

Preparation on the old site

  1. log into the original site as

  2. Deactivate all cache settings and cache plugins. Make sure all cache files are cleared/ deleted.

  3. If you have Askimet installed make sure you delete any spam comments in the moderation queue.

  4. Log in to the FTP account and copy the wp-content folder and config.php to your desktop.

  5. Copy any other files from other locations if they have been modified! (see notes above)

  6. Some plugins are poor at removing their database tables and configs from the database. Login to phpMyadmin and delete any tables that are no longer being used by your existing activated plugins.

  7. Now optimize your database using the cpanel or other utility

  8. Make a database backup, using cpanel, phpmyadmin, db backup, or some other utility.

No related posts.

Related posts brought to you by Yet Another Related Posts Plugin.

]]> http://wordpresshelp.org/2008/02/11/how-to-move-a-wordpress-site/feed/ 0