Directory installed and enabled. Taxonomy on. Completely white page.

Is their some additional theme linkage that needs to be employed manually?

Comments

mcurry’s picture

Check your server error log. This sounds like a memory problem (not enough memory available for PHP)

http://www.google.com/search?q=site%3Adrupal.org+white+page+memory

mg2020’s picture

No errors. The mem has already been pumped up in php.ini. Everything else works fine.

beginner’s picture

What is the memory limit?

Does the page comes back blank after a long while, or straight away?

How many vocabularies do you have?
How many vocabularies have you set to display on the directory page?
How many terms do you have for each of those vocabularies?

As a test, select only the vocabulary with the fewest terms to display on the directory main page, and see what it gives.

What happens if NO vocabulary is set to be displayed on the page?

What happens if you try to access directly a page like: directory/$tid where $tid is a term's ID?

Test all of the above, and report back.

beginner’s picture

Please give the name of each vocabulary, and for each the number of terms in it.

beginner’s picture

Status: Active » Postponed (maintainer needs more info)
mdlueck’s picture

We are having the same issue. Completely blank page when we click the menu link for "directory". View / Page Source shows completely blank. Blank page loads as quickly as pages in general.

I can not find where this module sticks its configuration settings under Administer.... aaaahhh, "By Module", there it is... Selected all vocabularies, pushed the save button, now things actually show up when I click on "directory". I am guessing this is the OP's issue as well... wonder if they are even still waiting...

mcurry’s picture

Title: Blank page » Blank page (COMPLETELY WHITE PAGE)

Thanks for the feedback.

No info back from the OP, so we don't really know what's up.

THe OP complained about a "completely white page" which is the hallmark of a fatal PHP error, which requires some investigative work looking at the server error log (not the Drupal watchdog log, but the server's PHP error log - so far, we've not seen anything. Still waiting...

beginner’s picture

If anybody finds this issue and is tempted to say "I have this problem, too", I would at least request precise answers to my questions in #3 and #4.

mdlueck’s picture

THe OP complained about a "completely white page" which is the hallmark of a fatal PHP error

I believe the error is the same as we were getting. The page was completely white. Further, I commented as to the View / Page Source contents... nothing.

As for beginner's various questions, I will indulge them...

What is the memory limit?

From phpinfo()
memory_limit 40M 40M

Does the page comes back blank after a long while, or straight away?

My answer...

Blank page loads as quickly as pages in general.

How many vocabularies do you have?

8...

How many vocabularies have you set to display on the directory page?

... but none of them were selected as I could not find the Directory admin interface at: /admin/settings/directory
When I selected ALL of them (initially), THEN Directory was working properly.

As a test, select only the vocabulary with the fewest terms to display on the directory main page, and see what it gives.

I do not see point in testing this as we know what was the cause of the error.

What happens if NO vocabulary is set to be displayed on the page?

Likewise...

What happens if you try to access directly a page like: directory/$tid where $tid is a term's ID?

This was the first encounter with this mod for us. I could not even begin to guess its URL syntax given the blank page.

So I conclude, no vocabs selected, end up with a blank page. Select all/some vocabs, end up with the expected results.

Any further questioning of that conclusion?

It would be helpful to, when a no vocab's selected is encountered, display some static prepared text... "Error: No Vocabularies selected, go to the admin interface and select at least one vocabulary."

beginner’s picture

Thank you for "indulging my questions" (or me).

The reasons I asked those specific questions, is that I am the author of most of the code that may be relevant in this issue. I am only trying to prove or disprove a theory I have.

Also, we spend a lot of time developing the module and providing support, so it is always helpful when people do provide the information that is requested. But we could do without the sarcasm. Even if we were paid.

I am very glad that you "know what caused the error", because I know the code much better than you do, and I still don't know.
I cannot reproduce the behavior you reported.
1) I turned on the Garland theme, to bypass all my custom theming for the module.
2) I deselected all the vocabularies.
3) I blanked out the help text for the Directory home.
but I still don't get a completely blank page. I get a fully themed page, with a blank content area.
I added some debug code to make sure that the function returns nothing but an empty string, which it does. But I still cannot reproduce what you are reporting.

So, if you know what's causing the problem, please indulge me more: I'd like to know, too.

Or else, until someone nicely answers my questions so that I can assist them free of charge, I am done with this issue.
I just wasted yet another 30 minutes because the original reporter is expecting support but can't be bothered to provide follow up information. I wish he had indulged me, too.

beginner’s picture

All of which leads me to another theory. It is far fetched but one never knows.

Please follow my steps described above, and try to reproduce yourself the same behavior on the same installation (the one where you are now successfully using the directory.module).
Do you still get a completely white page? Or a themed page (with Garland) with a blank content area?

mdlueck’s picture

I apologize for my bad attitude.

When I installed Directory I:

Untar'ed the module on the server in the modules directory
Read the readme that was untared
Went to the modules view and ran the update.php (logged in as the admin ((first created)) account)
Went to the modules view again and enabled Directory
Then went looking for an admin page. Finding none at /admin/build/modules I went on to simply taking a look at what /directory looked by without ever seeing the admin page.
Blank page.

Thus, the steps I took.

I did some initial hacking on the module to adjust capitalization. Simply uploading the module over top, however, did not capitalize the d. Only when I disabled the module AND went through the uninstall (admin/build/modules/uninstall), then re-enabled the module did my change of "directory" to "Directory" take affect.

In so doing, at the point I disabled the module / uninstalled the module, I had several vocabs selected. They were still selected after disabling / uninstalling the module. So I suspect that some configuration settings persist even through disable / uninstall. So, likely you will not be able to recreate this issue short of either doing a clean install of Drupal, or hand checking the database for lingering traces of Directory having been there.

Did I miss any questions...???

Directory seems a most useful module for us, so I would willingly assist in making Directory even better than it is.

beginner’s picture

Priority: Normal » Minor

About the uninstall problem, I opened a new issue: http://drupal.org/node/154575 .

Menu items are cached by Drupal. Saving the module list clears the cache, that's why you changes took effect only then.

I just did test on a completely clean install, and I still cannot reproduce. So, my far fetched theory in #11 was just a bit too far off.

Enough time wasted on this issue. This week I'll try to work on some of the remaining bugs in the queue. Patches are welcome.

beginner’s picture

Directory seems a most useful module for us, so I would willingly assist in making Directory even better than it is.

thanks for the offer.
you could:
1) subscribe to all issues: http://drupal.org/project/issues/subscribe-mail/directory (if not done already)
2) See this whole issue http://drupal.org/node/144743 and especially comment #8. The future of directory might depend on the decision taken there.