adrian
-
Posts
11,210 -
Joined
-
Last visited
-
Days Won
373
Everything posted by adrian
-
I knew that request was coming ? I have added all this to the latest version, including the click again on the tab to collapse. Please test and let me know if the behavior is what you are looking for.
-
Just do it like this: $mail->mailHTML('alex@gmail.com', 'Hello', '<html><body><h1>Message Body</h1></body></html> without redefining $mail
- 2 replies
-
- 3
-
-
-
- wiremail()
- mailhtml()
- (and 1 more)
-
Oh and I also made the dump in the additional tabs open (not collapsed) by default. My thinking on this is that if you dump lots of items, you don't want the default tab to be open by default because it could make for too much scrolling, but for the additional tabs, if you click on them then it's obvious you want to see the content so you shouldn't need to click again to expand the dump. Let me know if you guys don't like this behavior and if you have a preferred approach. See how below I can quickly scroll through to the dump I am looking for (because the default Debug Info tab content is collapsed), but when I switch to the Iterator or Full Object tabs, these are not collapsed.
-
It's not completely redundant - it still determines how dumps in the RequestInfo panel's Field List & Values sections are output. It also defines the default dump for the dump/barDump output for cases where the separate tabs may not kick in - not sure if there actually are any situations where this will happen. It now also controls the output of field values in the Iterator tab. Also with the new option (described below) to choose what tabs you want, if you choose none, then this setting will be relevant to how the one version of the dump is handled. Good idea - done: Thanks for reporting this undefined variable error - it's fixed now and hopefully there shouldn't be any other cases like this, but please let me know if you come across anything else.
-
Field pairings is only available when you define configurable pages - then in the Settings tab for those page you can setup the field pairings.
-
Thanks @szabesz and @Zeka for the kudos - much appreciated! I just added a new optional "Iterator" tab to the dumps output which return the output of PW's getIterator() method which in the case of page objects returns the values of all properties and fields for the page. For other objects, what is return varies somewhat, but in some cases it is more useful than the debugInfo result which is still lacking for many objects. Here is just one example - the debugInfo output for Permissions is basically useless, but the Iterator output contains useful info. Sure, you could manually dump the object with ->getIterator() added to it, but this makes it that much easier when you are looking for different bits of info and you're not sure which option will provide the exactly what you need in the easiest format to find it. An interesting side-effect of the Iterator tab is that the Full Object now also contains values for all the fields when dumping a page object because the getIterator() call queries all those fields and they are now joined to the page object. I have made this optional, so you will need to go to this setting to enable it:
-
Just wondering if anyone out there has tested @tpr's vanilla JS version: https://github.com/rolandtoth/CookieManagementBanner - it would be great to get it merged fairly shortly as I don't think any PW frontend modules should require jquery. Thanks for testing and letting my know if you find any problems.
-
@szabesz - just wanted to let you know that I have implemented more of your ID and count idea to the dumps output. Notice the tooltip titles (and link address below) on the edit links to various PW objects and then in the last one you can see the number of items in the PageArray (which also works with any WireArray, including images, repeater items, etc). Note that the tooltip titles also show you the name of the object which I think is also a nice preview rather than having to open the dumped object.
-
Looks to be working great here - thanks!
- 79 replies
-
- 1
-
-
- breadcrumbs
- admin
- (and 2 more)
-
Unfortunately that's not possible with the way this module works. There is lots of discussion floating around about why it's difficult to hide parts of the page tree - have a read starting here: https://processwire.com/talk/topic/1176-hiding-uneditable-pages-from-users/?do=findComment&comment=84916 - there are links to some different gists that might be helpful for you.
-
Soma - I had a very similar experience trying to uninstall it - I eventually got there, but it took some trickery to get it all removed. I feel like I maybe even resorted to DB editing.
-
Hey @Robin S - weird bug when editing a language page: PS - same goes for: Admin > Access > Users and I expect probably anything else that isn't a "normal" page.
- 79 replies
-
- 2
-
-
- breadcrumbs
- admin
- (and 2 more)
-
Sorry, I did grab it but did a diff and I guess I somehow copied the wrong one across to my testing site - apologies for the confusion! Anyway, thanks for those other changes. I think everything looks great now, so I have committed and modules directory is updated. Thanks again for your effort on this!
-
Oops ? Your latest version still didn't work because of position:absolute but the attached version seems fine: styles.css
-
No use now that you have checked this, but an FYI for the future, the Tracy Template Resources panel shows you all functions and where they were defined.
-
Looks good now - thanks!
-
Thanks @tpr - that looks really great! There was only one issue - in the Console panel, the page ID link was positioned at the far right of the console, rather than the dump element. Attached version fixes that if you want to take a look before I commit. @bernhard - not sure what's going on there, it seems to work fine here. Could you try to debug why it's not working at your end please? styles.css
-
Yeah, I think this could work quite well. If you feel like having a go at this tomorrow, that would be great thanks! You can start from the latest styles.css I attached above. Sorry, I understand - I actually use my touchpad exclusively these days - never thought I would give up a mouse, but I actually prefer it now that I am on a Mac and the touchpad is actually decent, although I am sure new Windows ones are good these days too. Anyway, I think the size I have it at now should be fine.
-
Compromise in tab height which I think is probably a decent alternative. CSS attached: styles.css
-
I'm not really sure how to make it look decent without a background - with this the title just looks out of place to me. But I'd love to see your idea for how it might look! Do you think TD is getting much use on a touch screen? I have done small amounts of work like that, but mostly drives me crazy!
-
@tpr - can you live with this? I overrode the dotted border in the module's css file and obviously reduced the padding on the tabs again. styles.css
-
Thanks - I like the darker hover (instead of white). I am not sure about the increased size of the tabs though - they take up a lot of space and I think they look a bit weird when you have added a title - see how they are taller than the title element. Good catch - thanks. Did you do this in the core Tracy files? If we're going to take this approach, I'd rather override if possible, rather than hacking the core. Did you try that and have problems? Thanks again - always super-appreciative of your skill with this stuff.
-
I just tried all browser and they of course all have the logo issue. The src looks like this: <img id="color" alt="Centura logo" src=""> Of course I see the issues with location/language selection ?
-
Of course - that is a good reason to not use it. It was on Ryan's roadmap to allow it to work over http, but not sure when/if that will happen.
-
Nice looking site - just a quick FYI that until you have defined your region/language, the logo doesn't display. Also, I wonder if it' worth selecting these automatically based on IP address first and letting the user change if they want rather than being forced to do this straight up?
