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:
<!--more--> to force a split.<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:
Follow the below steps until you have determine the incompatibility with PostTeaser:
Describe the problem as detail as you can and note the steps you have taken in this diagnostic in your report to me. Remember to also include as much information as possible of your environment in your report. E.g. WordPress version, PostTeaser version, hosting type, and etc.
The teaser text is placed inside a block level <div> element with a class of "post-teaser". 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 { font-weight: bold; }
You have two options here:
Both of them work by using a custom field for you post. Here's how to do it:
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:
NOTICE: Please hold off all translation effort until further notice. The PostTeaser admin page is now under heavy remodeling for the newer WordPress compatibility as well as adding new options and restructuring for simpler translation effort. When the new admin page is released it is definitely going to break all the translation files new and old.
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!




