More bug fixes. Thanks to everyone!
* Fixed bug where date, author, etc didn’t get set.
* Fixed bug where Postie was treating attached images as strings
* Fixed bug where inline images were not being attached correctly
* Fixed bug where the subject was not being decoded correctly if the charset was different from the system charset
* Fixed bug where base64 strings were being double decoded.
the post type is not being set in 1.4.9 – unless I am making a mistake I should be able to start the subject with Image// and the post format should be image, but it is still coming out as standard.
Thanks for the help.
Looks like there is come case sensitivity going on here. I’ll fix that in the next release.
Sorry, just to clarify. Is there something I can change in my email post or should I wait for the next release.
Make sure your post type name matches exactly what is WordPress.
Just updated to 1.4.9 and photos are no longer attached as “image” custom feild.
Thanks for the report. I’ll look into this.
I noticed another issue with setting Custom Post Type in the email subject. (I’m not sure if this cropped up in this version or a previous one.) The problem is that
$subjectneeds to be
trim()‘ed to remove leading and trailing whitespace after the Custom Post Type and Delimiter have been removed.
For example, when I use “Custom Post Type // My Post Title” in the email subject, the post title ends up having an extra space in front of it when it gets published.
Thanks. I’ve fixed a couple things with post types for the next release. This will be one of them!
Another thing related to the email subject that I just noticed, this time NOT using Custom Post Types in the subject line: When I sent an email with the subject “This is a Test Email by Raam Dev: Flow in order to grow”, only the “Flow in order to grow” was posted as the Post Title.
Why is it stripping everything before the colon in the Subject?
The colon is a category separator, so it is trying to use “Email by Raam Dev” as a category. I’ll update Postie to not remove the text if it isn’t a valid category.
Here’s another issue that I’m discovering (if you prefer I open new threads for any new issues, let me know). With ‘Settings -> Postie -> Message -> Preferred Text Type = HTML’, the following behavior is what I’ve observed Postie reporting when testing with various types of emails (manually pressing “Run Postie” from the settings screen):
Sending a Plaintext-only email, Postie reports “primary= text, secondary = plain”
Sending an HTML-only email, Postie reports “primary= text, secondary = html”
Sending a Plaintext + HTML email, Posite reports “primary= multipart, secondary = alternative”
Since “Preferred Text Type = HTML”, shouldn’t the HTML-only email set the primary text type to HTML instead of text? Or am I misunderstanding something about what Postie is reporting?
Wayne, one question is it possible to set a code or somehow that postie makes an auto feature image? ..or is it possible and I have miss this somewhere in the documentation ?
The image custom field bug was fixed in 1.4.10
When you are talking about custom post type (using // in subject) is that the same as post format?
I am trying to make a post with an Image post_format. For some reason it does not use the default post_format which is set to Image, but postie uses the Standard.
I can start a new thread if you would like.
- The topic ‘1.4.9 Released’ is closed to new replies.