I an configuring our site to support live tiles with notifications with IE11 and Windows 8.1. I have a browserconfig.xml file with polling-uri inside the notification section. I've discovered that if the polling-uri returns a 404 response code, then the corresponding notification is not shown in the tile.
The question is, once a notification is defined and showing using the notification XML file, how do I stop that notification from showing when the site is already pinned on the start screen?
There is an indication in the MSDN documentation that if I use the metadata approach instead of the XML file that I can specify "none" for the polling-uri to turn off that notification, but I'd much rather use the XML file approach.
Any ideas?
It appears that after a number of days of getting a 404 response code on the notification XML file that Windows 8.1 will finally give up and go back to just the tile image and text. See notes on the original post. I first pinned the site on Wednesday around 17:45 then turned off the notification XML file so that it returned a 404 response code. As of Sunday it was still showing the missing notification on the desktop. Monday at 8:45 it had reverted to the tile image.
Note: my Windows 8.1 is a Virtual Machine and does not run all the time. It's possible that Windows might give up on the missing notification sooner if it ran all the time.
Windows appears to look for the notification XML files when the user first logs in and whenever coming out of the screen saver.
Related
After Summit 2019, we were excited to start working on updates for 2018R2, and I practiced adding mobile screens for our custom modules in my sandbox.
We decided to fully refresh our DEV instance and reapply our customizations. No problem there, but when I try "Add New Screen" in the mobile section and then try to enter my screen number, the mouse goes to "waiting" and I can't add my new screen. Eventually, I get a "timed out" message. Same problem even when trying to add a standard Acumatica screen. Everything else in the project and Acumatica web interface seems to work fine.
Any ideas on where to look for what is preventing adding a new screen?
I'm on Build 18.209.0021.
It seems like an Ajax issue in the customization project editor. After callback to server the client page javascript is stuck waiting on the server response. You can try using Chrome browser which has less of those Ajax hangs and update Chrome if you're already using it.
There is also a known issue specifically affecting 2018 R2 Mobile that leads to generic error Sequence contains no matching element on mobile detail page. Based on your question this doesn't seem to be the issue you are having but you can give the workaround to this bug a try:
Open Generic Inquiry screen (SM208000)
Select FS-ServiceOrder inquiry, uncheck Expose to mobile and save
On Apply Updates screen (SM203510), click on Restart Application
This was identified by Acumatica support as a bug. Upgrade to a new release for the fix.
I'm using node-notifier (link) in node.js to show a toast notification in Windows 8. I have it working and I'm able to adjust the title, text, and main image in the notification just fine. However, in a Windows 8 toast notifications, there is a secondary (smaller) image. See below:
So, node-notifier uses toaster, which in turn uses ToastNotificationManager. But, I cannot find any reference anywhere to this secondary image. I've looked here and here on Microsoft's site.
This secondary image also shows in other notifications I receive from applications like Outlook, Slack, etc.
Where is this secondary image coming from? Is the documentation just out of date? Can Toaster be modified to access this secondary image?
The secondary image is the icon for the shortcut in the Start Menu folder for the program registered to raise a toast. To change it, you'll need to modify the icon on the shortcut.
For a desktop application to use the ToastNotificationManager class, it is required to have a shortcut in the start menu, and an AppUserModelId associated with that shortcut. At ToastNotificationManager creation time, the caller passes in the same AppUserModelId, which ties back to the associated icon for the shortcut. More about registering desktop applications to raise toasts this can be found on this MSDN documentation page.
Looking at the toaster code here, it is installing the shortcut to a file called toast.lnk in the Start Menu:
String shortcutPath =
Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) +
"\\Microsoft\\Windows\\Start Menu\\Programs\\toast.lnk";
And, it is creating the shortcut targeting the initial calling process:
String exePath = Process.GetCurrentProcess().MainModule.FileName;
Updating the icon in the shortcut manually should verify that you can change what is shown locally, but an update to toaster to set the icon location is likely required (to support multiple callers with different shortcuts, or by having it call IShellLink::SetIconLocation).
In developing Xpages applications I have noticed that the applications will intermittently and apparently randomly freeze. It happens when I am changing code and previewing quite a bit in XPiNC, which I might be able to understand. But at times it happens when I am just editing a document.
For example, I just updated a RT field in a document using CKEditor, and the app froze about 12 or 15 times. I will no longer be able to move the cursor or move scroll bars up or down. I am able to switch to a different tab (like my email) but if I try to switch back to the Xpages app, I will still see the email application.
I have checked the "IBM Technical Support" Folder for the Xpages log and the console log, with nothing there, and I have checked the Help ==> Support Trace and Log, nothing there either.
We are running Revision 20131022.1138 (Release 9.0.1) on the server, and I am running the same on my client and designer.
I want to lauch in C#
UnviewableContentIdentified
event to download an attachment in email e.g. gmail.
So i wrote another app using BackgroundDownloader to download attachment.
But how to launch it when i click on attachment, every time it opens IE metro style.
All i got on internet was Windows.System.Launcher.LaunchUriAsync(uri)
what is URI for a Windows8 app?
Even MSDN community didn't answer it when i asked question there?
Instead of launching uri I just wrote a BackgroundDownlaoder in Unviewablw content event.
So no need to launch a second application.
Sometimes the style sheet disappears when naviguating on our WSS 3.0 sites (white background on the site, no colors, no formatting, etc.). This has mainly happened with IE6 (corporate browser for the majority of our computers). The fixes were :
clean up temporary internet files
if it still doesn't work, upgrade to IE 7
However, this time, the upgrade to IE 7 hasn't worked, the style sheet isn't applied. When we clean up temporary internet files, things go back to normal, but after a while the css disappears again.
Here are a few ideas on what you could try:
Fiddler should be able to tell you if there is a network problem.
Check the HTML for anything unusual. Is it malformed in any way? Can you save a copy and run it through an online validator (although this is limited in use as SharePoint's default markup isn't compliant).
If some users are having the issues but others aren't, check their permissions on the server.
You could also try using the SharePoint "Log in as another user" feature to see if the problem can be reproduced on your machine when logged in as them. You may also want to try running Internet Explorer as that user.
Check the Event Viewer on both client and server for anything unusual.
Check the IIS logs on the server for any errors.
Check the SharePoint ULS logs on the server in the "12 Hive" for errors that might be related to this problem.
Try running Process Monitor on the client and reproduce the problem. Search for keywords such as FAIL or ERROR to see if anything appears. Make a note of the time the problem occurs and see if the Process Monitor logs give any additional information.
Is there some javascript that's involved as well? Could it be a virus scanner that is set way to strict? As you pointed out in one of the comments, the CSS isn't even being requested (at IIS log level, which is as basic as you get, not even in SHarePoint yet), so it HAS to be something on the client PC.