ErikMH

As things stand, is it possible to get the same sort of functionality for auto-compiling .less files for front-end CSS — like, put the .less files into the right place and add a line to config.php? If not, I see hints of how I might begin to script that sort of thing in @ryan’s post, but I’m sure I wouldn’t be able to figure out the fancy timestamp checking, &c. (Old-school applications programmer/systems analyst here, but still pretty new at PHP, Unix, &c.) I’m game to experiment, if someone could point me in the right direction. Thanks!

I’m a nearly brand-new ProcessWire user, and I’ve got to say I’m really impressed — not just with this functionality, but with how easy @ryan and @bernhard have made everything. I installed the new version of PW on my cloud server, installed the Less module, updated config.php and put a few Less statements into admin.less — and had it all working perfectly within about 15 minutes. Nicely done!

Ooh, thank you for this pointer, @wbmnfktr. I’ve done just what you suggested!

Excellent, @elabx — thank you again. It turns out it was the fingerprinting (not the sessionChallenge) — and I’m guessing it’s because I’m using Cloudflare’s 1.1.1.1 WARP for my local connection. I’ve removed the sessionChallenge override, and moved the sessionFingerprint line down in site/config.php to the spot that would correspond to where it is in wire/config.php. Everything’s still working, so I’m happy and I’ve learned something. Thanks! Onwards, through the fog!

Those were not in the file to un-comment, so I added them. Not knowing where to put them, I put them at the very top of the file. And — bingo! — I can log in! Yea! Thank you! Now.... Can you tell me what I’ve done, why those lines weren’t already in the file, and where I should actually put them in the file? Not at all — that’s an excellent question. I did explicity set it that way — but you’re right: I should’ve explicitly mentioned it here. Thanks for thinking of it!

I’m new to Processwire. I’ve installed the current release version at my very-long-time (25 years) host, pair Networks. MySQL db is created. Installation process completed with no errors. I’m now trying to log in. Rather than taking the default `/admin` suggestion, I chose `/xyzzy`. When I go to `example.com/xyzzy`, PW displays a login screen, as expected. I enter the username (`xyzzy`) and password that I assigned (and copied and stored in 1Password) in the installation process (five words separated by hyphens). So far, so good. I would expect then to be taken to the admin pages. Or (if I got something wrong) to be given an error message. Instead, I’m taken to the URL `example.com/xyzzy/page/?login=1`, which as far as I can tell is exactly the same as the initial login page. No error is given. I grew so frustrated by this, that I deleted the entire installation and the MySQL database, re-downloaded PW, installed it again using a different username and password for the admin account. And I’m seeing exactly the same behavior. Time for me to ask you experts: WTF? Many thanks for any insights you may have....

It took me a while to find this; I thought I’d link to it in case others wanted to see it:

wbmnfktr is right that there is a Bitnami folder. By default on macOS, you’ll find it hidden at ~/.bitnami — though I can’t tell you about other systems. However, you won’t find your standard ProcessWire folder there. Instead, you’ll need to do the following: 1. In the Bitnami ProcessWire app, go to the Volumes tab and tell “/opt/bitnami/” volume to mount (see attached screenshot). 2. You should now find an NFS volume mounted in your OS (by default named with your Bitnami ProcessWire’s server address). There’s useful information in the /bitnami/README.txt file on that volume. 3. You’ll then want to head on that volume to /bitnami/apps/processwire/htdocs/site/ — this is where you’ll find folders for your site’s assets, modules, and templates. Despite the reference to “exported” in the Bitnami window, it’s “live”: creating a new template file in the templates folder will make it available to your running ProcessWire server.