Since installing your new version, the custom field "Teaser" and the function "Disable," as set in the Advanced editing screen in WP 3.0.1, no longer functions for articles that use that command.
Can you look at this?
Peace,
Gene Steinberg
Since installing your new version, the custom field "Teaser" and the function "Disable," as set in the Advanced editing screen in WP 3.0.1, no longer functions for articles that use that command.
Can you look at this?
Peace,
Gene Steinberg
Hi genesteinberg,
Did you try to reset your settings in Post Teaser Settings page to default and configure Post Teaser from scratch?
There are some new options introduced in this version that could cause problem if not added to the settings. Unfortunately, I've not figure out how to automatically add those upon upgrade so, that steps is manual for the time being.
I did. The Teaser disable function is till not working.
Peace,
Gene
Hi genesteinberg,
I've found the problem that causes the failure to pickup the post Custom Field. Watch for the next release going out today.
Thanks for reporting the problem but please use the contact form to report bugs. I check that email a lot more frequent then the forum. Sometimes at length of months.
Thanks.
--Han.
It seems to work now. Thanks.
I've tried reaching plugin authors here and via their Contact Form, and more often than not, get no responses. I appreciate your follow-up.
Peace,
Gene
You are welcome.
I do have one more request, and maybe it does it now.
Can you configure this so that, when you click the "Continue" or "More" button, it jumps right to continuing point of the post rather than go back to the beginning?
If this can be done now, please tell me how.
Peace,
Gene
Not currently. It will be considered in future releases. However, due to the complex nature of keeping track of where the post was break and marking it with the # bookmark, it will not happened until the earliest on next major revision. Furthermore, because the way Post Teaser handles the break, some parts of Post Teaser will need to be redesigned in a major way to support this feature.
Sorry.
This topic has been closed to new replies.