Support Forum
Support Forum
Offline
Hi guys, I was getting Failed Post Data Validation errors in the Toolbox/Email Post Log, and tracked it down to the validateData() function. Specifically, it fails on the No topic post has been entered and post cannot be saved branch of logic.
Strange that $this->newpost['postcontent'] would be empty, I thought, so traced it back to $content.
When I logged the $content of the email/post, it was clearly a Base64-encoded message. So I'm not 100% sure this is the root of the issue, since possibly the software is actually getting a different part of a multipart MIME message and using that, but thought I would ask if you've seen this. Any further guidance you can give me for what to check next?
Thanks!
Offline
One of the main concerns with this plugin is the large disparity and non-standard nature of email clients so let's start by asking what client you are using and is that using the php imap or pop code?
 |
YELLOW
SWORDFISH
|
Offline
Outlook 2010 is the client. PBE is using the IMAP code.
Offline
Oh dear... I am going to have to check here if anyone has access to that and can try it out. I don't have it available myself. So - will need to run some tests I am afraid.
|
YELLOW
SWORDFISH
|
Offline
I have it working now. I will post the code soon (I have a ton of error logging in there from trying to figure out what was happening that I need to clean up first).
Do you guys use Github by chance for your source control? Just thinking this would be a perfect scenario for me to issue a pull request and then you guys could review my changes, and, if acceptable of course, merge them into your master branch at your leisure.
Anyway, the long and short of it is that the content-transfer-encoding parameter is rather important. 
And it may appear on the primary body part of the message, or if the primary body type is multipart, then you have to pick up the encoding from the TEXT/HTML part (since the code is fetching the body specifically from the 1.2 HTML part).
It will make more sense when you see the code, I am sure. Thanks!
Offline
No we do not use Github - we run our own svn server.
I am intrigued and eager to discover what you came up with. I did find this morning that one of my colleagues has been testing with OutLook - but the previous version - with what appeared to be success. I must also say that most of the code handling the gritty bits are actually modelled from either the WP post original or other third party apps.so this was quite a big learning curve for us.
Please do share. actually just sending a copy of your code file to 'support at simple-press dot com' would be great - I can run compares easily enough...
|
YELLOW
SWORDFISH
|
Offline
I spent a bit of time cleaning up the code (and then retesting) to decompose the nested logic a bit...just to prevent my shooting myself in the foot later with that code, and also to make it more aesthetically pleasing for my own personal satisfaction.
I sent it to you at the above given address--let me know if you don't get it and I'll get it to you somehow.
Thanks!
Offline
it was received... Andy was unavailable today so will look at it tomorrow...
Visit Cruise Talk Central and Mr Papa's World
All RSS1 Guest(s)