Column Resize Fix
A bug that did not allow columns to be re-sized has been fixed. All editors should be able to re-size and edit columns on their sites without any issues.
Google Maps API Key Fix
A bug reported by a number of users with domain mapped sites, as a result of changes we made, has been resolved. The problem effected sites that displayed a the location of an address within a Google map. In order to rectify your own site we ask Premium users & Partners to please log into your network(s) and check your maps. If there is any issue, before contacting Customer Support, please retrieve a new Google maps API key from http://code.google.com/apis/maps/signup.html and insert it in the field which can be found under the 'Settings' tab on your network.
As a result of yesterday's database migration there was an unintended impact on search functionality. Currently search results are returning a traffic jam error page, and saved searches are also not working. You may also notice issues with publishing posts in the Blog, this is because the post is not able to be indexed in the search database. For now we recommend to save draft posts until this issue is rectified.
The Factory team are looking into this at the moment and we hope to have the issue rectified later today.
UPDATE (12/02/2010, 11:55am): The search functionality has been restored. You should be able to use search and saved search and publish blog posts without encountering any issues.
Show Viewers' Friends - Friends/Members Module
In the 'My friends/members' module (found in modules > Me & my community) there is now a new option to display the friends of the person who is signed in and viewing the page. Once the module is added to the page this option is managed by clicking the 'EDIT' button and in the first drop down of the Settings tab, choosing to display 'All friends of the signed-in user'.
Save/Save As Style Menu
In the style editor (accessed in the 'styles' > 'Customise style' tab) you have the ability to save your custom style as well "Save style as" - which enables you to name or re-name your style.
We'll update you on the progress of this project. We suggest in the interim that you use the Firefox browser to access your networks on Webjam to ensure you can see the Rich text editor & the members tab.
Members Tab User Flow Fixes
Some fixes have been implemented to resolve some issues within the member management tab of a network. These fixes allow "Pending" members to receive newsletters - as well as allowing "Newsletter" members to be successfully invited to join a network.
PLEASE NOTE: there is a known issue with Chrome browser not displaying the members tab as a result of this push. As a work-around please use the Firefox browser until this is fixed.
Search Module Fix - Draft Blog Post
A bug was resolved that was causing the Search modules (Search and Saved search) to display draft blog posts in their search results. This was due to the search modules indexing the posts incorrectly. Please note that if you are still experiencing this issue - you will need to re-save your draft posts so that the search database indexes them correctly as drafts.
There is an intermittent error with our database hardware and while this isn’t affecting the current service, we want to correct the issue rather than let it get worse. Therefore, we are planning more in-depth analysis on Saturday 30/01/2010 starting at 9am GMT for three hours. This work should not affect the current service, however during this time, you may see some slow-downs or brief outages.
Thank you for your patience as we work to resolve this.
We scheduled a small fix to resolve two issues today:
Template Channel Traffic Jams
An issue was resolved where replicating templates was causing a Traffic Jam as the template was automatically attempting to assign itself to a channel as part of a legacy issue. The templates are now able to be replicated again (visit the templates page: http://www.webjam.com/templates).
Redirect Loop Causing sites to Traffic Jam
Some users advised that their network was not appearing when their typed the URL straight in to the browser (as opposed to following a link). This issue has also been resolved. Users who were experiencing this should now be able to access their sites fine but either method.
Activity Email Fixes
There were some issues where activity report emails were being received blank and in some instances not being received at all. We have investigated this issue and believe the issue is now resolved. The activity reports should now be successfully delivered with all the necessary content.
Calendar Module Fixes
We have resolved two bugs that were being experienced with the calendar module. One fix now means that users are able to successfully create events. The second fix means that the option to create a new category is now fully functioning.
Forum Module Settings Lightbox Fix
There was a small cosmetic fix made to the settings lightbox for the forum module. This fix was to lengthen a field that was rendering at half the width of the column when a user wishes to provide multiple forums.
Yesterday, starting around 11:30am GMT and lasting until 19:40pm GMT, Webjam’s partner who providing the systems that allow browsers to find the webjam servers (DNS nameservers) was the target of a massive denial of service (DDoS) attack (see http://en.wikipedia.org/wiki/Denial-of-service_attack for more information). The result was that many users had intermittent problems reaching the Webjam system, even though the system was up & running.
Because of the lack of information during the outage, Webjam decided to switch to another DNS provider. This was implemented last night and the changes went into effect throughout the night. Unfortunately two sub-domains weren’t setup correctly and caused issues this morning – most notably that the dashboard (my.webjam.com) wasn’t reachable. These have been fixed and the site is now fully operational.
We are currently experiencing some connection issues which are causing some users to not be able to reach the site. This is intermittently causing the site to appear down.
We are investigating this issue and hope to have a resolution soon.
We thank you for your patience and apologise for any inconvenience caused.