Robin S

It seems you must define the multidimensional array in $config in a single statement: $config->imageSizes = [ "foo" => ["width" => 12, "height" => 34], "bar" => ["width" => 56, "height" => 78], ]; Someone else may know the reason for this.

Unfortunately not. The submenu is positioned absolutely by JS and if I set a translate transform or a negative margin the JS accounts for it and places the submenu further to the right so the result is the same. The first submenu vertical position is okay (no gap), it's the horizontal position of the second nested submenu that's where the gap occurs. Edit: just noticed that the gap appears in Chrome too, so it's probably deliberate. Mousing over the gap doesn't cause the menu to collapse in Chrome but it does in Firefox. Edit2: nope, not deliberate because the gap doesn't appear for every dropdown menu - just randomly.

Issue occurs for me in both Firefox and Chrome. Narrowing it down as you suggested, it seems to be the "FieldAndTemplateEditLinks" submodule that's related.

AOS is preventing the normal rendering of an AsmSelect in the field settings for a RepeaterMatrix field. With AOS disabled the field below renders as an AsmSelect: The AsmTweaks option is not active and there are no errors in the JS console. The AsmSelect becomes operational after the field settings page is saved (the problem occurs when creating a new matrix type).

I went with something relatively tame - a Google image search reveals some truly horrendous pics.

For one site I did this... Created two roles - member and pro-member (pro-member is user with active subscription, with permission to view certain pro-only pages). Added expiry field to user template, as adrian suggested. Users can register for free - they get the basic member role with permission to post comments, limited view permission, etc. If a member purchases a (non-renewing) subscription via PayPal: pro-member role is given to user expiry date is set according the duration they purchased and pro-member role is given to user Daily Lazy Cron job: checks for users with subscription expiring in next three days and emails a reminder to renew subscription removes pro-member role from users with expired subscription

A: They're both big in Germany Not a scientific measure for sure, but for forum members who choose to disclose their location Germany seems to be the most common country. I'm curious about why ProcessWire would be especially popular in Germany. Was PW featured in a popular German-language publication or something like that? For German members (or any members actually): how did you first hear about PW?

Thanks for the tip - will try that for the main menu dropdowns.

This may be caused sub-pixel rounding, creating a 1 pixel or sub-pixel gap between the button and the dropdown. The main menu dropdowns in the default admin theme have a similar issue (in Firefox anyway), causing the menu to collapse as you move to the submenu unless you do it quickly. Looking for a fix for this is on my todo list.

Yep, that's it - removing the rule fixes the issue. The rule is on the html element actually: html.aos.AdminThemeDefault { overflow-y: scroll; }

I tried a few different things trying to get sub-selectors to work in the selector array format and I couldn't get it working either. Maybe someone else will chime in with a tip - otherwise I'd say it is a bug and you should create a GitHub issue for it.

I'm seeing an issue in Firefox where dragging a repeater item causes the item to jump upwards away from the cursor position. Perhaps something to do with offset from the bottom of the viewport, because the issue is particularly noticeable when the browser dev tools panel is open.

Did you try this as a non-array selector and it worked? Just wondering if there could be something in there that stops it working in any form of selector.

Pretty much anything is possible with PW. Make a start by yourself and if you have any specific problems just ask in the forums.

It does work! I tried to use Firelogger back when Tracy Debugger was first released and couldn't get it working. Really glad to be able to use that tool now.

You only need to force a new variation if there is an existing variation that was created with different quality, sharpening or upscaling settings. Once you have got rid of these existing variations you don't need to keep creating new images as that's a waste of server resources. From that point forward PW will serve your variation with the custom quality setting. If you are sure you want all your images with quality 60 then you could set that in config.php. Or if it will vary use the options array when you get the image via the API, as you are doing. If you want to do a one-off clearing of variations site-wide there is a module for that, but note the warning about variations used in RTE fields.

Yeah, but don't leave it in there permanently or you'll be recreating the image over and over again needlessly.

You probably have an existing image variation from before you set a custom quality setting. PW looks to see if there is an existing variation for an image before it creates one. This works well for variations of width and height, but unfortunately the quality, sharpening and upscaling settings are not recorded in the image name so you have to force a new image if you change one of these settings. Some time ago I made a wishlist post about this. You can clear the variations for an image via the admin, or you can temporarily add 'forceNew' => true to your settings array just to create the variation, then remove it. $option1 = array( 'quality' => 60, 'upscaling' => true, 'cropping' => true, 'forceNew' => true, );

Sadly Firelogger for Firefox hasn't been updated since 2013 and isn't compatible with the current version of Firebug.

Thanks for the bug report. If you grab the latest version from GitHub the issue should be fixed.

Hi @bernhard, Nothing wrong with having two similar modules out there. I'm always looking at other people's module code because it helps me learn, and I expect others are the same. The more modules, the more to learn from! I noticed your module has the same oversight that I just fixed in mine: a Page field doesn't necessarily return a PageArray (i.e. 'single' Page fields) so methods like has(), add() and remove() won't work in all cases.

@alexcapes, just pushed a fix to GitHub that allows ConnectPageFields to work with 'single' Page fields.

Hi @tpr, In agreement with what others have said, this is a hugely useful module and I really appreciate the work you are putting into it. The recent Esc key shortcut for closing notifications is one more excellent addition. Everyone's preferences are different so it's nice to be able to activate only the features you want. As well as the bold styling in the page list I mentioned earlier, there's another recent CSS change I can't see an option for turning off: the centered submit button on modal windows. Maybe there could be a checkbox list for individual CSS tweaks?

Tried it on another machine and the icons are there. Suspect it's because my main PC has a touch screen and PW falsely identifies it as a mobile device or something like that. Will file a GitHub issue for this because there are many large screen touch devices out there with mouse attached and PW should account for this.

Not quite sure what you mean. In the Chrome screenshot above I'm logged in with the same superuser account. Also tested in a clean PW 3.0.40 installation without AOS and no other modules installed. Still don't see the debug or quick-tree icons in Chrome or IE11.