adrian

I have pushed a fix for this, but I have discovered that Ryan's recent changes to the admin live search functionality has broken restricting of search results. I am working on this now, but could be a bit painful.

Thanks - I see the problem - it's to do with the way ARB blocks pages when viewed in Lister and because the Users page in PW uses Lister, it is causing the problem. I should have a fix shortly.

Glad I stumbled across this post - ARB should not get involved with displaying users - is there anything special I need to do to reproduce?

Just the default icons to give you guys an idea, but how's this looking? Still not sure if Debug Mode icon on should be orange or red? Perhaps I should check if on local dev or live server and go with grey for the former and red for the latter where it really is important!

Honestly I am starting to feel like this is something that should be solved by the PW core - I don't really feel like messing around with hacky solutions for this. @iank - would you be willing to submit an issue to the PW github account? I am honestly not sure if this should be an issue or a request, but I feel like it's strange that normal fields allow for an easy fallback, but module settings don't, so maybe it's an issue?

Sounds good - I don't think you need to go creating them - probably just need to spend some time looking around for better free ones, but whatever you think would be great. I think regardless of how you go about creating or finding them we should wait till you have them all ready before committing any changes.

Also, if there are any icon geeks out there, I'd love some help to revamp the icons on the debug bar - many of them are very ugly ? Any takers?

I just wanted to clarify that the grey/green/orange/red color scheme is already in place and has been since the beginning of the module. As per my mockup above I am more than happy to make all the icons that don't need this scheme grey instead of PW pink or PHP purple, or blue (the System Info icon). Hopefully we're all good with that change. I think this approach of grey instead of green to indicate no attention needed will be fine - I can't currently see any reason not to make this change. I think there will always be some difficulties in determining what should be orange and what should be red, although I do think that if we get rid of green altogether it will actually be simpler, for example I always felt a bit weird about debug mode set to on resulting in red. I think a new grey / orange only combo is probably much nicer. Orange being a warning that you need to be aware of the fact that it's on and this is a security concern on a live site. No problem at all - as with most things, Tracy has evolved and wasn't really planned from the beginning, so more than happy to revisit this stuff now and I really appreciate everyone's input.

Hi @iank - sorry, I have no idea how ProCache will handle this - I have never used it. Regarding dealing with fallback if empty - I think the only way to logically do this and also consider @tpr's point about allowing for an intentional blank value is maybe to only fallback when a field is required. I think that will work fine for this module. What do you both think?

Doesn't say much, but #3 on a list of the 6 best alternatives to Drumlapress: https://www.geckoandfly.com/27533/wordpress-drupal-joomla-alternatives/

Hi everyone - @netcarver has mentioned to me that he's not a fan of some of the ambiguity of the icon colors in the debug bar - mostly the blue for the System Info icon and the PW pink color used by the PW Info and Captain Hook panels, and the purple used by the PHP Info panel. I have quickly mocked up a version where these are all grey: He wanted me to poll you guys to get some input on this change and also any other changes you might like to see. In general the idea with icon colors is: grey - no significance green - everything ok - no attention needed orange - warning or attention to a new entry/item of interest red - warning, fail, or something else that you should be aware of So please post your thoughts - what do you think can be done to make it look cleaner and also more meaningful/useful? Thanks!

Typically the simple solution for this would be to drag the Tracy debug bar out of the way - this will work so long as you don't have the "Fixed Position" option checked in the config settings.

I had the same thought actually - thanks for bringing it up here. I do feel like in particular with module settings that it's something that shouldn't be hard to populate all languages with - it's not the same as new pages added to a site where you really can't enforce a site editor to populate all the alternate language values.

Thanks for testing. I have done the same here and can confirm your results. The problem is that I don't think PW has an inbuilt method for handling fallbacks for module settings. Because modules settings don't return an object you need to explicitly get the required value based on the user's language. I could write something custom in this module but I am curious if any of the ML experts out there have dealt with this when they have module config fields that have: 'useLanguages' => true

Love it ?

I have looked into OpenCollective and even suggested it to @tpr for AOS - the problem is that they require you to have 100 Github stars on a project before they'll accept it. So if you guys want to help out, send some star loving ? Obviously the PW core could get involved, but I don't think there are any modules with 100 stars yet.

Hi @martind - sorry about that. I am not sure when this started happening, but I feel like PW's file compiler is no longer correctly dealing with adding the namespace to classes in modules. Anyway, I have implemented a fix - please check the latest version and let me know how it goes.

Hi @iank - sorry about that - I honestly never tested this in a ML environment. Could you please check if the French values show if they are entered? If so, then we just need to make the fallback to default work if no alternate language values are entered.

Have a go and if it goes well, great, and if not, I'll try to find some time to pick up where you get stuck and get it working.

Hi @masslevel - Table field support could certainly be added to BCE. It already supports other multi-value field types using a separator like: | You could add code for Table fields here: https://github.com/adrianbj/BatchChildEditor/blob/339624b0a14a9f403ae73b37a08f3e0f5f8d6136/BatchChildEditor.module#L1608 You should be able to find the code you need here: https://github.com/adrianbj/TableCsvImportExport/blob/a4e6ad668fd92f668546ba62cf726d29871b6d05/TableCsvImportExport.module#L341 If you can add this, I'd be happy to accept a PR for BCE.

Hi @bernhard - I have upped them to 9999 here locally - I'll commit it to the next version. Hi @rick - that might be possible, but I am curious about why you want this - for me it's about quickly and temporarily getting every Tracy related hidden so I can see what's behind on the main page content.

Check out pw-remove in the Removing elements section of this post: https://processwire.com/blog/posts/processwire-3.0.49-introduces-a-new-template-file-strategy/

Take a look at this post (https://processwire.com/talk/topic/19024-selector-arrays-with-page-reference-fields-with-and-not-or/?do=findComment&comment=165462) and the rest of the thread. I really like the concept of selector arrays and they can make things much more readable and avoid concatenation stuff, but currently they can be a little tricky to get things how you want. Hope that helps.

Thanks @tpr - very generous of you to spend your time doing this! The ".pwcmb--top_push" class is no longer used - it was an option but it never seemed to work, so I removed the config option but never got around to cleaning up the other parts - thanks. Agreed, I don't see that cookieMonster.cfg.block being used anywhere. I have tasked someone else with testing this version - making sure all the GTM events fire as expected, along with the basic functionality, but if anyone here also wants to check, that would be awesome. Once we're sure everything is working, I'll incorporate into my repo (I'll get you to do a PR). Thanks again for this - I am sure many folks will be very appreciative of this new version!

Thanks ? It's a decent start, but I am kinda hoping for some contributions from the community for improving it. It's all available in the docs folder (markdown files) in the repo and anyone can edit and submit PRs. I think a nice Tips & Tricks section would be beneficial, as would improvements to the rest of the docs.