Kevin Langley Jr.

Closing support ticket

Closing support ticket

This is the default functionality of WordPress and there is no way to easily override that. Is there any reason why you would specifically need it to NOT generate those other image sizes?

It does this so the same image that has been uploaded can be used in any place within the theme that has a image size registered. For example if you were to upload a photo to the second post thumbnail position and then changed it to be in the first position, the image size has already been generated regardless of the fact that it was originally uploaded and set for the second post thumbnail.

This has been compatible with WP 3.6.1 since that version was released.

I’ve also tested the latest version with 3.6.1 as well and have not had any issues.

Closing due to no response from issue reporter.

Fixed in latest release

Closing due to no response from user.

Do you possibly have different sidebars on the site you’re attempting to import them onto?

If the sidebar names differ from the originating source, you would have to open the JSON export file and manually adjust that.

Switching sidebars upon import is a feature we have in the backlog, but have not had time to address yet.

The API does not return any information about the end user of the site. It only provides access to your WordPress content over a JSON API.

It seems that the user, Benuit, created that as a stand alone plugin. You could include it into your project a number of ways but the easiest would be to download the zip of that plugin from GitHub, https://github.com/Benuit/thermal-api-custom-fields/archive/7115d9a8ecf5a6ce360fb6692c6589ba797a00fb.zip, and put that into your wp-content/plugins directory.

You would then need to activate the plugin within your WordPress admin.

Just to be clear here, the plugin created you’re referencing here by Benuit, is in no way affiliated with Thermal API itself. For further support on this issue alone, you would need to contact that plugin author.

Hopefully this points you in the right direction though.

You could use any combination of cat, category_name, tag, and taxonomy.

Please refer to the documentation for a more in depth explanation of how to use those parameters.
https://github.com/voceconnect/thermal-api/blob/master/README.md#parameters

You can do so by hitting the same end point as posts but passing in the post_type parameter.

https://github.com/voceconnect/thermal-api/blob/master/README.md#parameters

Yes, that is exactly what this plugin is for.

You can learn how to get the content for your posts and more by reviewing the documentation https://github.com/voceconnect/thermal-api/blob/master/README.md#posts.

Thanks!

This should be resolved now as that was previously a git submodule to the plugin, but we are now using composer to manage dependencies.

Thanks!

Hi Ron,

I’m confused as to why this issue as been sitting here for over 6 months without any fix in the latest release… The latest release was pushed on 4-17-14, but yet this still is not within the latest plugin release?

Telling people to download the development version does not help users that pull in their dependencies via composer or some other automated method…

Any chance on getting this fixed in a reasonable timeframe here?
If not, I’m just going to write my own as it seems like this plugin is not even being supported anymore.