headonfire

Can confirm, a new attachment is being created on every save, including autosaving. However, should be clarified that the image file is uploaded only once (the very first time), there’s no duplicate files in wp-uploads. Only new ‘attachment’ post type entries are being created.

@mihdan Just a minor note. Managing your work in any language that is not english (commits, issues etc) is a prefect way to alienate people and prevent them from both using and contributing to the project. E.g. while I do speak russian (+ use the plugin and am capable of helping with improvements) I’ll never bother doing anything for a project that is non-english.

Latest CF7 update (4.9) fixed it for me.

Latest CF7 update (4.9) fixed it for me.

I still don’t know what was the issue, but the latest CF7 4.9 update fixed it. Now everything works.

Thank you for the hint! It was working on my pretty large site with many CPTs and CTs, except one post type. Setting orderby to ‘menu_order’ via pre_get_posts forced it to work. The plugin should work out of the box (and always did for me), but I guess there are some edge cases where it doesn’t.

@marajo you’re welcome ??

Thank you for the info! Sure, I understand the purpose (and used it couple times for Core translations to my native language). Just thought if it was switched from standalone model to a WP plugin it should be somehow integrated with WP. And the “export to .MO file somewhere in the filesystem” feature seems so obvious to me, kinda has to be built-in.

Will definitely have a look into the code closer to project finale. Auto-export is a must.

Yes, I understand that. Even in WP Core not all of them are documented properly or even at all ??

I was looking for a solution to this issue and one of the first google results led to this page. My situation is a bit different as I want to use a standard Polylang widget in navigation menu, and calling <?php pll_the_languages(array(‘display_names_as’=>’slug’)); ?> does not solve this. So, I’ve studied the code and found a useful filter ‘pll_the_languages_args’. And I wrote this code to change the value from functions.php:

/**
 * Display languages as slugs instead of full name.
 *
 * @param $args array Merged array of defaults and user settings for language selector
 *
 * @return array Modified array of arguments
 */
function pss_language_as_slug( $args ) {

	$args['display_names_as'] = 'slug';
	return $args;

}
add_filter( 'pll_the_languages_args', 'pss_language_as_slug', 10, 1 );

Hope this will help someone.

Thank you ??

@abhisekpadhi You should update your star rating. It’s really strange you gave it 3* ??

As for the settings – you should understand the Page Lifecycle and how object caching works, especially when you need to store full pages in cache. In this case you need to get access to Redis long before the WP is fully ready to go, because, well, that’s the purpose of caches – cache db queries, cache expensive calculations, cache full pages and avoid running all WP heavy stuff.

There’s a plugin for that. Meet the Enable Media Replace.

Well, @hugh222, if you see this message, you’re definitely doing something normal users usually don’t do. For all standard cases WP has appropriate error messages, extended debug information is also available for those whom it may concern.

the frustration presented by Shaped Pixels and others posted elsewhere

I am one of those, actually. And right now discussing the future of the theme on GitHub. And sending pull requests with changes.

The reason behind it may also be an underlying frustration that is not being addressed by Core Developers when they present their design choice of Themes.

Giving a theme 3-star rating just because it’s a blog theme? Totally wrong. Because of frustration? Even more wrong.

And, keep in mind, that Shaped Pixels is theme developer. I wonder how he/she would react, if someone downloads his Seasonal Pro blog theme and then say it sucks because it has no front-page with eCommerce widgets. Ridiculous.

Please accept my apologies if you took my comments as an insult.

Oh, you didn’t. I have very thick skin).