Re: [Radiant] Upgrading: 0.6.7 -> 0.9.1
But isn't it a bit "bad" (to put it mildly) that running the migrate rake tasks would drop all of my tables? That's not much of a "migration"--it's more like a hostile takeover. I'm reminded that a few months back I did an upgrade from 0.6.7 to 0.8.1 (that work has been lost, unfortunately) and I didn't have this data loss problem. -dan On Thu, Sep 23, 2010 at 2:26 PM, William Ross wrote: > On 23 Sep 2010, at 21:55, john muhl wrote: > > > On Thu, Sep 23, 2010 at 3:17 PM, D.Kreft wrote: > >> I'm attempting to upgrade Radiant from 0.6.7 to 0.9.1 and it's proving > to be > >> quite a pain. > > > > i prefer to upgrade one version at a time. so in your case i'd first > > go to 0.6.9, then 0.7.1, 0.8.1 and finally 0.9.1 > > ... which isn't quite as bad as it sounds. There are tags in the repository > for every version from 0.6.8 onwards, so it's just a case of doing: > >git checkout 0.6.8 >rake db:migrate > > a few times. You can skip some of the minor updates, as John suggests. > > The update task on the other hand is not incremental: all it does is copy > over the current set of files (and latterly this involves backing up and > replacing your configuration files, so running it more than once can be > destructive). With any luck you can step through all the migrations and then > run rake radiant:update once at the end. > > If your installation is more complicated, it's likely that you'll run into > problems with extension compatibility across major version changes. In that > case your best bet is probably to strip it down to radiant core and a few > essentials, update as above and then have a look at what's available now. > > best, > > will > > >
Re: [Radiant] Upgrading: 0.6.7 -> 0.9.1
On 23 Sep 2010, at 21:55, john muhl wrote: > On Thu, Sep 23, 2010 at 3:17 PM, D.Kreft wrote: >> I'm attempting to upgrade Radiant from 0.6.7 to 0.9.1 and it's proving to be >> quite a pain. > > i prefer to upgrade one version at a time. so in your case i'd first > go to 0.6.9, then 0.7.1, 0.8.1 and finally 0.9.1 ... which isn't quite as bad as it sounds. There are tags in the repository for every version from 0.6.8 onwards, so it's just a case of doing: git checkout 0.6.8 rake db:migrate a few times. You can skip some of the minor updates, as John suggests. The update task on the other hand is not incremental: all it does is copy over the current set of files (and latterly this involves backing up and replacing your configuration files, so running it more than once can be destructive). With any luck you can step through all the migrations and then run rake radiant:update once at the end. If your installation is more complicated, it's likely that you'll run into problems with extension compatibility across major version changes. In that case your best bet is probably to strip it down to radiant core and a few essentials, update as above and then have a look at what's available now. best, will
Re: [Radiant] Upgrading: 0.6.7 -> 0.9.1
On Thu, Sep 23, 2010 at 3:17 PM, D.Kreft wrote: > I'm attempting to upgrade Radiant from 0.6.7 to 0.9.1 and it's proving to be > quite a pain. i prefer to upgrade one version at a time. so in your case i'd first go to 0.6.9, then 0.7.1, 0.8.1 and finally 0.9.1
[Radiant] Upgrading: 0.6.7 -> 0.9.1
I'm attempting to upgrade Radiant from 0.6.7 to 0.9.1 and it's proving to be
quite a pain. I tried to use the upgrade instructions I found at
http://groups.google.com/group/radiantcms/browse_thread/thread/c2f5ecac923ddee9
:
% rake radiant:update
% rake db:migrate
But the second command does horrible things. First of all, it nukes all the
data in all my tables and then it complains thusly:
rake aborted!
An error has occurred, this and all later migrations canceled:
SQLite3::SQLException: table "sessions" already exists: CREATE TABLE
"sessions" ("id" INTEGER PRIMARY KEY AUTOINCREMENT NOT NULL, "session_id"
varchar(255), "data" text, "updated_at" datetime)
Is there some magic wand I can wave to solve this problem?
-dan
[Radiant] Re: How to handle a 1,000 page site???
Hey guys, bad news; the gorilla_blog extension is not compatible with radiant =< 0.9, mainly due to the admin_tree_structure part. I have been planning to rewrite this specific functionality in a seperate extension, but higher priority stuff keeps sneaking in.. by the way David, for the record, the fact that archive items are prepended with %Y/%m is default behavior for children of an ArchivePage regards, Benny On 22 sep, 08:03, "David Bacon" wrote: > We've used it with Paperclipped and the Settings extension. > > PageFactory and PageParts I haven't tried. > > Not sure how much documentation is available. I'm in the luxurious position > of asking our developers to install this type of thing, so I'm not going to > be much help on the finer technical details. > > Cheers, > David > > > > -Original Message- > From: "GV" > Sent: Wednesday, 22 September, 2010 3:46pm > To: "Radiant CMS" > Subject: [Radiant] Re: How to handle a 1,000 page site??? > > Looks good. I will install and test tomorrow. > > Does this extension work well with PageFactory, PageParts, > Paperclipped and Settings extensions?? > > Is there any help documentation? > > Thank You for your time. > > On Sep 21, 10:22 pm, "David Bacon" wrote: > > Sure - I've attached an image, hopefully it will come through. > > > The year/month directory structure is automatically created for pages that > > you set to have the type 'archive'. It's based on the publication date of > > the pages. > > > The children are contained within the 'month' directory. > > > This also affects the URLs on the site, so they would have > > '/features/2010/09/', which is not ideal in my opinion, but not a deal > > breaker. > > > -Original Message- > > From: "Nate" > > Sent: Wednesday, 22 September, 2010 1:01pm > > To: radiantcms@googlegroups.com > > Subject: Re: [Radiant] How to handle a 1,000 page site??? > > > On 9/21/10 9:11 PM, David Bacon wrote: > > > We've used the Admin Tree Structure extension on our sites. It creates > > > an automatic year/month directory structure in the admin tools which > > > helps manage directories with a lot of children. > > > > It's part of this extension: > > >http://github.com/jomz/radiant-gorilla-blog-extension > > > Could you perhaps post a screenshot somewhere that shows how the admin > > looks with that extension running? The page display on the admin side is > > one of the chief reasons I decided to move a client's site to Wordpress > > and it would be lovely if I didn't have to continue moving the site. > > Wordpress is a nightmare to build templates for. I miss radius tags so > > very much. All the PHP code in the layouts is melting my brain. And it's > > even harder to sift through all the crap plugins to find the ones that > > are actually useful. > > > ~Nate > > > ishot-4.jpg > > 103KViewDownload
[Radiant] Gallery Extension in Radiant 8.1
Hello List : I have an older 8.1 Radiant site with the Gallery extension, installed in early 2009. The client has a fairly large collection of images up there. The gallery on this site has never worked properly, though galleries on several other sites of the same vintage and config work fine. The problem is with the delete function in the Galleries admin. The admin appears to delete, but when we refresh the page, the "deleted" image reappears. I have copied in a new app folder inside the extension, but this did not change anything. I don't know what to try next. I'd hate for my client to have to remake her entire gallery, so installing a different extension would be my last choice. All help/suggestions welcome. ~ Alexis = Alexis Masters, author http://www.alexismasters.com 510 234-0027
[Radiant] feed_me extension for metaweblogapi
Hi gang, I am attempting to convert my blog over to radiantcms & rails 3. I am getting the following error when trying to hit api/xmlrpc: http://gist.github.com/579241 Now, I have researched myself enough to know that I am running radiant with rails 3 and feed_me has a dependency on actionwebservice which doesn't seem to support rails 3. The extension is simple enough and I want to try to fix it myself. Maybe even make a contribution back to the community. My question is what is the rails 3 way of standing up a web service? I can't seem to find any documentation on it and my google-fu is failing me. Thanks for any pointers in the right direction, even if it's a "go read this" kinda response. Bobby
