Image field not clearing issue

Viewing 6 posts - 1 through 6 (of 6 total)
Author Posts
November 17, 2016 at 9:52 pm #3785
Post count: 2

When image field is saved and then cleared and saved it is still appearing on page. Looks like saving empty value does not work and keeps existing one.

November 17, 2016 at 9:56 pm #3786
Post count: 207

That’s strange, as it should be working okay. Is that in a repeatable field set, or just a standard one?

November 17, 2016 at 10:11 pm #3787
Post count: 2

It is simple image field, not part of repeater. I have latest version of your plugin. Where should I look to debug the issue which file?
I am using this field as:

if($wf->the->sidebar_items->image) { ?>
<div class="sidebar-image">
<?php //$wf->the->sidebar_items->image->resize("w=400") ?>
<?= wp_get_attachment_image($wf->the->sidebar_items->image->attachment_id , 'medium') ?>
<?php } ?>

November 17, 2016 at 10:16 pm #3788
Post count: 207

It might be the case in that particular code that the attachment ID is not being cleared correctly, even though the image itself is. The if statement is also not correct, as that statement still returns “something” (an empty-field object). If you need to code it that way, by using wp_get_attachment_image, you could try this:

the->sidebar_items->has(“image”)) { ?>

November 17, 2016 at 10:30 pm #3789
Post count: 2

You are correct, using condition if($image = $wf->the->sidebar_items->has(‘image’)) works as expected. Thanks.
It seems that .has(‘image’) method does the clearing, yes?

November 17, 2016 at 10:32 pm #3790
Post count: 207

Great, glad that worked. “has” doesn’t do the clearing, but it checks if a value exists, and returns boolean FALSE if not, but the field itself if it does.

There is still a slight bug in that the attachment ID (which is stored as a kind of meta property of the image), is not being cleared along with the image. But the if statement gets around that!

Viewing 6 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic.

Latest From the Blog

MasterPress 1.4.1 is now available

27th May 2024

This update addresses backwards compatibility issues that were introduced in the previous update. There were some edge cases where PHP 7 had issues and it didn’t work at all on PHP 5.6. We have now changed it so that the PHP 8 compatibility changes will now only affect PHP 8 and will be more thorough… 

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 hosted service.

Three AM