Etherpad closure, it’s official!

So folks Etherpad.com is definatley closing, and only 2 weeks later than I predicted.  Do not fret though, Etherpad.org (Run by the Open source Etherpad Foundation) has promised to have a good transition plan in place within the next 7 days and I will be helping with the process.  Etherpad isn’t dead, if anything this is just the beginning 🙂

Obviously I recommend schools use Primary Pad but I am biased.

Here is an extract from Aaron Iba’s statement:

  • EtherPad service will remain the same until April 14th.
  • On April 14th, we will disable new pad creation, but you will still be able to access your existing pads.
  • On May 14th, we will shut down the service and replace the etherpad.com home page with links to other services.

As a reminder, here are two helpful ways to get your data off of EtherPad servers:

  • For free public pads, you can export the pad data to various formats through the “Import/Export” tab at the top of the pad page.
  • For Professional Edition pads, you can export pads individually or download a single ZIP file of all your pad data by clicking the “Download all pads” link at the bottom of the pad list.

Title: Fixing pro domain login for Etherpad installations running on XX YY ZZ type hosting IE prodomain.etherpad.mydomain.com

Overview:
This is a partial fix to the problem that etherpad assumes to be installed on a domain of the form x.y
This patch makes it work for an z.x.y domain, probably breaking it for x.y domains (but I don’t know javascript enough to be sure – parts[2] will be undefined though)
To make it properly we should check how many elements there are into parts[]. Until this is done this is a mere workaround.
Modified code:  (pro_utils.js) – Usually found in /usr/local/etherpad/trunk/etherpad/src/etherpad/pro
Lines 47 – 54 should be modified to read:
function getRequestSuperdomain() {
var parts = request.domain.split(‘.’);
parts.reverse();
if (parts[0] == “.”) {
parts.shift();
}
return [parts[2], parts[1], parts[0]].join(‘.’);
}
Google group discussion talking (without presenting a solution) of this problem is at this link:
http://groups.google.com/group/etherpad-open-source-
discuss/browse_thread/thread/a8c5ceda3186845d/abebff9b8d737428?#abebff9b8d737428

Overview:

This is a partial fix to the problem that etherpad assumes to be installed on a domain of the form x.y

This patch makes it work for an z.x.y domain, probably breaking it for x.y domains (but I don’t know javascript enough to be sure – parts[2] will be undefined though)

To make it properly we should check how many elements there are into parts[]. Until this is done this is a mere workaround.

Modified code: (pro_utils.js) – Usually found in /usr/local/etherpad/trunk/etherpad/src/etherpad/pro

Lines 47 – 54 should be modified to read:


function getRequestSuperdomain() {

var parts = request.domain.split('.');

parts.reverse();

if (parts[0] == ".") {

parts.shift();

}

return [parts[2], parts[1], parts[0]].join('.');

}

Google group discussion talking (without presenting a solution) of this problem