Robin S

For my CKEditor fields the "B" (Bold) button does apply the strong tag. I think the Format dropdown is for block-level elements.

Does reversing the sort order help? sort=-my_repeater.my_checkbox

If I have a Lazy Cron hook with an interval of "everyDay", when during the day does the hook fire? Is it every 24 hours from whenever the hook is first set or is it tied to a particular time of day such as midnight every day?

Nice work! Just a heads up that on the International page the map marker for the export to New Caledonia is actually sitting on New Zealand, not New Caledonia.

I doubt it makes much (or any) difference in terms of performance but you can do the same a bit more briefly like this: $items = $page->children("sort=title"); $items->prepend($items->find("featured=1, sort=timeon"));

Thanks for the suggestions. Going down this road could lead to a very fractured roles setup, and kind of amounts to treating each role like a permission. But that does give me the idea of solving this via custom permissions that can be shared by two or more roles. Which is probably the way to go.

Just installed PW3 so I could get a closer look at the new images field. The appearance and interactions are both really slick. Some feedback: I think having the option to get an overview of which images in the field are landscape vs portrait, which have descriptions and which have tags is very important. The aspect ratio thing could perhaps be solved with a toggle between fit and fill for thumbnails. But for the description and tags I think we need to be able to toggle to something like the old list view. Not being able to see these things across all images would be a real annoyance in some situations. I think there needs to be a max-height set for images in the enlarged view. As @titanium pointed out, some images could be very tall and narrow and at some point the enlarged view will get excessively tall. Perhaps the enlarged image area should be defined as a 1:1 ratio and the image scales to fit.

From what I've read on the forum I believe the Dynamic Roles module has some serious bugs and probably should not be used for production websites in its current state.

The new user-admin permissions introduced in v2.6.10 are great, but I don't think they work in quite the right way. Suppose I have these roles: superuser editor member guest The two of interest here are editor and member. Editor is a site editor/administrator and member is a front-end-only user. There are various restricted front-end pages that guest does not have access to - the member role is needed. Users with the editor role have also been given the member role, so they can browse the front-end as a member would. It is possible to set the site up differently so editors do not also have the member role and restricted front-end access is given to member or editor, but in principle roles are meant to be cumulative so it's not unusual for a user with a higher-level role to also be given a lower-level role. The problem comes when editor needs to be given admin access to the Users section. What is desired is that editor can only edit users with the member role alone (and the guest role of course). At first glance you would think that giving editor the user-admin-member permission and not the user-admin-all permission would achieve this. But if the role has user-admin-member permission it also gives the ability to edit other users with the editor role. This should not happen in my opinion. It would be better if the user-admin-[role] permissions worked such that a role needs to have the permissions for all the roles another user has before they can edit that user. So to edit another user with the editor role the permissions needed would be: user-admin-member user-admin-editor Hope I've explained this well enough.

Tracked the problem down to any field roles field having access restrictions for the role. It's possible to get the listers working again by checking the "Make field value accessible from API even if not viewable" option, but still seems like a bug to me so issue filed at GitHub. Edit: perhaps not a serious bug now I have discovered the issue only stems from access restriction on the roles field.

When attempting to change the field dropdown on any lister (e.g. Users section, Find), users with a non-superuser role just get a spinner. Looking in the browser console I can see: .../access/users/?InputfieldSelector=opval&field=name&type=&name=filters 503 (Service Unavailable) The role has the page-lister permission. Superuser can use the listers normally. Any ideas what can cause this?

v0.0.2 - follows better module naming conventions. https://github.com/Toutouwai/ProcessHotKeySearch/ I've become aware of an issue when using the hot keys in Page Edit where the page has unsaved changes. On hitting enter on a selected search result the unsaved changes popup is bypassed - not by the selected result URL but by the fallback behaviour of the search box itself, which navigates to "/page/search/?q=..." Am trying to find a solution to this. Any suggestions welcome. Fixed now in v0.0.3

I made a little module to address this issue.

My first module release. GitHub: https://github.com/Toutouwai/HotkeySearch ProcessWire module that adds configurable hot keys for easier use of the admin search via the keyboard. Uses Mousetrap for key bindings. Module provides two hot key bindings: Jump to and focus admin search input. Also handy for quickly getting to the admin menu tabs when they have scrolled outside the viewport. If you change your mind, tab out of the search input and press the hot key again and the viewport will jump back to your previous scroll position. Uses 's' key by default. Trigger link for focused search result. If you use the arrow keys to highlight a search result this hot key allows you to trigger the link from the keyboard. Uses 'enter' key by default. The hot keys are configurable in the module settings. Hot keys only fire when you are not inside an input, textarea or select. This module is only intended for use with the default admin theme. Admin Theme Reno already binds the up arrow key for closing the search input and doesn't show a visual highlight for search results focused via the keyboard so the module would be less useful there. Much credit goes to Soma's AdminHotKeys module. As an aside, I'm don't know if the admin search was meant to allow result links to be triggered with the enter key by default. I noticed a Javascript error when focusing search results but not sure if that's to blame.

The admin search is great because I find it the fastest way to move around admin. But is it possible to select a result from the list via keyboard only? When results are showing I can move the highlight up and down with the arrow keys but Enter does not navigate to the selected item. Is there some other key that does this? I use the default admin theme and I'm a Windows + Firefox user if that matters. Edit: there is a Javascript error associated with the search module which may be the cause of the Enter key not working as expected.

Thanks, all solved now as per the edit to my post. Just needed to uncheck "Enable Test Mode" in the module config.

This is the first time I've used WireMail and WireMail Mailgun and I'm having a problem where mail is showing as delivered in the Mailgun logs but nothing appears in my inbox, or in spam folder. Solved: see edit below If someone can confirm I've followed the installation and setup correctly... 1. Open account at Mailgun, choosing domain mg.mydomain.com 2. Set up TXT, CNAME and MX records for mg.mydomain.com at domain registrar, according the values provided by Mailgun. Mailgun verifies these records are set correctly. 3. Installed WireMail Mailgun module 4. Configured WireMail Mailgun module, filling out all fields. Unchecked "Disable cURL SSL Check". Default Sender Email Address: no-reply@mg.mydomain.com (does this need to be an address where there is an actual mailbox to receive replies?) 5. Tried to send test message by putting the following in a template file and viewing from frontend: $mail = wireMail(); $mail->to('myaddress@gmail.com')->from('no-reply@mg.mydomain.com'); $mail->subject('Testing Mailgun'); $mail->body( 'Just testing.' ); $mail->send(); In the Mailgun dashboard I can see entries in the log for mg.mydomain.com like Test delivered: no-reply@mg.mydomain.com → myaddress@gmail.com 'Testing Mailgun' But no mail arrives to me. Mailgun does not show any bounces or errors. The label "Test delivered" makes me wonder - is Mailgun in some sort of test mode? I'm not using the sandbox feature. Looked for entries in /site/assets/logs/mailgun.txt but no such log exists. Is that normal? Any help much appreciated. Edit: I obviously should have looked more closely at the module config. Maybe this should be unchecked by default? Yeah, excuses, excuses...

I have a date-only field configured as below and its unformatted value returns as a timestamp.

@adrian, when used in a selector, doesn't a datetime field return the unformatted value, i.e. a timestamp? So it should be okay to compare it with a supplied timestamp. Also, as I've been learning recently, you can use relative time words directly in a $pages->find() selector (but not in PageArray filter selectors) $allNews = $page->children("template=news, date<=now"); // edit: this doesn't work Edit: ha, and now that I pay attention I see that of course that isn't a $pages->find() selector, so would need be written differently to have the minor convenience of using relative time in the selector : $allNews = $pages->find("parent=$page, template=news, date<=now");

Nice!

@Soma, What do you think about adding an option to prepend the Home page (just that single page) besides the "show_root" => true option? The problem I'm finding with show_root is that it cancels the usefulness of using a PageArray for the root page argument. Take this example: $nav = $modules->get("MarkupSimpleNavigation"); $main_sections = $pages->find("parent=1, template=foo"); $nav_options = array( "show_root" => true ); $menu = $nav->render($nav_options, null, $main_sections); Here I want to use a PageArray for my menu root items rather than craft a long selector to match those pages and all children of those pages. But I also want a link to the Home page in the menu. When I add "show_root" => true I also get every descendant of the Home page, which effectively cancels out my root pages selection.

Thanks, Github issue here: #1811

@BitPoet, thanks, your module works well in PW 2.7.3 Feel like extending it with an unpublish button for published users? :grin:

@adrian, in the thread you linked to you say Do you mean that this is actually the correct/desirable behaviour for an empty checkbox and therefore it is not a bug that checkbox!=1 does not match pages with empty checkboxes? Soma's Github issue is worded a bit differently so am thinking of opening a new issue, but just want to confirm that checkbox!=1 is expected to match an empty checkbox.

I don't think this step is necessary. Checking the page source of the Edit Page screen to see the rendered CKEditor config is revealing. For your CKEditor field: Edit Field > Input > Plugins > Remove Plugins Delete 'magicline' if it is shown here.