Plugin Name

No, of course not, but it makes a nice addition and some people find it easier to skim over previews to find something that interests them rather than to scroll down huge chunks of text.

Post Teaser is a paragraph aware teaser. Not only just aware, it will not break in the middle of a paragraph unless explicitly told to do so with the <!--more--> tag. There are two reasons why Post Teaser seems to have failed to split a post:

1. The entire post is one long paragraph. Well, as stated, Post Teaser is a paragraph aware teaser. Therefore will split single paragraph post at the end of the post because it also happens to be where the first paragraph break. To fix this problem, either split the post into shorter paragraph or add a <!--more--> to force a split.
2. The post have multiple paragraph, however, instead of the <p> tag as the paragraph marker, the <br /> tag was used to simply make text appear like paragraph. It may read alright to us, those damn puters sees it as one long paragraph. Schematics, schematics. I tell you, it's a conspiracy! To fix this problem, replace those <br /> tags with the proper <p>...</p> paragraph marker pair.

This one is very common and applies to any WordPress plugin. There must not be any content in the plugin file other than PHP code. Sometimes if people have copied the code into their own file, rather than downloading it, they accidentally leave whitespace or other characters at the beginning or end of the file, outside of the <?php ... ?> block. Removing any excess characters will solve the problem.

PostTeaser is always tested against the latest WordPress version prior to release. However, it is impossible to test PostTeaser with all the plugins, widget, themes and what ever modification you have made for your blog. Most of the time when PostTeaser crashes a blog or causes some strange effects it is due to incompatibility in your environment (plugins, widget, themes, and etc). If you encounter some unexplained issue seemingly associated with PostTeaser, you are welcome to report it to me but to speed up the process of getting your issue resolved, please perform the following diagnostic steps to first determine what is the source of the problem. Prior to executing the diagnostic steps, please setup your environment so that you will start the diagnostic with basic configuration:

• Disable all your plugin, widget and change your theme to the default WordPress theme. Verify if the problem is gone. If you still have the problem, your problem is most likely your hosting environment. Check with your hosting provider to help solve your problem. Otherwise, continue the test.

1. Enable only PostTeaser and verify if the problem have come back. If the problem exist, it is either PostTeaser is not compatible with the current WordPress version or your hosting environment.
2. With only PostTeaser enabled, change your theme to your regular theme. If problem exist, PostTeaser and your theme is not compatible. Please check if your theme have any settings or scripts that will interfere with PostTeaser.
3. With only PostTeaser enabled, activate one other plugin at a time. Remember to only have PostTeaser and one other plugin activated at any one time. Verify that the problem exist. If you don't see the problem, repeat this step until you have found the plugin that is not compatible with PostTeaser or you have gone through all the plugin.
4. Do the same with widget as the step above except allow only PostTeaser and only one widget activated at any one time. Repeat until you have found the widget that is not compatible with PostTeaser or you have gone through all the widget.

The teaser text is placed inside a block level <div> element with a class of "post-teaser-block". This means that you can use CSS to style the teaser text. As an example, here's the CSS you'd use to make it bold: .post-teaser-block { font-weight: bold; } .post-teaser-more { font-weight: bold; }

You have two options here:

1. Have Post Teaser ignore that post entirely
2. Have Post Teaser "display the post in full", and display the message that it did so (like what happens if you have a post that is too short to be teased)

1. Edit/Write your post in the WordPress admin panel
2. If you are not in the "Advanced" mode, then get into it by clicking the "Advanced Editing" button
3. At the bottom of the form, where it says "Custom Fields", write 'teaser' in the box labelled "Key"
4. Next, go to the "Value" box, and write 'disable' if you want Post Teaser to ignore the post entirely, or 'showall' if you want Post Teaser to return the post in full
5. Click "Add Custom Field"

You can use the the filters under the "Advance tease control" section to control on which archive page Post Teaser will not tease.

• You can use any numbers of combination to setup these controls
• "Control tease in homepage" will take precedence over "Use filters to disable tease" and "Use filters to force fullpost", "Use filters to disable tease" will take precedence over "Use filters to force fullpost" and categories will take precedence over tags
• The category and tag text input box are free-text input box
• Post Teaser will accepts a comma separated list of categories or tags in any of the three forms:
• Category or tag name (the name where you use to create the category or tag)
• Category or tag id (the id use by WordPress to identify the category or tag in the db)
• Category or tag slug (the part of the url that identifies the category or tag e.g. http://www.example.com/category/uncategorized/) ** Note: The comma separated list you provide to Post Teaser can be any combination of the above**
• Archive pages of categories or tags configured in "Use filters to disable tease" will cause Post Teaser to ignore completely posts in their respective category or tag archive pages (Note that if <!--more--> is use in the post or the_excerpt is used in your theme, the post will be teased according to WordPress's post tease feature)
• Archive pages of categories or tags configured in "Use filters to force fullpost" will cause Post Teaser to display fullpost with post stats as configured in "Basic settings" in their respective category or tag archive pages
• The "Always apply filter" options, if set will cause Post Teaser's tease controls to take effect outside of their respective category or tag archive pages (e.g. in the home page if there are any post that is taged with a tag configured in "Use filters to disable tease", the "Always apply filter" option will cause Post Teaser to disabled tease among other post that will be tease as normal)

Yes. You just write <!--more--> where you want it to be teasered, in the "traditional" WordPress style, and Post Teaser will do the rest.

Absolutely. Please use the contact form on my website, and I will get back to you as soon as I can.

Yes. To use a translated version, you need to obtain the language file for it. At this point it would be useful to read Installing WordPress in Your Language from the Codex. You will need an .mo file for Post Teaser that corresponds with the "WPLANG" setting in your wp-config.php file. Translations are listed below -- if a translation for your language is available, all you need to do is place it in the wp-content/plugins directory of your WordPress installation. If one is not available, and you also speak good English, please consider doing a translation yourself (see the next question). The following translations are available:

• Belorussian
• Belorussian (by_BY)
• Dutch
• Belgium (nl_BE)
• Netherlands, The (nl_NL)
• English
• Great Britain (en_GB) -- This is the default language for Post Teaser
• French
• France (fr_FR)
• German
• Germany (de_DE)
• Greek
• Greek (el_GR)
• Hebrew
• Israel (he_IL)
• Italian
• Italy (it_IT)
• Norwegian
• Norway (nb_NO)
• Polish
• Poland (pl_PL)
• Russian
• Russian (ru_RU)
• Spanish
• Spain (es_ES)
• Swedish
• Sweden (sv_SE)
• European Union (sv_EU)

NOTICE: If you have translate for Post Teaser and have a couple of hours free, please help update the language files. Thanks. Of course! It will be very gratefully received. Please read Translating WordPress first for background information on translating. Then obtain the latest .pot file and translate it. There are some strings with a space in front -- please make sure you remember the space! When you have a translation ready, please send the .po and .mo files to han at sandboxblogger dot com. If you have any questions, feel free to email me also. Thanks!