I'm using a system that recently upgraded to Graylog3. In Graylog 2 dashboard widgets it was easy to click a button that looked like a "Play" triangle to dive into a query.
In Graylog 3 the widget looks like the image below and none of the options I've clicked on seem to get to the underlying query. If I edit the widget I can see the query and then go recreate it manually, but I just want a "one click" way to get to the underlying data so I can dig into it.
There is play button in graylog widgets from version 3.2.3
https://docs.graylog.org/en/3.2/pages/changelog.html#graylog-3-2-3
Related
I have a SharePoint online 2016 site, with a List. Now i want to have a URL (build in MS Flow) that will point directly to a specific item in Edit mode.
Meaning to have this view (both list behind and right "popup" screen):
And not like this (Copy link url)
I am able to have it opened in full screen but not like the screenshot.
Can anyone tell me if this is even possible?
I have looked into these:
http://mmkhome.blogspot.com/2010/12/sharepoint-edit-page-url-querystring.html
http://blogbaris.blogspot.com/2012/09/open-sharepoint-2010-display-edit-new.html
https://social.msdn.microsoft.com/Forums/en-US/c27e2cdd-bddb-473c-9782-0309e026204f/to-show-a-editform-in-dialog-box?forum=sharepointcustomizationprevious
https://www.spcnl.nl/redirect-link-to-item-url-from-out-microsoft-flow-to-editform-instead-of-displayform/
and tried literally everything suggested in all these links but no luck.
Things like:
Web URL/Lists/List Name/AllItems.aspx?displaymode=design
Web URL/Lists/List Name/EditForm.aspx?ID={List item ID}
/DispForm.aspx?ID=...
/EditForm.aspx?ID=...
?ID=123&pagemode=edit
?ID=123&mode=edit
PageType=4
Any suggestion is greatly appreciated!
Devtools shows that after clicking on "Edit" button above list name (the way you open this extended edit menu from first screenshoot), a REST API call is fired:
https://tenant.sharepoint.com/sites/test_site/
_api/web/GetList(%27%2Fsites%2Ftest%5Fsite%2FLists%2Ftest%5Flist%27)
/RenderExtendedListFormData(itemId=4,formId='editform',mode='2',options=15,cutoffVersion=0)
And that's it - RenderExtendedListFormData method fetch data and later, I guess, JavaScript does the rest of magic and slides out the edit menu.
To sum up: I am afriad it will be not possible using only pure URL.
we are using Jenkins LTS 2.150.1, Is it possible to hide the nodes/slaves list (by default at the lower left side of the screen) from "regular" users (i.e - not admins).
Is it even possible?
Am I missing something?
I tried:
looking in the configuration of the server, couldn't find any "switch" or anything of that sort to hide it.
looking for a plugin to do that, but couldn't find anything that isn't changing the entire "look and feel" of the basic jenkins theme.
Seems to be that this feature is not added yet. See this ticket.
Is there any setting I can change in Jenkins to make /consoleText the default page for console outputs? Right now, I have to click on console, and then click on the View as plain text link to get this page.
PS: I'm open to "hack" suggestions, if there's no way to officially do this in Jenkins.
Edit: While I'd be perfectly happy with just making /consoleText as the default page, what would be even better would be to replace the View as plain text link with a View dynamic log link, so that I can access the console link too, in case I need it.
You can try the Sidebar-Link Plugin which will give you the ability to add side links on various Jenkins pages like the build, top level, etc.
I am writing code that capture hotkey after user press control-button in preferences of addon - I want to change the label when user push the button and change again when user push some keys (to display the new hotkey). Official documentation about simple-prefs not mention that I can change something visual in loaded preferences view and in debug I looked into object prefs and saw that my preferences is just a strings - only the values and types.
I do not think you can unless you hack the preferences page. I saw your other question and the example add-on from the answer. It's not using simple-prefs and I don't think it's a great user experience either. I have the same problem and was thinking to use a control button to bring up a panel on which you can listen to the keystrokes and print them there. A panel is all html so you can do whatever you like.
I'm developing an internal Google Chrome Extension that needs a way to initiate print the current page to the printer. I do not want the default Print dialog to come up (so, javascript:window.print() is out of question).
As far as I understand, this is not possible just with the JS + HTML plug-in, so I'm also open to using the NPAPI plugin also (with a dummy mime-type). And I'm concerned for Windows platform only.
I'm also open for various hacks / workarounds if possible, though a standard solution would be nice.
If you think this is not possible, let me know if you know any feature request logged for it?
Any suggestions/clarifications are welcome..
In chrome (v18+) we have the --kiosk --kiosk-printing switches. One can print automatically to default printer without print confirmation.
You can see it from this video http://www.youtube.com/watch?v=D6UHjuvI7IE
Since NPAPI allows you to create native C++ plugins that you can interact with through an object tag (which you can use from an extension), that would probably be the way to do it.
The tricky bit is that I don't know of a good way to get the bits for printing the page. The only person I know of who has done something similar to this actually got the window handle for the browser (available through NPAPI) and scraped the bits off of it to print that way, but that won't take into account print stylesheets or anything. You could also try using automation events to try to control the print dialog, but I have no idea if that would work or not.
By design, the browsers try not to let you do something like this, as it could open some serious vulnerabilities if any website could just start printing things to your printer without confirmation...
Anyway, if you find a way to do it with C++ you can use FireBreath to ease the creation of the NPAPI plugin.
There are various extensions that take snapshots of the current web page (for example, this one); you could adapt one to send the image to a printer via an NPAPI plugin.
I've recently been looking for a similar ability, and it seems like it would be quite possible using Chrome's new native messaging api.
https://developer.chrome.com/extensions/nativeMessaging
There are plenty of examples of this with C#, but here is one quick example of troubleshooting Chrome native messaging with a basic C# application
Native messaging from chrome extension to native host written in C#
I realize this may be a day late and a dollar short, but in case anyone else comes across this question, this is the solution that worked for me. From inside a C# app, you can directly print to installed printers using the PrintDocument class. If you figured out a way to get the page image, this would be far easier than using firebreath or NPAPI.
Disable print preview in Google Chrome on Mac
Quit Google Chrome
Launch Terminal on your Mac. (Search “Terminal” using the Search box)
Type defaults write com.google.Chrome DisablePrintPreview -bool true
Close Terminal and open Google Chrome
Disable print preview in Google Chrome on Windows
Close Google Chrome
From your desktop, right click Google Chrome
Click Properties
In the dialog box, add ‘ –disable-print-preview‘ at the end of the Target field sans the apostrophe (make sure to include the space before –)
Click Apply
Disable print preview in Firefox on Mac
In the address bar type “about:config” and press Enter.
Right click on the page, hover over ‘New’ and click on ‘Boolean’
Type ‘print.always_print_silent’ as the preference name and click ‘OK’
Click on ‘true’ and click ‘OK’.
Close the about:config window.
Disable print preview in Firefox on Windows
In the address bar type “about:config” and press Enter.
Right click on the page, hover over ‘New’ and click on ‘Boolean’ Type
‘print.always_print_silent‘ as the preference name and click ‘OK’
Click on ‘true’ and click ‘OK’.
Close the about:config window.
https://support.dryfta.com/how-to-disable-print-preview-in-chrome-firefox-on-windows-mac/