Jupitercow

I realize after thinking about it that when we regenerate images, we want to regenerate them all, so obviously it has to regenerate existing webp images. I was too focused on what I was doing and not how this plugin needs to work. Just needs to not change the filename when it is already a webp. Great plugin either way.

I did see that request. I like the idea of control over the extension, but I don’t mind having “-jpg” or “-png” kept as a reference to where the file came from…

The issue here seems to partially be that it converts webp files to webp and then keeps adding to the extension. I just had a problem where somebody added a banner image to a site that was already webp format, and when I ran regenerate on the site, it broke those images. Likely due to a CDN conflict. Working on that now.

It seems like it would be ideal to leave existing (either uploaded or converted) webp images alone, but I might be missing something. I will comment on the github thread.

It was the ‘only include active’ setting. I am not sure how that got changed. Thank you so much for your help finding that! Fixed!

I made that update, but it didn’t change anything unfortunately. It is like the map imagery doesn’t exist. I am lost.

Have seen the same problem on post types that would use Gutenberg by default, but are being replaced by the Classic Editor (eg: posts and pages). Custom post types which don’t rely on the Classic Editor don’t have the issue. If I Turn off the Classic Editor, and just use Gutenberg, the issue goes away.

WP version: 5.6.x

How was this resolved?

These settings worked great in the wp-config.php. This is a really great feature for Multisites. Thanks!

The plugin is fairly simple, so it seems like there is good opportunity to modify it (would love to see any changes you make!).

There is also this premium plugin that takes things up a few levels: https://deliciousbrains.com/wp-migrate-db-pro/

• This reply was modified 8 years, 1 month ago by Jupitercow.

If it is successful, it really just logs you out. You click on “pull” and it immediately starts to pull, and when it is finished it logs you out. Log back in with the remote database. So no confirmation, but it does its job pretty well.

• This reply was modified 8 years, 1 month ago by Jupitercow.

You should save a post/page, and then look in your root directory for your sitemap file. You should also see a remove from sitemap checkbox on posts and pages.

That filter would use a post id to redirect to a page or post with that id. So find the id of the post you want to redirect to and replace “4” with it.

For you, you should be able to do this:

// Redirect using post id
add_filter( 'sewn/login/logged_in_redirect', 'custom_sewn_logged_in_redirect_id' );
function custom_sewn_logged_in_redirect_id()
{
    return get_the_ID();
}

add_filter( 'sewn/post_delete/redirect_success', 'custom_post_delete_redirect_success' );
function custom_post_delete_redirect_success( $url ) {
    // Change $url
    // For example: $url = get_permalink();
    redirect $url;
}

compare is not a parameter. If you used meta_compare, which is a parameter along with ‘EXISTS’, you would get what you already have. That would basically be the default that you are already dealing with. So that will NOT solve the issue. It won’t change anything. at all.

Unfortunately. It looks like there are three possible solutions to this, but they are not just a simple setting to your base query.

1. Make sure every post has that meta_key with at least an empty value.
2. Multiple queries, one where you get the posts in which the meta_value is 'something', and one where the meta_value is NOT 'something'.
3. Use a custom Left Join and Order By query. Something like this. Though I have not tried this specific solution, I have done something like it a while back.

Link: https://wordpress.stackexchange.com/a/141367/11966

• This reply was modified 8 years, 4 months ago by Jupitercow. Reason: code marks

It is weird that it doesn’t output an error for me, but there is a bug. I am uploading a new version to fix this for now. The metabox system is getting converted over cmb2 in the near future.

Assuming this is resolved.