patrickposner

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;
});

Hey @tobiasburri,

I’m 100% sure it hasn’t uploaded 40k files, but only 9.
As we store the value of the total uploaded files in a transient, this might be the result of some DB caching.

I will close this ticket here now as it is again about Simply Static Pro and is against the guidelines of the w.org forum (we can only support the free plugin here), but if you reach out via our pro support, I’m happy to dig into it and give you some recommendations on speeding things up!

Thanks for your understanding,
Patrick

Hey @tesso,

thanks for reaching out!

Take a look at the discussion here on StackOverflow: https://stackoverflow.com/questions/68419875/static-site-generation-checking-if-wordpress-can-make-requests-to-itself-from-1

It’s either about the missing host in your docker-compose or an issue with the ports.

Hey @tobiasburri,

thanks for the follow-up!

Could you reach out to our pro support?

I built a pagination handler now into the current beta version of Simply Static Pro which will take care of that automatically for you, but I obviously can’t include a download to it here in the forum! ??

Thanks,
Patrick

Hey @tobiasburri,

thanks for reaching out!

This is indeed not yet automated by the single export integration.

We have it as part of our internal roadmap already (alongside some other things like auto-including non-image files, improving the delete page/post mechanism, and the ability to combine single exports with builds).

Still, as of now, this would require either a build or full export.

Hey @idefixx,

you probably need to reset our DB table to reset the background processing.
Go to Simply Static -> Settings -> Utilities and scroll down to “Reset”.

Click on the Reset Database Table Button and then navigate to “Generate” again – the process should be stopped now, and you should be able to re-run the export

Hey @idefixx,

can you try it again with today’s release?

This might help solve that as we now included object cache handling in the generation process (on generate and on cancellation of the export).

Let me know how it goes!

Thanks for the update @phillsav – much appreciated!

I’ll go ahead and close this ticket now.

Hey @acp693,

we will also add an easy option to deactivate all feed-related URLs from the static export in the next update!

We received quite some feedback regarding this, and ultimately, you (our users) decide what we do! ??

Hey @phillsav and @tripslip38,

that is an issue inside the Simply Static integration from Blocksy (it’s not part of our plugin).

We are still waiting for an official update from them to resolve that. It’s not entirely clear whether we will provide the integration ourselves in the future or whether they will continue to maintain it as part of their theme.

Hey @dsl225,

thanks for reaching out (and for your update!)

1) Noted! I’ll add that to the list in the next update!
2) I would recommend re-running the export with “Relative Path” or “Absolute URL” – this way, the paths are already optimized to work on a hosted environment.

You can also do it manually with a code editor, but I’m not sure how viable that solution is for you.

3) 100%! I’m also thinking about completely relabelling these settings. These are from the super-early days of the plugin and probably cause more confusion than they help! ??

Thanks for the heads-up!

Hey @titanrob16,

there is no limit in the number of exports you can run!

Have you checked the “Diagnostics” screen? Are there any errors shown there?
You can also fully reset the plugin in Simply Static -> Settings -> Utilities -> Reset Settings.

Have you enabled the debug log? There might be some explanation why it’s stuck: https://docs.simplystatic.com/article/72-how-to-use-the-debugging-mode

Hey @pkd2989,

I don’t think we add that as the plugin is intended to have your static site completely separated from your WP website: https://docs.simplystatic.com/category/57-prepare-wordpress

However, we are working on automatically rewriting the URLs for media files in WP to the URL of the static site – this way, you achieve the same results (less storage usage), but the source of truth should be the static site, not the WP site.

Hey @shreyas5,

I would suggest starting with our documentation to get a bit more familiar with how Static WordPress works: https://docs.simplystatic.com

Missing files: https://docs.simplystatic.com/article/55-how-to-find-missing-css-and-js-files-on-your-static-site

How a Static WordPress Setup works: https://docs.simplystatic.com/category/57-prepare-wordpress

Hey @micheleficara,

thanks for reaching out!

Cloudflare Plugin

You won’t need the Cloudflare plugin anymore when going static – once you serve your static files from Cloudflare Pages you get all the optimizations from the APO plugin automatically.

However, if you absolutely need it for another reason, you can whitelist the plugin in Simply Static -> Settings -> Debug -> Whitelist Plugins – add the slug of the plugin, save the settings and it gets excluded from our Diagnostics.

URLs

You won’t need to touch anything – the files indeed end with .html, but the URL will still be mywebsite.com/page/ and not mywebsite.com/page/index.html

Servers automatically convert the .html ending to the correct URL structure.