Feed on

Category Archive for 'Known Issues'

Resolved as of November 17, 2014: with the release of Wesleyan Alumni 3.2.1 on Google Play today, this issue is now resolved. We tested on a Nexus 7 running Android 4.4.4 and were able to log in using LinkedIn. We could to set a PIN without any keyboard issues. (We had to clear the app cache […]

One of Wesleyan’s email servers experienced delays this morning between 2:00 a.m. and 6:00 a.m. affecting roughly 20% of alumni accounts on the affected server (Cyrus). Some users may have noticed that actions to move or delete mail failed during this period, and that mail was not being delivered. Full service has now been restored, and […]

Late last week, based on additional feedback from WesChat list members, we reverted the recent change to WesChat’s headers. Several regular readers/contributors noted that the changes made the list harder to use: to such an extent that it was worse than the original problem. When we made the header change a few weeks ago we […]

Update (Oct. 7, 2014): WesChat header configuration has been reverted to its original setting. Back in the spring some WesChat members who use Gmail began reporting increased cases of emails from some list members going to their Spam folders. In late summer, with help from ITS, the Alumni Helpdesk made some technical changes (by activating DKIM on Lyris) […]

Resolved: Wesconnect outage

1:05 p.m.: iModules has provided this update in an email to clients: Earlier this morning, between 10:55 a.m.–11:05 a.m. Central time, U.S.-hosted iModules clients experienced an unscheduled, 10-minute outage affecting access to non-admin, secure servers. The outage was caused by a dropped connection during a routine network review. All sites are now fully operational. We apologize […]

RESOLVED — February 21, 2014 This issue is resolved. Wesconnect is working normally. We experienced typical traffic volumes this week and the site has performed as expected, with no further outages. For more information on the recent outages please see Moving Forward by iModules President Fred Weiss (Feb. 18), and A View From the Trenches by […]

Another Wesconnect outage

11:52 p.m.: Wesconnect is currently timing out. Our platform vendor iModules is aware of the problem and is working to resolve it. We’ll post an update here when we know more. In the meantime, more information may be available at status.imodules.com. 1:12 p.m.: iModules has confirmed that another attack on their servers is underway. We’ll post […]

2:12 p.m.: Wesconnect is currently timing out. Our hosting provider’s servers are affected (i.e. multiple websites), apparently due to a high volume of unknown traffic. The technical team is investigating. We’ll provide updates here. In the meantime, Alumni Support Requests can made via the Alumni Helpdesk, on Facebook or on Twitter. 5:02 p.m.: Wesconnect is working […]

How to resolve the “Bad Request/Error 400” problem on Wesconnect. Update, Dec. 12 This problem occurs because of links containing special characters. It appears to affect Mozilla Browsers (e.g. Firefox). To resolve the problem you need to delete the __utmz cookie that is set for the wesconnect.wesleyan.edu domain. Instructions To delete the cookie that is causing […]

11:22 a.m.: Wesleyan’s online giving form is currently experiencing an outage. University Relations staff are aware of the problem and are working to fix it. We expect to have the issue resolved today, and will post an update shortly. We apologize for any inconvenience. If you attempted to use the giving form and experienced a […]

Next »