bernhard

= I have not thought about that, but it's a good idea and easy to implement. = I have not thought about that and I'm not willing to add any other services. ? ?

Hi @Mats thx, this has been on my wishlist for quite some time ? Have you thought about also integrating other services like https://www.pexels.com or https://pixabay.com ?

@psy Could you please try to get https://github.com/BernhardBaumrock/tabulator.test running - then we'd have the same environment wich would make debugging / helping a lot easier!

Hi @psy Does it work if you change that to ->addColumns(['title', 'booking_status']) ?

Hey @dotnetic could you please change the translation of "move" from "bewegen" to "verschieben" ?

Seems that things changed slightly ? This worked for me today: Translate file /wire/modules/Inputfield/InputfieldDatetime/types/InputfieldDatetimeText.php Set path: /wire/modules/Jquery/JqueryUI/i18n/jquery.ui.datepicker-de.js Search keys: datetime, date picker, monday, translate, sunday, german

Hi @Crowdland Technology Thx for the report - the wrong version compare is fixed in v1.0.7 ? I'd need more info on that - what is the exact query you used? What is your setup? What is the output (dump+sql)?

Another question: Any ideas how I can transform this: into that: ? ?

v0.0.11 adds support for repeater matrix fields ? Thx to @aComAdi of https://www.a-commerce.ch/ for sponsoring this update! ? $rm->setMatrixItems('your_matrix_field', [ 'foo' => [ 'label' => 'foo label', 'fields' => ['field1', 'field2'], ], 'bar' => [ 'label' => 'bar label', 'fields' => ['field1', 'field3'], ], ]);

Hey @Sebi have you thought of registering $twack as API variable? // in your module $this->wire('twack', $this); // in any template // no need for $twack = $modules->get('Twack'); $general = $twack->getNewComponent('General');

Didn't take that as offense at all ? Just tried to make clear that I have already thought of that but I don't plan to implement it any time soon. But if anybody would be up for it, I'd be more than happy to assist or to pull the changes ? Sorry if that was not clear.

Thx for that report @elabx ? The other module works totally different. My migrations can be run from anywhere, anytime. That makes it a lot easier to use but of course this has drawbacks. Keeping track of with migrations have already been applied is more complicated. I'm not sure how that could be done exactly. But I have to say that since I'm using RockMigrations I have not REALLY needed such a feature. My main goal was to make the changes as easy as possible. Migrations can always be applied several times so it does not really matter if they have been applied or not. But I'd love to have a good concept for that and since RockMigrations is totally free and open source I invite anybody to contribute and improve it ? I have lots of other more important things to do. Command line support sounds interesting though. But I'm not sure if that would bring a huge benefit compared to the tracy console. And even more I wonder if it might make a lot more sense to have a command line module that can be used by any other module. Not one that is locked to RockMigrations...

Good point! Populated ?

Sorry, of course you get the ids! ? But you can already be enough depending on your situation. Do you dump lots of data? Or is in-memory an option? What does that mean? How do you know? How does a tracy dump look? Did you follow the docs? https://github.com/baumrock/rockfinder3#relations Did you already read about callbacks? https://github.com/baumrock/rockfinder3#callbacks

Do you guys have a recommendation how to sort method names of a class by their name alphabetically? Thx ? // turn this Class Foo { public function foo() {} public function bar() {} } // into that Class Foo { public function bar() {} public function foo() {} }

Ok, now I get it. If you used a page reference field on your order template that holds all related invoices you'd get exactly the output you want just by adding this field as a column in the finder. Another option is using relations: https://github.com/baumrock/rockfinder3#relations 3rd Option is building your own column type: https://github.com/baumrock/rockfinder3#custom-column-types

What kind of fields do you have? Page reference? Repeater? That's all necessary informations... What finders did you try already?

// not tested class TextformatterP2BR extends Textformatter { public static function getModuleInfo() { return [ 'title' => 'P2BR', 'version' => '1.0.0', 'summary' => 'Textformatter that strips all <p> and replaces </p> by <br>', ]; } public function format(&$str) { $str = str_replace("<p>", "", $str); $str = str_replace("</p>", "<br>", $str); } }

Hi @zoeck, could you please provide an easy to grasp example (like cats and dogs) with example data and the output you want? // template cat id | title ----|------- 1 | foo 2 | bar

Thx @zoeck I've added a shortcut method getRepeaterTemplate() for that: https://github.com/BernhardBaumrock/RockMigrations/commit/dd741064cd19b661bdcb441cdabe153b3abe8e57

Hm, that's interesting - I didn't think about that ? I think it's not too late for that change and will make using RockFinder3 easier, so I just committed that change, thx!

Very good news for the weekend: RockFinder3 does now work again with the latest dev version of PW (thx to @adrian for making Ryan aware of the issue that also affected tracy!) ? v1.0.6 is up and running smoothly and ready for a long future ? $owners = $rockfinder3 ->find("template=person") ->addColumns(['title', 'age']) ->setName('owner'); // set name of target column db($rockfinder3 ->find("template=cat") ->addColumns(['title', 'owner']) ->join($owners) ->getSQL()); SELECT `pages`.`id` AS `id`, `_field_title_5ed16c868e555`.`data` AS `title`, GROUP_CONCAT(DISTINCT `_field_owner_5ed16c868e66d`.`data` ORDER BY `_field_owner_5ed16c868e66d`.`sort` SEPARATOR ',') AS `owner`, GROUP_CONCAT(DISTINCT `join_owner_5ed16c868ea01`.`title`) AS `owner:title`, GROUP_CONCAT(DISTINCT `join_owner_5ed16c868ea01`.`age`) AS `owner:age` FROM `pages` LEFT JOIN `field_title` AS `_field_title_5ed16c868e555` ON `_field_title_5ed16c868e555`.`pages_id` = `pages`.`id` LEFT JOIN `field_owner` AS `_field_owner_5ed16c868e66d` ON `_field_owner_5ed16c868e66d`.`pages_id` = `pages`.`id` LEFT JOIN ( SELECT `pages`.`id` AS `id`, `_field_title_5ed16c868de1f`.`data` AS `title`, `_field_age_5ed16c868dea8`.`data` AS `age` FROM `pages` LEFT JOIN `field_title` AS `_field_title_5ed16c868de1f` ON `_field_title_5ed16c868de1f`.`pages_id` = `pages`.`id` LEFT JOIN `field_age` AS `_field_age_5ed16c868dea8` ON `_field_age_5ed16c868dea8`.`pages_id` = `pages`.`id` WHERE (pages.templates_id=48) AND (pages.status<1024) GROUP BY pages.id ) AS `join_owner_5ed16c868ea01` ON `join_owner_5ed16c868ea01`.`id` = `_field_owner_5ed16c868e66d`.`data` WHERE (pages.templates_id=44) AND (pages.status<1024) GROUP BY pages.id PS: I decided to change the case of the API variable from $RockFinder3 to $rockfinder3 (all lowercase)!

No. migrate() is just a shortcut array syntax. You can always combine both: $rm->migrate([ 'fields' => ['foo' => ...] ]); $rm->setFieldOptionsString('foo', ...); ? No. Pages for the win. A lot easier to handle in many situations (Migrations, RockFinder, ...). But I have a custom Repeater implementation... Maybe the need for migrating repeaters will arise one day for me and maybe I'll implemenet something then if nobody that needed it earlier did submit a PR...

Hi @zoeck See setFieldOptionsString() method I guess I've never came up with any migration for repeater fields, so this might need some custom integration. PRs welcome. I don't use Repeaters at all these days ?

There's at the moment no concept of pagination in RockFinder3, because it was initially built to build the data array for client side datatables that do the pagination and sorting on the client side. Could you please explain your use case a little more? Why is a regular $pages->find() no option if you get the data paginated anyhow?