I just upgraded my Javascript Tools to 5.x-0.2 and was testing my test site in both firefox and IE. It works fine in firefox, but on reload of IE I get this error
Fatal error: Call to undefined function: jstools_modules_includes() in .... (my site address).../sites/all/modules/jstools/activemenu/activemenu.module on line 50
It only begins after I try to visit my site the second time and then onwards with IE.
If it helps, my testsite www.pemberworth.com/drupal
| Comment | File | Size | Author |
|---|---|---|---|
| #2 | error message.png | 4.84 KB | drupalluver |
Comments
Comment #1
nedjoHmm, this is a new function in this relase but I'v confirmed it's there in the jstools.module code. Maybe this error has to do somehow with page caching?
Comment #2
drupalluver commentedI am not very knowledgeable about some of this. I have included a snapshot as I'm going to try to change my version of jstools to remove the error.
By the way, I have now had a friend visit the test site in both IE and FF and she gets the error message with both.
Comment #3
nedjoI'd incorrectly put the
jstools_modules_includes()in ahook_init()function. I've moved it tohook_menu(), where it should be safe from caching errors.Applied to trunk. I'll need to merge with the 5.0 branch. Then, I guess, post a new release.
Comment #4
drupalluver commentedThanks!
Comment #5
nedjoI've posted a new release with the fix.
Comment #6
robertgarrigos commentedsorry, but your 5.x branched files are older than your 5.x.0-3 release, and those are the ones you download when using "cvs -r DRUPAL-5". could you update the 5.x branched code with this bug fixing? thanks
Comment #7
nedjoThanks for the note, indeed I'd forgotten to merge some files into the 5.0 branch, but had merged others, producing this bug.
I've now merged them but need to do more testing, tomorrow.
Comment #8
nedjoThe fix appears to have worked. Applied to the 5.x branch. Book support should work in the next 'official release' of jstools. Meantime you can use the 5.x dev download, http://drupal.org/node/113162.
And, yes, please reopen this issue if that dev version is still generating the error.
Comment #9
(not verified) commented