Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Drupal 6.x is available several months. It would be nice to have an updated version.
Comment | File | Size | Author |
---|---|---|---|
#31 | importexportapi-ISSUE-283462.patch | 28.55 KB | Anonymous (not verified) |
#26 | importexportapi-d6.patch | 116.71 KB | Jaza |
#19 | importexportapi-ISSUE-283462.patch | 28.6 KB | Anonymous (not verified) |
#9 | importexportapi-drupal6.2.patch | 28.09 KB | tauno |
#5 | importexportapi-drupal6.patch | 25.15 KB | rmh3093 |
Comments
Comment #1
bneel CreditAttribution: bneel commentedI'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
Comment #2
appel CreditAttribution: appel commentedSubscribing!
Comment #3
rmh3093 CreditAttribution: rmh3093 commentedim am working on porting it to 6
Comment #4
rmh3093 CreditAttribution: rmh3093 commentedComment #5
rmh3093 CreditAttribution: rmh3093 commentedHere 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.
Comment #6
ñull CreditAttribution: ñull commentedsubscribing
Comment #7
joncup CreditAttribution: joncup commentedsubscribing *bump*
Comment #8
nathanjo CreditAttribution: nathanjo commentedsubscribing
Comment #9
tauno CreditAttribution: tauno commentedHere'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).
Comment #10
mohamed_e CreditAttribution: 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!
Comment #11
SamRose CreditAttribution: SamRose commented(testing patch now...)
Comment #12
edwardrapley CreditAttribution: edwardrapley commentedTesting patch.
Comment #13
z3cka CreditAttribution: z3cka commented*subscribing*
This would be awesome! please keep us posted. I will test the patch when I get a chance too.
thanks all.
Comment #14
SamRose CreditAttribution: SamRose commentedI tested this patch, and so far found no issues. Works as advertised. I will leave it to maintainer to change status, though.
Comment #15
paddy_mul CreditAttribution: paddy_mul commentedsubscribing
Comment #16
paganwinter CreditAttribution: paganwinter commentedSubscribing...
Comment #17
slimabraham CreditAttribution: slimabraham commentedSubscribing
Comment #18
Anonymous (not verified) CreditAttribution: Anonymous commentedIn 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"
file="importexportui.info"
I will update the patch based on CVS and resubmit.
Comment #19
Anonymous (not verified) CreditAttribution: Anonymous commentedI'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.
Comment #20
Tom Ash CreditAttribution: Tom Ash commentedThanks 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!
Comment #21
Anonymous (not verified) CreditAttribution: Anonymous 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.
Comment #22
Anonymous (not verified) CreditAttribution: Anonymous commentedJaza: 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.
Comment #23
Tom Ash CreditAttribution: Tom Ash commentedI'd missed the change in the 'dependencies' line - seems to work now!
Comment #24
Summit CreditAttribution: Summit commentedSubscribing, great the D6 seems to be supported!, greetings, Martijn
Comment #25
rapsli CreditAttribution: rapsli commentedcool. Let's get a first beta out there -> more people will test it.
Comment #26
Jaza CreditAttribution: Jaza commentedNice work, Earnie, but your patch had a few problems. Attached patch includes these fixes (among others):
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.#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.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.
Comment #27
Duplika CreditAttribution: Duplika commentedSuscribing!
Comment #28
tobiberlinsubscribing
Comment #29
Anonymous (not verified) CreditAttribution: Anonymous commentedFYI. 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.
Comment #30
Anonymous (not verified) CreditAttribution: Anonymous commentedI 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.
Comment #31
Anonymous (not verified) CreditAttribution: Anonymous commentedHere's what was committed.
Comment #32
Summit CreditAttribution: Summit commentedHi, Great you are going to work on this. Let importexportapi be the glue to importexport content in/out drupalsites to other drupalsites!
Greetings, Martijn
Comment #33
Anonymous (not verified) CreditAttribution: Anonymous commentedPatches from others are welcome. 8D Especially for the table definitions.