bernhard

Done 🙂 Just realized that this update actually breaks a lot of the functionality provided by RockFinder3 - so it's critical to get an update for this! 😐

Hey @adrian would it be possible to make the panels open in fullscreen on shift-click? I think that could be a great benefit not only for the console but also other panels with lots of content!

Thx, is removed 🙂

I really don't care a lot about those things (neither the plus icon nore the favicon), but couldn't you also set the page title to something like: #DEV# xxx on the dev site and leave the favicon untouched? 🙂

That just happened with the latest commit 🙂 Thanks! Didn't think of that and that would have really made the development difficult! I'll post a comment in the issue 🙂 Thx for clarifying. I also don't like them, but it seems that Ryan likes them, because we have this setting in /wire/.editorconfig trim_trailing_whitespace = false Thx, just enabled the setting in VSCode as well 🙂

Thx @adrian works a treat 😎 I have slightly modified it so that it checks if Tabulator exists before loading it. Seems you have some code prettifier active: https://github.com/baumrock/RockFinder3/commit/2863b76e9109673d7095e08d5d0d9b6ad5193f3c What are you using? I've followed this issue and was a little afraid something would break anything in rockfinder, but I did the upgrade just before posting this topic and everything seemed to work. If you are referring to the screenshots containing "old" values instead of bind variables that's just because I made them before upgrading the core. Or is there anything I missed out or need to check again?

How does it look on your end? Why not use the fontawesome icons we already get shipped with PW?

True. Do I state somewhere that you need to use the processmodule for dumping?

Please try the latest commit 🙂

Hey @adrian a thank you is not enough!! The console was so helpful while building the new version of RockFinder - I hope you have a use for RockFinder3 so that you get something back for your brilliant work! 🙂

Thx @adrian does the error disappear when you remove the "created" column?

Combine the power of ProcessWire selectors and SQL Differences to previous RockFinder modules RockFinder3 comes with extensive docs 😉 RF3 supports chaining: $RockFinder3->find("template=foo")->addColumns(['foo']). RF3 fully supports multi-language. RF3 makes it super-easy to add custom columnTypes. RF3 makes it easier to use custom SQL statements. No bloat! The module does just do one thing: Finding data. This module is built to stay, so I'm quite sure there will be no need for RockFinder4. The concepts are proven and used in many of my modules. RockFinder3 has seen some major refactoring and reduces LOC compared to RF2 by more than 50% from 1220 to 560 😎 I love the new API and if there where needs for changes the API should stay untouched meaning no need for a breaking version update in the future. ### ATTENTION ### The latest DEV version of ProcessWire breaks RockFinder3 (and all previous RockFinder modules); See here: https://github.com/processwire/processwire-issues/issues/1173#issuecomment-633284519 DOCS & DOWNLOAD: https://github.com/baumrock/rockfinder3 I'll do some more testing in the near future and add it to the modules directory once it proves as stable as I expect it to be. Thank you ...for using RockFinder3. If you find RockFinder3 helpful consider giving it a star on github or saying thank you. I'm also always happy to get feedback in the PW forum! Happy finding 🙂

That's what RockMigrations is for 😉 I've thought about a similar thing back in 2016 because I didn't know better (https://processwire.com/talk/topic/14603-rocksvn-brings-version-control-to-your-fields-templates/ ) but migrations are the way to go. The new migrate() function makes it very easy to build reusable setups: https://github.com/BernhardBaumrock/RockMigrations#migration-config-files

Thx for the interest everybody! I'm in contact with @elabx and @Sephiroth and we will try to build something useful and document the process so that everybody can learn from it. Similar to what ryan planned with the events fieldtype, but step by step, so it's easier to follow 🙂

Sorry, I can't get that to work properly and I don't want to hunt through all the options... Yes, it could. I thought about that. But I'm loading the tabulator library only if there is a RockTab field rendered on that page. Not sure - maybe it would be better to load those scripts automatically? It would be cached anyhow... Might be the better solution! RockFinder does actually not use Tabulator at all - that's a different module 😉 So as it is just used for testing/debugging finders a processModule that loads tabulator via CDN ist the best option imho 🙂