adrian

Thanks @teppo - I knew I had seen it somewhere before :) I have a very long Content tab and so didn't notice it at the bottom. Thanks!

@teppo - I could have sworn this was already an option I'd seen, but can't find it now, so what do you think about having a LoginHistory tab (or fieldset on the Settings tab) on user pages?

@elvina - I've added some basic ML support (for text based fields) so hopefully it will now do what you need. Just a note that I couldn't even get a simple ML Text field to show results (they were in the DB but not in the table) when adding via the admin GUI. Textarea fields worked though, so that is what I used to test this. Hopefully if Text fields work for you, the import should also work for them.

Well, it took a long time, but the Console tabs are now available in the latest version - turns out there were actually a lot of things left to do which took way longer than I expected. If anyone finds any issues, please let me know. Please note that you will have to do a hard reload to get the tab CSS working - the way the core Tracy package loads CSS I can't seem to figure out how to bust the caching of it.

Thanks @Robin S - all fixed in the latest version.

Thanks @Robin S - I have fixed the history forward icon - I honestly have no idea why I used the left arrow and flipped it :) I have also changed the behaviour if a snippet is already open in a tab and also added scroll into view for the tabs as needed (if lots are open and some are out of view due to horizontal scrolling). Anything else you can see that needs attention before release?

@Robin S - just occurred to me that my fix for the history issue won't work if you upgrade your already upgraded version, so if you do that, please delete these localStorage items manually so that they will be automatically re-created in the right format. https://github.com/adrianbj/TracyDebugger/commit/9d7d42501ead93460d27cda4829eed780239c2aa

Thanks @Robin S for the testing, much appreciated. 1) Sorry, I thought I had dealt with all upgrade issues but missed that one 2) Yeah, that is the intended behaviour - I was treating it as a way of loading up the saved version in a separate tab without losing any potential changes to the currently open version. I know it's different to how VSCode (and probably other editors) work though, so maybe I should reconsider. Anyone else have thoughts? 3) This was also an upgrade issue - the structure of the history stack needed updating but wasn't being overwritten if it already existed. 4) I am not seeing this pixel issue - any chance you could help narrow that down: Latest commit should fix 1 & 3 Thanks again.

Happy new year everyone! I've been working on adding multiple tab support for the console panel. It works in conjunction with the snippets panel so you can load up multiple snippets, or create any number of temporary (unsaved) tabs of code. Each tab has its own execution history stack and the last result for each tab is also maintained so you can flip between tabs to see the differences between results. It automatically names tabs like a typical code editor does: Untitled-1 initially, and then using the first line of code. Of course when you save the tab to a snippet, the tab name will be that of the snippet filename saved to disk. I'll push it live soon, but if anyone sees this and would like to test and provide feedback beforehand, please take a look at this branch: https://github.com/adrianbj/TracyDebugger/tree/console-tabs Thanks!

The hooks info that Tracy shows is basically a copy of what is shown in PW's Debug Mode Tools (using getHooks()) and AFAIK it's only hooks that are triggered by AddHookAfter/Before calls. From what I can tell what Bernhard is showing is all hooks that are run as PW is booting up - there are lots of entries missing in that list. Not saying that it's not a useful list, but they are very different things. Unfortunately it seems that Tracy isn't available at the point that runHooks() is called, so I couldn't replace your log file approach with a bd() call so at the moment it will need Ryan's input to make it possible to display this list in Tracy.

@bernhard - available in the latest version.

@artfulrobot @ryan - I wonder if some of the new techniques described here would help?

Thanks for the help debugging @elvina - I have a new version which should work for you. Note that at the moment it will only work if your CSV has an empty column for the image field, but I also have the code in place to support importing images and files, but there is a bug in the Table field which I need to get @ryan to fix before it will work. Here's the report I prepared for Ryan which includes a hacky fix to get things working if you do want to import images:

That line #1189 suggested there is an image subfield/column involved: I wonder if there is some old image field that wasn't properly deleted. If you look at the database table for the table field, does it contain any unexpected fields? Or maybe the json settings for the field have reference to an image field? Can you please try on a new table field built from scratch with just the fields you need and see if that still has issues?

It looks to me like it has something to do with your table settings under the "What pages should be selectable?" section. Can you try a simple example with just a template, eg: If that works, then maybe you can help to figure out what selector is causing the issue.