I have this module listing out a taxonomy tree and once in while when i refresh my page i get the following error.

Fatal error: Call to undefined function drupal_get_path() in ............................/vocabindex/vocabindex.module on line 13

Also, its strange cause with different people accessing the same instance some get this error and some dont.

drupal_get_path is obviously not an undefined function and hence please look into what might be causing this problem.

Comments

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented
Status: Active » Closed (duplicate)

Please use the search to find out if the bug you're encountering hasn't already been reported. Also, are you using the latest development version?

Duplicate of #324218: Call to undefined function - vocabindex module.

lejon’s picture

lejon commented

I have the same problem - it's urgent to fix because it's on a live site!

It was working before. The only new thing I've installed since is Google analytics module. I get this error message:

Fatal error: Call to undefined function drupal_get_path() in /home/timber/public_html/sites/all/modules/vocabindex/vocabindex.module on line 13

You can see it on www.humanitariantimber.org

lejon’s picture

lejon commented

I uploaded the latest dev version (16 November) and it fixed the problem. Phew!

I'll leave this open in case it doesn't solve the problem for the original poster...

xano’s picture

xano
he/they
Primary language English
Location Southampton
commented

Have you even read my previous reply? I asked if gauravkumar87 was using the latest development version, which means you should too, and that this issue is a duplicate, which means that you're not supposed to reply here, but in the other thread.
Also, the 5.x-2.x release notes clearly state this:

You are discouraged to use development versions for live sites, unless you're willing to take the risk.

If you are still having this problem after updating to the latest development version, please post step by step instructions on how to reproduce the problem using a clean Drupal installation and (again) the latest development version in the other issue.

lejon’s picture

lejon commented

sorry, i thought the line through the duplicate reference meant it wasn't a duplicate.

I was using rc1 (5 november) and am now using the functioning 5.x-2.x dev. I am willing to take the risk using the dev version as the rc1 version crashed my site!

Complements on the module - it's very useful.