error - Karma Error: Communication (0)
guppydrupal - November 14, 2007 - 22:11
| Project: | Simple Karma |
| Version: | 5.x-1.6 |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | guppydrupal |
| Status: | closed |
Jump to:
Description
quick question:
where do I insert the
<?php
if(module_exists('simple_karma')){ print simple_karma_template_forms();}
?>in the page.tpl.php of my theme?
thanks!
#1
Quick answer: wherever you like, really :-D
The important thing is that it's towards the top, because there are important JS variables there. I'd put it right avter actually.
I updated the user documentation as well.
Merc.
#2
#3
This may be related to where I'm putting the
<?phpif(module_exists('simple_karma')){ print simple_karma_template_forms();}
?>
in the page.tpl.php,
I put it after at the end of the head section like this:
head
<?phpif(module_exists('simple_karma')){ print simple_karma_template_forms();}
?>
/head
Sorry if I'm an idiot on this, I tried to put it in the section that didn't fix the error message.
I am getting this error message when I try to rate the comments:
Karma Error: Communication (0)
what's goin' on here?
this module is incredible by the way, thanks for all of the work.
#4
Hi,
No problem at all. I am here to help.
The module obviously needs some ironing out - that's what I here for!
It's best to put the forms right after the body tag. I am looking for a way so that I don't have to ask you guys to put that ugly line in the templates, but am finding it a little hard.
However, the communication error might be something else. Question: is your Drupal in the domain's root directory? If the answer is "no", please install the next version of the module, 1.7, and report back (1.7 fixes a bug that prevented the module to work unless Drupal is running in the domain's root).
ALSO, you _need_ to have clean URLs enabled.
If you send me your URL, I will have a look for you :-D
Bye!
Merc.
#5
Hi,
I will close this bug unless you tell me otherwise...!
Merc.
#6
CLosed! Pirandelo confirmed that the new version, 1.7, fixes it...