Re: [Radiant] Backdating posts when moving to Radiant
Are you using Mechanize to import pages into Radiant? That was actually the fastest way I could think off to get my data in there i.e. the code I used for the login: http://www.pastie.org/501391 I can figure out which article number a page has given the page's title as long as it is not a 2nd lvl child (because the page hierarchy is not expanded, the page does not return all links and I can't see a way of clicking the small + sign with mechanize) But that doesn't present a problem for me since I have a root/section/article hierarchy and I only want to add articles to sections. Cheers, V.- ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Backdating posts when moving to Radiant
On Tue, Jun 2, 2009 at 5:02 PM, Charlie Robbins charlie.robb...@gmail.comwrote: The edit published_at field is disabled by default in the Admin interface. You can enable it by changing a config value. Radiant::Config['page.edit.published_date?'] = true More on the wiki: http://wiki.github.com/radiant/radiant/change-a-pages-publication-date Thanks Charlie, that's the part I was missing. I went the mechanize way in order to pump the data into Radiant and everything works fine. Small nag: none of the forms have names, means one needs to pretty print the mechanize output and figure out where in the array to find a form in. All in all about 50 line of code, so I can't complain. Cheers, V.- ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
[Radiant] Backdating posts when moving to Radiant
I have a self-built blog engine that stores article content in text files. Most of the entries are in Textile so I don't see a problem there. I would like to move this content to the new Radiant-based blog I got up and running, and ofcourse I want to backdate them so that posting dates reflect the original posts. Now, I do not want to do this per hand. The article volume is big enough, that contemplating changing the dates per hand gives me carpal tunnel syndrome. I've lready figured out how to post articles to Radiant and have them land in the appropriate places but I can't figure out how the fields for the publication dates are called. So a post about turning these fields on in the Radiant forms, bt I once again failed to do that. And since it was a hint I picked up from the old site I can't find it again - and in the git wiki that page has not been created yet. Anyone have any pointers for me? Cheers, V.- ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Re: [Radiant] Volunteers Needed! Radiant Wiki Migration
John W. Long wrote:
On Apr 7, 2009, at 1:21 PM, Steven Southard wrote:
I'm happy to help. I'll do the first part or the second. It only
looks like about 50 pages. Let me know which you want from me.
Awesome Steven. Why don't you start on the first part.
I took a quick look at the site and there's a couple of this that might
help expedite the situation:
The root of the wiki is the 'Documentation' page. I guess orphan pages
will be handled by the GitHub wiki so you can safely ignore those.
But there are a few pages that can be ignored from the beginning (like
the Welcome to Junebug page). Actually this should be easy, the
welcome page has no edit link.
Some pages (like admin and dbPrueba - spanish speaking devs I see :) )
don't have any content. You might want to filter them out as well.
I think the trickiest part will be the images and how to map the links
from one site to the other (see simple_password page).
Some pages are marked as obsolete in the title. I don't know if you
might want to do some cleanup on that as well.
Now, what we did when moving the ruby-lang content was dump the old
content as a Hash (i.e. {:title,:date,:author,:content} ) with yaml and
then pump it back into radiant. That should make a nice simple handover
format for the second stage.
Hmmm, I won't deprive you of the pleasure in doing this Steven, although
my hands have started itching already :)
Cheers,
V.-
--
http://www.braveworld.net/riva
___
Radiant mailing list
Post: Radiant@radiantcms.org
Search: http://radiantcms.org/mailing-list/search/
Site: http://lists.radiantcms.org/mailman/listinfo/radiant
