adrian

Nope, 18 was a brand new version (after your bug report). Sorry, I missed that line - I did get the one (and one other) from your initial report, but that was one I missed. The latest should hopefully be OK now.

@gRegor - thanks - should be fixed in the latest version. Note that PW's core might also suffer from this here: https://github.com/processwire/processwire/blob/3cc76cc886a49313b4bfb9a1a904bd88d11b7cb7/wire/core/WireInput.php#L991

Fantastic @Robin S - I hadn't been paying attention to AVIF browser support for a while, but it looks like we are finally good to go: https://caniuse.com/avif Just a minor thing but I just added AVIF support reporting in Tracy:

This functionality is now available in 3.0.236 and now seems to work with AJAX loaded repeaters as well.

@bernhard - how about as a title attribute like this when you hover the Tracy icon? This way it's available if you want it, but it doesn't affect anyone otherwise.

Hi @TomPich - the latest version allows blank default filters and hides the parent selector (I moved it from defaultSelector to initSelector).

You might find this useful: https://processwire.com/modules/page-rename-options/

If you're getting that message after clearing the flag, then it means there are more errors being logged. The whole idea is so you don't get multiple emails each time an error is logged, so once you fix the code that is causing the error, you clear the flag and it won't appear again until another error is logged and emailed to you. Make sense?

@tires - an addition to the regex on this line (https://github.com/adrianbj/GetVideoThumbs/blob/31a7fb443abd1b1cb9143840954f3f25d52d4fe5/ProcessGetVideoThumbs.module.php#L129) should be able to support it. If you want to give it a go and send me a PR, I'd be happy to include it. PS - that said, most of the videos on piped don't seem to play for me - some do, but it's pretty hit and miss, so maybe not a very stable service at the moment.

Thanks @bernhard - should be fixed in the latest version. It looks like at some point PW starting deleting the fieldgroup along with the template automatically, hence the new error.

It is weird to me seeing all those paths like "ProcessWire\UserPage.php" in amongst the other full correct paths. They are clearly not valid and will trigger errors for any open_basedir restrictions. So it does seem like a question for Ryan from what I can see.

Hi @bernhard - I am not sure why PW is trying to an is_file() on ProcessWire\BasicPagePage.php because that's obviously not a valid path. Perhaps you could assist by checking back through the stack trace to see where it is coming from. The referenced line in the RequestInfo panel is a $p->child() call, so not sure how that alone could be triggering this error.

@nexuspolaris - the screenshot you posted is not for the settings tab of that page. Please enter those field pairing in the BCE settings on the Settings tab.

@artfulrobot - sorry, I really don't know. I haven't ever seen this or had anyone else mention it. Is it specific to one server / machine, or can you reproduce on others?

Thanks @Laegnur - I have committed those changes to the repo.

The field pairings is only available from the Settings tab of those pages selected under Configurable pages. Does that help?

Thanks - that has taken care of things. I actually think there are lots of modules that get loaded via CLI scripts even though they aren't needed. I kinda think PW should have a module autoload option for this to make it easier / more obvious to the developer to disable via CLI unless needed.

That would make sense, except I have been running 8.2 on that server for many months and the error started appearing immediately after updating Jumplinks from 1.5.61 to 1.5.63. Yep, that should work just fine. Just a little FYI about something I have noticed in the past - sometimes $_SERVER['REQUEST_URI'] returns false rather than the URL or NULL (https://github.com/nette/tracy/issues/351) which means checks need to consider that. Obviously not relevant given your CLI check. PS - thanks so much for continuing to support your modules even though you're no longer using PW - very generous indeed.

@Mike Rockett - sorry, I should have come with more details - looks like it's happening from a cron executed PHP script that bootstraps PW. That would explain why it's null. I'm not sure why it's a new error though - on a quick scan I can't see anything from your most recent commit that would cause this change.

Hi @Mike Rockett - brand new issue with the latest version: PHP Deprecated: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in ProcessJumplinks.module.php:206 EDIT: I see that line hasn't changed recently, but I've never seen the error before on the same server with no recent PHP upgrades. Regardless, it still needs a fix please and thanks.

Have you tried a hard reload in the browser? I know it sounds strange, but I have seen PW return cached results before. Please let me know if that works.

Actually, something to consider - what about on Windows - wouldn't that need the extra slash because instead of the filepath starting with a slash it would start with a drive letter.

Yeah, I know about this and not sure there is an easy way around it, but it fixes itself after a modules refresh.

Hey @bernhard - you can change this in the module settings in the "Editor Links" section. Just change: vscode://file/%file:%line to: vscode://file%file:%line I'll change the default value and note in the next version.

At a quick glance, it feels like you are missing a level when getting the video. You need to get the video_field from the select_video, but instead you are getting video_field from $item. Does that sound right?