Image Posts Fail
-
I am trying to crosspost something that is not just a regular post (those work fine, with just send excerpts) but if you want the actual image to upload, it has been instructed to use the IMAGE post type and I have and it keeps generating this error and never works, thoughts?
I am posting the message with debug enabled:
Crossposting to Tumblr failed. Remote service said:Response code: 400Response message: Bad Request Debug output:object(stdClass)#1092 (2) { [“meta”]=> object(stdClass)#1094 (2) { [“status”]=> int(400) [“msg”]=> string(11) “Bad Request” } [“response”]=> object(stdClass)#1096 (1) { [“errors”]=> array(1) { [0]=> string(22) “Error uploading photo.” } } } Unfortunately, I have no idea what Tumblr is talking about. Consider asking Tumblr Support for help. Tell them you are using Tumblr Crosspostr, that you got the error shown above, and ask them to please support this tool. ‘Cause, y’know, it’s not like you don’t already have a WordPress blog, and don’t they want you to use Tumblr, too?
-
Tumblr is reporting “Error uploading photo.” This could mean:
- The post you are uploading to is not a Photo post type. This is possible if you’ve saved a draft of the post with a different post format on WordPress before changing the post format to Image. In this case, you’ll need to either delete the post from WordPress (which will delete it from Tumblr) and recreate it with the Image post format, or else remove Tumblr Crosspostr’s
tumblr_crosspostr_tumblr_post_id
custom field from the WP post and then re-save it (which will create a new post on Tumblr). - Tumblr cannot access the image you are using. This can happen if the image you are trying to upload is not available to anonymous visitors (which would include the Tumblr API) on the public internet. This is a limitation of the way Tumblr Crosspostr currently works and a fix is in development but not ready yet.
- The image data itself is corrupt. This might happen if you are uploading the image to your WP account but there was an error in the upload process. In this case, you should delete the image from the WP media library and re-upload it.
Unfortunately, Tumblr’s not very clear on what the error was, exactly, so it’s hard to know more without seeing the HTTP conversation. You can see the HTTP conversation by accessing your WP site’s
debug.log
file as described in the Tumblr Crosspostr settings screen.Hope this helps.
Thank you for getting back to me maymay ?? and I hope you are having a blast on whatever you are working on right now.
#1 No, this is a fresh post, no drafts, image format, I made sure of it and no go, gives this error every time.
#2 I am not sure why, since the image is part of a blog post that is openly visible, cacheable, downloadable, and linkable, and currently despite my better judgement, I have no hotlinking rules active, so unless it is somehow getting the wrong path/to/file from the plugin, it should see it, anyone can.
#3 The images all successfully upload, display in the post on the blog just fine and I have now tried it with 4 separate images (first: 640×480 – second: 800×600 – third: 1024×748 – fourth: 1920×1920) to make sure size and so on wasn’t the issue. Didn’t work. I tried the first one as JPG/100, second one as PNG, third one as GIF and last one is JPG/90. All failed.
I can upload to them directly from tumblr without issue, same pics, and even using the direct link to upload them, so that’s what’s got me scratching my head. Could crosspost maybe encoding the image data badly? or not constructing the request quite right? I don’t know, that’s why I am asking you. Advice? Suggestions?
I can upload to them directly from tumblr without issue, same pics, and even using the direct link to upload them, so that’s what’s got me scratching my head. Could crosspost maybe encoding the image data badly? or not constructing the request quite right? I don’t know, that’s why I am asking you. Advice? Suggestions?
Yeah, that’s odd. Sorry, I’d have to see the HTTP conversation to give any more advice. Post or send me that and I’ll have a look.
Can you tell me what relevant information you need and where/how I can get them for you? I would be happy to provide it, but not quite sure where to look EXACTLY, but I will start poking around while if you get a chance, get back to me and let me know how and where from so I can give you the most useful information, not guess work.
I did, in my first reply:
You can see the HTTP conversation by accessing your WP site’s
debug.log
file as described in the Tumblr Crosspostr settings screen.Right, but that doesn’t just exist, you have to make changes to the installation to enable DEBUGGING to gather that information, its not like it just exists, so that’s why I asked – there is scalpel method and machete method, this seems to err on the side of the machete, anyway, I will make the changes that seem a bit drastic to debug a plugin that should really have a more robust internal debugger than rely on the WHOLE SITE to go into debug mode so you can see why its not working. Just a thought for future debugging. Especially that when the ENTIRE site is in debug mode, you get EVERYTHING, so not just your plugin’s behavior, and that’s just excessive. I’ll post it shortly.
Well there is an obscene amount of log information relating to this plugin and what is even more overwhelming is that all these hundreds of requests made by the plugin for ONE SINGLE POST REQUEST and it makes it look like its posting thousands of stuff, why so damn chatty for a single request, especially that it fails to actually post it.
Anyway, here it is, I had to remove thousands of lines from the log or it would be impossible to manage, now what? ?? I don’t see how to send it to you without having to post it here, there is no PM or email system to get to you and the form on your site to contact you is just too silly and not suited for this kind of thing, so here it is:
[17-Apr-2016 20:00:08 UTC] OAuth client: Accessing the API call at https://api.tumblr.com/v2/user/info [17-Apr-2016 20:00:08 UTC] Connecting to api.tumblr.com [17-Apr-2016 20:00:08 UTC] Resolving HTTP server domain "api.tumblr.com"... [17-Apr-2016 20:00:08 UTC] Connecting to HTTP server IP 66.6.43.23 port 80... [17-Apr-2016 20:00:08 UTC] Connected to api.tumblr.com [17-Apr-2016 20:00:08 UTC] C GET /v2/user/info HTTP/1.1 [17-Apr-2016 20:00:08 UTC] C Host: api.tumblr.com [17-Apr-2016 20:00:08 UTC] C User-Agent: PHP-OAuth-API (https://www.phpclasses.org/oauth-api $Revision: 1.143 $) [17-Apr-2016 20:00:08 UTC] C Accept: */* [17-Apr-2016 20:00:08 UTC] C Authorization: OAuth oauth_consumer_key="redacted",oauth_nonce="redacted",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1460923208",oauth_version="1.0",oauth_token="redacted",oauth_signature="redacted%3D" [17-Apr-2016 20:00:08 UTC] C Connection: Keep-Alive [17-Apr-2016 20:00:08 UTC] C [17-Apr-2016 20:00:09 UTC] S HTTP/1.1 200 OK [17-Apr-2016 20:00:09 UTC] S Server: nginx [17-Apr-2016 20:00:09 UTC] S Date: Sun, 17 Apr 2016 20:00:09 GMT [17-Apr-2016 20:00:09 UTC] S Content-Type: application/json; charset=utf-8 [17-Apr-2016 20:00:09 UTC] S Transfer-Encoding: chunked [17-Apr-2016 20:00:09 UTC] S Connection: keep-alive [17-Apr-2016 20:00:09 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:00:09 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:00:09 UTC] S Set-Cookie: tmgioct=5713eb48d6fcd60441991600; expires=Wed, 15-Apr-2026 20:00:08 GMT; Max-Age=315360000; path=/; httponly [17-Apr-2016 20:00:09 UTC] S P3P: CP="Tumblr's privacy policy is available here: https://www.tumblr.com/policy/en/privacy" [17-Apr-2016 20:00:09 UTC] S X-UA-Compatible: IE=Edge,chrome=1 [17-Apr-2016 20:00:09 UTC] S [17-Apr-2016 20:00:09 UTC] S 2f8 [17-Apr-2016 20:00:09 UTC] S {"meta":{"status":200,"msg":"OK"},"response":{"user":{"name":"redacted","likes":0,"following":6,"default_post_format":"html","blogs":[{"title":"G\u00b5\u00e5r\u00d0\u00ef\u00e5\u00f1","name":"redacted","total_posts":182,"posts":182,"url":"http:\/\/redacted.tumblr.com\/","updated":1460920077,"description":"","is_nsfw":false,"ask":true,"ask_page_title":"Ask me anything","ask_anon":false,"followed":false,"can_send_fan_mail":true,"is_blocked_from_primary":false,"share_likes":false,"twitter_enabled":false,"twitter_send":false,"facebook_opengraph_enabled":"N","tweet":"N","facebook":"N","followers":2,"primary":true,"admin":true,"messages":0,"queue":0,"drafts":0,"type":"public","reply_conditions":2,"subscribed":false,"can_subscribe":false}]}}} [17-Apr-2016 20:00:09 UTC] S 0 [17-Apr-2016 20:00:09 UTC] S [17-Apr-2016 20:00:09 UTC] Keeping the connection alive to api.tumblr.com [17-Apr-2016 20:00:10 UTC] OAuth client: Accessing the API call at https://api.tumblr.com/v2/user/info [17-Apr-2016 20:00:10 UTC] Connecting to api.tumblr.com [17-Apr-2016 20:00:10 UTC] Resolving HTTP server domain "api.tumblr.com"... [17-Apr-2016 20:00:10 UTC] Connecting to HTTP server IP 66.6.42.23 port 80... [17-Apr-2016 20:00:10 UTC] Connected to api.tumblr.com [17-Apr-2016 20:00:10 UTC] C GET /v2/user/info HTTP/1.1 [17-Apr-2016 20:00:10 UTC] C Host: api.tumblr.com [17-Apr-2016 20:00:10 UTC] C User-Agent: PHP-OAuth-API (https://www.phpclasses.org/oauth-api $Revision: 1.143 $) [17-Apr-2016 20:00:10 UTC] C Accept: */* [17-Apr-2016 20:00:10 UTC] C Authorization: OAuth oauth_consumer_key="redacted",oauth_nonce="redacted",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1460923210",oauth_version="1.0",oauth_token="redacted",oauth_signature="redacted3D" [17-Apr-2016 20:00:10 UTC] C Connection: Keep-Alive [17-Apr-2016 20:00:10 UTC] C [17-Apr-2016 20:00:10 UTC] S HTTP/1.1 200 OK [17-Apr-2016 20:00:10 UTC] S Server: nginx [17-Apr-2016 20:00:10 UTC] S Date: Sun, 17 Apr 2016 20:00:10 GMT [17-Apr-2016 20:00:10 UTC] S Content-Type: application/json; charset=utf-8 [17-Apr-2016 20:00:10 UTC] S Transfer-Encoding: chunked [17-Apr-2016 20:00:10 UTC] S Connection: keep-alive [17-Apr-2016 20:00:10 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:00:10 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:00:10 UTC] S Set-Cookie: tmgioct=5713eb4ac847110703116330; expires=Wed, 15-Apr-2026 20:00:10 GMT; Max-Age=315360000; path=/; httponly [17-Apr-2016 20:00:10 UTC] S P3P: CP="Tumblr's privacy policy is available here: https://www.tumblr.com/policy/en/privacy" [17-Apr-2016 20:00:10 UTC] S X-UA-Compatible: IE=Edge,chrome=1 [17-Apr-2016 20:00:10 UTC] S [17-Apr-2016 20:00:10 UTC] S 2f8 [17-Apr-2016 20:00:10 UTC] S {"meta":{"status":200,"msg":"OK"},"response":{"user":{"name":"redacted","likes":0,"following":6,"default_post_format":"html","blogs":[{"title":"G\u00b5\u00e5r\u00d0\u00ef\u00e5\u00f1","name":"redacted","total_posts":182,"posts":182,"url":"http:\/\/redacted.tumblr.com\/","updated":1460920077,"description":"","is_nsfw":false,"ask":true,"ask_page_title":"Ask me anything","ask_anon":false,"followed":false,"can_send_fan_mail":true,"is_blocked_from_primary":false,"share_likes":false,"twitter_enabled":false,"twitter_send":false,"facebook_opengraph_enabled":"N","tweet":"N","facebook":"N","followers":2,"primary":true,"admin":true,"messages":0,"queue":0,"drafts":0,"type":"public","reply_conditions":2,"subscribed":false,"can_subscribe":false}]}}} [ HUNDREDS OF THE SAME BLOCK WITH ONLY DIFFERENCE BEING THE AUTH CODES OTHER THAN PERSONAL/SECRET AND ALL THIS FOR ONE SINGLE POST REQUEST, ITS INSANE ] [17-Apr-2016 20:03:57 UTC] OAuth client: Accessing the API call at https://api.tumblr.com/v2/user/info [17-Apr-2016 20:03:57 UTC] Connecting to api.tumblr.com [17-Apr-2016 20:03:57 UTC] Resolving HTTP server domain "api.tumblr.com"... [17-Apr-2016 20:03:57 UTC] Connecting to HTTP server IP 66.6.42.23 port 80... [17-Apr-2016 20:03:57 UTC] Connected to api.tumblr.com [17-Apr-2016 20:03:57 UTC] C GET /v2/user/info HTTP/1.1 [17-Apr-2016 20:03:57 UTC] C Host: api.tumblr.com [17-Apr-2016 20:03:57 UTC] C User-Agent: PHP-OAuth-API (https://www.phpclasses.org/oauth-api $Revision: 1.143 $) [17-Apr-2016 20:03:57 UTC] C Accept: */* [17-Apr-2016 20:03:57 UTC] C Authorization: OAuth oauth_consumer_key="redacted",oauth_nonce="e5dafc77bad742bf9cb835534b4a1dd3",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1460923437",oauth_version="1.0",oauth_token="redacted",oauth_signature="DJxhgefZnns62QuWzhI6UuG4SHI%3D" [17-Apr-2016 20:03:57 UTC] C Connection: Keep-Alive [17-Apr-2016 20:03:57 UTC] C [17-Apr-2016 20:03:58 UTC] S HTTP/1.1 200 OK [17-Apr-2016 20:03:58 UTC] S Server: nginx [17-Apr-2016 20:03:58 UTC] S Date: Sun, 17 Apr 2016 20:03:58 GMT [17-Apr-2016 20:03:58 UTC] S Content-Type: application/json; charset=utf-8 [17-Apr-2016 20:03:58 UTC] S Transfer-Encoding: chunked [17-Apr-2016 20:03:58 UTC] S Connection: keep-alive [17-Apr-2016 20:03:58 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:03:58 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:03:58 UTC] S Set-Cookie: tmgioct=5713ec2e0e28200525218960; expires=Wed, 15-Apr-2026 20:03:58 GMT; Max-Age=315360000; path=/; httponly [17-Apr-2016 20:03:58 UTC] S P3P: CP="Tumblr's privacy policy is available here: https://www.tumblr.com/policy/en/privacy" [17-Apr-2016 20:03:58 UTC] S X-UA-Compatible: IE=Edge,chrome=1 [17-Apr-2016 20:03:58 UTC] S [17-Apr-2016 20:03:58 UTC] S 2f8 [17-Apr-2016 20:03:58 UTC] S {"meta":{"status":200,"msg":"OK"},"response":{"user":{"name":"redacted","likes":0,"following":6,"default_post_format":"html","blogs":[{"title":"G\u00b5\u00e5r\u00d0\u00ef\u00e5\u00f1","name":"redacted","total_posts":182,"posts":182,"url":"http:\/\/redacted.tumblr.com\/","updated":1460920077,"description":"","is_nsfw":false,"ask":true,"ask_page_title":"Ask me anything","ask_anon":false,"followed":false,"can_send_fan_mail":true,"is_blocked_from_primary":false,"share_likes":false,"twitter_enabled":false,"twitter_send":false,"facebook_opengraph_enabled":"N","tweet":"N","facebook":"N","followers":2,"primary":true,"admin":true,"messages":0,"queue":0,"drafts":0,"type":"public","reply_conditions":2,"subscribed":false,"can_subscribe":false}]}}} [17-Apr-2016 20:03:58 UTC] S 0 [17-Apr-2016 20:03:58 UTC] S [17-Apr-2016 20:03:58 UTC] Keeping the connection alive to api.tumblr.com [17-Apr-2016 20:03:59 UTC] OAuth client: Accessing the API call at https://api.tumblr.com/v2/user/info [17-Apr-2016 20:03:59 UTC] Connecting to api.tumblr.com [17-Apr-2016 20:03:59 UTC] Resolving HTTP server domain "api.tumblr.com"... [17-Apr-2016 20:03:59 UTC] Connecting to HTTP server IP 66.6.43.23 port 80... [17-Apr-2016 20:03:59 UTC] Connected to api.tumblr.com [17-Apr-2016 20:03:59 UTC] C GET /v2/user/info HTTP/1.1 [17-Apr-2016 20:03:59 UTC] C Host: api.tumblr.com [17-Apr-2016 20:03:59 UTC] C User-Agent: PHP-OAuth-API (https://www.phpclasses.org/oauth-api $Revision: 1.143 $) [17-Apr-2016 20:03:59 UTC] C Accept: */* [17-Apr-2016 20:03:59 UTC] C Authorization: OAuth oauth_consumer_key="redacted",oauth_nonce="redacted",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1460923439",oauth_version="1.0",oauth_token="redacted",oauth_signature="redacted%3D" [17-Apr-2016 20:03:59 UTC] C Connection: Keep-Alive [17-Apr-2016 20:03:59 UTC] C [17-Apr-2016 20:04:00 UTC] S HTTP/1.1 200 OK [17-Apr-2016 20:04:00 UTC] S Server: nginx [17-Apr-2016 20:04:00 UTC] S Date: Sun, 17 Apr 2016 20:04:00 GMT [17-Apr-2016 20:04:00 UTC] S Content-Type: application/json; charset=utf-8 [17-Apr-2016 20:04:00 UTC] S Transfer-Encoding: chunked [17-Apr-2016 20:04:00 UTC] S Connection: keep-alive [17-Apr-2016 20:04:00 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:04:00 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:04:00 UTC] S Set-Cookie: tmgioct=5713ec3003e5750300802370; expires=Wed, 15-Apr-2026 20:04:00 GMT; Max-Age=315360000; path=/; httponly [17-Apr-2016 20:04:00 UTC] S P3P: CP="Tumblr's privacy policy is available here: https://www.tumblr.com/policy/en/privacy" [17-Apr-2016 20:04:00 UTC] S X-UA-Compatible: IE=Edge,chrome=1 [17-Apr-2016 20:04:00 UTC] S [17-Apr-2016 20:04:00 UTC] S 2f8 [17-Apr-2016 20:04:00 UTC] S {"meta":{"status":200,"msg":"OK"},"response":{"user":{"name":"redacted","likes":0,"following":6,"default_post_format":"html","blogs":[{"title":"G\u00b5\u00e5r\u00d0\u00ef\u00e5\u00f1","name":"redacted","total_posts":182,"posts":182,"url":"http:\/\/redacted.tumblr.com\/","updated":1460920077,"description":"","is_nsfw":false,"ask":true,"ask_page_title":"Ask me anything","ask_anon":false,"followed":false,"can_send_fan_mail":true,"is_blocked_from_primary":false,"share_likes":false,"twitter_enabled":false,"twitter_send":false,"facebook_opengraph_enabled":"N","tweet":"N","facebook":"N","followers":2,"primary":true,"admin":true,"messages":0,"queue":0,"drafts":0,"type":"public","reply_conditions":2,"subscribed":false,"can_subscribe":false}]}}} [17-Apr-2016 20:04:00 UTC] S 0 [17-Apr-2016 20:04:00 UTC] S [17-Apr-2016 20:04:00 UTC] Keeping the connection alive to api.tumblr.com [17-Apr-2016 20:04:01 UTC] OAuth client: Accessing the API call at https://api.tumblr.com/v2/user/info [17-Apr-2016 20:04:01 UTC] Connecting to api.tumblr.com [17-Apr-2016 20:04:01 UTC] Resolving HTTP server domain "api.tumblr.com"... [17-Apr-2016 20:04:01 UTC] Connecting to HTTP server IP 66.6.43.23 port 80... [17-Apr-2016 20:04:01 UTC] Connected to api.tumblr.com [17-Apr-2016 20:04:01 UTC] C GET /v2/user/info HTTP/1.1 [17-Apr-2016 20:04:01 UTC] C Host: api.tumblr.com [17-Apr-2016 20:04:01 UTC] C User-Agent: PHP-OAuth-API (https://www.phpclasses.org/oauth-api $Revision: 1.143 $) [17-Apr-2016 20:04:01 UTC] C Accept: */* [17-Apr-2016 20:04:01 UTC] C Authorization: OAuth oauth_consumer_key="redacted",oauth_nonce="redacted",oauth_signature_method="HMAC-SHA1",oauth_timestamp="1460923441",oauth_version="1.0",oauth_token="redacted",oauth_signature="redacted%3D" [17-Apr-2016 20:04:01 UTC] C Connection: Keep-Alive [17-Apr-2016 20:04:01 UTC] C [17-Apr-2016 20:04:02 UTC] S HTTP/1.1 200 OK [17-Apr-2016 20:04:02 UTC] S Server: nginx [17-Apr-2016 20:04:02 UTC] S Date: Sun, 17 Apr 2016 20:04:02 GMT [17-Apr-2016 20:04:02 UTC] S Content-Type: application/json; charset=utf-8 [17-Apr-2016 20:04:02 UTC] S Transfer-Encoding: chunked [17-Apr-2016 20:04:02 UTC] S Connection: keep-alive [17-Apr-2016 20:04:02 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:04:02 UTC] S Vary: Accept-Encoding [17-Apr-2016 20:04:02 UTC] S Set-Cookie: tmgioct=5713ec31e0b0290180983370; expires=Wed, 15-Apr-2026 20:04:01 GMT; Max-Age=315360000; path=/; httponly [17-Apr-2016 20:04:02 UTC] S P3P: CP="Tumblr's privacy policy is available here: https://www.tumblr.com/policy/en/privacy" [17-Apr-2016 20:04:02 UTC] S X-UA-Compatible: IE=Edge,chrome=1 [17-Apr-2016 20:04:02 UTC] S [17-Apr-2016 20:04:02 UTC] S 2f8 [17-Apr-2016 20:04:02 UTC] S {"meta":{"status":200,"msg":"OK"},"response":{"user":{"name":"redacted","likes":0,"following":6,"default_post_format":"html","blogs":[{"title":"G\u00b5\u00e5r\u00d0\u00ef\u00e5\u00f1","name":"redacted","total_posts":182,"posts":182,"url":"http:\/\/redacted.tumblr.com\/","updated":1460920077,"description":"","is_nsfw":false,"ask":true,"ask_page_title":"Ask me anything","ask_anon":false,"followed":false,"can_send_fan_mail":true,"is_blocked_from_primary":false,"share_likes":false,"twitter_enabled":false,"twitter_send":false,"facebook_opengraph_enabled":"N","tweet":"N","facebook":"N","followers":2,"primary":true,"admin":true,"messages":0,"queue":0,"drafts":0,"type":"public","reply_conditions":2,"subscribed":false,"can_subscribe":false}]}}} [ KEEPS REPEATING THE SAME BLOCK OVER AND OVER - JUST ONE CROSSPOST REQUEST - ITS AN OBSCENE AMOUNT OF CHATTER FOR A FAIL ON A SINGLE POST REQUEST ]
The snipet you posted does not include any crosspost request. I.e., it does not include the portion of an HTTP conversation where Tumblr Crosspostr tries to send a post from your blog to Tumblr.
That’s all that was there, there is nothing else making tumblr requests on my site, so what now? The debug was collecting before, during, and after the attempt to crosspost and these were all that was there, I just deleted a bunch of lines because they were redundant.
I just deleted a bunch of lines because they were redundant.
If you tried to crosspost an image and received the error you first posted about, then there should have been an attempt to
POST
that image to Tumblr in the debug log. I believe you simply overlooked it. It’s easy to do.How about this, I will do it again and this time will make multiple attempts. I will upload it in the morning.
That sounds just fine, I don’t really care…?
Let me be clear about something. I’m trying to determine if there is a legit bug in the software I wrote. I only care because I’m curious and I generally like making things that work as I expect them to work. This is free software, not a product you purchased. I have no obligation to support you or this software. If it becomes too much of a hassle for me to communicate with you about whether or not the software is flawed, either because I feel annoyed, bored, or simply lose interest and choose to spend my time on any of my other projects rather than on this particular piece of software, then I will simply stop interacting with you.
How about that?
Well while I understand why you take that stand, I am familiar with your work but it conflicts with your ethos that is presented in your sign about being helpful, the least of which is expected with something you have created and put out there, free or not. Afterall, if it was working then I wouldn’t need your attention, time or input, right? If it helps you to pretend you didn’t make this plugin, you have zero responsibility then let’s pretend you are the helpful hacker you say you are and are providing free help with a problem because someone asked you. How about that? ??
So back to what we are doing here, I am baffled as hell because I ran the debug log again and again and used crosspost again and again and again and yet there isn’t a single reference in the log to anything it SHOULD be doing that should show up other than what I posted before, which doesn’t show up since I disabled another plugin. So I don’t know why there is nothing being logged about your plugin here, are you sure its providing debug information properly to the core to be collected? Because there is NOTHING there about this plugin, even when it posts regular posts successfully using the excerpt method, even those don’t show up in the logs at all. Not a single line. I would consider that a legitimate bug, no?
So what can I do?
Sorry, I can’t replicate that problem. The debug log shows the expected HTTP conversation every time I try it.
I’m going to pretend I didn’t hear the rest of your insulting, obscenely entitled comment.
What was insulting and obscene about my comment? That was not even remotely the intention or even the motivation, I think you read too much into it based on preconceived notions and whatever is running through your own thoughts. I think your goal is more to sound like you don’t care and be a “i do what i want when i want and damn everyone else” might be causing you to miss or misinterpret things.
Anyway, let’s keep philosophy and personal emotional quirks out of this and just both focus on the tech instead. I ran the debug AGAIN this morning and when I clicked post, something interesting happened this time, I got this output on the screen and the POST after didn’t update like it normally would to show you the interface post publish.
Notice: add_object_page is deprecated since version 4.5! Use add_menu_page() instead. in /wp-includes/functions.php on line 3662
Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3662) in /wp-admin/post.php on line 197
Warning: Cannot modify header information – headers already sent by (output started at /wp-includes/functions.php:3662) in /wp-includes/pluggable.php on line 1171
Could the complaint about the headers being sent already the reason why its not working? or seeing anything in the logs? Maybe because it never completed the request since maybe it didn’t get it off before the headers were sent and so in its mind, nothing happened to report? I don’t know, I am just thinking out loud to try and see if I can get this resolved.
In the meantime, if I go back to the main page, it will show the post was made on WP side of the installation and a notice is hanging around the top, although for some reason it is multiplied and appears like 4 times but says the same thing. For IMAGE posts, it failed no reason given, For regular posts using the send excerpt, it works fine.
Suggestions? Thoughts? Directions? I am trying to provide all the information you asked for, but its JUST NOT IN THE LOGS. Nothing about this plugins actions show up in the logs, and I am not sure why, because I suppose that if you are saying to look there, you have made sure they would appear in there, but maybe something about how its done is not registering it in time with the system? Especially that the post action is not completing all the way through with DEBUG active (core not your plugin, that’s already been set on) so I am thinking that somehow the “break” in rendering all the way through might be the cause? But what is causing it to just stop dead in its tracks though. Even with errors and notices you would expect it to go all the way through, just complain about it, right? But not what’s happening.
- The post you are uploading to is not a Photo post type. This is possible if you’ve saved a draft of the post with a different post format on WordPress before changing the post format to Image. In this case, you’ll need to either delete the post from WordPress (which will delete it from Tumblr) and recreate it with the Image post format, or else remove Tumblr Crosspostr’s
- The topic ‘Image Posts Fail’ is closed to new replies.