patrickposner

Hey @joernguysuesscsiro,

thanks for your report.

Simply Static will include all kinds of files (including PDFs) automatically as long as they are linked from your website; no special settings or configurations are required.

This mostly happens because of two things:

1. Some unsupported plugin is used to embed these files and they use non-valid HTML markup (If so, try it with a plain link instead)
2. They are referenced with a relative path instead of the full URL (and thus get skipped because Simply Static can’t locate them).

Hey @bibica,

we noticed that you are sharing Simply Static Pro on the Babiato forum, which is against our terms of service.

I appreciated your feedback, but this isn’t cool.

We will use the contact information provided on your website and escalate that now to our legal agency.

Remember: the code is GPL, but the assets aren’t, and you are using our design in your activation video.

Hey @jonalmada,

thanks for taking the time to put so much thought into this!

You are right on many levels. We have already started lowering the requirements to run Simply Static (and we continue to do so!).

We are largely influenced by the feedback we receive (and IT and security companies seem to be the most active users in our user base).

SSL Notification

One thing I can already confirm is the removal of the SSL check within the next update.

While it took us months to get to that point (and 1000s of lines of code), I understand that having an SSL certificate might be an issue for a considerable part of our user base.

Warnings and Disabling Notices

I still try to avoid adding a “disable this notice” feature.

The problem is that many people reach out to us on various channels (GitHub, the forum, e-mail, DMs in Slack, etc.) without spending 5 minutes thinking about a solution themselves.

While this was okay for years, we are now faced with hundreds (if not thousands) of messages every week, and we are still a super small team (four people and only two devs).

So, the reason we are putting so much effort into the diagnostics and extending them is to give people a better idea of what we need to ensure their exports run as smoothly as possible while working behind the scenes to lower these barriers even more.

Hosting Problems

The number one problem was (and still is) hosting setups.

I’m explaining WP-Cron almost every day to folks trying to export websites with 20k pages/files on a shared hosting provider – I would LOVE to give people an option to not deal with these things.

At the same time, we try to stay free (or affordable with a pro) for many people and don’t move into expensive monthly plans like most competitors.

To solve that, we need to be a bit nagging in terms of showing errors, automate as much as we can, and give our users as much help as possible (via tutorials, docs, and we even release an entire video course in a couple of weeks about Static WordPress).

I know it’s not perfect for everyone, but we definitely try to keep a healthy balance between being a technical product and being a tool that can (theoretically) be used by everyone who is using WordPress!

Have a great day and thanks again for your feedback,
Patrick

• This reply was modified 1 year, 10 months ago by patrickposner.

Hey @langdinah,

thanks for reaching out.

Please follow the steps mentioned here: https://ww.wp.xz.cn/support/topic/troubleshooting-guide-faq-read-before-post/

As Woodmart is a commercial theme, we don’t offer specific support for that.
However, I’m almost certain there is an issue in your server setup that is unrelated to your theme.

Hey @mikkelcrunch,

sorry for the trouble – I just released a patch for this (3.1.7.4)!

Hey @bibica,

convinced – we add a setting to whitelist plugins by slug in the next minor update.
However, I want to give some context to the plugins you’ve mentioned:

WP Search with Algolia:

This one causes a fatal error in combination with Simply Static Pro because both use the same composer package. The plugin is also unprepared for a static site setup (you have to rewrite the URLs manually), so it’s unsuitable for use without modifications.

Cloudflare:

The Cloudflare plugin has zero effect in a static WordPress setup.
While it doesn’t break anything, it also does nothing for you – so why have it in the first place?

WP Cron:

That’s fine, but why don’t you tell Simply Static about it?
As shown in the docs, we have a constant that tells Simply Static there is a UNIX cron in place.

All you have to do is adding the following line in your wp-config.php file:

define('SS_CRON', true);

We will not add an option to disable the topbar (yet).
That might change if we see enough demand for it.

Cheers,
Patrick