Since a few versions, I can no longer update the taxonomy_menu. If I try, than I can't see the home and no other side anymore. I have no indication of an error or a logfile. I guess my Taxonomy table is corrupt, but I can't find the error. What can I do?

When I try on my local Drupal installation , I get those error: Fatal error Allowed memory size of 33554432 bytes exhausted (tried allocate 256 bytes) in / opt / lampp / htdocs / modules / taxonomy / taxonomy.module on line 1110

If I give in php.ini more memory, than the home site is empty.

Thanks for any help
Christian

Comments

wwwoliondorcom’s picture

Hi,

I had this problem s I guess that you need to do as I need, change the memory_limit in settings.php, i had to set it at 200 because my taxonomy has 65000 terms.

But are you sure that your host allows to set your memory higher ? If it's a shared host you need to ask them I guess.

Hope it will work for you also.

mardersenf’s picture

Sorry, You mean settings.php? I can't find this section in my drupal settings.php. If You mean php.ini, that can I local change ( test ), but not in my realy environment.
My taxonomy has round about 200 terms. I think not that is the problem.

Thank You nevertheless.

wwwoliondorcom’s picture

Yes, settings.php

I had to add:

ini_set('memory_limit', '200M');

in this file, but now that i cleaned the taxonomy (only 20000 terms left!) if works with:

ini_set('memory_limit', '100M');

Cheers.

mardersenf’s picture

I have change the settings ini_set('memory_limit', '100M'); but I get after run the module upgrade on the new version a white page, without errors. In the moment I have activatet the version backwards, I think it is the same problem.

sdudenhofer’s picture

What if you move the limit higher? Like to 200?

indytechcook’s picture

This is fixed in the D6 version here #539046: Use Batch API to regenerate menu.

indytechcook’s picture

Status: Active » Fixed

Marking this as fixed because the new code is in the latest beta release.

Status: Fixed » Closed (fixed)

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