Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
I have installed PM GROWL module and downloaded the jgrowl plugin. The popup is not showing. The process I have implemented is, I uploaded the module put the jgrowl-1 folder into the pmgrowl folder. Activated the module in the administration area and should it just work? I have sent a private message and nothing........ Should the folder inside pm module folder be named jgrowl-1, that is just what it was installed as?
Comments
Comment #1
newitt CreditAttribution: newitt commentedI have changed the name of the folder to jgrowl and makes no difference.
Comment #2
NaheemSays CreditAttribution: NaheemSays commenteddid you clear your caches?
Comment #3
newitt CreditAttribution: newitt commentedNo I have not. If I go to Admin>Config>Perfomance and click on clear cached data will this do it. People are using this site, so will anything be lost?
Comment #4
NaheemSays CreditAttribution: NaheemSays commentednothing will be lost - just the "cache" which is for faster access, so while that is rebuilt, the site may be a bit slower. Otherwise there should not be any data loss issues and this normally happens when running the update functions anyway.
Comment #5
newitt CreditAttribution: newitt commentedokay cleared cache still no popup. I sent a private message from a dummy account to my admin account and it just comes up on the normal messsage(1).
Comment #6
NaheemSays CreditAttribution: NaheemSays commentedOn that settings page, fo you have js aggregation on?
If so, for a quick check, turn it off, and then have a look at the page source. check where the page is trying to load the jgrowl files from and whether they exist in the correct location.
Comment #7
newitt CreditAttribution: newitt commentedThe only thing I can find is aggregator in modules. I activated this it did nothing. This error comes up everytime I go to send a message.
[Wed Dec 02 12:15:23 2009] [crit] [client 000000000] (13)Permission denied: /var/www/vhosts/domainname.com/httpdocs/sites/all/modules/pmgrowl/jgrowl/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.domainname.com/node/141
The referer in the error message changes every time a message is sent.
Also there is no .htaccess file in the jgrowl folder is there suppose to be?
Please help........frustrating
Comment #8
NaheemSays CreditAttribution: NaheemSays commentedno, afaik ther eis not supposed to be an .htaccess in there. I am unsure as to why you get this error message.
Comment #9
newitt CreditAttribution: newitt commentedDoes anyone else have any ideas what is going on?
Comment #10
newitt CreditAttribution: newitt commentedDoes any other module interfere with PM Growl that any one Knows?
Comment #11
newitt CreditAttribution: newitt commentedDo I install jgrowl from http://stanlemon.net/projects/jgrowl.html#options or do I install it from the drupal site. which is for drupal 5 aswell as the update? http://drupal.org/project/jgrowl
Please could someone tell me a step by step instruction on how they did it and where they got the files from?
Comment #12
NaheemSays CreditAttribution: NaheemSays commentedfrom the first site and NOT the drupal project for it.
What I did was get it from there, unzip the folder into the pmgrowl directory. then it started working.
You need to make sure that there is a file called "jquery.jgrowl_minimized.js" existing in the "sites/all/modules/pmgrowl/jgrowl" folder.
Comment #13
newitt CreditAttribution: newitt commentedThank you for your help nbz, I uninstalled the whole module and reinstalled it and it seemed to work.
Comment #14
BerdirCleaning up the issue queue. If someone still has issues, try my patch at #672534: Requirements check for jgrowl and check the status overview page.
Comment #15
jouflas CreditAttribution: jouflas commentedI have done everything mentioned above... no luck. Working fine on my development machine (mac osx).
minimized and css are there ...
flushed cache...
uninstalled... applied patch... reinstalled...
still no joy...
I did this ... here are all the sources:
src="/misc/jquery.js?Z">
src="/misc/drupal.js?Z">
src="/sites/all/modules/fivestar/js/fivestar.js?Z">
src="/sites/all/modules/img_assist/img_assist.js?Z">
src="/misc/autocomplete.js?Z">
src="/misc/textarea.js?Z">
src="/misc/collapse.js?Z">
src="/sites/all/modules/tribune/js/tribune.ajax.js?Z">
src="/misc/jquery.form.js?Z">
src="/sites/all/modules/calendar/jcalendar/jcalendar.js?Z">
src="/sites/all/themes/litejazz/js/jquery.pngFix.js?Z">
src="/sites/all/modules/pmgrowl/jgrowl/jquery.jgrowl_minimized.js?Z">
src="/sites/all/modules/pmgrowl/pmgrowl.js?Z">
both files are where they should be... I'm sure I'm not seeing something obvious.
I disabled Tribune ... no change
Please advise
Comment #16
jouflas CreditAttribution: jouflas commentedComment #17
Artman CreditAttribution: Artman commentedFor those that have pretty much 'tried everything' and still can't get the popup divs to work, maybe this will help you. I've been beating my head against a wall for three days on this thing and this morning finally (while working on something else) figured out what was keeping mine from showing. I decided that I wanted 'Clean URLs' turned on, but the test (in D6) said my system configuration didn't support it. Well, I read up on it a bit and found that turning on RewriteBase / would let me use the 'Clean URLs' option. I thought "Cool", then noticed up in the right corner were all the dang test messages sitting there looking pretty in their little jgrowl popups!
So it seems that the pmgrowl needs RewriteBase to be turned on (whether you actual 'use' the 'Clean URLs' option or not).
Maybe this can help prevent someone from pulling their hair out or giving up on PMGrowl. ;)
Comment #18
NaheemSays CreditAttribution: NaheemSays commentedok, that explains a few things - in pmgrowl.js the following string are present
which seem (from the above report and from reading the code) to not work well without clean urls.
Comment #19
BerdirOk, looks like we need a patch then to call the urls correctly. Re-titling the issue.