Drupal 6.x is available several months. It would be nice to have an updated version.

CommentFileSizeAuthor
#31 importexportapi-ISSUE-283462.patch28.55 KBAnonymous (not verified)
#26 importexportapi-d6.patch116.71 KBJaza
#19 importexportapi-ISSUE-283462.patch28.6 KBAnonymous (not verified)
#9 importexportapi-drupal6.2.patch28.09 KBtauno
#5 importexportapi-drupal6.patch25.15 KBrmh3093

Comments

bneel’s picture

bneel commented

I'm interested for an updated version.
But the idear will be to import data from a 5 version to a 6 version.
Is it possible.
Thx
Ben

appel’s picture

appel commented

Subscribing!

rmh3093’s picture

rmh3093 commented

im am working on porting it to 6

rmh3093’s picture

rmh3093 commented
Assigned: Unassigned » rmh3093
rmh3093’s picture

rmh3093 commented
StatusFileSize
new importexportapi-drupal6.patch25.15 KB

Here is my attempt to port this module, it does not work 100%, maybe someone can take it the rest of the way. I dont know what is wrong.

ñull’s picture

ñull commented

subscribing

joncup’s picture

joncup commented

subscribing *bump*

nathanjo’s picture

nathanjo commented

subscribing

tauno’s picture

tauno commented
Status: Active » Needs work
StatusFileSize
new importexportapi-drupal6.2.patch28.09 KB

Here's an updated patch that I rolled. It's very untested, but it fixes some omissions from the previous patch (namely adding the &$form_state parameter to the hook_form functions and fixing the schema).

mohamed_e’s picture

mohamed_e commented

*subscribing*

Great! Thanks guys! Any ideas what the time frame is? I am happy to test as soon as there are any alphas out!

SamRose’s picture

SamRose commented

(testing patch now...)

edwardrapley’s picture

edwardrapley commented

Testing patch.

z3cka’s picture

z3cka commented

*subscribing*

This would be awesome! please keep us posted. I will test the patch when I get a chance too.

thanks all.

SamRose’s picture

SamRose commented
Status: Needs work » Needs review

I tested this patch, and so far found no issues. Works as advertised. I will leave it to maintainer to change status, though.

paddy_mul’s picture

paddy_mul commented

subscribing

paganwinter’s picture

paganwinter commented

Subscribing...

slimabraham’s picture

slimabraham commented

Subscribing

Anonymous’s picture

Anonymous (not verified) commented

In my first pass of the patch at #9 the problems I see reside only in the .info files.

The portion of the file as indicated below needs removed from the patch.

file="importexportapi.info"

 ; Information added by drupal.org packaging script on 2007-04-20
-version = "5.x-1.1"
+version = "6.x-1.x-dev"
 project = "importexportapi"

file="importexportui.info"

-; Information added by drupal.org packaging script on 2007-04-20
-version = "5.x-1.1"
-project = "importexportapi"
+version = "6.x-1.x-dev"
+project = "importexportui"

I will update the patch based on CVS and resubmit.

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new importexportapi-ISSUE-283462.patch28.6 KB

I've corrected the above issues with this patch. I need to review more by actually using the module. The patch was built against the DRUPAL-5 branch tag. The two hunks I mentioned above failed to patch the files.

Tom Ash’s picture

Tom Ash commented

Thanks greatly for your effort, but your patch fails when it tries to add 'core=6.x' lines to the 2 .info files, and even when I add these I get a "This version is incompatible with the 6.10 version of Drupal core." message under the UI module listing at /admin/build/modules

I'll follow any progress keenly - our site has a huge (8 year, c. 5,000 article) archive we need to get from 4.7 to 6!

Anonymous’s picture

Anonymous (not verified) commented

@Thomas Ash: You will need to manually apply the difference to the info files if you're patching a distributed file. The creation process for those files mangles the file signature so that the patches to the files will not apply properly. There is one change to the importexportapi.info file and there are two changes to the importexportui.info file.

importexportapi.info: Add core = 6.x
importexportui.info: Change the dependencies variable to depedencies[] = importexportapi and add core = 6.x.

Anonymous’s picture

Anonymous (not verified) commented
Assigned: rmh3093 »
Category: feature » task
Status: Needs review » Reviewed & tested by the community

Jaza: My tests with the patch at #19 show me that the module is working as before. The patch is against the 5.x-1.x-dev cvs tag. If you give me access I'll create the tags and release for 6.x.

Tom Ash’s picture

Tom Ash commented

I'd missed the change in the 'dependencies' line - seems to work now!

summit’s picture

summit commented

Subscribing, great the D6 seems to be supported!, greetings, Martijn

rapsli’s picture

rapsli commented

cool. Let's get a first beta out there -> more people will test it.

Jaza’s picture

Jaza commented
Status: Reviewed & tested by the community » Needs work
StatusFileSize
new importexportapi-d6.patch116.71 KB

Nice work, Earnie, but your patch had a few problems. Attached patch includes these fixes (among others):

  • Various spots in importexportapi_db_put.inc where queries were getting patched to add prefixes to table names twice. For all of these spots, an $into variable with the table name is getting prefixed separately, before the query is built. I recommend using DB prefixing on Drupal test installs, in order to catch bugs like this one.
  • Removed all #db_uses_sequences properties from field definitions (the 'sequences' table was removed in D6... completely removing sequences support from importexportapi is also still pending work). These were causing numerous errors on import.
  • Removed the 'score' DB field from the 'comments' table, which no longer exists in D6.

I'm afraid that after doing a few test runs, import isn't working for me. I created a bunch of dummy data, and exported it as XML. This worked fine. However, when I then subsequently tried to import the XML, it wouldn't work. It seems that MiniXML wasn't able to parse the import file - its regular expression simply wasn't matching the structure of the file. Not sure if this is just a problem with how I'm exporting and/or saving the file, or if this is a bug with MiniXML or PHP. I also upgraded MiniXML to the latest version (that's also included in this patch), but this had no effect. Ideally, I'd like to get rid of MiniXML and just use SimpleXML from now on, but that's going to have to wait until later. Is anyone else able to get XML import working? If so, please post here about it. I also haven't tried CSV import / export as yet.

This can't be committed until both import and export has been tested to be working for a basic set of data.

Duplika’s picture

Duplika commented

Suscribing!

tobiberlin’s picture

tobiberlin
Primary language German
Location Berlin, Germany
commented

subscribing

Anonymous’s picture

Anonymous (not verified) commented
Version: master » 6.x-1.x-dev

FYI. I've had a busy April that kept me away from this issue. Most of my free time has been spent on the xmlsitemap module. I plan to get back to debugging the patch soon.

Anonymous’s picture

Anonymous (not verified) commented

I am going to submit this patch because it gives us a starting point. I will open issues to track other items such as the menu modules, the possibility to incorporate the schema API, and other things. This will not be an easy port, the data layout has changed and I need to understand the API of this module as it exists today.

Anonymous’s picture

Anonymous (not verified) commented
Title: Drupal 6.x version for this module » Drupal 6.x starting point patch
Status: Needs work » Fixed
StatusFileSize
new importexportapi-ISSUE-283462.patch28.55 KB

Here's what was committed.

summit’s picture

summit commented

Hi, Great you are going to work on this. Let importexportapi be the glue to importexport content in/out drupalsites to other drupalsites!
Greetings, Martijn

Anonymous’s picture

Anonymous (not verified) commented

Patches from others are welcome. 8D Especially for the table definitions.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.