bernhard

RockMatrix --> thats a modules similar to RepeaterMatrix. When a matrix item is created, a meta entry stores the reference to the page, where the matrix item lives on. That's similar to the TrelloWire example ? RockMeta --> that are fields for the PW backend that do not store their value in their own DB table but in page meta-data. This is great, because I can add Inputfields to existing Inputfields to make them more flexible without having to create many fields in the system.

Not sure where I want to take this... At least it will be a successor of https://processwire.com/talk/topic/18166-processwire-kickstart/; Maybe more... Anybody here still using wire shell and wants to share experiences/learnings? How were you using it? What was missing? What did you like most? etc

Thx ? Here you go: https://github.com/BernhardBaumrock/RockMigrations/releases/tag/v0.0.26 I hope I'll get used to tagging and not forget about it in the future ?

Yeah, maybe I should get used to that. But for me they do not add any benefit... Maybe you could explain why they might be important for others?

I think this is a helpful post for anybody new to hooks: https://processwire.com/talk/topic/18037-2-date-fields-how-to-ensure-the-second-date-is-higher/?tab=comments#comment-158164

This is really easy either via RM or via default API: $modules->get('TracyDebugger'); // or $rm->installModule('TracyDebugger'); I'm using a GIT setup with submodules. So all I have to do is git submodule update --init --recursive That way I always have my modules under control of GIT and can efficiently commit new changes from any project that I'm currently working on ? But I went ahead and added support for rockmigrations via composer: https://packagist.org/packages/baumrock/rockmigrations Would be interested to hear if everything works!

Hi @Richard Jedlička, thx for your message ? Thx, that's a good point! I've added a new example file of how I am using RockMigrations nowadays that should be really helpful to get started with the power of RockMigrations and building easy, fast and reusable modules: https://github.com/BernhardBaumrock/RockMigrations/blob/master/examples/MigrationsExample.module.php You might not need this feature any more once you saw the new example file, but anyhow it was an easy update and I've made the getMigrationsPath() method hookable so you can use whichever folder you like ? I'd be happy to get a quick tutorial of how all that works and what the benefits would be and then I can take that into account. PRs are always welcome.

1.0.4 adds a litte new helper to add all fields of a template as columns: $rockfinder ->find("template=foo") ->addColumnsFromTemplate("foo"); 1.0.5: add getJSON() method

You should get some good inspiration here: https://github.com/processwire/processwire/blob/d8945198f4a6a60dab23bd0462e8a6285369dcb9/wire/core/ProcessWire.php#L410-L459 ?

1st: Make a backup!! I'd try setting the type of the field to FieldtypeText in the DB, then the error should be gone and you should be able to delete it. Or you delete the row in db table "fields" and then you delete the db table field_yourfieldname

Thx Robin for another great module! ? I'm always stripping down the interface of CKEditor as much as possible using your great hooks. I wonder where and why you'd be using this field? I think markdown is still too complicated for clients. I'm not using any of those nowadays. Maybe that's why I can't think of where to use this field at the moment. But I'd be happy to hear where you are using it and what you dislike with ckeditor (or why you built the module in the first place). The only thing that I really don't like is copy/paste issues with custom formatting that can get annoying. But there's also a solution for this here.

9 years later I hit the same wall ? I have a kickstart script that installs several modules. I got this error: ERROR: application encountered an error and can not continue. Error was logged. Then I found this log in /site/assets/logs/tracy/exception.log: [2020-12-14 20-17-00] ProcessWire\WirePermissionException: You do not have permission to execute this module - ProcessDatabaseBackups in \wire\core\Modules.php:1337 @ CLI (PID: 15532): site/modules/RockBuilder/kickstart.php @@ exception--2020-12-14--20-15--dd5f3e67ab.html When setting the user to the superuser everything works: <?php namespace ProcessWire; /** @var Wire $wire */ include("index.php"); $users->setCurrentUser($users->get(41));

Hi everybody, This is the php support matrix as of today: https://www.php.net/supported-versions.php @adrian has posted some findings regarding PHP8 here: I know someone who is running a ProcessWire installation on a server on PHP7.1 ?? Now I'm asking for this person: What would you recommend to do? Upgrade to PHP7.4 or PHP8 ? I'm a little afraid that PHP8 will bring in some issues and it might be a little too early to jump on that train now. Maybe the transition would be a lot smoother when upgrading to 7.4 now and jumping on 8 around mid-2022 (in 1,5 years). What do you think? Does anybody already have findings to share?

Welcome @Grigorij Schleifer, This does also look like a good tutorial and he is also working on mac ?

Maybe this module would be a better fit then?

Hm. I thought maybe I could strip the EXIF data from the image but did not have enough time to look into it. Do you know if PW has a method for that? Otherwise it seems to be 7 lines of code using php+imagick (which I'm using).

Yeah, good point. I have no idea... I have another problem in my app. I'm generating a PDF from a page with some images and one of them keeps getting rotated by 90°. Only one, all the other images work as expected. ?

Ok thx, I've refactored a little and that's totally fine, you're right ? $phc = $this->wire->modules->get('PageHitCounter'); $event->return = $phc->buildPageListHitCounter($page->phits) .$badge($type($page)) .$page->range->format() .", ".$page->title;

It will be back on the next update of ProcessWire unless Ryan fixes the issue in the core until then. So you either need to wait with that update or you apply the changes again after your upgrade.

@Robin S is a genius! ? Based on his posts in the github issue I did the following and finally got the bug fixed (it seems): For Server Side Resizing: Search for "$corrections = array(" in all your files. You should find 3 files: Replace those arrays with this one: $corrections = array( '1' => array(0, 0), '2' => array(0, 1), '3' => array(180, 0), '4' => array(0, 2), '5' => array(90, 1), '6' => array(90, 0), '7' => array(270, 1), '8' => array(270, 0) ); This did already fix my issue. Client Side: Replace PWImageResizer.js with this file created by @Robin S and delete the old minified version PWImageResizer.min.js to make sure that the new version is loaded: https://github.com/processwire/processwire-issues/files/4660217/PWImageResizer.zip Would be great to hear if that also fixed your issue @Mikael ? Thx again @Robin S for the great work!!

I have no solution yet. @Robin S seems to have found a way, but I had no time to test what he wrote in the issue. I was always hoping that Ryan will come up with a fix sooner than I have to build a quickfix on my own. I thought of adding custom buttons/checkboxes to rotate the image after saving... For now I've just added a comment that says "if the orientation is wrong please use this online editor and upload the image again" ?

Thx David, hm... reading this portion of code again, I think it would be a lot nicer to have a method on the page object for that: $event->return = $page->phcLabel() .$badge($type($page)) .$page->range->format() .", ".$page->title; What do you think? $this->addHookMethod("Page::phcLabel", function($event) { $page = $event->object; $cnt = (int)$page->get(PageHitCounter::PHCFIELDNAME); $event->return = $this->buildPageListHitCounter($cnt); });

This is a more than annoying bug that will hopefully be fixed sooner than later: https://github.com/processwire/processwire-issues/issues/1154 Please add a comment to the issue that you are also having problems with this. Hopefully it will get Ryans attention.

@dotnetic had a problem after upgrading to the latest PW. I've pushed a fix for this today to support PW 3.0.158+ https://github.com/BernhardBaumrock/RockFinder/commit/7d8e0a33a5ed0d0ffaf2b009689f523f7ec14ef6

? https://google-webfonts-helper.herokuapp.com/fonts