There is still no way to use Markdown and WLW together.

What is missing is a way to keep line breaks when using Source mode in WLW.

This is a test post.

I am going to save it as a Draft first, and then, after a while, publish it.

This is a test article for seeing how various HTML elements are styled by WordPress themes. It uses all elements available in the basic view of the WordPress edit screen, plus a few more that are useful for web content, especially headings of two levels: h2 and h3.

Let’s start!

After the introductory paragraph and an h2 heading comes an image. It’s a resized image that links to its full-size original, and that has a short sample caption:

This is the caption of the image.

Inline elements

Now comes a simple list that demonstrates how various inline elements are styled:

• This is an emphasized phrase (using em)
• This is a phrase displayed in strong type (using strong)
• This is a deleted phrase (using del)
• This is a linked phrase

Quotes

Next are two lines from Hamlet enclosed in blockquote:

There are more things in heaven and earth, Horatio,
Than are dreamt of in your philosophy.

Lists

Time to see how lists are styled…

Ordered and unordered lists, mixed and nested

Lists (ordered or unordered) are easy to get right. Nested lists, however, often reveal problems in the styling, usually by uneven and illogical vertical spacing.

• First item in an unordered list (ul)
• Second item in an unordered list
  1. Here starts an orderd list (ol), nested in the unordered list
  2. Second item of ordered list
  3. Third item of orderd list
     • Going one level deep, to start an unordered list
     • Second item of nested ordered list
  4. Back to the the ordered list of the previous level
• Back to the top-level
• Last item of the top-level unordered list

Definition lists

Next is a definition list. Definition lists are a useful device for web content but are not available in the WordPress content editor. Maybe that’s why some themes ignore them or, even worse, reset the default browser styling and then leave definition lists completely unstyled. (Horror!)

Apple

Pomaceous fruit of plants of the genus Malus in the family Rosaceae.

An american computer company.

Orange

The fruit of an evergreen tree of the genus Citrus.

Peach

Species of Prunus native to China that bears an edible juicy fruit also called a peach.

An especially pleasing person or thing.

Preformatted text

A piece of code wrapped in pre:

#include <iostream>

int main()
{
   std::cout << "Hello, world!\n";
}

Tables

And, after an horizontal rule (hr), our simple sample post reaches its end!

Cheers!

Credits

• Green Layers photograph by nospuds

The latest dev. version of WordPress (currently heading towards 2.9 Beta 2) is what op109.net uses. With it, the 32MB of memory available to the site were often not enough to do a plugin upgrade. Each time, to get the upgrade to finish successfully, I had to deactivate either one of the five active plugins, or the translation (I use op109.net to test the Greek L10n of WordPress).

What the comparison showed:

The numbers

I tried each of WordPress 2.7, 2.8, and 2.9 Beta 1 with and without the Greek translation and with three different themes: Default, Simplish, and Thematic. In each case only one (1) plugin was active: WP Memory Usage. The numbers in parentheses show the memory usage when the translation was active.

Environment info

SERVER

• Linux 2.6.18
• CentOS 5 64bit
• Apache 2.2.13
• PHP 5.2.11
• MySQL 5.0.81

WORDPRESS, THEMES, AND L10N FILES

• WordPress 2.9 beta 1 (r12290 from trunk)
• WordPress 2.8 (r11552 from trunk)
• WordPress 2.7 (r10188 from trunk)
• Default theme 2.9 beta 1 (r12290 from trunk)
• Simplish theme 2.2.2
• Thematic theme 0.9.6 β 06 (r571 from trunk)
• Greek L10n 2.9 beta 1 98% complete (r10450 from trunk)

HOSTING

A Small Orange, Tiny Orange shared-hosting package

TOOLS

The RAM numbers are from the WP Memory Usage plugin by Alex Rabe:

wordpress.org/extend/plugins/wp-memory-usage

Method and other notes

For this comparison I downgraded op109.net via SVN from the latest WordPress trunk (r12290) to WordPress 2.8, then to WordPress 2.7. Then I upgraded again to WordPress 2.8 and finally to the latest trunk (r12290).

I repeated these four steps twice; that is, two runs in total. The numbers in the table are the averages. (MB values varied from 0.00 to 0.09 between the two runs.)

After each downgrade/upgrade WordPress asked me to “upgrade” the database. Interestingly, all eight database “upgrades” went OK and everytime everything seemed to work OK down to WordPress 2.7 (including the themes Simplish and Thematic, which were at their very latest versions, and also a few plugins I tried).

Quick conclusion

See the table! :-) Also, 64bit operating systems eat a lot of memory – but we already knew that. :-D

2009-11-29

δκ
http://op111.net/