MarkE

Thanks a lot. I’ll give that a go.

Yes I have, thanks - but that limits users to just one branch. In my case, I need them to access more than one branch. I tried the "role-based" approach, thinking I could set up a role for each of the relevant branches and then assign those, but I couldn't get it working. In any case it wouldn't really meet my requirement which is to just display pages of the relevant templates - restricting page-view for the templates does this, but with the consequences I described.

The access mechanisms for PW seem pretty powerful, but a bit complicated. I'm struggling to do something that i thought would be quite simple but I keep tripping up. The pages in my site include a large number which are not rendered - essentially a database - but they are outside the "admin" section. I have a number of roles to which I need to provide access to selected groups of these pages in the back end. It is easy enough to limit the "edit" access by template. Because it would be confusing for the users to see a tree with a load of pages not relevant to their roles, I would also like for them not to see the pages to which they don't have edit access. So I removed their "view" access to these templates. However, they can still see them in the back end, because of inherited rights from the "guest" role. Now, I needed the "guest" role to be able to view many of the pages because that is the role used by webhooks and batch runs invoked by LazyCron. So I thought perhaps I could set up separate roles for them and add those roles to their guest role in the API when they run - that way I could reduce the default "guest" access to just renderable pages and give enhanced access to other roles as needed. However, this does not seem to work. The role is shown as being added, but doesn't actually seem to provide the additional access rights to the "guest" user. What is wrong with my approach and is there a better way of doing this?

It is just hard-coded into your module on line 62: $this->modules->duplicates()->setUseDuplicate("AdminThemeUikit", "/site/modules/AdminThemeUikit/AdminThemeUikit.module"); I tried picking up the path root from $config instead: $this->modules->duplicates()->setUseDuplicate("AdminThemeUikit", $this->config()->urls->siteModules . "AdminThemeUikit/AdminThemeUikit.module"); but that didn't load the css so I also changed lines 71 & 72 to $config['cssURL'] = $this->config()->urls->site . "assets/RockSkinUikit/theme.less"; $config['logoURL'] = $this->config()->urls->site . "assets/RockSkinUikit/processwire.svg"; Interestingly, these files had been installed to /site-ncog/modules/RockSkinUikit/assets, so I had to move them manually. (Leaving them where they were gave a server error.) Now it's working nicely ?

wire>core>ModulesDuplicates.php (line 200-201) is looking for a pathname of /site/modules/AdminThemeUikit/AdminThemeUikit.module, which will only be the case in a single-site installation - the installed modules are in /site-ncog/modules/AdminThemeUikit/AdminThemeUikit.module and /wire/modules/AdminTheme/AdminThemeUikit/AdminThemeUikit.module.

Yes. I'll take a look as suggested.

Not sure I understand. /wire/modules/AdminTheme/AdminThemeUikit/AdminThemeUikit.module is part of the core /site-ncog/modules/AdminThemeUikit/AdminThemeUikit.module was put there by your module

Just trying to install this. I set AdminThemeUikit to be the site module, but I still get an error message on installing: Unable to install module (RockSkinUikit): Duplicate module pathname must be one of: /site-ncog/modules/AdminThemeUikit/AdminThemeUikit.module /wire/modules/AdminTheme/AdminThemeUikit/AdminThemeUikit.module

Thanks a lot for that. I see that ASM and auto-complete both work without a parent and with a template. From a practical point of view, given the size of the list, ASM select is not really suitable. Auto-complete looks favourite. Ideally one would be able to use auto-complete but revert to a list select if that yields nothing, but I think that auto-complete with a sufficient number of fields to search in gets me there. BTW, the initial problem in my OP is still a bit of a mystery. I wonder if there is some sort of bug. Now I have it working (and can see how it is supposed to work), I can see that the problem was caused by an "improperly selected" parent - in other words, there was no selected parent, but the box to select it showed "change" and had a spinning icon whenever the field was opened to edit. Selecting a parent and then unselecting it fixed that problem.

Update. It allows me access if I set a parent page for the page list select, as well as a template. However, I don't want to do that, as the pages could have different (and not predictable parents). I just want to select on template (or maybe a custom selector). Having selected a parent, I then unselected it and I no longer get the error message, but the template selector is not working - pages with any template appear to be selectable.

Hi. I am signed in as Superuser. I have a very simple template ("List") for an email list, being a title and a page reference field. The page reference field is a multi-select (page list select multiple) for a particular template ("Member"). I can modify the title, no problem, but if I try to add a member I get the message "You don't have access to list page". If I change the field to ASM select, the dropdown is empty. I have removed access control from the List template and and the page reference field, but no joy (and in any case I am superuser). I have another field to link back the other way which works fine. I set this up a while back, and tested it without leaving the fields populated and have just returned to work on it. It also worked well with @Robin S's excellent ConnectFields module. The only relevant thing that I think has been changed in the meantime is that I moved the Member pages under different parents, but the parent was not and is not part of the selection criteria for the page select. What is going on?

Thanks for the helpful suggestions. I'm taking a look at MailGun - looks like the right fit for my needs plus a decent API and a good PW module.

I have a system with about 100-200 pages of members. Being a small local group, it’s unlIkely to get much bigger. There will also be some pages for different mailing lists, with many-many links between members and lists. I will want to send custom emails to each list (prepared using an “email” template). I have wireMailSmtp installed. Is that good enough for the job, or would people recommend a dedicated email service like Mailgun or Mailchimp? Any thoughts on pros and cons are welcome.

Thanks. Very helpful. In fact, I’m thinking of going for listerpro now, especially for the page actions. Is this hookable in a similar fashion?

Is it possible (in a custom module) to supply a variable to a lister page? My custom module ("ProcessReports") simply lists a number of reports (mostly lister bookmarks). Some of these bookmarks have a filter using a date comparison and I want the module to supply a date (based on the current date) before displaying the lister, rather than the user having to change it each time.

Unfortunately, quite a few modules (including Form Builder) use modals.

I've noticed that both the Reno and UIkit admin themes are responsive when accessing pages, but this doesn't apply to modals. If viewing on a relatively small screen (say iPhone 5), part of the modal is always off-screen. Is there a fully responsive theme anywhere? If not, what would be required to achieve it? Or is this a pipe dream? Thanks.

It seems to me that access control in PW is powerful but quite complex. Does anyone know of a tutorial/blog etc. that covers these complexities. I particular, how to make sure that the end result achieves the required access control. From what I have learned so far, a number of things interact: • Whether a page is published, unpublished or hidden • The access given to users of a template • Field level access – both global and as over-ridden in a template • Whether or not a template has an associated php template file • The output formatting of a page, set in a php script (false can disable field-level access controls) These need to be considered in combination to determine what is the actual level of access in any situation. Is there any way of getting an overview of all this? For example, if there is no guest access to a template then that restriction will also apply to any API invoked by a guest action which requires access to a page instance of that template. The only way I can see to allow API access but to prevent direct access is to allow guest access to the template, but not provide a template php file. Is this secure? Also, if fields have restricted access (e.g. no guest access), then any API invoked from the front-end (including webhooks) will not be allowed to see the contents (this is achieved by blanking the contents in formatting). Over-riding this can be achieved either by setting the relevant option on the Access tab of the restricted fields, or by turning off output formatting for the affected page just before accessing it (e.g. $p->of(false); ). See discussion at

Yes. I just mentioned it because it is very big and full of things like <span class="tracy-dump-indent"> | | </span><span class="tracy-dump-key">fuel</span> <span class="tracy-dump-visibility">protected</span> => <span class="tracy-dump-object" ... I have no idea what it does.

... just having a root around - I seem to have 12mb session file - is that normal?

It seems to be all pages. It was fixed after a reboot last time. I'm inclined to blame windoze - that's the usual source of my problems. Meanwhile, I'll turn Tracy off until I need it then reboot again...

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 33764184 bytes) in M:\xampp\apps\processwire\htdocs\site-ncog\modules\TracyDebugger\tracy-master\src\Tracy\Helpers.php on line 133 Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10530816 bytes) in Unknown on line 0

Thanks, but as you say - it ought not to be necessary. Anyway, today it is working ?

It seems to make no difference which panels are enabled (or even none). However, unchecking the "Show debug bar" removes the error from the front end or back end accordingly.

Just got this error message: Fatal Error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 25956352 bytes) (line 27 of M:\xampp\apps\processwire\htdocs\site-ncog\modules\TracyDebugger\tracy-master\src\Tracy\assets\Bar\panels.phtml) Any idea what might have caused it or how to fix it? I uninstalled the module and the error went away. After re-installing it, the error came back. The message at the bottom of the screen reads: Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 10563584 bytes) in Unknown on line 0