Password Protect Single Page - Question | JoomShaper
🎃 Halloween Sale is Live! Get 35% OFF on all plans. Sale ends soon! Get Offer

Password Protect Single Page

J

johnny

SP Page Builder 7 months ago

I'm using Joomla 4 with SP Page Builder Pro. I have a hidden menu item pointing to an SP Page Builder page that displays some basic text and images.

Although the menu item is hidden, the page is still accessible via direct URL.

For a test project, I’d like to password-protect this page — no username or user login, just a simple password prompt. When a visitor lands on the page, they should be asked for a password. If entered correctly, the content is revealed.

I know it’s not secure — this is just for testing purposes.

Is there a way to implement this easily?

0
5 Answers
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 7 months ago #188885

If I may, Fully possible, but You have to use premium component for Password Protection.

For example:

  • JLex Block (jlexart) - I used it for Joomla 3 and Joomla 4 sites.
  • Page and Article Restriction (miniOrange) - I used ones, but worked well.

Is there a way to implement this easily?

Yes, but you have to buy an extra extension :/

1
J
johnny
Accepted Answer
7 months ago #188980

Thanks Paul. I did see this extension, looks like it's the only way! It's surprisingly difficult to protect a Joomla page with just a password. I'm not even bothered about security, it's not a production site - it's simply a test on a demo site.

0
Atick Eashrak Shuvo
Atick Eashrak Shuvo
Accepted Answer
Support Agent 7 months ago #188882

Apolozy for the inconvenience. Unfortunately, there is no option to achieve this using SP Page Builder.

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 7 months ago #188982

To protect site or pages from guests (not wanted) users I use different methods (free), but this topic is beyond JoomShaper support.

0
Paul Frankowski
Paul Frankowski
Accepted Answer
Senior Staff 7 months ago #188983

Since Joomla 1.0 nobody implement that inside the CMS core. It was always a extra installed feature.

0