adrian

Thanks guys for the donation request - stay tuned @Zeka - I am sure we can figure something out. I am having trouble reproducing at the moment - could you perhaps provide a full code example that I could test?

I was just thinking of appending a checkbox at the top and using that as the toggle. Maybe like this: http://jsfiddle.net/NogginBox/ScnQT/1/ or maybe with this extra checkbox directly above Option 1.

Hey @tpr - curious if you'd be an option for adding a check/uncheck all option for InputfieldCheckboxes ? If you're not, just let me know and I'll cook something else up, but I think it might be a nice addition to AOS. Thanks for considering!

Hi @barneyy and welcome to PW! Perhaps you'd be happy with this AceEditor module instead? http://modules.processwire.com/modules/inputfield-ace-extended/

Thanks @ukyo - I have deleted that new module from the directory. Not sure about deleting this topic though - I think it's still a worthwhile discussion - perhaps it might be worth editing the opening post to note what's happened?

To follow up from @teppo's point - is there any reason your old WireMailPHPMailer need to exist? I assume it's because PHPMailer 6 requires PHP 5.5? It sounds like Ryan might be moving PW to a 5.5 minimum sometime shortly, so maybe it's ok moving forward.

Thanks Robin - you saved me some time figuring this out - much appreciated. I have pushed this change to my fork here: https://github.com/adrianbj/processwire-fieldtype-assisted-url

Thanks for changing it to extend WireMail! I am curious why PHPMailer would result in better scores at mail-tester.com than WireMailSmtp or WireMailSwiftMailer. Do you have any idea why?

Thanks @joshuag - just curious - did you also take a look at the rrule code icon idea I brought up?

@ukyo - thanks for your work on this! Please don't take this as a criticism - it's an honest question - why did you decide to not extend WireMail? I am sure you have a good reason. I think there might be other reasons as well, but the first limitation I see is that Tracy's Mail Interceptor won't work with this, nor will the new Mail Debugger module. My other question is about your choice to make InputfieldHelper a requirement. I read through the support thread for that module and I still don't get it. I am sure I am missing something and it is probably very useful for certain tasks, but I do think it will be a barrier for getting people to install your WirePHPMailer module, especially when there is already three other working mail modules. Perhaps if you could better explain the advantages to this over those other mail modules, it might help. Cheers!

Several nice improvements over the last few days: 1) Major improvements to panel zIndex behavior - this should make things much less annoying - no more trying to get your panel of interest to be on top of another one. Mousing over the panel icon should now always bring it to the top, but with already open panels, now they only get promoted to the top if you click somewhere on the panel. Before it was onmouseover which made it quit annoying at times. Also panel order is remembered when reloading the page. 2) Console panel will no longer disappear if you use the keyboard shortcut to run code without having clicked somewhere on the panel first - much friendlier. 3) ESC key to close all open panels - I am finding this really handy already. I don't think this interferes with any other use of the escape key, but let me know if anyone thinks this should be optional. 4) Add test email address option to the Mail Interceptor panel - this was mentioned in another thread, but added here in case anyone missed it. If no address is entered, it behaves how it always did - it prevents the email from being sent and instead captures and displays what would have been sent. If you add a test email address, in addition to it's normal behavior, it also sends the email to the test address (but still not the original recipients). 5) Various bug fixes - especially in the Request Info panel when viewing certain module settings pages. As always, thanks for any feedback on these new features!

I'd like to have more people see this as well. I'll let another moderator pin this if they see fit, but in the meantime we have 30 new stars since this post - much appreciated to everyone who took the time, but I am sure we can do much better! I promise I won't gratuitously bump this again

Nice work @joshuag - looks like it's all sorted here!

Thank you @horst for everything you have done for images in PW - you deserve way more recognition than you are getting!

Glad you made friends with Tracy > My PW version is 3.0.61 That might be the problem. I would definitely recommend upgrading to the latest dev version. Many of us are using it on production sites and it will likely become 3.1 stable this week or next.

Check out the PW cheatsheet - it's on there. Thanks for noting the error if no matches are returned. Not sure if @bernhard fixed that further along in that thread - I know he tweaked things quite a bit.

https://caniuse.com/#search=requestAnimationFrame

Glad you figured it out. Could you also reduce this down to one loop by making use of has_parent in the selector? Not sure your structure, but might be worth investigating.

That's why approach I linked is so easy to work with - let PW take care of getting all the matched IDs and then getting the fields you need from that match via SQL. At least I think it helps your situation, although honestly I didn't read through this thread very thoroughly, so maybe I am not getting all the issues.

You might also find this interesting: https://jsperf.com/requestanimationframe-vs-setinterval-loop/7

This is where I first read about it: https://swizec.com/blog/how-to-properly-wait-for-dom-elements-to-show-up-in-modern-browsers/swizec/6663

@theo - here's another approach that you might like to add to your arsenal. Note that this was just an experiment on my part and there will be an upper limit on using the results of findIDs in an SQL query like this, but if you follow the rest of the discussion on that thread you'll get an idea of the pros and cons. https://processwire.com/talk/topic/15524-preview-rockdatatables/?do=findComment&comment=158104

Would requestAnimationFrame be useful here? It's become my goto method for waiting for an element to exist.

Great! I just took a look at the Tracy log file scanner code and I am actually extending PW's core log file find() method which seems to have a lot of operations for chunking and limiting the number of lines read so at the moment I don't really know why it's not working efficiently. I'll keep it in mind to revisit at some point, but for now, this is definitely a good reminder for others to check this if things seem to be slowing down lots.

I have actually had this happen once before - it's why I implemented the "Delete All Logs" button. It seems that when a file gets huge, it can cause problems. Maybe I can make the reading of the log files more efficient - I'll take a look.