swinggraphics

Perfect, thanks!

I reverted back to 5.16.1.1 to fix the problem.

No. Seems pointless to keep discussing. This would take what, twenty seconds to fix in the plugin?

The script that loads is not the same without the ID. Do not mark this resolved while the bug exists.

A text box where they can be entered manually would be better. Feature suggestion.

Yes, we are getting this error, too. Stupid Microsoft. Oh, gee, an iframe for the same domain you’re on; let’s block that. ??

Yep, I switched to W3TC

The SiteGround Optimizer plugin works perfectly fine with CSS code that follows the standards for Stylesheets coding

No, it doesn’t. That’s why I’m reporting this bug.

@import "file.css";

.colorize { color: red; }

is perfectly valid CSS. Your plugin screws it up.

Your plugin should work with any valid CSS file and not introduce errors that render any part invalid. I am not going to search the directory for an example. You can jolly well create the minimal example from the code I already provided. A child theme you create is free, after all.

This is a problem with the plugin, not with my account.

Steps to reproduce:
1. Use a stylesheet that includes @import.
2. Enable SG Optimizer with Minify CSS Files and Combine CSS Files enabled.
3. See that the first style rule that follows @import is broken.

Thanks. It’s good to note that pre_get_posts can filter results, but I am specifically looking to reduce the size and time of indexing. My site with 300 pages took 15 minutes to index. As I tweak and customize, I’ll have to rebuild. I don’t want to keep waiting that long. Same site with Relevanssi took a few seconds.

Is this the best/only way?

add_filter( 'wpfts_index_post', function( $index, $post ) { 
    if ( 'my_cpt' == $post->post_type ) {
        $index[ 'post_title' ] = '';
        $index[ 'post_content' ] = '';
    } 
    return $index; 
}, 3, 2 );

Would I also need to add $index[ 'clust_name' ] line for each custom cluster?

A plugin in production should not generate errors. You need to add some checks in your code to make sure you aren’t trying to access something that isn’t available.

In this case, I was purposefully waiting to run the index until after making some shortcode and post changes that would affect indexing.

Updating a post also fails with “Updating failed. The response is not a valid JSON response.”

Ah yes, I see. Have to wrap my head around that. Thanks!

I’d like to suggest adding a screen shot after the example code in https://fulltextsearch.org/documentation/#item4_2 that shows the updated Cluster Weights. That would jump out to someone like me looking to add options there.