Reply To: How to use "WOOF_Image :: save_image"

Author Replies
traversal # Posted on October 6, 2015 at 10:19 am

Hey, save_image won’t help you here, as that is intended to load an existing image resource and save it out somewhere else.

I’m assuming you already have the image on the server inside wp-content/uploads, so you shouldn’t need to do that.

Are you trying to insert it into the core Feature Image field in WordPress? That would likely require you to insert an attachment to the post first, which is outlined here:

https://codex.wordpress.org/Function_Reference/wp_insert_attachment

You may also need to generate the metadata:
https://codex.wordpress.org/Function_Reference/wp_generate_attachment_metadata

And then you may also need to set the post meta to point to the new attachment ID:
https://wordpress.org/support/topic/how-to-programmatically-set-posts-featured-image

On the other hand if you’re using a MasterPress custom image field, you should be able to set the VALUE of that field to be the full URL to the image, and MasterPress should be able to see that image inside your wp-content/uploads directory.

So if you had “wp-content/uploads/car.jpg”, you could set the value of an image field to:

http://yoursiteurl.com/wp-content/uploads/car.jpg” and MasterPress should be able to recognise that image.

Latest From the Blog

MasterPress 1.3.6 is now available

Masterpress 1.3.6 is a compatibility release. It resolves an edge case with shared fieldsets not working for MySQL 8 when the fieldset is limited to more than 1 post type or taxonomy or excluding any post types or taxonomies.

Plugin Requirements

MasterPress requires a minimum of WordPress version 4.9, MySQL 5.6, and PHP version 5.6.20.

We also recommend that PHP is configured to use a memory limit of 64MB per request (128MB may be required for sites with higher complexity).

This plug-in is not compatible with the WordPress.com hosted service.

Three AM