drupal 5
Tue, 2007-01-23 12:30 — calebtr
Has anyone upgraded to 5 yet? (Just curious)
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.Has anyone upgraded to 5 yet? (Just curious)
This work is licensed under a Creative Commons Attribution- NonCommercial- ShareAlike 2.5 License.
Haven't done so yet, but I
Haven't done so yet, but I have no excuse for not upgrading Drupalib, since all the modules the site uses are available for 5 (although one is still "-dev"). The only thing holding me back is that the "News Portal" theme hasn't been updated for 5 yet. I can't see any mention of plans to do so on the theme's project page. I maintain two other public sites and both use modules that I wrote, so the ball's in my court for these ones.
I have installed it on my laptop and I have to say that the improvements from the admin's point of view are dramatic and long overdue, particularly the way modules are managed.
Upgrade Path from Flexinode to CCK - Data Integrity?
I run a number of community sites based on Drupal as well.
We're still mired in 4.6 & 4.7 for the simple fact that I haven't yet found a solution for "reformatting" event listings orginally done with Flexinode into the new CCK.
They're dropping Flexinode with 4.7 so this kind of transfer is important -- especially since for one site at least, I've got thousands of events.
So this is a problem.
It's funny how they said they were investing so much time in improving the usability of Drupal with version 5. They can have all the usability in the world and it won't matter if there's no upgrade path to ensure data integrity from one version to the other.
flexinode!
I have close to 37,000 flexinodes in 4.7. I am assuming I will either create a custom content type or convert to CCK, but either way, I don't really think I can expect anyone to do it for me.
I haven't played with CCK yet beecause flexinode is installed. A fresh Drupal install is also out because my host supplies only one MySQL database - I suppose I am going to have to do a heap of testing on a non-work server.
I think I will be able to keep the node table as-is (except $node->type) and run a Perl script to map the old flexinode table to CCK without changing any node IDs to preserve commenting and taxonomies.
Or is it not that simple?
Easy enough to say...
Good luck on converting all 37k nodes. Your solution doesn't sound at all simple.
Flexinode was a major module. The decision to abandon it in favor of CCK wasn't made by some lone "maintainer" but by the people who decide the general direction of Drupal.
The fact that there's no easy upgrade path is an extraordinary oversight. It's an absolute red alert to anyone considering using Drupal. This isn't getting people to do my work for me. Rather, it's a pretty basic expectation of what a CMS ought to do. Nobody chooses a CMS just to be led to this kind of cliff.
And of course the ultimate irony is the attention paid to usability. What audience requires a CMS that's easy to use but not at all easy to preserve? Given the context, such concerns are pretty much superfluous.
I hear you, leo. I didn't
I hear you, leo. I didn't mean to imply that /you/ should have to do the conversion yourself, just that I've applied a fairly complex hack and it's up to me to also hack my way out of it.
Everything I've read on drupal.org indicates that flexinode was meant as a "proof of concept". I've only been around Drupal for about a year though, and started on 4.7, so your take is helpful. I don't see why the community hasn't stepped up on this.
It seems to me that though many developers are listed for flexinode, only one person is really active on in updating it, and he's focused on converting 4.6 to 4.7. Maybe the lesson learned is to not base an entire site on a module with such a tiny developer community - and of course a newbie can't know.
I'm a little iffy on the user interface and form development aspects of drupal, but if I can manage a hack that you might be able to use, I'll be happy to share.
I wonder if the import/export module will help, though that's in 4.7....
looky
looky, flexinode to cck converter
http://drupal.org/project/flexiconvert
quite a few "limitations"!
Yup, Helpful But...
I saw the module. My problem, at least potentially, is that I've got a couple thousand events to migrate/convert.
They all have date and time fields and it doesn't look like the flexiconvert module will handle them. In a post on the module he says, "Only converts text types".
I left a question on the original post. Who knows.
5.x Still Not There (For Me)
I'm working on a new Drupal Site which I'm dying to declare to the world (once it's in working shape).
I spent maybe two days last weekend trying to get it working in 5.x but after a number of problems I decided to go back to 4.7 -- at least for the initial launch.
It wasn't simply a case of modules not being upgraded to 5.x -- in fact, most of the ones I needed were already there -- it just seemed as if the modules didn't play nice with each other -- at least to the degree that they do in 4.7.
I may be imagining this but after a lot of fits and starts, as I said, I just went back to 4.7.
which modules?
which modules?
I'm playing with a 5.1 installation, but all I'm working with right now is CCK.
Now I Switched Back to 5.1!
Yes, I know, schizophrenia...
I went from 4.7 to 5.1, then from 5.1 to 4.7. Now I'm back to 5.1.
It's on a test site. Originally in 5.1, I was having problems with Subscriptions and then the patch to Community Tags didn't work. I wasn't sure if maybe I would be going with a Theme only available in 4.7. "Comment Notify" which I was thinking of using was only available in 4.7, etc.
So I switched back to 4.7. But then after a little more work, I decided that I could do without a couple of features at the moment (eg. Community Tags or Taxonomy User, VoteAPI working properly with Views, etc.) and that the advantage lay with 5.1.
So now I'm back again with 5.1.
I figured that once I got Project X into production that upgrades would be far easier.
Going back and forth like this has made be good at:
Post new comment