On 29 Jul 2005, at 19:39, Kevin Ballard wrote:
> The problem is ideally, the old URLs should be redirected to the  
> new ones. You can do that with mod_rewrite, but to do it with  
> routes you'd have to add a new method to a controller as well to do  
> the redirect.


Yeah I would have liked to redirect the old urls to the new ones ...  
but I have to put my hands up and say I couldn't figure out how to do  
it ... that remains a black art to me.  I don't understand what you  
mean about adding a new method to a controller though.  Will  
something go horribly wrong if I deploy the duplicated lines in  
routes to a live platform?  I was planning the live migration for  
Sunday(ish) :)

It seems to work locally.  URLs are displayed as localhost/articles/y/ 
m/d/title so crawlers should pick up the posts with that taxonomy,  
and any new posts I test have those URLs.  But if I try to navigate  
to an old post (imported for testing, but lets say it was from a  
Google referral) it still handles the old taxonomy I had (localhost/y/ 
m/d/title).  And you're right in saying this only works because I had  
the /year/month/date/title taxonomy both on Textpattern and my  
earlier Wordpress blog ... the only difference between the two is the  
addition of '/article/' in the link.

Gary
------
www.gpshewan.com
From jluster at jluster.org  Fri Jul 29 15:52:27 2005
From: jluster at jluster.org (Jonas M Luster)
Date: Fri Jul 29 15:46:48 2005
Subject: [typo] Redirects / and a themes question
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

> Yeah I would have liked to redirect the old urls to the new  
> ones ... but I have to put my hands up and say I couldn't figure  
> out how to do it ... that remains a black art to me.  I don't  
> understand what you mean about adding a new method to a controller  
> though.  Will something go horribly wrong if I deploy the  
> duplicated lines in routes to a live platform?  I was planning the  
> live migration for Sunday(ish) :)

Something I did before I simply killed four years of WP/Drupal/MT  
imports, was to add a Rewrite for /archives/.../(slug-name) and hand  
it to search?q=$1 (slug-name). A mini-mod to the search code, to  
strip "-" and anyone hitting a non-existing permalink from my old  
site would be getting a search for the title, which worked quite  
well. Idea?

jonas
From tobias.luetke at gmail.com  Fri Jul 29 16:43:55 2005
From: tobias.luetke at gmail.com (Tobias Luetke)
Date: Fri Jul 29 16:38:11 2005
Subject: [typo] Need help upgrading
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

Thanks for figuring this one out! We should definitely fix that

On 7/29/05, Christopher Bailey <[EMAIL PROTECTED]> wrote:
> Thanks everyone for your help.  I finally figured out why it wasn't working.
> If any blog entry didn't have a [valid] value in the "text_filter" column of
> the articles table, then the migration would blow up when it got to that
> record.  Fixing that enabled the migration to work fine.  For both my blogs,
> I happened to have a record that had an empty value (not null though) in
> that column.
> 
> Now that I've upgraded, I'd like to say great work on the various changes!
> The new Sidebar stuff is very cool, amongst other things.  Also, assuming
> you don't have funky data in your DB, the upgrade process was very slick.
> 
> 
> On 7/28/05 1:53 AM, "Robin Bowes" <[EMAIL PROTECTED]> wrote:
> 
> > Kevin Ballard wrote:
> >> In a production environment, you want to do `rake migrate
> >> RAILS_ENV=production`. Without that, you're migrating the development
> >> environment, which isn't very useful.
> >
> > So, to recap, the process to upgrade would be:
> >
> > svn update
> > rake migrate  RAILS_ENV=production
> >
> > Job done?
> >
> > I did this:
> >
> > svn update
> > Browse to http://typo.robinbowes.com/admin
> > Login
> > Run the migrations
> > Clear page cache
> > Restart apache
> >
> > Is there anything else I need to do? Like removing any static files, etc.?
> >
> > R.
> 
> 
> _______________________________________________
> Typo-list mailing list
> Typo-list@rubyforge.org
> http://rubyforge.org/mailman/listinfo/typo-list
> 


-- 
Tobi
http://www.snowdevil.ca - Snowboards that don't suck
http://typo.leetsoft.com - Open source weblog engine
http://blog.leetsoft.com - Technical weblog

Reply via email to