patrickposner

@sitebolts,

good catch!

I’ve created a GitHub issue for it and we’ll tackle it within the next update: https://github.com/Simply-Static/simply-static/issues/307

Hey @mudbone67,

it sounds like a permission issue (more specifically that there aren’t writing permissions for our log file).

Have you checked our documentation for local development environments?
Any security plugins installed in your installation that might cause restrictions on the filesystem?

Hey John (@dsl225),

I 100% agree with you here – I wouldn’t purchase a yearly subscription for that myself! 😁

It’s indeed as you said, the number of people looking for that use case is somewhat limited, and most of the requests we got over the years are all about running a static WordPress website, which is constantly updated (like how people use Hugo, Gatsby, etc.)

So, we opted to do our best to support that use case (and had to neglect the plugin’s archival features).

We even built a little site project around the archival idea here: https://webtozip.com/ – it’s using Simply Static, but reduced the configuration to an absolute minimum, and while I like it, it’s more a hobby project than an actual business, which I can use to pay our employees 😅

Hey @dsl225,

I understand your point, but Simply Static is used for many different use cases and complex scenarios nowadays.

I would choose “Relative Path” and add a “/” as a value for your use case. You want to replace the WP website with a 1 to 1 replacement.

Absolute URLs make more sense if you run a WP locally (or protected somewhere) and push it to another server (and thus, a different domain).

Enable “Force Replace URLs” as you most likely won’t use any advanced features like forms or comments (which is why the option exists in the first place).

Just a quick note about your follow-up question: We can’t really provide one-on-one support here in the forum, we can only help by giving general recommendations or referring to our (very extensive) documentation here: https://docs.simplystatic.com/

Especially for the images, I would take a look at this article: https://docs.simplystatic.com/article/54-add-missing-pages-files-to-your-static-website

You probably need to tell Simply Static where to look for the image path (The “How to fix” section in the article above) to get that sorted.

Hey @gauravyad,

thanks for reaching out.

We can’t really help in that case as we can’t even take a look at the site in that scenario.

I would recommend checking our documentation right here: https://docs.simplystatic.com/article/54-add-missing-pages-files-to-your-static-website

Hey @gbicdmn,

thanks for the update!

I don’t think you have to switch to LocalWP right away, it’s just something to keep in mind for the future (especially if you run into any memory-related issues).

I wonder if the problem has something to do with Elementor’s performance settings – maybe the button is loaded with lazy loading? So that it isn’t part of the page right away?

I would probably dig into the Elementor settings and check the results based on some adjustments: https://developers.elementor.com/how-elementor-improved-asset-loading-and-made-your-website-run-faster/

Hey @karlyborgy,

thanks for reaching out.

We published an improvement regarding memory handling in today’s update that might help with that – so feel free to check it out!

If it’s still stuck, enable the debugging mode and check if there is a specific file/page that triggers the error.

Hey @sakoryu,

thanks for taking the time to publish an utterly unfair review.

No, it’s not in any way an upsell for the pro version.

I understand that setting up (or removing) Basic Auth from your web server might be above your technical knowledge, but that does not justify your wild accusation.

I expected something better from a Japanese user (we have many of them, and we love working with them because of their politeness and kindness).

To solve your problem, take these steps:

• Go into Simply Static -> Settings -> Utilities -> Reset Settings and click “Reset Settings” this will not only revoke our settings, but also clears the PHP system variables holding the basic auth credentials
• Go to your .htaccess file and remove the following lines:

AuthUserFile "<path>/.htpasswd"
AuthName "Realm"
AuthType Basic
require valid-user

That’s it, Basic Auth should now be removed entirely from your project.

The next time you claim we are doing something bad, remember humans are building the product and providing support—we are not some giant enterprise company trying to make a quick buck out of our users.

Thanks,
Patrick