tpr

Just for the info: latest Nette/Latte plugin for PhpStorm works fine - syntax highlight, autocomplete and such thing works like charm. I will update the module readme later.

:empty works only there is literally nothing between the tags. I don't know if this is the case here, but most of the cases I can't use it for such purpose.

This is my dilemma too. Emogrifier is easy to setup so I'm not sure if it deserves an own module. Of course I'm open to other ideas.

Version 1.7.3 works fine, thanks!

Partly yes - it says Validated but the panel contains too much info - or is this normal? It seems that the two validators have different markups or perhaps the html5 validator page markup was changed. The green bordered line is a "p" tag with "success" class. Maybe I see this because I'm the only one here writing valid markup?

Great, thanks! Just updated the readme. I'm thinking about adding Emogrifier to the module. I have only one usecase for inlining CSS (newsletters) but I think it won't hurt having a "$view->setInlineCSS('path') or similar helper at disposal.

Sorry to bother again, but even with disabled httpasswd the validator panel says Validation Errors, and its content is Sorry, but there was a problem accessing the validation server at https://html5.validator.nu/ But when I manually visit html5.validator.nu and paste the URL of the site, it says everything is fine (valid). Commenting out this line fixed this, valid/invalid messages appeared fine. Maybe this line is required only for the non-html5 validator?

Yes, that was it, on the dev site I have httpasswd, totally forgot about that. All I get now is nasty validation errors

Thanks, but use parts only that you think are enhancements. I might have overlooked something that breaks functionality.

I played with pixels and here is the concept. What bugged me the most were the green tick icons, they were too loud imho. Szabesz was right that they were confusing because the checkboxes are very similar (both meaning "checked"). Now I replaced them with an asterisk. Maybe this is not the best solution, but I think such signal is enough. "Once" orange icons went to the left, it's easier to overview them if they are under each other. My first idea was to put them to the far right, but then one couldn't see which panel they belong. The template file changer works great, though I use a template engine so I have to change the view file name inside home-dev.php. But I guess there is no general fix for this and I can live with it. Here are mainly design mods, to make more obvious where is what. I'm not entirely happy with the Once-Sticky buttons, but such differentiaton should make clear which one is active. There's also an error: if I check Toggle All, I get this: exception 'ErrorException' with message 'file_get_contents(http://...domain.com/?tracyValidating=1): failed to open stream: HTTP request failed! HTTP/1.1 401 Authorization Required ' in /....../public_html/...sitename.../site/assets/cache/FileCompiler/site/modules/TracyDebugger/ValidatorPanel.inc:34

Well that's the main thing, figuring out a system that integrates well into PW and is simple enough. See the images below of my current newsletter page in the admin and the final outcome. There's a dedicated Newsletters page in the root page tree, newsletters are listed below them. This is useful because newsletters have their own URLs so "View in browser" is easy to implement. The subscribers have another page in the root, each subscriber is a page. They can be active or inactive, based on the page status published or not. I use simpe subscription, no confirmation emails. I do not use subscriber lists, this should be also implemented somehow. I use wireMail() for sending (with MailGun), but queing would be also nice. It would be nicer to have a new nav item in the admin "Newsletter", and move the newsletters and subscribers there. Anyway, this is what I've got, maybe these can generate some ideas.

Interesting feature, will try it next time. I think the once-sticky-reset control is not very understandable, at least for me. Maybe adding a pushed state to the sticky button would clear things a bit (when it's active). And perhaps adding different colors to once-sticky buttons would also help. Reset could go to the far right and be shown as a text link. I can do a design mockup if you think tho is a good idea. But it may be that I shoot in the dark as I have never used these kind of panels.

@Sephiroth Heads up! If you look for something to design (I mean on specification level), what about a simple newsletter module? This is something I occassionally need and as I know there is no "boxed" solution for it. What I have in mind: - integrate with other modules, eg. WireMailGun (to handle statistics) - newsletter blocks with the ability to include other pages (I use PageTable or Matrix Repeater for this) - newsletter subscription/unsubscription - send preview - css inliner (eg. Emogrifier) I have these functionalities working but at a very low hand-made level. Anyway, just and idea that may get you electrified

I use this for such a thing, eg creating a new admin section for form submissions: https://processwire.com/talk/topic/1272-new-page-nav-in-admin/

I agrree, but still, Reno feels better Here is a quick idea of having the sidebar accordion always open:

Thanks @Sebii, I'll look into them. @szabesz I like the Reno theme better, even with its little quirks. It does have "dropdown" menus, at the end of the rows there's a flash-like icon. A very basic customizer would be FUN (and not FAN)

I've set a custom image to replace the PW logo in the admin in "/site/modules/AdminTheme/AdminThemeReno/styles/images/logo.png". This worked fine until now, but since about v3.017 it doesn't show up, but the original PW logo. Is there a way to fix this? I'm using the Roboto color variations as explained here: https://processwire.com/blog/posts/processwire-2.6.8-brings-new-version-of-reno-admin-theme-and-more/#admin-theme-reno-roboto-colours However, it's a bit out of date, eg. the new dropdown buttons don't show correctly and other minor glitches appear here and there. Could we get the source scss (or less?) files for the Reno style, to customize them? I'm interested mainly in colors, and it would be even better if we could have a "color customizer" in the admin interface for the Reno theme. I've made this manually and there are only a few main colors, and by tweaking them the admin can match the client's color scheme.

Right. Previously the readme contained a wrong syntax for latte files "_('text')", but it shouldn't need the brackets. So if your syntax is also right it would work fine. Clearing latte cache is recommended though. But you should see at once whether it works or not

v015 is uploaded to GitHub. Syntax for string translation in .latte files is changed to "{_'text, context, textdomain'}". In textdomain use "__()" if you need no context, and "_x()" if you do.

For such situations the profield matrix repeater module is a good option. It saved me a lot of headaches I would have faced if I have gone the ckeditor route.

I got it working, but the "General" context will be gone. I think it's even better this way. Will upload a new version soon, after testing the different variations a bit.

You were right, "General" context was used even when it shouldn't. Currently I have no idea how to fix this but will try to come up with something. Since the translator gets only the string to translate, there is nothing to check that it was called "_()" or "_t()", not even calling debug_backtrace.

No, the second column. Moving the columns elsewhere doesn't help. On a 3.0.17 site images are OK in the lister but it's another project, maybe this is unrelated.

The images field is getting superb, thanks! I may have an issue here in Lister (default, not ListerPro). Adding an image column to the columns shows no image though they worked fine before. Might be a CSS-only issue because disabling these rules shows the image: .gridImage__overflow > img { /* position: absolute; */ /* top: 50%; */ /* left: 50%; */ /* transition: transform ease .3s; */ /* -ms-transform: translate3d(-50%, -50%, 0); */ /* transform: translate3d(-50%, -50%, 0); */ }

Just tested with latest Tracy and it seems everything works fine here, no slowdowns and the bar appears even using the Master option (http & https). I wasn't using xdebug btw. Thanks!