Hi,

I get an error 500 each time I try to edit a taxonomy term.

Not sure but it seems I have this behavior since I update Drupal to 7.2 to allow an ajax behavior to be compatilble with ie8 (http://drupal.org/node/1018714). The ajax answer is not wrapped into a textaera tag.

Have someone an idea about how to correct this ?

CommentFileSizeAuthor
#10 code.png17.12 KBdinhthinh
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

asb’s picture

I'm getting this error in Drupal 6 (Pressflow actually) when editing terms at URLs like ./admin/content/taxonomy_manager/voc/8/2865. The error message given:

An HTTP error 500 occurred. /admin/content/taxonomy_manager/termdata/edit

I am not using IE (but browsers like Opera or Chromium) on Ubuntu.

A workaround is to open the term's link in another browser tab and edit it there. That gives the error as well, but the term's changes are saved properly. However, the display is not refreshed.

Thanks for this great module which actually makes Drupal's taxonomy usable!

jtsnow’s picture

This may be related to #1120178: Error 500 on term edit

asb’s picture

Status: Active » Reviewed & tested by the community

@jtsnow: Yes, the patch from #1120178: Error 500 on term edit actually seems to help.

Thanks for this!

ChoY’s picture

I have tghe same proplem, but there is no error message - the ajax waiting circle just hang up in a loop and turn and turn ...

mh86’s picture

Status: Reviewed & tested by the community » Needs work

Patch from #1120178: Error 500 on term edit doesn't apply any more (function doesn't exist any more). I can't reproduce it and at the moment I have no idea why this happens. Do you see any errors in your log?

asb’s picture

For me the patch applied cleanly, and solved the issue on a dozend of sites running taxonomy_manager 6.x-2.2 from 2010-Feb-05. Thusly, after applying the patch from #1120178, I don't get any errors in watchdog log anymore.

I don't have any D7 site in production, so I don't know about issues in the 7.x branch; however, the issue exists in 6.x-2.2 and is fixed by the patch, thusly I'd suggest to committ it to the 6.x branch and publish a 6.x-2.3 release with it.

ShaneOnABike’s picture

For what it's worth I was having editing and viewing issues until I applied the patch on #1120178: Error 500 on term edit

fordprefect76’s picture

I am having the same issue. Here is the error showing up in my logs when i try to reorder:

PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '' for key 'uri': INSERT INTO {file_managed} (filesize, status, timestamp, type) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( [:db_insert_placeholder_0] => 0 [:db_insert_placeholder_1] => 1 [:db_insert_placeholder_2] => 1332641551 [:db_insert_placeholder_3] => default ) in drupal_write_record() (line 6975 of E:\inetpub\wwwroot\DonsCommerce\includes\common.inc).

fordprefect76’s picture

Further investigation found that there was an issue with the image attached to the taxonomy term. It did not exist. Once I removed the image relation the ordering started working again. I hope this helps someone.

dinhthinh’s picture

Version: 7.x-1.x-dev » 7.x-1.0-beta2
FileSize
17.12 KB

I have problem with update term and refresh the tree.
I do a simple comment in the code and it works for me.
I open the file taxonomy_manager.admin.inc in module folder.
Go to line 855, and comment the two line as follow
'#ajax' => array(
'callback' => 'taxonomy_manager_term_data_form_ajax_callback',
'method' => 'replaceWith',
/*'event' => 'click',
'wrapper' => 'taxonomy-term-data-replace',*/

'progress' => array('type' => ''),
),

and another problem is the load term to edit. The module could load the term form to edit, but the cycle keep running around cannot stop. I think there some loop in callback function.

mh86’s picture

Status: Needs work » Postponed (maintainer needs more info)

This should be fixed with the last beta3 (image fields are not directly embedded any more)

mh86’s picture

Status: Postponed (maintainer needs more info) » Closed (cannot reproduce)

Closing this issue, as there was no response.