adrian

Ok, I think I understand your scenario now - you are trying to batch add pages on a remote server but the images are in a local path on your computer? If that's correct, then this won't work - you'll need to move the images to the server and adjust the paths but that should be a pretty simple search / replace in your text editor. For example, search for /Users/xxuser/Desktop/201124_Website/binary/ and replace with something like /var/www/site/assets/tempimages/ (or wherever you decide to FTP them to).

Hi @sww, I just checked with an image at a local path and it worked fine, but I think the issue might be the "file://" at the beginning. Does it work if you remove that?

The other thing you can do is check for a Tracey Bluescreen exception html file in /site/assets/logs/tracy/ - hopefully that exception would have been logged there and it will show the full stack trace.

@LAPS - the other thing to try is to enable PW debug mode (if it's not already). I have a feeling that with Tracy disabled and debug enabled, you'll probably see that error again. I don't know where the error is coming from, but I don't think it's Tracy - Tracy is likely just reporting it whereas otherwise it's going hidden and therefore not affecting the download.

What about the strict mode option?

Ok, sorry - I missed that. If you are running php 7.2+ it might be worth updating to the latest version of Tracy, although I don't really expect it will help. I am running out of ideas here, but perhaps you could try putting Tracy into strict mode to see if it provides a full stack trace of the error.

Ok, so what version are you using?

Change 2.8.x to 2.7.x

@LAPS - the error originates here: https://github.com/processwire/processwire/blob/d8945198f4a6a60dab23bd0462e8a6285369dcb9/wire/core/WireHooks.php#L520 I just checked out that other post - I don't think it's an issue with Tracy, but I'd appreciate it if you could try disabling all panels in the panel selector and see it that makes a difference. If it does, can you narrow things down to a particular panel for me? I'm also curious if it might be related to the latest Tracy core update. Could you try forcing 2.7.x by modifying this line: https://github.com/adrianbj/TracyDebugger/blob/94047302d6ffe3e933ee7d8eaf9514c192f2c50d/TracyDebugger.module.php#L333 so that it loads 2.7.x - be sure to hard reload the browser to flush the cache. Let me know if either of those help.

Ok, I get it now, but it is pretty confusingly worded - either that, or I am just a bit slow ? Anyway, it's easy enough to add, but do you think the icon should be displayed for all users, or just superusers? Also, which icon - the issue is that the key and lock icons are already used in the page tree for other indicators. The other question I have is whether to use the ProcessPageListRender::getPageLabel hook and add the icon as a "PageListStatusIcon" like the lock, exclamation icons are added by the core (at the end of the title in grey), or using the Page::getIcon hook which adds to the front of the page title and the icon is pink. I think the "PageListStatusIcon" option is more correct and looks nicer, but it means that it will be broken on sites that use that ProcessPageListRender::getPageLabel hook to modify the page titles - something I do on a few sites. Of course the other option would be if this wasn't included as part of the module, but rather those who want it can add it themselves with one of those hooks like this: $this->wire()->addHookAfter('ProcessPageListRender::getPageLabel', function($event) { $p = $event->arguments[0]; if($p->protected) { $event->return = $p->title . "<i class='PageListStatusIcon fa fa-fw fa-key'></i>"; } }); OR $this->wire()->addHookAfter('Page::getIcon', function(HookEvent $event) { $page = $event->object; if($page->protected) { $event->return = 'key'; } });

Well it sounds like that is a useful thing for it to alert you to ? - if you take a look at the RepeaterMatrixPage.php file, you'll see that the render() method isn't hookable. Perhaps You are probably looking for InputfieldRepeaterMatrix::render

Hi @SwimToWin - I am not seeing any issues with the page tree not showing, but maybe I am not understanding the scenario correctly. Any chance you could post screenshots showing the settings you have and the issue where the page tree isn't visible?

@jploch - I have committed those changes to the Tracy repo - let me know if it needs any tweaks.

Glad you got it working. The simple to figure these sorts of things out are to right-click on a field and "Inspect" to find the name of the field. Tracy's Request Info panel is also helpful to see all the settings.

$f->optionColumns = n should do the trick. I think that should apply the InputfieldRadiosFloated automatically.

Excellent point of course!

That's sounds great and if this is available, I wonder if this might change your answer to @Robin S's question about using this approach for all fields in PW. From my point of view I have always had a bit of a love / hate relationship with Tall-Thin vs Short-Wide approach to data storage in PW. There are obviously huge advantages in flexibility with Tall-Thin, and I know that in some cases they are more performant to query, but other times they are much less performant. While I don't expect moving the PW core in the direction of the Combo field actually makes sense, I do think that using it in certain templates for all fields (except page name / title) might make sense.

Thanks for the great post @ryan, but I am curious about this - why does the combo field have to load all subfields (db table columns). Why not have a way to select just the subfields we want? I know it's not a completely correct example, but think of SELECT field1, field2 FROM table vs SELECT * FROM table. Perhaps I am missing something about how it all works though?

@jploch - can you try the attached version please. Sounds strange, but it's actually a bit more complicated than expected just because there are a few ways that the bar can be enabled / disabled / hidden. I think I might have them all taken care of, but would be good if you could help test. Thanks. BTW, the class I added to body is: has-tracy-debugbar TracyDebugger.module.php

I'm not quite ready to move any existing sites to 8, but I will be developing all new sites on 8. I haven't seen any PW core showstoppers yet and I am happy modifying any 3rd party modules if the need arises (along with a PR of the fix).

@FireWire - not sure if you want to bother with this, but I just found out that DeepL doesn't yet support translating between US and UK English. I was hoping to be able to change things like neighbor to neighbour. I have contacted DeepL and asked them to consider supporting this. Strange thing is that you can actually translate from US English to Spanish to UK English, eg: neighbor -> vecino -> neighbour. Hopefully they'll support direct translation in the future, but until then I wonder if you want to remove that option from the Translation process module?

I am curious why you suggested this - I can't think of a reason not to apply it frontend as well?

Actually, regarding the name vs label in the first (header) row, I am curious what you think about the subfield for page reference fields. This module supports exporting other subfields of the selected page reference (ie not just the title), so the header row currently shows things like pr_location.title or perhaps pr_location.body - these look fine for field "names", but I am not sure how these should be best formatted formatted for field "labels". Perhaps with the title subfield, it should be just left off, but with the body example, maybe: PR Location > Body Any thoughts on what would look best?

I am using 7.4 on all live sites and 8 on my local dev setup so I can get my modules updated and help to report any PW core issues so Ryan can get these taken care of ASAP - I know he is typically slow to upgrade so needs us to report. I'll probably start using 8 in production in a couple / few months.

I'll take a look at implementing this. FYI - looks like I made a mistake about the OR selector - seems like it's still not working for page reference fields - you should ask Ryan about this on the Table field support board.