Open johnkrause05 opened 6 years ago
Can you open developer tools (F12) and try to print something. Do you receive an error?
Thank you for your quick response. Running the developer console and printing something gives no message at all. I would be willing to share my screen in team viewer if that would be helpful.
John Krause | 810-229-9334 | john.krause@promessinc.commailto:john.krause@promessinc.com
Promess Incorporated | 11429 Grand River Rd., Brighton, MI 48116
[Promess Logo]
www.promessinc.comhttp://www.promessinc.com
[Promess Twitter] https://twitter.com/PromessInc [Promess YouTube] http://www.youtube.com/user/PromessInc?feature=watch [Promess LinkedIn] http://www.linkedin.com/company/promess
From: MrTarantula notifications@github.com Sent: Friday, March 16, 2018 10:49 AM To: MrTarantula/WIPrint WIPrint@noreply.github.com Cc: John Krause john.krause@promessinc.com; Author author@noreply.github.com Subject: Re: [MrTarantula/WIPrint] Work Item Print Not Working All Of A Sudden (#21)
Can you open developer tools (F12) and try to print something. Do you receive an error?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/MrTarantula/WIPrint/issues/21#issuecomment-373736544, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYMVG6iPycMxFGEVlu-D89GEQVdyJFH4ks5te9DVgaJpZM4StzhV.
No, I don't have the time to devote to issues like this. I have a day job and this is just a side project. Have you tried clearing your cache in Chrome?
O absolutely, my apologies 😊
I will try that, thanks a bunch. Excellent job on the extension by the way, you did a great job.
John Krause | 810-229-9334 | john.krause@promessinc.commailto:john.krause@promessinc.com
Promess Incorporated | 11429 Grand River Rd., Brighton, MI 48116
[Promess Logo]
www.promessinc.comhttp://www.promessinc.com
[Promess Twitter] https://twitter.com/PromessInc [Promess YouTube] http://www.youtube.com/user/PromessInc?feature=watch [Promess LinkedIn] http://www.linkedin.com/company/promess
From: MrTarantula notifications@github.com Sent: Friday, March 16, 2018 11:37 AM To: MrTarantula/WIPrint WIPrint@noreply.github.com Cc: John Krause john.krause@promessinc.com; Author author@noreply.github.com Subject: Re: [MrTarantula/WIPrint] Work Item Print Not Working All Of A Sudden (#21)
No, I don't have the time to devote to issues like this. I have a day job and this is just a side project. Have you tried clearing your cache in Chrome?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/MrTarantula/WIPrint/issues/21#issuecomment-373752189, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AYMVGzobACY-gYJ_hJVku-CY8uVJRzlfks5te9wwgaJpZM4StzhV.
It's possible that it's taking too much time for VSTS to load the data before Chrome begins printing, especially if you're printing a lot of items or if your network or VSTS are slow. It has been an issue before, and I hacked a fix in. I don't have a good fix for it yet.
I deleted my cache in chrome and still doesn't work. When trying to use in firefox or edge, this now happens when I try to go to the settings page. Any thoughts on this?
I'm not experiencing that problem in VSTS. Have you made any changes to your work item templates or processes?
In google chrome I am able to load the settings page, but when trying to print it just prints a blank page. When using edge (now doesn't work, worked previously) or firefox this happens. Below is the console printout if this helps.
If you go to the network tab, then refresh, are there any files with 404 error?
This is the results in edge.
It looks like VSTS is giving you a 302 redirect when trying to load my extension. I'm not sure why that would happen. It could be VSTS, or (less likely) corporate firewall or antivirus. Do you have issues loading any other extensions?
Same here this is what I get:
I am getting the same error as @MKGNZ, but only on work items with comments. Printing work items without comments seems to be working fine.
revisedBy.name
should never be null. If there is a comment, then there is an author. What's more likely is that revisedBy.name
has been replaced with a new field. I'll have to dig through the ever-changing documentation and find it.
Debugging in the Chrome console gives me an object with this structure:
revisedBy: { displayName:"" id:"" imageUrl:"" uniqueName:"" url:"" }
It also appears that instead of an array of WorkItemComment
VSTS now gives me a WorkItemComments
object with an array of comment
properties. I think I have it sorted out in the latest release, which I have in the marketplace but not Github.
Thanks very much for the fix. That seems to have resolved the issue I was having.
@johnkrause05 are you still having issues printing work items?
Just yesterday, I go to print using Google Chrome and my work item print is blank. I go to the configuration settings and it has fields selected. I try to add and remove some fields and then save, still shows blank. I tried on microsoft edge and it works correctly. It seems to have broke on google chrome within the last few days? This always worked before, this is something I use very often.
Thanks