User Usage

User Usage Information

•

mailto has no defined limit on the number of characters but there are limits in practice (as of 2015)

Web Browsers:

  •  Apple Safari
    • 705000000
    • Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56
    • limited by 16GB RAM
  • Mozilla Firefox
    • 268435455
    • Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:41.0) Gecko/20100101 Firefox/41.0
    • limited by maximum string length
  • Google Chrome
    • 2097132
    • Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/45.0.2454.101 Safari/537.36
    • limited without explanation
  • Microsoft Internet Explorer
    • 2029
    • Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; rv:11.0) like Gecko
    • limited without explanation

Email Clients:

  • Mozilla Thunderbird
    • 2097132 works in 1 second
    • 268435455 uses 100% CPU for 2 minutes but fails to render the body and is not usable
    • version 38.3.0
  • SeaMonkey
    • 2097132 works in 5 seconds
    • 268435455 uses 100% CPU for a long time (more than 5 minutes)
    • version 2.38
  • Apple Mail
    • 500000 works in 14 seconds
    • 2097132 uses 100% CPU for a long time (more than 5 minutes)
    • version 8.2
  • Microsoft Outlook
    • trims any url to 2070 in 1 second
    • version 2013

•

There is a Microsoft Office bug (2019105) that will attempt WebDAV windows authentication from non WebDAV links. To work around this bug the server can specify the "Content-Disposition" header as an "attachment" (requesting the browser save the file instead of opening it). Microsoft Internet Explorer will still ask if you want to open the file but will not attempt WebDAV. When making links with ShowItemData.po use the "download" in place of the "filename" parameter. For example:

/ShowItemData.po?handle=123&download=file.ext

•
  1. Use a mobile device that is not restrictive (LineageOS is recommended) or at least permits the Installation of Google Chrome.Push_1
  2. Install Google Chrome.Push_2
  3. Open Noodle (SSL must be used).Push_3
  4. Login.Push_4
  5. View Messages, and click subscribe.Push_5
  6. Use a desktop browser to create and fill in the push URL setting.Push_6
  7. Push subscribe with your mobile again, and now when someone sends you an instant message you will be Notified. Notifications will also show up on smart watches.Push_7

•

Emails can be sent in the following 5 ways:

  • Subscriptions (per user)
    • My Profile > Edit > What's New > Subscription
    • System Tools > People > [USER] > What's New > Subscription
    • System Tools > Settings > General > Email usage report
  • Auto notifications (per folder)
    • Administration > Auto Notification
    • (supported folder application types only)
  • Workflow (per folder)
    • Workflow Tab
    • (supported folder application types only)
  • Memo manger (per site)
    • System application
  • Mention and reply
    • Can be disabled in Profile > Edit > Email on mention
  • Notification (any item or folder)
    • any user can notify any other user of any item
  • Password reset
    • System Tools > Security > General > Allow the "Forgot my Password" feature
  • Health warnings

•

The Search Bar gives Noodle users the power to quickly and conveniently locate Noodle content.

In the following example, the user has decided to search using the search text 'Accounting'. Noodle will now present the user a list of all matches based on the search criteria given:

The user may now click one of the links shown to be taken to the information page for that file. Any results that are contained in a folder will direct a user to the information page - others such as emails and forum posts, the user will be taken directly to them.search

•
Chrome Bugs:
  • Version 37.0.2062.120 (and 39.0.2159.0 canary) inconsistently crash with "Aw, Snap!".
    • Empty the cache, etc, and restart the browser.
    • Send us your ids from chrome://crashes/ (Google keeps some bug reports private, but any IDs we are sent will be added as related to our report or one of the 72937 other outstanding chromium bugs).
  • Version 40.0.2214.111 will not run functions if they have ever been called(onmouseover) from another window (iframe)
    • reported as a regression.
  • Version 44.0.2403.125 loses scope on deeply nested AJAX
  • Version 50 Disabling "Use a prediction service to load pages more quickly" is advised to avoid incorrect redirects.
  • Version 72+ web driver is not blocking and thus unusably buggy
  • Version 84+ resets live CSS changes only when developer tools is open
  • Version 85 writes it's own CSS instead of respecting dark mode
Solutions:
  • Use Firefox.
  • Upgrade
  • avoid nested AJAX

•

Steps to make IE behave more like Chrome or Firefox:

Upgrade to version 11 (or 8 if on XP)
Reset IE:
  1. Tools>internet options>advanced>reset>check delete personal settings>reset
  2. close IE (all windows)
Make IE usable on windows server:
  1. Tools>internet options>advanced>uncheck automatically recover from page errors with compatibility view
  2. Tools>internet options>security>select trusted sites>set to low>sites>remove all the current sites and add the Noodle url.
  3. Tools>internet options>security>select trusted sites>set to low>custom level>scroll all the way down and disable "XSS filter"
  4. tools>compatibility view settings> remove and uncheck all.

•

For mailto:

  1. Make sure you are on your Google Mail page.
  2. Copy/paste this into the address bar:
    • javascript:navigator.registerProtocolHandler("mailto","https://mail.google.com/mail/?extsrc=mailto&url=%s","Gmail")
  3. Add the javascript: to the front again if it got automatically trimmed. Then hit enter.

For webcal:

  1. Make sure you are on your Google Calendar page.
  2. Copy/paste this into the address bar:
    • javascript:navigator.registerProtocolHandler("webcal","https://www.google.com/calendar/render?cid=%s","Google Calendar")
  3. Add the javascript: to the front again if it got automatically trimmed. Then hit enter.

 

•

If users experience a "Session closed" message there are 2 possibilities:

  1. The user accessed Noodle with more than one IP address.
    • change the setting "System Tools>Settings>General Settings>Session Security Level (IP address matching)" to "0". ("4" being the maximum).
  2. The user accessed Noodle with more than one cookie (or browser/OS)
    • solution: logout on one browser before using another.