patrickposner

Hey @chugeno,

thanks for reaching out!

That is indeed only handled by the pro version of Simply Static.

We implemented a modified crawler that validates the meta tags added by TranslatePress (and other multilingual plugins) and automatically adds these pages to the export.

However, you might get at least some progress on the issue by using the following code snippet:

add_filter('ss_match_tags', function( $match_tags ) {
	$match_tags['link'] = array( 'href' );
	return $match_tags;
});

Hey @gbicdmn,

thanks for reaching out!

I woulld recommend using the “Force URL replacements” setting in Simply Static -> Settings -> General -> Replace URLs

This should ensure that the button URL is updated as well.

Local Development:

One thing I want to mention is that we highly recommend using LocalWP instead of XAMPP if your are not comfortable touching the configuration files: https://docs.simplystatic.com/article/56-how-to-fix-problems-with-your-local-development-tool

Hey @berniq,

that makes a ton of sense.

We only support “pretty permalinks” and this should also be flagged as an error in Simply Static -> Diagnostics.

Because of the index.php part of the URL, Simply Static will automatically skip all URLs.

The recommended solution is to use pretty permalinks in WordPress, as this is also a common practice in general.

However, if you absolutely need to keep the URL structure for some reason, you can also use the following code snippet to whitelist PHP files:

add_filter( ‘ss_excluded_by_default’, function ( $excluded ) {
return array_diff( $excluded, array( ‘.php’ ) );
} );

@tremlas I wonder if that is related to the object cache purge we implemented here: https://github.com/Simply-Static/simply-static/blob/65958a69a432d261610dd8f61de99494f7401c7e/src/class-ss-plugin.php#L210

We now clear the object cache before running the static export to avoid cached results from our DB table.

While not needed on solid web servers, the increasing adoption of (sadly messy) Litespeed server setups forced us to get that into the plugin to fight the constant “cache-all-the-things” behaviour LS servers do to sell better performance.

Hey @zivcomp,

thanks for reaching out!

I’m by no means a pro regarding Astra, and their support team can probably deliver a better answer to this, but I would assume there is some automation happening in Astra, especially for mobile versions of the website.

Maybe they apply some minification/optimization to the output or conditionally exclude some scripts from the mobile version?

There might even be some caching optimized explicitly for the mobile version.

Hey @crossy,

thanks for reaching out!

Take a close look at the URL and if there is a trailing slash at the end or not.
This issue is quite common and happens because of your “canonical” tag.

Let’s say your WP website runs at https://old-url.com (also configured in WP under Site URL), but the canonical tag (often added by SEO plugins) points to https://old-url.com/.

This would result in the exact problem you’re facing right now, as the tag would tell Simply Static to add a 301 redirect instead of fetching the page’s content.

Hey @tremlas,

this one works just fine for me:

add_filter('ss_excluded_by_default', function( $excluded ) {
	unset( $excluded['feed'] );
	return $excluded;
});

Can you double-check it?

Hey @tremlas,

we indeed added “feed” as a keyword to the excluded list for URLs unless the add feeds option is enabled:

// Exclude feeds if add_feeds is not true.
if ( ! $this->options->get( ‘add_feeds’ ) ) {
$excluded[] = ‘feed’;
}

I have to do some testing, to see if it’s still happening if the option is enabled, but you can also remove it yourself with the following filter:

add_filter(‘ss_excluded_by_default’, function ($excluded) {
$excluded[] = ‘wp-json’;
$excluded[] = ‘.php’;
$excluded[] = ‘debug’;
return $excluded;
});