motocomdigital

Hi @andersthorborg

Thank you for quickly fixing this issue for us. Much appreciated.

A few issue that we’ve spotted…

Force user to crop
Can’t really see this doing anything. I can still add an image, and publish the page with out cropping the image. What is meant to happen here?

Save cropped image to media library = yes & Return = Image object
This actually does not seem to create a new media library item anymore? And this is what is returned as the image object…

stdClass Object
(
    [image] => 2014/07/GSX-RL4_action_1_646x340_acf_cropped.jpg
    [preview] => 2014/07/preview_GSX-RL4_action_1_646x340_acf_cropped.jpg
)

So I’m guessing its a little broken, but it works but we need to work a little differently.

—-

This is how I think it should work. Please hear me out…

Save cropped image to media library

Rename this to…

Save cropped image as new media library item

If is ‘NO‘ get the image URL of the target image, use this image and delete using unlink(‘$target_img) and then save the new cropped version with exactly the same name. Do not add _acf_cropped into the file.

Also please note you are using an underscore before the dimensions in your image filename, wordpress uses a hyphen just before the image dimensions rather than a underscore.

This means, we can use the Image URL, Image ID and Image Object. No need to disable Image ID and Image Object this way ??

And this is better because you are updated the original media library item. But you are only ever updating the target size. Which is great because this allows the user to have different cropped sizes for all their images sizes, all in the original media item. In turn allowing us to use the Image Object and Image ID.

If is ‘YES‘ then this should just create a new media library item just for this target image size. Just like it did in version 4. And you can add _acf_cropped into the file name for this version so it does interfere with original media item.

—-

We tried to implement this ourselves. But we didn’t test the plugin thoroughly enough before we started modifying the plugin, then released the plugin does not create a new media item anymore, so we were struggling to get the whole thing bug free.

Many Thanks

Hello @andersthorborg

Do you have an ETA on this?

Thanks

Something is not wrong with your install.

I just tried installing an thought this might be the solution to my storage problem, but the after spotting your same issue, it has fallen completely on its ass.

I need my media library attachments to run as normal (not fussed about editing) as in mainly just upload attachment and delete attachment. But this does not.

Shame – if it did the above and worked on multisite installations, this would be the simplest and best cloud storage plugin.

Seriously I lost an day to this bug before I realised it was 3.4.2 causing the issue!

What the hell!!!

Anyway, thanks chris for your solution, however, am I missing something?

I put this code into functions…

function fix_custom_fields_in_wp342() {
	global $wp_version, $hook_suffix;

	if ( '3.4.2' == $wp_version && in_array( $hook_suffix, array( 'post.php', 'post-new.php' ) ) ) : ?>
<script type="text/javascript">
jQuery(document).delegate( '#addmetasub, #updatemeta', 'hover focus', function() {
	jQuery(this).attr('id', 'meta-add-submit');
});
</script>
<?php
	endif;
}
add_action( 'admin_print_footer_scripts', 'fix_custom_fields_in_wp342' );

…and although I can actually add multiple custom fields in one go (as oppose to the bug where you can only add one at a time and you need to hit post update in order to apply it)

I’m not seeing the freshly added custom post types appear before my eyes?

I have to refresh the page (without hitting post update) in order to see my recently added custom fields?

Is this correct? – as this is not an absolute fix for me, only a partial one.

Thanks

@ennan your anwswer was very useful. Thank you.

The documentation was not quite clearer enough for me to understand how to get the terms to appear ticked (selected), and this helped me solve the puzzle of getting the actual boxes selected.

Top level terms have to be preceded either by an empty string or a 0 (zero).

I don’t get this bit about an empty string, but using a 0 (zero) does the trick and actually selects the tick box.

However, as you explained, by doing a line break (alt+enter) you can do multiple hierarchy taxonomy terms at once.

exclude tags only works for me if I put this in my functions…

remove_all_filters('the_excerpt');

Try putting this in your functions

remove_all_filters('the_excerpt');

I like the admin bar in the backend, it’s a nice touch.

But on most of my projects I like to keep my front end clean with my UI only, so no admin bar. And it’s a pain to remember to un-tick the option in the user profile when setting up new users.

Ipstenu’s filter worked for me, he said it only works in the TwentyEleven theme, but seems to work for me on my custom themes.

Add this too your functions.php

// Remove Admin Bar Front End
add_filter('show_admin_bar', '__return_false');

Thanks @ipstenu!