fsquared

Not in the current version, but it’s in the underlying widget so I shall add it to the ‘to-do’ list; it needs to be updated anyway to be more properly aware of things like the new block editor stuff…

Hmm, it seems to be working for me – do you have a URL where it’s not working (and ideally, the Tumblr it’s trying to pull from)? It might be something data-specific…

I suspect they have; it’s an old API that they seem to like to change without saying anything ??

I will have a look today and see if I can work out what they broke this time…

Honestly, because it’s not needed it!

However, I will run through some tests on the latest WordPress and check if there is anything lingering in the to-do list so we can get rid of that nasty “this hasn’t been updated for ages” warning that WP.org puts up ??

I’ve just pushed a new version (0.2.15) which should solve this issue – Tumblr seem to have started capitalising some words in their API responses which was … unexpected ??

Hmm, I don’t think it’s a user agent issue – at a quick glance, I think Tumblr *may* have changed the way they are encoding some things. I will try to dig into it in the next day or two to work out what they’ve broken and work around it!

As far as I know, there is no way to change the post type of existing posts on Tumblr, nor do I know a way of setting a default post type (those may be questions better directed at Tumblr support).

However, I have just pushed an update (0.2.14) to the plugin which should handle images embedded in plain text Tumblr posts:

* this will only be done when the content type in the widget is set to ‘whole post’

* to avoid those ‘regular’ titles being shown, tick the ‘make whole post clickable’ option

Hopefully things should start looking more like you were hoping for with this new update – let me know!

Hi there – there is some code to try and handle ‘unusual’ text encoding, but it’s entirely possible there’s an error in it.

Can you give me the tumblr url that is exhibiting the problem? Given that, it should be pretty quick to reproduce (and hopefully fix!) the problem.

Thanks!

Hi Andrew,

I’m not entirely clear what you’re trying to achieve with this widget – it’s just a cloud of tags from your posts, so I’m not clear where external links come into it?

Hi Gregory, sorry for the slow response – I’ve been out of the country!

If you can give me some details about what the problem actually is, I’m more than happy to take a look…

At the moment no, this isn’t possible.

The widget uses Tumblr’s old API which doesn’t provide any data for “favorited” posts – that’s only available through their V2 API, which would involve rebuilding a lot of the internal code.

I’ll certainly add it to the wish list, but it’s not something that will happen soon I’m afraid.

Glad to hear it – if you needed to do something odd to work around the problem, let me know and I can make sure it’s fixed in future versions!

That looks to be right.

Looking in more detail at that pageful of warnings, it looks like the widget isn’t able to request the data from Tumblr – instead of receiving the XML data, it’s getting back some HTML that includes the phrase “The URL you requested has been blocked” which suggests that your hosting is blocking the outgoing request.

This isn’t something I’ve come across (it seems an unusual restriction, but presumably they have their reasons) but I’d suggest contacting them and asking if they can modify their rules to allow a request to https://watershedplus.tumblr.com to get through.

It still shouldn’t be putting all those error messages in public view (they usually go to the error log, but again your hosting seems to do something a bit odd), and it should handle the failure more gracefully – but the underlying issue appears to be with that block from your hosting company.

Oh dear – that doesn’t look good does it?!

At a guess, I suspect there is an issue with the Tumblr URL, but it certainly shouldn’t be spitting all those horrible error messages out. If you can let me know the URL you’ve set in the widget I can investigate further.

(I’ll also make sure that those sorts of errors get handled a lot better in the next release!)

Ok, digging into the code it looks like the widget doesn’t attempt to extract media from non-media posts (like ‘regular’) – I’ve added this to the issue list, and will update this thread once that’s included.

Is there a particular reason why you’re not posting this pictures as picture posts? That might be a solution in the short term.

Incidentally; you shouldn’t need to wait for the widget to update content – whenever you change the widget settings it clears it’s cache and should fetch fresh content right away.