adrian

parent!=7

Tweaked, although I still like the "Toggle All" out on its own. I have also cleaned up the time/size values at the bottom of all panels - very simple now with no superfluous text.

Is this better? That's how it looks in the latest version.

@tpr - columns for the panel selector does sound like a decent idea. The Tracy core CSS is a bit of a pain - I already have to make one core hack because of the way they have things set up. I am actually using all: initial in one place already, but not everywhere. Maybe I'll revisit using it more. That's always been my thought too, but when I see what you have done with AOS I second guess that decision

Thanks for your thoughts as usual. I keep for forgetting about your screen real estate limitations. My laptop is 1680 x 1050 and my last one was actually 1920 x 1080 (from 2003) so I forget that people have smaller resolution to work with. I thought I took care of this recently - are you still seeing this problem? There are lots of things that I need to override but it takes time to come across them all. Please let me know whenever you find a CSS attribute that I have missed. What would the logical groupings be? I just made them in alphabetical order which I thought would be simplest. I agree that the admin settings could be improved. I'll admit I don't have @tpr's flare for that though

Have you looked at BatchChildEditor: You can move the interface to anywhere you want - either part of the Children tab, the Content tab, or even its own tab. You can predefine field pairings for the CSV columns to PW fields, etc. In Update mode it will update existing PW pages. You can also choose from Add and Replace modes depending on your needs. Maybe it might be helpful?

I decided to add a dedicated "Tracy Toggler" panel. Well it's actually just a button - you can see it second from the end: and when it's disabled, this is all you see at the bottom right of your site: I left the "Disable Tracy" button in the Panel Selector because I figured some users may prefer that approach - it's your choice.

Ok, the latest version has a new disable/enable option. I added the Disable button to the bottom of the Panel Selector because I think most of you have that enabled all the time. Please let me know if that won't work for some of you and I can rethink @szabesz's suggestion for adding it to the System Info panel. I would have done that straight away, but that is a Tracy core panel, so I would have to add with JS. The main problem is that panels are lazy rendered, so the DOM for panels is not available until the first time they are loaded. Still do-able, but requires a little more effort. The Enabler button is simply a red bug icon (like the one I am using for Tracy in the site modules list). It appears at the bottom right of the page when you have disabled Tracy. It only appears on frontend and backend if the debug bar is enabled for those locations. Note that this disabler doesn't actually uncheck the "Enable Tracy Debugger" checkbox in the settings - it's just disabled with a cookie. I am happy to revisit this approach, but my reasoning was that I'd rather the settings checkbox had a little more power, so that if it's unchecked there, the enable icon won't actually appear at the bottom right of your site. Anyway, hope this helpful and don't be shy if you think I have messed it up by doing it this way

Ok, I'll see what I can do. Obviously a disable link like AOS has would only be available when you're in the admin, but if the only problem you are having is module updating, then that is probably ok. I had actually been thinking about a "Disable Once" button available from the debug bar that would prevent Tracy from being loaded on the next page load, but I don't think this would handle your situation anyway because module updating involves a few page loads. One thing though - if you are getting warnings from PW core files - have you reported these as issues on Github? Sorry, what is the "main panel" you are referring to? Do you mean the debug bar, or the panel selector panel? Do you have any specific ideas for how best to provide a disable feature? You have noticed something that I have been considering changing. It was meant as a feature, but I wonder if it's more of a confusion. Basically the logic is that if you are in DETECT mode and Tracy also determines that you are on a localhost, then it will display the debug bar regardless of whether you are logged in or not. If you switch to DEVELOPMENT or PRODUCTION mode, it will behave the same as a live server. I was trying to make it easy to have the debug bar available to test things when not logged in, but now that Tracy has the User Switcher panel, we don't really need this, because we can use the User Switcher to change to a non-superuser (or even logout) and still have access to the debug bar for the length of the user switcher session. Do you (or anyone else) have any thoughts on the best scenario here?

I am not sure what you're trying to do with that. $event->arguments[0]->id returns the ID of the user page. You don't want to override the $page object ever. Given that we are talking about a user, the convention is often to use $u. $u = wire('users')->get($event->arguments[0]->id); but that is basically what I showed you up above.

Follow the instructions in this post to move the Name to the Content tab Then hide the Settings tab altogether using this module (http://modules.processwire.com/modules/restrict-tab-view/)

Hi @biber - I think your problem might be similar to this: https://github.com/justonestep/processwire-imageextra/issues/9 Can you cleanup the db table for the images field: "field_images" (or similar) by removing the extra language fields? Looks like the problem should be fixed in the dev branch of that module, but you still might have to cleanup manually at this point.

The PW namespace is ProcessWire, not Processwire

The latest version now uses a proper csv parser, not php's str_getcsv so now it supports line breaks within csv "fields". This should deal with the problem that @elabx reported earlier this year - sorry it's been so long coming. I'd love to hear how this new parser works out for everyone's CSV importing needs. If it seems good, then I will also start using it in my Table CSV Import/Export module: http://modules.processwire.com/modules/table-csv-import-export/ Thanks for any feedback. Does anyone else have anything outstanding that needs fixing?

Actually just thought to go back and check the: $process = $this->wire('process'); bd($process->getPage()); and it works fine also: and: $process->getPage()->id returns 41

Sorry, I shouldn't give advice without really checking into it. This is what you need: $event->arguments[0]->id That will get you the id of the user/page. BTW, the way I figured this out was to bd($event) inside the validEmail() function. With TracyDebugger installed I see this: bd($event, '$event', array('maxDepth' => 5)); Then to confirm, I did this: bd($event->arguments[0]->id); and got this: With the ID you can get the full user object like this: $uid = $event->arguments[0]->id; bd(wire('users')->get($uid)); See all the user fields under "settings"

Sorry wasn't really checking through everything properly. Take a look at how I am doing it for InputfieldPassword::render https://github.com/adrianbj/EmailNewUser/blob/master/EmailNewUser.module#L50 $process = $this->wire('process'); if($process instanceof WirePageEditor) { $userpage = $process->getPage(); if($userpage->is(Page::statusUnpublished)) $event->object->notes = 'NB: Because you chose to automatically generate the password for new users, you can leave these blank. However, if you do enter a password here, it will override the generated one.'; }

Have you tried: $event->object->getPage();

Sounds useful, but I'll wait and see if there is demand. I don't honestly know how many people are using this module anyway, let alone with ML setups.

Ok, I have added the checkbox: Not sure how best to implement this cleanly. If it was a simple matter of checking if there was an additional field at the end of the row that was 1 or 0, that would be ok I guess, but with the CSV field pairing functionality and it's checks, I think it is going to start to get a bit messy, but if you think it would be really worthwhile, let me know and maybe I'll revisit it.

I know this is a little OT (ok, maybe a lot OT), but I just discovered the $sanitizer->testAll() option - maybe you guys all noticed it when it was introduced, but I missed it Anyway, I think it is very handy and a great use of the console panel Finding this I did notice that the list is not complete at the moment though (https://github.com/ryancramerdesign/ProcessWire/issues/2028) Anyway, hope someone finds this useful like I did!

So to clarify, there are time when you wouldn't want newly added pages automatically activated in all other languages? (Sorry not a ML user so not sure how most people work). Do you think it should be checked or unchecked by default? @mel47 - I took a look at the html tag issue - was a very easy fix (just committed) - sorry I hadn't come across this before. I was sanitizing as "text" - now I am using the "purify" sanitizer - hopefully that will work for everyone in all scenarios, but if anyone notices a problem, please let me know.

Sorry for the crazy delay on this @Soma but I think it should now all work as expected. Would there be any reason to make this a config option? Would anyone not want new pages to be automatically activated? Could it be a module-wide setting, or would it need to be part of the interface where the new pages are added?

I am switching my test install between 2.x and 3.x all the time for module development and have had no problems (I use the version switcher in Tracy). The data schema is unchanged. The only changes I can think of are one from text to mediumtext for the SessionHandlerDB module and the addition of a published field in the pages table (but this may have actually happened in 2.x - I don't recall).

Minor column width / padding issue