I am unable to use this module. I am getting "you are not authorized to access this page" upon submission. I am running with Taxonomy Manager, Taxonomy VTN, and Taxonomy Node installed. I have tried running as user/1 or any authorized user.

CommentFileSizeAuthor
#9 testcsv.txt11.61 KBchrism2671
#5 Copy_glossary2.txt28.58 KBredpuma

Comments

redpuma’s picture

redpuma commented

I am experiencing this as well.

I have just done two imports with three or four a week ago on this current project, but on the last import attempt have this issue.

I've logged out and back in, cleared caches. Uninstalled this module re-enabled it. Of course I'm user 1 with all perms granted.

[mydomain]/batch?op=start&id=35

"Access denied
You are not authorized to access this page."

redpuma’s picture

redpuma commented

UPDATE:

I can import sometimes - seems to be a combination of settings or some ad-hoc thing. I haven't yet managed to identify a pattern to it. Doesn't look like I'm doing anything wrong or anything the GUI is not letting me do. However I've a feeling the "Update terms and merge existing" might be where this starts to be a problem.

pauldawg’s picture

pauldawg commented

I have tried this with all options including creating a new vocabulary, with the same results. It was able to create the new vocabulary but no terms were created.

Daniel_KM’s picture

Daniel_KM commented

Hi,

I 'm currently checking module on access rights with the last (6.12) version of Drupal. Could you send me your import file (or an anonymized extract of it)?

Sincerely,

Daniel Berthereau

redpuma’s picture

redpuma commented
StatusFileSize
new Copy_glossary2.txt28.58 KB

Hi Daniel,

I've attached my import file. I've since managed to successfully import this file (to be used with the Glossary module).

(Note: I had to rename it as .txt as .csv is not in permitted list)

regards
Steve

pauldawg’s picture

pauldawg commented

Unfortunately I didn't use a file for the import. I just copied and pasted the terms. I only listed the terms I wanted to import, with no description, so the import looked something like this:

TermA
TermB
TermC
.
.
.
TermZZZ

pauldawg’s picture

pauldawg commented
Priority: Critical » Normal

It seems this may be related to the number of items. I was importing about 450 items and it failed every time. But if I split it up into chunks it imports just fine. Downgrading priority to normal.

Daniel_KM’s picture

Daniel_KM commented

Hi,

New release 6.x-4.1 may correct this type of problem, but I can't replicate an issue with access rights problems.

Daniel Berthereau
Knowledge manager

chrism2671’s picture

chrism2671 commented
Version: 6.x-3.1 » 6.x-4.7
StatusFileSize
new testcsv.txt11.61 KB

I'm also having this problem with 4.7. Attaching CSV.

chrism2671’s picture

chrism2671 commented

I tried enabling all the big file tweaks at the bottom and this didn't help.

chrism2671’s picture

chrism2671 commented

I tried this on a fresh install of D6 and it worked just fine. My guess is that another module is interfering. Can't say what though.

Daniel_KM’s picture

Daniel_KM commented

Hi,

Thanks for your remarks. That's right, there are some taxonomies modules which interfere with Taxonomy csv.

Sorry for this late answer: I saw you find a solution. Taxonomy csv module is a one shot module: you use it and you uninstall or forget it. So, currently, in case of interferences, best solution is to import terms first, then install and use interfering modules.

4.8 release (next week) will automatically bypass identified interfering modules (as pathauto).

Sincerely,

Daniel Berthereau
Knowledge manager

Daniel_KM’s picture

Daniel_KM commented
Version: 6.x-4.7 » 6.x-4.8
Status: Active » Closed (fixed)

Hi,

4.8 release is out. I add a memory or compatibility warning when some modules are enabled (currently only pathauto, taxonomy_vtn and taxonomynode).

In fact, I can't reproduce issues, except with Pathauto, which slows down import process. For other modules, it is often a memory problem.
So, it's advised to increase server and php memory temporary (no problem reported with 256 MB) or to disable these modules manually. After import process, memory can be decreased and modules can be reactivated. Settings are not lost when a module is disabled (and not uninstalled).

Another method: as Taxonomy csv is often a one shot module (you import items then you uninstall module), items can be imported in a fresh install of Drupal, without any other module, but with a lot of memory. Then, other modules can be installed without any issue. A backup module can be used too to export items from fresh install to true site.

Sincerely,

Daniel Berthereau
Knowledge manager

ryan88’s picture

ryan88 commented

Just an update -- just ran into this problem. I just installed Drupal again and I was re-installing all of my modules at once. And after which, Drupal was telling me to rebuild the node permissions, and doing so fixed the problem.

So if you have the problem, go to /admin/content/node-settings/rebuild and rebuild the permissions.