Leaderboard

Honestly I would find another host - having chmod disabled is likely to continue to cause problems.

RockGatekeeper A lightweight ProcessWire module that provides simple password protection for your website using a configurable gatekeeper password. Overview RockGatekeeper adds a basic authentication layer to your ProcessWire site. When enabled, it blocks access to all pages for guest users unless they provide the correct password via URL parameter. Features Minimal footprint: Only runs when gatekeeper is configured Session-based: Once authenticated, users stay logged in for the session IP tracking: Remembers the IP address of authenticated users Clean URLs: Automatically removes the password parameter from URLs after authentication CLI safe: Won't interfere with command-line operations Installation Copy the RockGatekeeper folder to your site/modules/ directory Install the module in ProcessWire admin Configure the gatekeeper password in your site config Configuration Add the gatekeeper password to your site configuration: // In site/config.php $config->gatekeeper = 'your-secret-password'; Usage Basic Authentication To access the protected site, users need to append the password as a URL parameter: https://yoursite.com/?gatekeeper=your-secret-password After successful authentication, users will be redirected to the same page without the password parameter, and they'll have access to the entire site for the duration of their session. Download & Docs: baumrock.com/RockGatekeeper

Ok that might be the official record 🙂 Works a treat! Thanks and greetings from Bavaria!

Glad if it is helpful! I have just pushed an update to the dev branch 🙂

I went ahead and finished the installation to see what happens and I got this error which is bizarre to me: Error: Exception: Template 'admin' is used by the homepage and thus must have the 'guest' role assigned. (in wire/core/Templates.php line 287) I can't understand why the home template got replaced by admin which should not be publicly accessible. I'm pulling my hair out.

Module has been updated to 2.2.39 including the fix.

First of all, hats off to everyone involved in the redesign! I can only imagine the countless hours that must have gone into this project – really impressive work. Of course, a redesign will always divide opinions. Some will love it, some won’t – that’s the nature of design (a bit like beer: there’s no accounting for taste). But let me share a perspective from my three decades of experience working with clients: 99% of paying clients couldn’t care less about what CMS powers their site. What matters to them is that the website looks good and feels professional. The ones we really need to convince are the second tier of decision-makers: the people who will actually use the system day-to-day. These users are rarely designers. They don’t care much about animations or typographic finesse – what matters to them is clarity, ease of use, and a sense that the CMS won’t get in their way. That’s why, in practice, we almost never show clients a backend during the decision-making phase. Instead, we show them beautiful, carefully crafted frontends, and sometimes highlight the inline editing capabilities. That sells. Clients are impressed when they see polished websites that “might be running on ProcessWire” (since, let’s be honest, you can’t tell a CMS from the frontend anyway). How this focus on real-world client priorities could be reflected more strongly in the redesigned ProcessWire website is something I’d love to explore further. Cheers, Mike

I'm confused. Isn't ProcessWire primarily the tool we want to convince more developers to use in order to gain a larger user base? So this page should primarily be used to convince developers of the advantages with examples (sorry to say that) instead of animations that have nothing to do with ProcessWire. To convince customers of the system, it would be better to provide a good demo that shows how simple ProcessWire is to user. However, this could also be done here, among other places: https://www.softaculous.com/apps/cms/ProcessWire

The main metric for an open-source website is converting visitors into software users. However, the main issue with the open-source adoption cycle is that there is a years-long gap between users becoming aware of the project and actually starting to use it. Overall, the goal of any rebranding is to maintain recognition while solving new challenges for the brand. The level of visual identity change for ProcessWire would be acceptable in the case of rebranding when a product has totally failed, but that's definitely not the case here. This redesign will likely result in a dramatic failure of adoption for PW among new users because they will not understand that PW is something they were familiar with before. There are hundreds of CMSs and random visitors don't remember ProcessWire by name alone, and all visual branding on the new website has no brand consistency from the dozen years of the previous PW website. The new website (as commenters in other threads noticed) simply "hey what happened to my browser bookmarks, it‘s not PW." It's hard to provide suggestions without understanding what goals the new web design is solving, but I can recommend at least changing the German interface on the first screen to a screenshot with skyscrapers, because they were there all along and are strongly associated with PW even through new designs. @ryan, please don't take my word for it and instead look at the metrics. Something like PW downloads or PW module downloads per month compared with the same period in the previous year should show the real effect of this redesign. Update: there are some performance issues that result in over 200% CPU overload on the first page.