hrosenhagen

@kevin + @alexandrbig: Which language do you use? To me it seems that non-english languages break date validation (see here)

Hi @caridadz,

maybe I can provide a hint:

Since strtotime() only covers a limited number of date formats, the plugin falls back to this default time format:
$date_format = 'F j, Y'

… “F” meaning “A full textual representation of a month, such as January or March”. , of course.

This seems to break date validation/parsing if the locale is – for example – set to german or other languages where months carry different names, making strtotime() bound to fail.

I seem to have found a workaround for my wordpress installation by putting in a fallback that’s not prone for locale errors, like e.g. ‘Y-m-d’ (ISO style date). My datepicker seems to be working again after modifing the default in wpcf_get_date_format() and getDateFormat().

I’m experiencing the same problems as ge-sehen (german WordPress, types but no woocommerce)

I think I’m having the same problem here. Simply put:

• I upload a brand new image.
• since the autogenerated 150×150 thumb crops out the wrong part of the image, I open the image for editing
• I crop the image (draw the selection, confirm with the toolbar button etc.) and save it with “Thumbnail Only”. Size is exactly 150×150.
• WP admin tells me everything went fine (there’s no error message with debug activated or hidden in the AJAX going on in the background)
• No sign of the freshly cropped image in the post or on the server.

However, if I choose a image size that does not match 150×150, it seems to work.

So, “Thumbnail Only” cropping is no good for cropping regular thumbnails?!