patrickposner

@madtownlems,

100% agree, let’s go with all these recommendations! 💪

• add a filter to bring back clearing up after the export with a simple flag (true/false)
• add a button to quickly clear the dir inside Utilities
• auto-clear the directory on deactivation

And thanks for the shoutout, btw! 😁

@madtownlems,

we do a lookup for both and run an array_intersect() to catch boths (Now that I think about it, we might want to change that!)

Hey @madtownlems,

happy to help!

We haven’t fully updated the documentation around the Enhanced Crawl feature (just because Scott got tired of keeping up with all the changes related to it as I’m pushing some minor improvements in almost every release! 😅)

We have a bunch of filters you can use here:

Post Types:

add_filter('simply_static_post_types_to_crawl', function( $post_types ) {
	unset( $post_types['post'] ); // $post types is an array that contains the names of all the post types included.
	return $post_types;
});

Plugins:

This one still needs a filter – it was introduced in the last update (but only for Pro users) with an option to manage it inside the Enhanced Crawl settings. However, I’m happy to add a dedicated filter for this as well.

What you can already do is exclude directories inside each plugin (like /node_modules/ or /git/) like this:

add_filter('ss_skip_crawl_plugin_directories', function( $excluded_dirs ) {
	$additional_dirs = ['node', 'vue'];
	return array_merge( $excluded_dirs, $additional_dirs );
});

Let me follow up here as well, once the new filter is implemented!

Hey @jamesjosephfinn,

thanks for reaching out!

I’ll put that on my backlog for testing.
While Algolia works, I’m also not particularly happy with their latest developments.

The pricing approach was always somewhat opaque, but the recent SDK changes and the requirement to have at least PHP 8.1 have made it even more challenging, as we still have many users working with PHP 7+.

Did you run a test with that? I wonder if it just works?

Cheers,
Patrick

@madtownlems I don’t want to sound like Chat-GPT, but… you’re absolutely right! 😅

We get that fixed ASAP and ship that with the next update – thanks for the heads-up!

Cheers,
Patrick

Hey @vraisa,

thanks for heads-up!

Happy to get that removed in the next update – we had it to support some PHP 7.2 environments, but since we upped the minimum version to 7.4 a while ago, it’s no longer needed.

Should be gone with the next update!

Cheers,
Patrick

Hey @schmoewordpress,

thanks for reaching out!

I assume you are using the local directory export and you export it to your own server, right?

I’m having a hard time replicating it locally and on our testing environments, but we also don’t use anything besides UTF-8 for encoding the content.

So this is most likely produced by the server trying to force their own encoding here (as we no longer deal with UTF-8 conversion inside Simply Static – it’s just too much work to adapt to each and every language).

Can you please test the following fix I just committed to our repository?
Here is the link: https://github.com/Simply-Static/simply-static/commit/1484b424e71178764f36c0938e99d70d4a18d189

Hey @kywong85,

not sure what you have installed, but this endpoint isn’t used by Simply Static nor by Simply Static Pro.

You might have either installed another plugin or used one from an unofficial source – our Cloudflare Deployments work via our GitHub integration.