1waytoheaven

Actually, a simple written text page would be enough for most of us newbies, just to explain what the plugin is trying to do for them, as you’ve done here in this thread.

The term “LocalWP” also confuses, because an online staging site on a sub domain IS local to the live site. But now I see you meant LocalWP to mean Offline on your device’s HD.

It’s easy for beginners to find what they need to set up BasicAuth, just a link to a tutorial you endorse would be enough.

The video on switching A records will spook many, so I was happy I didn’t need to do that. The cPanel “Softaculous” tool switched my staging site smoothly.

Thanks for your help ??

Colin

I think we need a beginner-friendly video to explain this!
I might do 1-3 videos on this to cover the very basics:

• What to do with WordPress (LocalWP vs. Basic Auth for protection)
• How to bring your website to Local WP (Create a backup, download it, import it..)
• How to use Basic Authentication instead of LocalWP (to keep WP online)
• What is my static site and where is my WP site (and how do I spot the difference?)

Anything else you like to see?

Thank you, this one sentence of yours is what I needed to read;

The idea is to make your website entirely static but have WP somewhere available (locally or protected somewhere online) to make updating content easy.

I agree with that concept, and will try to get our live site there.

I made it using SimplyStatic as a staging site, behind BasicAuth, then just used a tool in cPanel to move it to the live site, delighted to have retained the same urls, but confused that much of WP still functions, hence the confusion I had.

To be honest though, I do like the “slim WP” site even though it’s not really static… yet.

It is nearly as fast loading as our hand-made flat-file sites.

Now that the penny has dropped, I’ll rewatch your videos before going further.

Thank you, its a good plugin, and should do very well.

Colin

Thank you Patrick,

Actually, I did indeed read through all those pages, and even watched all the videos you made before using Simply Static.

But I honestly think you need another to answer my question :)

I still have not understood the Simply Static "philosophy", the idea behind transforming WP to static.

As I wrote in my original post, I thought the idea was to covert the WP site entirely to static, but that is not the case is it?

Instead, it seems to be, let the user decide the degree of static they wish to make their WP site into.

If that is the case, then non-nerd users like most of us, will not know what to include and exclude.(Despite watching your video on that topic twice now. It's too superficial.)

WP is already a lumbering behemoth, and I don't even use "Blocks", so it will only get worse, and more and more folks will want to use your Simply Static plugin to get some sanity back.

So I urge you to find time to make a video addressing this :)

And I would make it the first one to watch!

Colin

Wilco ??

Thank you Peter, understood.

I’ll take your advice ??

As one who has had this happen on both the last updates, I’d like to offer myself as a beta-tester of any new updates.

I manually update, so a brief note from the Devs to me prior to launch will allow me to verify the update works on my WP site, and alert them to any code changes they need to make, before zapping the innocents.

Via the contact form on our site:

https://www.born-again-christian.org/news/contact/

I suggest others affected, offer to do likewise.

I confirm the last update has now been fixed. ??

Thank you again for your diligent coding.

• This reply was modified 12 months ago by 1waytoheaven. Reason: Sp
• This reply was modified 12 months ago by 1waytoheaven.

I confirm the exact same update error, though I update manually.

I had to use WP Recovery mode to get our site back online.

In Recovery mode, I then uploaded my smtp2go backup from the prior version.

Thank you for your hard work, we appreciate you very much, but I will wait a few more days before trying to update smtp2go again to ensure the code has been cleaned up.

Yes, I discovered it the hard way ??

Interestingly, I did try deactivating the live Membership plugin for a few minutes, flushing caches etc. and generated a Simply Static copy, but even after adding every 404 url to the Additional urls pane, it still could not retrieve the css.

Though I do use the Litespeed plugin caching, and was loathe to deactivate that as well because it’s so sensitive and complicated.

And no, same result, even when I allowed the whole dir /litespeed/

Not to fuss ??

Have a Blessed Christmas and New Year to all our readers!

Colin

Thank you Patrick for posting the FAQ Troubleshooting guide, where I read…

Quote/

Plugins which absolutely not work with Simply Static:

• WooCommerce
• Membership plugins
• LMS plugins
• Plugins that require a logged-in area of any kind

/Quote

Whilst I’ve been waiting for a reply, I have experimented with various settings, even deactivating our Membership plugin, and can confirm Simply Static does NOT work with Membership plugins.

I +do+ understand that you are busy; best wishes with future development, and have a very blessed Christmas and New Year ??

Colin

I ought to mention the Membership plugin I’m using is this one;

https://en-gb.www.ads-software.com/plugins/simple-membership/

Thank you for your help ??

Colin

PS: Am I misunderstanding what your plugin does?

I’m trying to make my WP dynamic site into a flat file static site, eliminating the need for all plugins.

Perhaps you are trying to work with plugin developers to make their WP plugins function as static html plugins.

Could you clarify for me please?

• This reply was modified 1 year, 3 months ago by 1waytoheaven. Reason: Added PS
• This reply was modified 1 year, 3 months ago by 1waytoheaven.

No need to reply, I found the source of the problem.

When I looked inAppearance>Themes>Neve Child-Master

After a few moments a small message appeared on my desktop bottom left column; Style>3.0

When I looked at the alternatives to 3.0, the drop down offered “Legacy skin”

I selected that, and the screen refreshed and I now have the hamburger icon working properly on mobiles, AND my sidebar links have the correct GREEN colour that was there before I dated to Neve 3.8

(I have of course reverted to Neve 3.5)

The site is working and looking as it was before I tied updating to Neve 3.8.

Sorry to trouble you.

No need to reply, I found the source of the problem.

When I looked inAppearance>Themes>Neve Child-Master

After a few moments a small message appeared on my desktop bottom left column; Style>3.0

When I looked at the alternatives to 3.0, the drop down offered “Legacy skin”

I selected that, and the screen refreshed and I now have the hamburger icon working properly on mobiles, AND my sidebar links have the correct GREEN colour that was there before I dated to Neve 3.8

(I have of course reverted to Neve 3.5)

The site is working and looking as it was before I tied updating to Neve 3.8.

Sorry to trouble you.

*Cough, anybody there?

I’m just a fellow Neve user (like you), but whilst you’re waiting for an official reply, I suggest switching back to your site backup, either through cPanel, or manually uploading your WP backup.

Support here seems to take days.

You DO have a recent backup, don’t you?

If not, that’s the first lesson to learn from this experience.

Thank you Kush, I appreciate the advice.

I have done as you suggested, but the problem is still as described above on mobile platforms.

So I assume the bug is in Neve and NOT a conflict with any other plugin I use.

Can you check it out please, and advise a fix.

I have now deactivated and deleted the Health Check plugin.

I noticed a further Neve bug on both desktops and on mobiles; when you tap through to an article from the main site page (Blog page) all of the menu links on top and on right side links lose their Green colour, and appear black, they still link, but will confuse users who have been used to green coloured links used in the body text of articles.

Could you supply some code to put in my Neve child theme to fix these bugs please?

Colin

• This reply was modified 1 year, 3 months ago by 1waytoheaven.
• This reply was modified 1 year, 3 months ago by 1waytoheaven. Reason: New bug found