Port taxonomy_xml to Drupal 5

Here is the info file to also add.

The info file is not there, can you please provide it again. Thanks for writing the patch, it will be committed.

Oops, I should not have left the .info extension, it's prohibited.

The drupal 5 port works great except that it does not import terms in the order of depth from the XML file. Terms that have a parent that have not yet been previously imported get orphaned. I've created another patch with changes that have the terms imported in order of depth.

Tom thank you I will look it over for the 5.0 release when I get a bit of time.

hello,
i am quite a newbie and i would like how to apply this patch.
Thanks in advance for your help

@yobenny, see this page. That should help. :-)

subscribing

I tried to apply the patch, but it was rejected (the .rej file : http://dev2.comminit.com/taxonomy_xml.module.rej ). Has anyone else had this?

Thanks in advance,

Mike

I applied the taxonomy_xml_drupal5--2.patch directly to the module-file of version 4.7.

Is this the right way? I also tried to apply patch2 after applying patch1, but then patch2 was rejected. And I think that patch2 contains also the changes of patch1.

The export of a taxonomy worked fine.

But when I tried to reimport the exported taxonomy (I used the exported file and only changed the vid and the name of the vocabulary) I detected 2 problems:

1. The list of the node types is not correctly imported. Instead of "doctypA, doctypB" I got "0, 1".

2. The structure of the taxonomy was lost.

Instead of

HTerm1
--ATerm2
--NTerm3
----ETerm4
------ETerm5
--NTerm6
ITerm7
MTerm8
--ETerm9

I got

ATerm2
ETerm4
ETerm5
HTerm1
ITerm7
MTerm8
--ETerm9
NTerm3
NTerm6

Any ideas?

Does somebody has a working 4.7 version with this patch please?
Can you email or post this patch/version please.

Thanks in advance,
Martijn

I saw, I changed the titel excidentaly to a wrong sentence, sorry about that.
Please file a working taxnomy_xml 4.7.6. version with depth working!!

greetings,
Martijn

This issue is about porting the module to Drupal 5. The depth issue would be a separate one. Thanks.

I found out, that the hierarchical structure of the taxonomy is correctly imported, if you remove all carriage returns in the file.

In my first trials I had entered carriage returns after each tag, to get a human readable view of the syntax. And because according to the XML specification whitespaces should not mind, I did not remove them prior to the re-import.

Because I remembered some other applications to have problems with whitespaces I removed them in later tests: and it works.

So I think the problem should be solved.

subscribing

Hi,

I tried leaving out the carriage returns in my 4.7 taxonomy xml solution, but the depth still is not working.
Greetings,
Martijn

Hello - has anyone got anything that works [at all]. The patch did not work on my system and my 'hand change' does not appear in the menu system

So - can anyone post a working Taxonomy_XML for Drupal 5 [or know why this will not work with PHP 5 etc]

This is stopping my migration to drupal 5

Thanks

Roger

Do you have it working on 4.7 then, with the depth correct?

greetings,
Martijn

Hi Roger!

Please find attached the the taxonomy_xml.module, which I got by patching the 4.7.x-1.x-Version (2006-Nov-13). For me it worked fine after removing all carriage returns in the xml-file.

This project is open for a takeover, I don't have time or need for this project anymore.

subscribing: this would be super useful to me, and I'm happy to help if someone picks it up...

We would like to take it over. Please let me know what we have to do.

NicolasH: contact the author. If he doesn't reply within 2 weeks, ask in the devel mailing list. I believe that's the pseudo-official procedure.

NicolasH: You may takeover this project. Please approve NicolasH for a CVS account and I will be happy to give him commit rights over the project or you can do it. Thanks.

I have updated the HEAD version to be compatible with 5.x. I also added support for synonyms and to optionally keep duplicate terms.

Before I create a branch, it would be good if people can test it from CVS. If there is a better way of handling this, pls let me know. I'm still finding my way around this CVS thing...

HEAD version is here

It would appear that this has been done.

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