Closed (cannot reproduce)
Project:
Chatblock
Version:
7.x-1.3
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
15 Feb 2013 at 08:30 UTC
Updated:
21 May 2015 at 02:02 UTC
Jump to comment: Most recent
Comments
Comment #1
doitDave commentedYes, of course. First of all you are running the letmeguess module which is unfortunately completely incompatible with chatblock. Another very likely reason is that you are using the probably browser in the notsure.if configuration, this is really hard to handle. And then it might be the whatever theme, which is also known for many odds.
;) Now seriously, these are things I really need to know in order to investigate. I always test on "fresh" Drupal installs, so it is important to be able to find out which modules interfere. Since someone else had similar problems some time ago (but unfortunately didn't post his setup either), I would really appreciate your support. You could e.g. temporarily switch your theme and see if it works then, or try to disable some of your modules just to see whether the problem disappears. With that info it would be possible to reproduce and, well, debug the problem. Thanks in advance for your help!
Comment #2
doitDave commentedEither the reporter did not get my slight sarcasm, or he got it and did not like it or he was too confused to provide more support on this issue. Whatever it is, I am not in the mood for wild guessing (who is, actually?) and so this won't be tracked any longer.
Comment #3
bauhaus commentedGot same problem.
In Apache logs
PHP Notice: Undefined variable: last_timestamp in /var/www/chatblock.php on line 194,
PHP Fatal error: Call to undefined function path_is_admin()
PHP Fatal error: Call to undefined function drupal_get_path_alias() in /var/www/includes/common.inc
And whole chatblock is not working too. It was for a moment then stopped. Perhaps when I install JS module.
I'm lost.
Comment #4
bauhaus commentedComment #5
doitDave commentedOK, then please - give me more information.
It is really important to identify everything that is not what you would call a "fresh standard D7 install, latest release, no 3rd party modules and themes enabled". Really. (Really.) Thanks.
Comment #6
FrancoNogarin commentedHi,
I will assist in debugging this.
I installed the module, and the log and the info are both a blank white page. I run a LOT of other modules including close to 100 custom ones I wrote. The wdlog shows nothing, the apache error.log shows nothing, but tomorrow I will dive into the source and see what the issue is.
Franco
Comment #7
FrancoNogarin commentedFYI im on latest drupal 7 hosted on ubuntu 12.04 LTS with PHP 5.3
Comment #8
doitDave commented@6, 7: Yes, please! I will be more than happy with any assistance. Tia!
Comment #9
FrancoNogarin commentedHi David,
ok, after browsing the source I see you are using atypical (I am unfamiliar with your approach) menu items for everything, for example, your admin menu items are stored in structure rather than in the configuration area of drupal 7, which does not cause issues but simply adds to the confusion. You are using CONSTANTS for menu paths and using MENU_SUGGESTED_ITEM (which is non commital until the menu item is enabled) then anchoring MENU_LOCAL_TASK menu items onto those noncommital items.
Now that is just me thinking about what is odd out loud. I would think that since MENU_SUGGESTED_ITEM is not really a menu item until your enable it, that those folks (like me, and perhaps the OP) that disable the default drupal menus and make thier own, might then have this trouble becuase your menu scheme might only work for a stock drupal with system menus enabled.
One test I did was to go to the url:
which returned a single blank line instead of a webpage or html - resulting in blank white page (WSOD).
oddly enough it does the same thing if you go to:
Which tells me that your menu item(s) related to chatblock are somehow not working because it SHOULD return a typical drupal Page not found - The requested page "/chatblock/infoqwerty" could not be found.
oddly enough when I enable the module on a vanilla drupal it works just fine.
I will do more tests tomorrow and feedback here.
Franco
Comment #10
FrancoNogarin commentedOne very fast fix that solved it for me was to do a search and replace in chatblock.module
search chatblock/info
replace chatblock-info
search chatblock/logs
replace chatblock-logs
drush cc menu
drush cc module-list
it fixed it right up. so I am guessing that becuase you do not define chatblock as a menu item, my complicated system cant handle it, while a vanilla drupal can (or maybe its a htaccess or php53 or custom menus issue).
will keep picking away at it tomorrow....
F
Comment #11
doitDave commentedIt would be interesting to know what menu callbacks are implemented in your complex system trying to catch the callbacks you changed. Is anything in the menu_router table giving a hint? IMO, a third party module could have overridden them with more generic paths like
Is there anything alike?
Concerning admin/config or admin/structure, there has been a lot of confusion. However, originally I planned different items for that page. At that time, structure was somewhat appropriate. As for the actual state, you are absolutely right. I will move this to config in the next release [done].
Regarding the menu constants, does changing MENU_SUGGESTED_ITEM into MENU_NORMAL_ITEM prior to installiation (i.e. after uninstalling the module completely) solve the problem without renaming the paths (which does not make sense IMO;
mymoduly/mytaskis a widespread practice in Drupal and I do not see why this should be different here). If it doesn't, it would be nice if you could narrow down the scope of what might be in conflict (ideally by turning [a clone of] your site step by step back into vanilla by falling back to a default theme and then disabling one extension after another and checking over and over again; I am not aware of a better way to find out).Thanks for your assistance, also in advance!
Comment #12
doitDave commentedComment #13
doitDave commented@bauhaus thx btw for the PHP notice. Seems like i missed that. I added an initial value to the current dev branches (both D6 and D7).
Comment #14
doitDave commentedWhat also just comes to my mind regarding the problems with other errors @bauhaus reported:
Can you please provide details on your Drupal installation, such as
Drupal not finding certain functions probably points to an issue with non-standard paths. Just a wild guess. Thx for more infos!
Comment #15
doitDave commented