Declare PHP dependency for reference variables

A blank page is also called a "white screen of death" and in most cases it indicates PHP encountered an error that hasn't been printed to your screen. Please check your PHP error log for such an error and paste it here.

I don't think that after three months this is a problem anymore.

Hi Xano,

I got his same problem after switching on vocabindex-6.x-2.0-rc2 vs. drupal-6.6.
Also, whenever I viewed a Block for the Vocab Index I got a white page.
I am really interested in this module, however it simply does not work for me.
I am reactivating it as critical.

Please check if the solution in #1 works for you. If it does, the behaviour you are experiencing is not a bug.

Hi Xano,

I am reporting here on results when switching on vocabindex-6.x-2.0-rc2 vs. drupal-6.6.

1. I edited php.ini to switch on error logging to file, and specified an error log file.
2. I restarted my Apache (on Mac OS X) with inbuilt PHP, and checked with a test.php whether error logging and file enabled ok.
3. (vocabindex-6.x-2.0-rc2 was already unpacked into '/modules')
4. admin/build/modules: switched on Vocabulary Index ok: "Vocabulary Index has been enabled. Please proceed to the settings page and set up the permissions to get started."
5. build/vocabindex/settings: I set 'Terms per page:' to 0.
6. admin/build/vocabindex: (Pages): my vocabs appear ok with options: I do not know what "index page" to set for each vocabulary.
7. admin/build/vocabindex/blocks: I enable one Vocabulary 'Technology' with View "Tree" and no node counts.
8. admin/build/block/list/mytheme: I assign the 'Technology (Vocabulary Index)' block to the Left Sidebar of my Zen-based sub theme
9. admin/build/block/list/wca: WHITE SCREEN OF DEATH
10. There is no /tmp/php.log file created ! (This is the first time I have ever used the error logging file option, however all settings seem to be ok according to my test.php.)
11. I reload admin/build/vocabindex/blocks and get a WHITE SCREEN OF DEATH again.
12. I load my home page and get a WHITE SCREEN OF DEATH again.
13. Still no /tmp/php.log error file created, so no diagnostics.
14. can't get to 'modules' admin by reloading to disable, so have to try using direct URL or menu on another tab.
15. I notice that the dropdown menu tree on the admin bar on Firefox3.0.3 is now not working also (maybe the problem is JavaScript)
16. I delete the 'vocabindex' package to rescue my site.
17. admin/build/modules/list: reload via direct URL, 'modules' list appears again.
18. Admin menu bar still not working, I restart Firefox.

Xano,

I might be that the user simply gave up, because not everybody wants to have to switch on and check logs. Often if a module does not simply work a user goes elsewhere.

Thank you very much for your detailed report, but please try to set your PHP limit higher than it is now (I recommend 32MB or higher, simply to be sure). In most cases this is the cause. If this does not solve the problem, try the latest dev version and see if the problem still exists there (since the latest RC is over one and a half month old). If it does, please report back.

Am changing version of this report from 6.x-2.0-rc1 (as reported by brakkar) to 6.x-2.0-rc2 to correspond with my experience and so lists properly.

fwiw, this module white screens my in-dev drupal 5 site:

drupal 5.14
untar http://ftp.drupal.org/files/projects/vocabindex-5.x-2.0-rc2.tar.gz
refresh browser
"Parse error: parse error, unexpected '=', expecting ')' in [...myhost...]/sites/all/modules/vocabindex/vocabindex.view.inc on line 426"

just a quick follow-up to say on reflection the error i saw while i was trawling through taxonomy block modules looks similar to a php5 requiring module running on php4 server. and fwiw i realised i didn't need the extra functionality and just went with a php snippet in a block.

I'll check it out. Thanks you very much for this tip, I hope it's a nudge in the right direction :)

This is line 426, which looks good to me:

function _vocabindex_list_render_tree($tree, $children, $vi, $pid = 0, &$zebra_i = 0) {

I'll check out if this it incompatible with PHP4.

Looking at the line of code above I came to think the reference variable was responsible for the error. I found this php.net manual page stating the minimum requirements for using references is PHP 4.0.4. Could you please tell me which PHP version you are using?

PHP Version 5.2.6

@Tobyspark: which PHP version are you using?
@Webel: Are you experiencing the same error as mentioned in #9? If not, could you please create a new issue about it?

No activity > closed.

"Are you experiencing the same error as mentioned in #9? If not, could you please create a new issue about it?"

Sorry, I don't have time to look into this at the moment, however the problem stands.

That may very well be, but I can't do anything about it without some more information.

same problem where with white screen of death while attempting 'update.php', and this error on admin's modules:

Parse error: syntax error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/misgnome/public_html/09/sites/all/modules/taxonomy_menu/taxonomy_menu.module on line 76

.

removing module i guess -- especially with the status of 'won't fix'

Taxonomy Menu is no Vocabulary Index.

Just ONE LAST TIME: I can't do anything about this problem if nobody helps. If you want this fixed, follow the instructions when creating an issue which state that you write down all steps necessary to reproduce your problem, write down what versions (Drupal, PHP, vocabindex) you are using and what kind of errors are logging/printed to your screen.

It's up to you.

Xano,

I appreciate your point, however I have another solution to this task using another module that is adequate, and I can't spend any time debugging now. I merely want to let you know that this problem still exists. In this case, I am not able to help any further. Therefore, please do not close this due to lack of attention from me or others. And I certainly won't complain that it is not getting fixed by you, I appreciate your efforts. But closing it also does not solve it.

The problem is that I get reports from multiple people that seem to have completely different causes. If somebody can tell me more, I'd really much like to start fresh with a new issue dedicated to that particular problem, because this one is getting quite cluttered.