By ziobudda on
Hi all, I want to upgrade my web site from drupal 4.7 (without cck but with my modules) to drupal 5.3 (with cck but not with my modules because I can do all with cck). I have tried node_import module without success, so I need to import users, categories and nodes (varius type) in another way.
Is there some RTFM that explain me how can I do it ? How can I use node_save into my scripts ? How can I import the users and their settings ?
M.
Comments
OMFG... as a noob I shall be
OMFG... as a noob I shall be watching this thread carefully. Does this suggest that future upgrades of Drupal will not be compatible with the site I build now? For instance when 6.x is released? Thank you for bring this to may attention now, before I potentially waste the next six months of my life learing Drupal.
don't panic and get all worked up.
There is always always always a data upgrade path for Drupal core. Contributed modules often have an update path as well.
What the user is doing, is rebuilding/redesigning his site architecture completely to possibly more fully leverage the newer technologies in core that are now available. This maybe a simple thing, this may be a complex thing. It really depends on his target, goals and objectives..
There are export / import modules. There is also various other database direct things that can be done by those far more familiar with the database schema.
I have been upgrading my sites from original installs for several years now.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
> I have been upgrading my
> I have been upgrading my sites from original installs for several years now.
Yes, perhaps. But you write the 'best practices' guide and are an IT tech.
And I notice that you didn't begin to help ziobudda solve his problem?
As someone who is new to Drupal, I find this thread quite disconcerting.
I remember reading in past reviews that devs don't care much about backward compatibility.
And I have read on this site a few articles which imply upgrading is a major deal.
It's not that bad actually,
It's not that bad actually, i am a begginner as well, y upgraded my site from 4.7 to 5. I recommend to stick with the core modules, because upgrading makes life easier, you can accomplish almost everything with the core ones.
Not sure how to help the original poster myself.
Tecito.com
The growing Hispanic community in Canada.
extroplation leads to false conclusion
none of this relevant in any way to my answer. I do not know php, nor am I a MySQL expert. I have a number of fairly stock Drupal contrib sites that I maintain is all. Your response seemed alarmist and fearful of involvement to Drupal based on a mis-understanding of the original question which you them seem to have turned into a personal attack on me.
Upgrading is a major deal in some ways but the tools work really well. When I started, I didn't know how to do this. I merely followed the instructions on a test site and succeeded, then uploaded that success onto my live site. I wrote what I did and contributed it for others to benefit. There are over 200,000 registered user accounts on drupal.org. There are thousands of implementations in various configurations supported by people who are skilled, neophytes, people who refuse to follow instruction, cautious testers who always follow instructions... The skill set of Drupal site implementors is diverse. So of course, you will see people who have issues. This is not unexpected.
Ziobudda doesn't have a problem. Ziobudda has a desire to re-engineer his site architecture, not upgrade it. As such, I don't have a ready answer for him. I know others who have done this sort of thing. This is NOT the Drupal upgrade path, this is a re-implementation of an existing site. There are flexinode to cck mogration tools. You can move/port/convert content in a database to a different type of content. These operations are NOT simple but are certainly do-able. They are advanced things.
He does not have enough information in his initial request to answer with more then generic responses. Even if he did, I suspect it would take someone quite knowledgeable quite some time to go over everything. For potential strategies, look at the methods the modules in the import/export category uses. It really seems his best bet is going to be that route.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
Sorry, I didn't mean to
Sorry, I didn't mean to sound like I was attacking you in any way. It's just the thought of losing 35000 pages of info just because you can't update your modules is frightening. This modules thing freaks me out as it is - having to install five redundant modules to get one piece of functionality that you need simply because they all rely on each other in some sort of weird cascading fashion is a strange and scary concept to me. Throw upgrade paths into that, and you get the reaction illustrated in my first post. If I couldn't develop a 35000 page site any further due to an upgrade issue, I'd be devastated.
Upgrading is obviously something I'm going to have to research before even considering to use Drupal.
=-=
You don't seem to understand the way modules use "hooks"
if a function is included in module A, there really is no need to include the same function in module B ? The dependancy on other modules reduces reduncancy in modules. IMO. This becomes clear with modules that have morphed themselves into API's allowing other modules to expand off of them.
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Thanks for the
Thanks for the explanation.
But surely the module that you need relying on installing one, two or three other modules that you don't need increases rendundancy in the whole system? And there is presumably no guarantee that modules will always remain compatible with each other? I don't know - sounds like a web of potential disaster to me. Plugins sharing core functions but not relying on each other seems safer and less complex?
=-=
The only modules that fall through the cracks are modules that are no longer needed by core for the most part. All major contributed modules are updated. Drupal developers also do a fantastic job of documenting the changes in core API's so that contributed modules can quickly be reworked to adapt to the new/changed API's in core.
I disagree. Some modules work their way toward core or core winds up providing hooks for them to "hook" into.
API's for modules to plug into is a fantastic way to go. A library of funtions much like the PHP language itself.
have a voting API, and voting modules can piggy back off of it, helping to created a plethora of voting modules without each voting module having to write their own API. This also helps modules not cause conflicts with other modules because functions become somewhat standardized. Thus you don't have two different functions named the same bringing a site to a halt.
What modules are you investigating that you don't like the dependencies ? or don't understand the dependencies in place ?
If the modules are dependant on each other, chances are great that it will have to be updated because developers are using them on their own sites, ventures, experiements. This happens because they/we can't update our sites without updating the modules. when module is updated patches are supplied and maintainers review and roll the patches.
Many of the major modules for Drupal if you track backwards through the project pages have been around in some form or fashion since the earliest stages of Drupal. The ones that have fallen off are ones that either weren't popular and never got updated by anyone because of the lack of users using it or got pulled into core in some form or fashion and are no longer needed as a contributed module.
have you read the Drupal Philosophy = http://drupal.org/node/65922
_____________________________________________________________________
My posts & comments are usually dripping with sarcasm.
If you ask nicely I'll give you a towel : )
Hi, I think that you have
Hi, I think that you have not understand my situation: I don't upgrade from standard drupal 4.7.3 to 5.3, but from drupal 4.7.3 where I use modules that I have write to drupal 5.3 where I will use standard module.
Freelancer Senior Drupal Developer -- http://www.ziobuddalabs.it