Wordpress Migration

#1

Hi All,

I’m considering various Ruby-based CMSs to host a small company
website and blog. The site is currently running on Wordpress, whose
support for non-blog pages is an afterthought.

I like the somewhat seamless ability of Radiant to host both types of
content, but before I dive in I wanted to ask whether there has been
any experience migrating content from Wordpress into Radiant?
Mephisto has a converter, which I’ve not yet tried:

http://mephisto.stikipad.com/help/show/Converting+WordPress+to+Mephisto

Another question: suppose I wanted to manage a small database on the
side, and needed to provide a basic UI to manage it. How hard is it
to add an extra tab to Radiant’s admin UI?

Of course I’m happy to get dirty and write some of this code if
necessary, but I need to figure out what I’m getting into first.

best,
christian.

#2

Christian Niles wrote:

Another question: suppose I wanted to manage a small database on the
side, and needed to provide a basic UI to manage it. How hard is it
to add an extra tab to Radiant’s admin UI?

Presently it’s pretty difficult. The next version of Radiant will
feature an extesion system which will allow this.


John L.
http://wiseheartdesign.com

#3

Presently it’s pretty difficult. The next version of Radiant will
feature an extesion system which will allow this.

If you dig through the mail-list archives I think you will see this
next version is supposed to be out sometime in January.

I just played with the extension system and was really impressed
with how easy it was to drop existing rails code into Radiant.

So to do this db management you mentioned… it would only be a
matter of generating the scaffold for the table via rails. Then
generating the extension for Radiant. Then copy a few files and edit
one file and viola!

Cheers-
Michael

#4

I’m trying to keep all my Radiant content in a separate schema in my
database.
For instance, I’d like the layouts table to be ‘radiant.layouts’

Can anyone point me in the right direction?
I’ve not yet tried anything in my development environment.

-Jim

#5

I believe changing the nomenclature of tables would be tough. Rails
relies heavily on naming conventions to generate models and objects,
so even though you can change the table names, it would entagle things
for you.

If you don’t have CREATE privileges in the DB server, I suggest having
your ISP or DBA create a new DB for radiant purposes.

#6

You would set the database as “radiant” in your config/database.yml. Is
this what you’re asking?

Sean C.
seancribbs.com

#7

On 11/29/06, Jim G. removed_email_address@domain.invalid wrote:
I’m trying to keep all my Radiant content in a separate schema in my
database.
For instance, I’d like the layouts table to be ‘radiant.layouts’

Can anyone point me in the right direction?
I’ve not yet tried anything in my development environment.

-Jim

On Nov 29, 2006, at 11:30, Sean C. wrote:

You would set the database as “radiant” in your config/
database.yml. Is this what you’re asking?

Sean C.
seancribbs.com

I’m building some other rails applications in a database called “Dev”
and I want all my tables for one application to be in the “app”
schema. So for example I’d have the table “app.users” in the “Dev”
database and I want to have “randiant.layouts” in the same “Dev”
database.

#8

My apologies. I am using MS SQL Server and I had forgotten to set the
default schema for my user
I changed it to my ‘radiant’ schema and redid the setup_database
All is well. Sorry for using up the bandwidth.

Thanks very much for the help.

#9

Great! Hopefully I’ll get some time to do this soon. I assume from
the responses that I can play around with the system if I start using
the development version from the repository?