• Resolved MikkelCrunch

    (@mikkelcrunch)


    Hi,

    I think everything is working fine – and I just started to play with it today.

    What i see in the Code – there are the Feed URLs with the “Secret Subdomain”.

    Usually I do not need these URLs at all – but I think there should at least be the Domain of the static Installation.

    Or did I miss some Settings where this can be set up?

    Thanks in advance
    Mikkel

Viewing 10 replies - 1 through 10 (of 10 total)
  • Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Sorry, I just changed the Theme to Astra and suddenly the URLs changed to /static-site/.

    Thanks anyway for this Plugin ??
    Best, Mikkel

    Plugin Author patrickposner

    (@patrickposner)

    Thanks for the update @mikkelcrunch,

    can you tell me which theme you have used before?

    They might use some custom structure for these URLs that aren’t tracked by our parser (but we might add an exception for that in another update!)

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Hi,

    thanks for your answer. I had the 24 Theme installed. It is a totally naked, fresh site for testing.
    But I would say, I had something misconfigured on my site.

    I work with WordPress for a long time now, and I’m always looking to optimize the load time and manage the typical security tasks.

    So this is fascinating for me and I want to test if I could use your plugin for my clients (existing and new ones).

    So one Question I have, would be about the URLs which are “active”.

    As I told you, I have a Subdomain sec-cms.domain.at so of course the Frontend is also reachable as sec-cms.domain.at/kontakt and the static site is reachable at domain.at/kontakt

    I don′t feel well to know that sooner or later a crawler will come by, and I will have the same wp-admin issues again as before.

    So my question: Is there something to do, that this URL is simply not reachable or even on the radar of anybody or anything except me?

    Thanks again for your help and answer in advance.
    Best, Mikkel

    Plugin Author patrickposner

    (@patrickposner)

    Hey @mikkelcrunch,

    thanks for the follow-up!

    The solution you are looking for is called Basic Authentication.
    We have a pretty detailed guide (including code examples) in our documentation here: https://docs.simplystatic.com/article/67-how-to-set-up-basic-auth

    Cheers,
    Patrick

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Hi,

    thanks for this link.

    A .htaccess already exists in the root (Apache). Where would I put in the new one?
    Or do I add this lines into the existing one?

    Best regards
    Mikkel

    Plugin Author patrickposner

    (@patrickposner)

    Then you can add the code directly into the existing file:

    AuthType Basic
    AuthName "Access to the WordPress website"
    AuthUserFile /path/to/.htpasswd
    Require valid-user

    Just make sure to add a .htpasswd file (and adjust the path within the code).

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Perfect – it is working!

    Thanks for your time and this great Plugin.

    Mikkel

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Ok,

    this was too early, I did the last step to give Simply Static Access for export.

    Saved it, went over to the Export the whole thing. Nothing happened, so I did “Cancel Export” – nothing happened. Refreshed the page – now my Backend is gone. 500 Error.

    Is there a trick to get back?

    Mikkel

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    I removed the Password in the htaccess. Now it is working again. I double checked the path and all of it – I did manage to get to the Password Question, but couldn′t get in, but they are the right credentials. I′ll try it tomorrow.

    Thanks
    Mikkel

    Thread Starter MikkelCrunch

    (@mikkelcrunch)

    Ok, after realizing that I have the Pro Version it was kind of easy to set it up ??

    Good evening!
    Mikkel

Viewing 10 replies - 1 through 10 (of 10 total)
  • You must be logged in to reply to this topic.