This answer basically breaks down the detective work done to uncover the issue as outlined by the initial question and could prove useful for further debugging/diagnosis if a similar issue appears in the future.ĮDIT: The larger content about image leeching seems invalid. The developer’s were notified and a fix appears to be in place. UPDATE: It seems the core issue with images not loading stemmed from the way the EFF’s HTTPS Everywhere plugin/extension handled some Tumblr URLs. The example uses a theme made for larger screens so it does not need the smaller version. Usually, though, the one used in the image post (as compared to the zoomable image page) uses a smaller version of the image to fit the theme of the page. In the example for #6, direct links both point to the same image.Turning off the Tumblr rules for HTTPS-Everywhere seems to sometimes fix the problem. Upon further tests and replying to the emails of Tumblr support, wget has stopped working (getting 403 errors on direct links) on some occasions. My friend and I are located in the Philippines. J9GxX1HY9vX3ElWjYf7M48ByvKXLRIwRBJ2al2voS3J/C+WhILWHyd3crFhhNtkXuvG0zaxBTxw= wget works for both, but upon going to any direct link with Firefox, this error appears: This XML file does not appear to have any style information associated with it. This is the direct link to the image in the post and here is the one for the bigger version (both don't load here). The main blog has other image posts that load properly. Here is an example of a reblogged post that fails to load on the browsers. What can possibly be the reason for this happening? The part that really gets me is the fact that wget works, so I think I can assume that it’s not a problem with the network connection. Image posts automatically make the images a link to another page in Tumblr using a (usually) larger version of the image used in the post that is closer to the size of what the user uploaded for the post. For example (this example is not one of the affected blogs), in this image post (randomly selected), this would be the direct link to the image in the post. The images are from user-created Tumblr posts where the user uploads an image to post and are hosted by Tumblr.Conversely, if an affected blog is reblogs from an unaffected one, the image loads fine. The problem seems to be blog-specific in the sense that if a certain blog's image post doesn't load in the browser, other blogs (unaffected or not) that reblogged the same post won't load the image in the browser as well.Most load properly, but when making a list of pages with posts that don’t load images show that they’re mostly from the same bunch of users. This does not apply to all Tumblr pages.Using wget on the images' direct links works.Happens with any browser on the computer (Tested on Firefox and Chrome/ium both with and without ad/script blockers).User avatars, banners, headers, various theme and/or page-related images still appear. Only images that are part of the post won’t load.I found it weird because of the following reasons: If your site has more than one user, you may need to check the box that says Connection available to all administrators, editors, and authors on the Connections page.Helping a friend out with their Internet connection because “some pages won’t load”, I noticed that the problem was that the images of certain blogs' image posts weren’t loading on the browser.If you’re on a plugin-enabled site, you can use the Jetpack Social plugin to enable support for your custom post types like Portfolios, Testimonials, and WooCommerce products. Static pages and custom post types will not be shared.After connecting/reconnecting the services, you can publish a new post to test auto-sharing. See the instructions above for how to reconnect for each different social network. If you have trouble with your posts not being sent to a specific service, disconnecting/reconnecting will often help fix it.To share a post to your social media platforms again, see this section. If you revert a post to a draft, then publish it again, the post will not be shared again.If you schedule a post, it will not be shared until it is actually published.If you publish a post and the post did not get shared to your connected social media platforms, here are some common causes: Common Reasons Why a Post Fails to Auto-Share
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |