vocab index install blank pages

karlis - April 16, 2009 - 10:00
Project:Vocabulary Index
Version:5.x-2.0
Component:Code
Category:bug report
Priority:critical
Assigned:Unassigned
Status:active
Description

I used to have vocabindex 1.2. I completely uninstalled this module and installed vocabindex 2.0. Any vocabulary index I create, when I follow the path I've entered, I get the title of the vocabulary and the description of the vocabulary, but no list of terms, just a blank page. Having a look at the vocabindex table in the db, each vid has two identical entries, except only one of the two (for each vocabulary index I've enabled) has a path. The dual entry thing seems odd. Anyone else have this behaviour? What's wrong here? Drupal 5.16.

#1

Xano - April 16, 2009 - 17:13
Status:active» postponed (maintainer needs more info)

The two entries are by design and they are not identical. Are you sure the vocabulary you created an index for contains any terms at all? Also clear Vocabulary Index' cache and check the index page again.

If this doesn't help, please write step-by-step instructions on how to reproduce the problem using a clean Drupal 5.16 installation and the latest vocabindex-5.x-2.x-dev.

#2

karlis - April 18, 2009 - 00:55
Status:postponed (maintainer needs more info)» fixed

Just a quick update, I haven't had time to set up a clean 5.16 install with the vocabindex dev version yet.

The vocabulary I've (tried to) create an index for has about 600 terms. The old vocab index displayed those terms well. I've also tried clearing the vocab index cache. I tried adding a new term after installing vocab index. I tried enabling a block as well as the page for the vocabulary. In all cases, I get nothing, there is no content in the block, no content on the page.

I think I found the problem. Tracing back from theme_vocabindex_page, in function vocabindex_vi_view in file
vocabindex.view.inc: (around line 290)

// There is no cached data, so render the output from scratch.
if ($cached_data === 0) {

I changed this to
if (!$cached_data) {

and then the whole thing seems to work ok.

#3

Xano - April 18, 2009 - 05:35
Status:fixed» active

This is not fixed yet. Thanks for the info :)

#4

viktor.denischik - November 29, 2009 - 14:23

hello. I had the same problem that many other users did with path is already in use error. So, since i have the ability of using q or clean urls i have set the path to ? q node .. When i went to that node it was blank - ofcourse. So, while trying to figure out what the issue was i have right clicked on "currently located at" and copied the link location which was %3Fq%3Dnode/412 AND surprisingly this path does work! but it's ugly - the path ofcourse. I hope there's a better solution outhere

#5

viktor.denischik - November 29, 2009 - 14:27

thinking about it it does not make much sense, to me. If %3F is ? then why the actual path ?q= is blank while the escaping path works... i dun get it

#6

Xano - November 29, 2009 - 14:46

A blank screen indicates something went wrong internally so I suggest you check the error logs first.

Also, using paths that are already in use by other modules is highly discouraged. Chances are that a node with NID 412 will be created in the future.

 
 

Drupal is a registered trademark of Dries Buytaert.