I'm sure this stuff is easy once you have done it a few times...

I get this... 'A username and password are being requested by http://www.thebestplans.org. The site says: "Comt API"'

I've set up an account here https://thebestplans.co-ment.com

However even as user 1 with the same user name and passwords on Drupal and co-ment nothing is accepted.

The damn thing only has a 2 day trial I hope you can help me sort this ASAP before that ends.

CommentFileSizeAuthor
#5 co-ment1.png176.84 KBakayani
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

akayani’s picture

And shouldn't
The URL of your co-ment account (ex. https://account.coment.com/).
be...
The URL of your co-ment account (ex. https://account.co-ment.com/).

akayani’s picture

The module would also benefit from a but of JS to enable the user to change the size of the iframe.

akayani’s picture

Not sure if this from the log means anything useful...

Type php
Date Monday, November 14, 2011 - 20:18
User Yani
Location http://www.thebestplans.org/co-ment/client/?prefix=%2Fco-ment
Referrer http://www.thebestplans.org/co-ment/text/tJSMxlfwQga/comments/MeDt6tBEap...
Message Notice: Array to string conversion in drupal_http_request() (line 879 of /home/teamplans/thebestplans.org/includes/common.inc).
Severity notice
Hostname 59.100.117.211
Operations

I got the damn thing working for about 5 minutes. And in the last 4 hours I've got nowhere.

akayani’s picture

$request = $options['method'] . ' ' . $path . " HTTP/1.0\r\n";
this is line 879 foreach ($options['headers'] as $name => $value) {
$request .= $name . ': ' . trim($value) . "\r\n";
}
$request .= "\r\n" . $options['data'];
$result->request = $request;
// Calculate how much time is left of the original timeout value.
$timeout = $options['timeout'] - timer_read(__FUNCTION__) / 1000;
if ($timeout > 0) {
stream_set_timeout($fp, floor($timeout), floor(1000000 * fmod($timeout, 1)));
fwrite($fp, $request);
}

akayani’s picture

FileSize
176.84 KB

log in

This I find suss too. Why isn't there a .... in the password fields for the lower levels of permissions?

gibus’s picture

Status: Active » Fixed

Abour the message "The URL of your co-ment account", you're right, this is a typo. It is fixed in 7.X dev branch.

gibus’s picture

The iframe size can be changed using theme_co_ment_body

gibus’s picture

Status: Fixed » Postponed (maintainer needs more info)

*edit: I was looking at another site, sorry for the inconvenience*

OK, now concerning your main problem, it seems that your login/password settings are not correct. This can be caused by the way your browser remembers passwords, mixing passwords for different login (that's why you've only one password field auto-completed). Please double check all your logins/passwords.

On the Drupal side, re-enter all logins/passwords in the configuration page of the co_ment module, overwriting the browser auto-completion. You can also check they are correct in the variables Drupal sql table (select * from variable where name like '%co\_ment%';).

On the co-ment.com side, I've just extended your trial period for two more days, it will expire on 2011-11-17 13:32:41. Check that all your users (admin, admin2, admin3) can connect on the co-ment.com interface, and that their logins/passwords match the values entered in the Drupal side.

gibus’s picture

Status: Postponed (maintainer needs more info) » Fixed

Indeed the warning in #3 was showing an error in the call of drupal_http_request() Fixed in release 7.x-1.0-beta3 (which also includes reverse-backport from 6.x-1.11), also backported to release 6.x-1.12.

The error was not related to an authentication issue, as indicated in the initial message ('A username and password are being requested by http://www.thebestplans.org. The site says: "Comt API"'), but was actually popping up when adding a new comment, with an error message saying the comment cannot be saved. Apparently randomly, the addition of a new comment was nevertheless successful. It can be guessed that failure or success depends on the way the Drupal web server forwards malformed headers in HTTP POST requests to the co-ment server.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.