Outward

Thanks, I had to check whether I'd ever tried this! Turned out I had, unfortunately it doesn't stop saves being made from the API or front-end, so I think I need to look towards hooks to disabling the key functions like adding, saving and trashing pages.

Hey everyone, I'm looking for advice from anyone who might have built a demo site using ProcessWire with user login. I have a site that's accessible only via login, and I'd like to create a demo for them to browse around. Everything happens in the front-end, so users are already locked out of the admin panel. It uses the API for just about everything in terms of creating/updating/trashing pages. My idea is as follows: Use the users session info to create a user account and pre-fill login data. Let them log-in any browse around, but not make any new/save/trash page actions After 60 mins, run a lazy cron that will delete their temporary account I'm struggling on point #2 and whether there's hooks or similar I might use. Of course I don't want to show errors, so ideally I would define a pop-up via hook to say for example 'Saving is disabled for this demo'. I think I could manage that if I knew what I was targeting! Has anyone done similar? I know the Skyscrapers site disables saving for example. Thank you!

Brilliant talk Bernhard - I picked it up through the PW Weekly over the weekend. You're a great spokesperson for PW on the whole and of course very talented - I use your modules like RockAwesome and RockMailLogger on just about every PW instance. Now I need to learn more about Latte!

@ID Studio Web Agency The whole concept used across the site is beautifully executed. Kudos!

Fantastic work Jonathan, you should be very proud of this project!

I'm looking forward to using your module Bernhard. I have written an application in ProcessWire over the past year, and 3 months into development I started kicking myself for not starting from a multi-site perspective. Now with this I can see a solid workflow for migrations whilst benefiting from keeping users locked in their own instances. Having now read the docs I'm keen to try it out with a single new feature that will require several templates, fields and pages!

I really like your implementation of ingredients as pages, as well as the structure of your recipe template - I've not yet brought RepeaterMatrix into my workflow but now feel I may have wasted a lot of time not doing so! You mentioned a little about SEO text and the first thing that struck me when browsing the recipes is that unlike most recipe blogs the ingredients and recipe is the priority. So many food blogs force you to scroll through walls of text to get to the recipe. I understand it's for SEO, reducing bounce rate and creative writing - but most don't even provide an anchor to the recipe! Great work and I imagine you had a lot of fun building it.

Hello, I've been adapting Soma's great Page Edit Soft Lock module for a project that keeps trusted users editing in the front-end. This works great for the Dialogue editor as it hooks to 'ProcessPageEdit::execute', as in the example below: As well as the dialogue editor, I use inline editing for several CKEditor fields, e.g.: <div edit="events"> <!-- code to output events --> </div> Is there any way to hook into inline editing? Thanks!

This module is 8 years old and it still works beautifully. Kudos Soma!

Thanks for the module PWaddict, very useful for my current use case. I'm building a site with numerous roles, none of which have access to the admin panel as everything is done through the API and front-end editing. I had to enable view access for some templates, so the only 'look-in' to the top level page tree is through a trusted user adding a link in CKEditor fields. It's nice to have a module that focuses simply on the main page tree, so I can still define page reference fields for hidden templates where the role still has view access, and they display fine.

If I'm reading this right, you can do this by creating a page reference and specifying "template=repeater_yourfield". You should be fine in terms of access, but you will want to test using their role if they aren't superusers. If the select box is blank for the user you can use a custom find for the page reference and add 'include=all' or check permissions.

Hello all, I'm having an issue with allowing front-end edit of Users for a non-superuser role. It's an 'administrator' role with most permissions, however it's locked out of the administration panel (aside from through modals and ajax). I've created the appropriate permissions for the user to edit users (under specific roles). If I turn off the redirect out of the admin, the user can view and modify users, yet the edit modal does not open in the front-end. This isn't an issue for the Superuser, and the modal opens fine. Anyone had this issue? Thanks! Edit: On further inspection, I can even access the modal directly in the browser at a URL like the one below: /admin/access/users/edit/?id=1040&fields=display_name,email,user_inactive,photo,bio,location,user_phone&modal=1 It seems the front-end modal just will not trigger, can't see anything in the console either.

This is a fun, simple project I built over the holidays and really goes back to what initially drew me to ProcessWire several years ago after being inspired by Ryan's Skyscrapers Demo. Backwards Compatible allows searching and browsing by various performance related tags and game pages display detailed data on each title. List of modules used: Import Pages by CSV - Essential for this kind of site, the vast majority of data was imported in one CSV upload Procache - Invaluable after an influx of 650k page views in 6 days(!) Form Builder - A simple implementation for monitored page updates and YT video submissions Soma's AjaxSearch Mike Rockett's Sitemap Additional styles/scripts: Bootstrap Grid only for CSS Fancybox.js Tippy.js Commento

Thanks for a great module Teppo. I don't suppose anyone has had success recording version control changes with front-end inline editing? I'm using inline editing on a personal project with just one specific field which is a large textarea (the rest use dialogue editor - works great). Edit: Silly me, Version Control changes are indeed recorded with in-line editing. The field is within a repeater, so the front-end editor only saves changes to the repeater ID. It's still saved to the appropriate Version Control database tables.

Are you using PHP 7 or above? '??' is a null coalescing operator added in PHP 7.