Help in migrating from Drupal 5 to 7
The situation with our blog is getting pretty dire. We're running a custom written Drupal 5 designed to be secure before functional. It seems this code is heavily reliant on some old php functions which no longer exist in modern-day php5. Rather than re-writing the code, upgrading to modern Drupal is the current best answer. Is anyone here a drupal expert? Do you want to help us out? We need to migrate the content and comments to modern Drupal. We have an endless ticket of love at https://trac.torproject.org/projects/tor/ticket/10022#comment:15 discussing this topic. Since consensus-based decision making isn't working, I'm deciding we're going to Drupal 7. Helpful thoughts, advice, and pointers are welcome. Thanks! -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
There is a Drupal module that can be used to help the migration called migrate_d2d. I have not used it, but there seems to be a good tutorial here. Going to Drupal 7 is your best at the moment. Drupal 8 looks like it will be much better than 7, but is too new at the moment. On Aug 27, 2014, at 10:41 AM, Andrew Lewman <andrew@torproject.is> wrote:
The situation with our blog is getting pretty dire. We're running a custom written Drupal 5 designed to be secure before functional. It seems this code is heavily reliant on some old php functions which no longer exist in modern-day php5.
Rather than re-writing the code, upgrading to modern Drupal is the current best answer.
Is anyone here a drupal expert? Do you want to help us out?
We need to migrate the content and comments to modern Drupal.
We have an endless ticket of love at https://trac.torproject.org/projects/tor/ticket/10022#comment:15 discussing this topic.
Since consensus-based decision making isn't working, I'm deciding we're going to Drupal 7.
Helpful thoughts, advice, and pointers are welcome. Thanks!
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
Andrew - if indeed this needs to stay on Drupal, can a copy of the Drupal installation/DB be generated for us to play with locally? Feel free to email directly to coordinate that. E On Aug 27, 2014, at 4:49 PM, Sean Rafferty <seanmrafferty@me.com> wrote:
There is a Drupal module that can be used to help the migration called migrate_d2d. I have not used it, but there seems to be a good tutorial here. Going to Drupal 7 is your best at the moment. Drupal 8 looks like it will be much better than 7, but is too new at the moment.
On Aug 27, 2014, at 10:41 AM, Andrew Lewman <andrew@torproject.is> wrote:
The situation with our blog is getting pretty dire. We're running a custom written Drupal 5 designed to be secure before functional. It seems this code is heavily reliant on some old php functions which no longer exist in modern-day php5.
Rather than re-writing the code, upgrading to modern Drupal is the current best answer.
Is anyone here a drupal expert? Do you want to help us out?
We need to migrate the content and comments to modern Drupal.
We have an endless ticket of love at https://trac.torproject.org/projects/tor/ticket/10022#comment:15 discussing this topic.
Since consensus-based decision making isn't working, I'm deciding we're going to Drupal 7.
Helpful thoughts, advice, and pointers are welcome. Thanks!
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
If it can wait two weeks I'd love to help, I have quite a bit of experience migrating data into Drupal 7 and securing it. It might also be worth installing Aegir which is an application for managing Drupal sites and makes upgrading/migrating/cloning simpler, be it for a major upgrade between versions, creating development clones or just testing minor upgrades that come out fairly regularly. Someone will need to maintain the Drupal installation afterwards to be sure any security updates get applied quickly. I haven't used the migrate d2d module before but have a lot of experience with the import module which lets you feed a CSV file to be imported. It's pretty straightforward, extract the blog posts/comments from the D5 database in CSV format, modelize the new blog post/comment structure in D7, map the D5 fields to the D7 fields and import the CSV file. Unless there are already character encoding issues this goes very smoothly. On Wed, Aug 27, 2014 at 1:01 PM, Eric Schaefer <omg@eric-schaefer.com> wrote:
Andrew - if indeed this needs to stay on Drupal, can a copy of the Drupal installation/DB be generated for us to play with locally? Feel free to email directly to coordinate that.
E
On Aug 27, 2014, at 4:49 PM, Sean Rafferty <seanmrafferty@me.com> wrote:
There is a Drupal module that can be used to help the migration called migrate_d2d. I have not used it, but there seems to be a good tutorial here. Going to Drupal 7 is your best at the moment. Drupal 8 looks like it will be much better than 7, but is too new at the moment.
On Aug 27, 2014, at 10:41 AM, Andrew Lewman <andrew@torproject.is> wrote:
The situation with our blog is getting pretty dire. We're running a custom written Drupal 5 designed to be secure before functional. It seems this code is heavily reliant on some old php functions which no longer exist in modern-day php5.
Rather than re-writing the code, upgrading to modern Drupal is the current best answer.
Is anyone here a drupal expert? Do you want to help us out?
We need to migrate the content and comments to modern Drupal.
We have an endless ticket of love at https://trac.torproject.org/projects/tor/ticket/10022#comment:15 discussing this topic.
Since consensus-based decision making isn't working, I'm deciding we're going to Drupal 7.
Helpful thoughts, advice, and pointers are welcome. Thanks!
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
On 08/27/2014 10:49 AM, Sean Rafferty wrote:
There is a Drupal module that can be used to help the migration called migrate_d2d. I have not used it, but there seems to be a good tutorial here. Going to Drupal 7 is your best at the moment. Drupal 8 looks like it will be much better than 7, but is too new at the moment.
Thanks. migrate_d2d seems good. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
Too bad that it’s staying on Drupal! I had worked out exporting all posts, comments, and events into markdown files for Jekyll (this is totally done) with a ruby script [https://trac.torproject.org/projects/tor/ticket/10479]. I could have a Jekyll version of the complete Tor blog up and running by Friday. But then of course there’s the issue of where to host comments, etc etc. Still seems like an easier task than a Drupal migration though. At any rate, I’ve done a Drupal migration before, although I wouldn’t call myself an expert. But I can move the legacy data around. Someone else will need to secure the yawning security issues with D7. Happy to chat more either here or on tor-www on IRC. Eric On Aug 27, 2014, at 4:41 PM, Andrew Lewman <andrew@torproject.is> wrote:
The situation with our blog is getting pretty dire. We're running a custom written Drupal 5 designed to be secure before functional. It seems this code is heavily reliant on some old php functions which no longer exist in modern-day php5.
Rather than re-writing the code, upgrading to modern Drupal is the current best answer.
Is anyone here a drupal expert? Do you want to help us out?
We need to migrate the content and comments to modern Drupal.
We have an endless ticket of love at https://trac.torproject.org/projects/tor/ticket/10022#comment:15 discussing this topic.
Since consensus-based decision making isn't working, I'm deciding we're going to Drupal 7.
Helpful thoughts, advice, and pointers are welcome. Thanks!
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
On 08/27/2014 10:19 AM, Eric Schaefer wrote:
Too bad that it’s staying on Drupal! I had worked out exporting all posts, comments, and events into markdown files for Jekyll (this is totally done) with a ruby script [https://trac.torproject.org/projects/tor/ticket/10479]. I could have a Jekyll version of the complete Tor blog up and running by Friday. But then of course there’s the issue of where to host comments, etc etc. Still seems like an easier task than a Drupal migration though.
I'm with you Eric. I created a sandbox Juvia server that we could have used to host comments but no one ever contacted me about using it. I therefore deleted the VPS instance a while ago. I'm happy to set it up again if there is any interest. Thank you, Tom Purl
On 08/27/2014 01:34 PM, Tom Purl wrote:
I'm with you Eric. I created a sandbox Juvia server that we could have used to host comments but no one ever contacted me about using it. I therefore deleted the VPS instance a while ago. I'm happy to set it up again if there is any interest.
The challenge here is Debian. If everything is "apt-get install" easy, then we can use it. If not, we don't run 3rd party code on our servers, this custom drupal 5 installation is a perfect example of why not. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
Eric Schaefer wrote:
I could have a Jekyll version of the complete Tor blog up and running by Friday.
This would be great if it's not too much work. Remember this community is more of a do-ocracy; if you think something needs to be done, do it :) Bests, -- Nima 0XC009DB191C92A77B | @nimaaa | mrphs "I disapprove of what you say, but I will defend to the death your right to say it" --Evelyn Beatrice Hall
Remember this community is more of a do-ocracy; if you think something needs to be done, do it :)
Indeed! Barebones, unstyled version of the Jekyll version can be found downloaded here: https://github.com/eschaefer/tor-blog Live demo: http://tor-blog.deadhare.com/ Just needs comments + events imported (I have a JSON blob of these) E On Aug 27, 2014, at 9:07 PM, Nima Fatemi <nima@riseup.net> wrote:
Eric Schaefer wrote:
I could have a Jekyll version of the complete Tor blog up and running by Friday.
This would be great if it's not too much work.
Remember this community is more of a do-ocracy; if you think something needs to be done, do it :)
Bests, -- Nima 0XC009DB191C92A77B | @nimaaa | mrphs
"I disapprove of what you say, but I will defend to the death your right to say it" --Evelyn Beatrice Hall
________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
Hi Eric, hi www-team,
On 27 Aug 2014, at 21:56, Eric Schaefer <omg@eric-schaefer.com> wrote:
Remember this community is more of a do-ocracy; if you think something needs to be done, do it :)
Indeed!
Barebones, unstyled version of the Jekyll version can be found downloaded here: https://github.com/eschaefer/tor-blog
Live demo: http://tor-blog.deadhare.com/
Just needs comments + events imported (I have a JSON blob of these)
I've recently started maintaining the website a little, and the blog still has a bunch of tickets open and work left. Are you still working on it, do you need anything, are you blocked on anything? What can we do to help? Cheers Sebastian
Hey Sebastian -- I just noticed I didn't get back to you on this, but Jeremy's been killin' it on the final steps for the blog: https://trac.torproject.org/projects/tor/ticket/10022#comment:40 <https://trac.torproject.org/projects/tor/ticket/10022#comment:40> Basically I guess we just need to figure out of Isso is a valid enough commenting system, or if we're stuck with Juvia. It's surprisingly hard to find a commenting solution that fits our needs. I tried to get Isso running on a local VM, but it was surprisingly hard to get it going. If you wanna test-drive it, then be my guest! http://posativ.org/isso/docs/install/ <http://posativ.org/isso/docs/install/> Eric
On Feb 9, 2015, at 5:37 AM, Sebastian Hahn <sebastian@torproject.org> wrote:
Hi Eric, hi www-team,
On 27 Aug 2014, at 21:56, Eric Schaefer <omg@eric-schaefer.com> wrote:
Remember this community is more of a do-ocracy; if you think something needs to be done, do it :)
Indeed!
Barebones, unstyled version of the Jekyll version can be found downloaded here: https://github.com/eschaefer/tor-blog
Live demo: http://tor-blog.deadhare.com/
Just needs comments + events imported (I have a JSON blob of these)
I've recently started maintaining the website a little, and the blog still has a bunch of tickets open and work left. Are you still working on it, do you need anything, are you blocked on anything? What can we do to help?
Cheers Sebastian ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
Thanks for continuing to pay attention and work on this! -- Andrew +1-781-948-1982 https://www.torproject.org/ ------ Original Message ------ From: "Eric Schaefer" <omg@eric-schaefer.com> To: "Tor Website Team" <www-team@lists.torproject.org> Sent: 2015-03-02 16:47:23 Subject: Re: [Tor www-team] Help in migrating from Drupal 5 to 7
Hey Sebastian --
I just noticed I didn't get back to you on this, but Jeremy's been killin' it on the final steps for the blog: https://trac.torproject.org/projects/tor/ticket/10022#comment:40
Basically I guess we just need to figure out of Isso is a valid enough commenting system, or if we're stuck with Juvia. It's surprisingly hard to find a commenting solution that fits our needs.
I tried to get Isso running on a local VM, but it was surprisingly hard to get it going. If you wanna test-drive it, then be my guest! http://posativ.org/isso/docs/install/
Eric
On Feb 9, 2015, at 5:37 AM, Sebastian Hahn <sebastian@torproject.org> wrote:
Hi Eric, hi www-team,
On 27 Aug 2014, at 21:56, Eric Schaefer <omg@eric-schaefer.com> wrote:
Remember this community is more of a do-ocracy; if you think something needs to be done, do it :)
Indeed!
Barebones, unstyled version of the Jekyll version can be found downloaded here: https://github.com/eschaefer/tor-blog
Live demo: http://tor-blog.deadhare.com/
Just needs comments + events imported (I have a JSON blob of these)
I've recently started maintaining the website a little, and the blog still has a bunch of tickets open and work left. Are you still working on it, do you need anything, are you blocked on anything? What can we do to help?
Cheers Sebastian ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
Hi Eric,
On 02 Mar 2015, at 16:47, Eric Schaefer <omg@eric-schaefer.com> wrote: I just noticed I didn't get back to you on this, but Jeremy's been killin' it on the final steps for the blog: https://trac.torproject.org/projects/tor/ticket/10022#comment:40
No worries, and thanks.
Basically I guess we just need to figure out of Isso is a valid enough commenting system, or if we're stuck with Juvia. It's surprisingly hard to find a commenting solution that fits our needs.
I tried to get Isso running on a local VM, but it was surprisingly hard to get it going. If you wanna test-drive it, then be my guest! http://posativ.org/isso/docs/install/
Currently focusing more on the regular website, not the blog. Let me know if you need anything from me tho. Cheers Sebastian
On 08/27/2014 11:19 AM, Eric Schaefer wrote:
Too bad that it’s staying on Drupal! I had worked out exporting all posts, comments, and events into markdown files for Jekyll (this is totally done) with a ruby script [https://trac.torproject.org/projects/tor/ticket/10479]. I could have a Jekyll version of the complete Tor blog up and running by Friday. But then of course there’s the issue of where to host comments, etc etc. Still seems like an easier task than a Drupal migration though.
This is awesome. Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term. We may find out that our drupal 5 design doesn't work at all with drupal 7 and have to revert. If it does work, in the short term (1 month), we'd at least have a working blog again (comments, posting, spam control, search functionality, event calendar, etc) -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
Totally understandable. What are the first steps to get a copy of the old Drupal site (with scrubbed/new admin credentials, etc)? E On Aug 27, 2014, at 10:25 PM, Andrew Lewman <andrew@torproject.is> wrote:
On 08/27/2014 11:19 AM, Eric Schaefer wrote:
Too bad that it’s staying on Drupal! I had worked out exporting all posts, comments, and events into markdown files for Jekyll (this is totally done) with a ruby script [https://trac.torproject.org/projects/tor/ticket/10479]. I could have a Jekyll version of the complete Tor blog up and running by Friday. But then of course there’s the issue of where to host comments, etc etc. Still seems like an easier task than a Drupal migration though.
This is awesome. Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
We may find out that our drupal 5 design doesn't work at all with drupal 7 and have to revert. If it does work, in the short term (1 month), we'd at least have a working blog again (comments, posting, spam control, search functionality, event calendar, etc)
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
Also what version of Debian / PHP / MySQL should I set up for running/testing locally, to match what’s available in production? Apologies if this is documented somewhere, I just couldn’t find it. On Aug 28, 2014, at 8:45 AM, Eric Schaefer <omg@eric-schaefer.com> wrote:
Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
Totally understandable.
What are the first steps to get a copy of the old Drupal site (with scrubbed/new admin credentials, etc)?
E
On Aug 27, 2014, at 10:25 PM, Andrew Lewman <andrew@torproject.is> wrote:
On 08/27/2014 11:19 AM, Eric Schaefer wrote:
Too bad that it’s staying on Drupal! I had worked out exporting all posts, comments, and events into markdown files for Jekyll (this is totally done) with a ruby script [https://trac.torproject.org/projects/tor/ticket/10479]. I could have a Jekyll version of the complete Tor blog up and running by Friday. But then of course there’s the issue of where to host comments, etc etc. Still seems like an easier task than a Drupal migration though.
This is awesome. Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
We may find out that our drupal 5 design doesn't work at all with drupal 7 and have to revert. If it does work, in the short term (1 month), we'd at least have a working blog again (comments, posting, spam control, search functionality, event calendar, etc)
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
On 08/28/2014 04:08 AM, Eric Schaefer wrote:
Also what version of Debian / PHP / MySQL should I set up for running/testing locally, to match what’s available in production? Apologies if this is documented somewhere, I just couldn’t find it.
We run debian stable with wheezy backports. Whatever is in debian repos is what we're going to install. This appears to be: apt-cache show drupal7 | grep Version Version: 7.31-1~bpo70+1 Version: 7.14-2+deb7u6 Version: 7.14-2+deb7u4 Thanks! -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
I had some time this weekend, so just to see if I could, I managed to import all comments to a self-hosted Juvia server. These get loaded into static pages generated by Jekyll. In addition, I also imported all the old events from the blog into their own category in Jekyll too. Anyway, just a thought on how to *in theory* move forward with this... Server1: - apt-get install jekyll - Hosts static jekyll blog. New posts generated with git hook after new Markdown files (posts) are committed. Server2: - Self-hosts Juvia comments, since Juvia is a rails app. Comments are delivered through a javascript snippet in the Jekyll blog post template. Seems like less headache than Drupal to me. Plus the blog content is nicely stored in Markdown files and away from any database. Andrew - Juvia is third-party, yep, but at least it can live in it's own lil container... E On Aug 28, 2014, at 3:54 PM, Andrew Lewman <andrew@torproject.is> wrote:
On 08/28/2014 04:08 AM, Eric Schaefer wrote:
Also what version of Debian / PHP / MySQL should I set up for running/testing locally, to match what’s available in production? Apologies if this is documented somewhere, I just couldn’t find it.
We run debian stable with wheezy backports. Whatever is in debian repos is what we're going to install. This appears to be:
apt-cache show drupal7 | grep Version Version: 7.31-1~bpo70+1 Version: 7.14-2+deb7u6 Version: 7.14-2+deb7u4
Thanks!
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
On 09/07/2014 08:27 AM, Eric Schaefer wrote:
I had some time this weekend, so just to see if I could, I managed to import all comments to a self-hosted Juvia server. These get loaded into static pages generated by Jekyll. In addition, I also imported all the old events from the blog into their own category in Jekyll too.
Anyway, just a thought on how to *in theory* move forward with this...
Awesome. Is there a juvia demo somewhere? -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
Awesome. Is there a juvia demo somewhere?
There's a demo at http://juvia-demo.phusion.nl/users/sign_in login: discard@phusion.nl pw: 123456 But I don't have a public version of the local one (vagrant/debian) I imported the comments to. Should have a public VPS set up soon tho. One more thing... I would like to patch our copy of Juvia so it does not keep track of commenter IP address and user agent [0] [0] - https://github.com/phusion/juvia/blob/master/app/controllers/api_controller.... line 74/75 Eric On Sep 8, 2014, at 3:47 PM, Andrew Lewman <andrew@torproject.is> wrote:
On 09/07/2014 08:27 AM, Eric Schaefer wrote:
I had some time this weekend, so just to see if I could, I managed to import all comments to a self-hosted Juvia server. These get loaded into static pages generated by Jekyll. In addition, I also imported all the old events from the blog into their own category in Jekyll too.
Anyway, just a thought on how to *in theory* move forward with this...
Awesome. Is there a juvia demo somewhere?
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
On 08/28/2014 02:45 AM, Eric Schaefer wrote:
Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
Totally understandable.
What are the first steps to get a copy of the old Drupal site (with scrubbed/new admin credentials, etc)?
I'm working on it. Hopefully today. -- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982
I'm working on it. Hopefully today.
Ok cool. Just keep me posted! I'd love to get started on this. On Aug 28, 2014, at 3:54 PM, Andrew Lewman <andrew@torproject.is> wrote:
On 08/28/2014 02:45 AM, Eric Schaefer wrote:
Mostly what I'm looking to do is to keep our blog working in the short term, and figure out a better plan for long term.
Totally understandable.
What are the first steps to get a copy of the old Drupal site (with scrubbed/new admin credentials, etc)?
I'm working on it. Hopefully today.
-- Andrew pgp 0x6B4D6475 https://www.torproject.org/ +1-781-948-1982 ________________________________________________________________________ Tor Website Team coordination mailing-list
To unsubscribe or change other options, please visit: https://lists.torproject.org/cgi-bin/mailman/listinfo/www-team
participants (8)
-
Andrew Lewman -
Eric Schaefer -
Nima Fatemi -
Olssy -
Sean Rafferty -
Sebastian Hahn -
Sebastian Hahn -
Tom Purl