RapidWeaver Forums

I have installed a blog on RW and ticked the comment tick. It suggests that I suscribe to a free JS Kit. I went there to realize that it costs now $24/year (due to high number of subscribers they stopped the free version). Is everybody experiencing the same or am I reading this wrong?

Also it seems that the Echo system has been recently deployed. RW manual does not mention Echo. How does this work with RW blog?

Thanks a lot for your ideas.

morissej - 15 August 2009 03:36 PM

I have installed a blog on RW and ticked the comment tick. It suggests that I suscribe to a free JS Kit. I went there to realize that it costs now $24/year (due to high number of subscribers they stopped the free version). Is everybody experiencing the same or am I reading this wrong?

Also it seems that the Echo system has been recently deployed. RW manual does not mention Echo. How does this work with RW blog?

Thanks a lot for your ideas.

This is a recent occurrence. Like you said, JS-Kit was free until recently. I am very curious to hear Realmac’s response to this one.

Best,
Josh

I have to say I’m having problems with Echo and RW blog. I simply CANNOT get the comment box to sit neatly under the blog post and have tried tweaking the code in various ways without success. Echo has only been around since 6 August so teething troubles are inevitable. We just haven’t got a group knowledge-base yet but I’m sure we will. One feature I don’t very much like is the way in which registration is the default requirement. It puts people off. (If anyone wants to suggest a solution to my coding problem, please take a look at Colophon Blog. I’d be v. grateful).

Hi Guys

We were not aware that JS-KIT would remove the free option (for the time being), and so this has totally caught us off-guard. I’ll drop the JS-KIT CEO an email (I’ve dealt with him before) and I’ll be sure to let you know as soon as I hear anything more.

I’m really sorry for this inconvenience, however it’s not something we were previously aware of.

Kind Regards,

Nik

Nik: JS-Comments worked just fine until “Echo” in early August. The non-free issue is a big one so thanks for looking into it.

In addition their service is quite spotty. I realize this may improve, but they’ve definitely gone backwards compared to the service before. At random times I’ll have a blog page showing 0 comments for an entry that, in fact, has many comments. Since I use my website for a course I’m teaching this is very confusing to students (and to me). This doesn’t happen all the time, but it does happen occasionally. Perhaps more than once a day. I’ve now check that this also seems to happen across browsers. That last time this happened (this evening) I checked with OmniWeb, Safari 4, Firefox 3. All gave the same result of ALL entries showing 0 comments even though a few had several.

I know you can’t solve all these problems, but my guess is there’s going to be a lot of problems and complaints about Echo service—and unfortunately this may end up making RapidWeaver look bad. Somehow those JS-Kit dudes have taken on a lot more than they can handle and it’s showing in many different ways. If desperate enough I may just have to switch to Blogger via RapidBlog.

I just found this thread, which must have started up after I started this thread.

I’ve been thoroughly confused by JS-Kit’s web site and I wonder if they haven’t been able to keep their site current with their practice. I, too, came across the $24.00 price, but yesterday I ended up seeing a window that said it was $12.00.

Further, one window I came across listed their products as Echo Core (free), Echo Light ($98.00 a year), Echo Pro (contact them for price), and the attachment I’ve included lists Echo Live ($12.00) and Echo Pro (contact them for price). As a neophyte blogger it’s a little much for me parse through what I perceive to be not only a confusing product, but also a confusing web site.

Christopher

Image Attachments

Click thumbnail to see full-size image

 

It’s me again,

First, on the support.js-kit page someone has written:

Echo is still available 4 Free, LogIn @ http://js-kit.com & u’ll automatically redirected 2 http://js-kit.com/moderate/ where u can make ur settings & get the code

So, a free version is still available. Good! Not that I begrudge the $12.00, but I wanted to try it out before I paid any money.

Next, Philippe Cailloux, an employee of js-kit has posted a guide with instructions for RapidWeaver users.

In this he’s got two lines of code to be pasted at the bottom of each post:

Do we really paste both of these lines at the bottom of each post? They seem identical except the second is a more concrete example.

And is the “uniq” (a new term to me) simply a name I give my post in RapidWeaver under Permalink? For example, if I write a post titled “Painting my house” and give it the permalink of “house,” my pasted code would look like this:

And that would be it, at least for that post? If the answer to this is “yes” then I think I understand. If it’s “no,” I’m totally befuddled.

And of course we’re to check “Enable Comments” under the General tab of the Page Inspector.

Sorry for these basic questions… all this html stuff is new to me as of a couple of weeks ago!

Christopher

Hi Christopher,

Thanks for your message. You shouldn’t need to manually enter any code. So long as you’ve got the JS-KIT comments mentioned in the Page Inspector you should be able to start commenting right away once the site is live.

Thanks!

Nik

Thanks, Nik!

I’m going to try to get this working this evening when I have some time. I wonder why all the rigamarole, then? I’ll post back about my success or lack of it!

Christopher

I tried to get comments set up on my blog, but I can’t be sure it’s working. I sent myself a test message, but it never appeared on the site, nor did I get an email or see anything about moderating it.

The site is here: http://www.pristinemadness.com/, and it loads a lot more slowly than it did prior to my attempt to implement comments. Plus, there’s often a comment window at the bottom of the page with a gear icon that turns constantly.

I did not paste any code at the bottom of each blog post, as Philippe Cailloux, an employee of js-kit, has posted here, but I did copy the code from the JS-Kit Admin Dashboard (found in the “install” section) and paste it in the Footer” section under the “General” tab of the “Page Inspector.” Then thinking that perhaps that wasn’t needed (Nic did say I shouldn’t have to paste any code), I deleted the code and returned the “Footer” to my default setting.

The page still loads pretty slowly, but without the (apparently) non-functional comment window at the bottom of the page. And it’s possible that it’s loading slowly because I added two other pages to the site at the same time. It’s been confusing because I’ve been encountering two different sets of instructions.

I’d be interested to hear of the experiences of others.

Thanks!

Christopher

I m still lost setting up Echo and rapidweaver. seem like going to switch to Echo competitors if i dont get this comments thingie fix. really disappointing and discouraging + time wasting.

Anunymouse - 16 August 2009 09:22 AM

I have to say I’m having problems with Echo and RW blog. I simply CANNOT get the comment box to sit neatly under the blog post and have tried tweaking the code in various ways without success........

Hi, I noticed this to but only on some posts others it was fine, so I am wondering if somewhere JS-Kit has inserted a minimum blog post length that it anticipates and places the white box at least that far down regardless of the actual length of the blog post.

Sorry not a proper solution, more speculation, but maybe add a picture to the top or bottom of you post to go past this minimum length, whatever it is.

Dave

themadman - 24 August 2009 08:02 AM

Anunymouse - 16 August 2009 09:22 AM

I have to say I’m having problems with Echo and RW blog. I simply CANNOT get the comment box to sit neatly under the blog post and have tried tweaking the code in various ways without success........

Hi, I noticed this to but only on some posts others it was fine, so I am wondering if somewhere JS-Kit has inserted a minimum blog post length that it anticipates and places the white box at least that far down regardless of the actual length of the blog post.

Sorry not a proper solution, more speculation, but maybe add a picture to the top or bottom of you post to go past this minimum length, whatever it is.

Dave

Thank you. In fact, what has been happening is, no matter how long the post (and some have been LONG), the first comment box for the latest blog post is always way down the page although the boxes for older entries sit quite neatly. Unortunately, after trying some workarounds suggested elsewhere in the Forums, I seem to have scrambled everything and although I’ve reverted to previous code, I’ve lost comments entirely on recent pages. You could be right about “invisible code” from JS-Kit. Probably I’m just thick!

i think it’s no good the js kit new wave.

i think is better than to transport my blog on blogger…

no troubles...no pay per comment’s...no paste code in each post....

i want only to write my post and read the comments.....no more

...and spend time for a good layout with all the RW templates, plugs and options

cheers.....

only a doubt...Rapidblog or WP+RW?

Nik - 19 August 2009 02:08 PM

Hi Christopher,

Thanks for your message. You shouldn’t need to manually enter any code. So long as you’ve got the JS-KIT comments mentioned in the Page Inspector you should be able to start commenting right away once the site is live.

Thanks!

Nik

My only problem now is even with “test comments” on my test page I still “0 Comments”.  So I am staying with what you are saying and not add any code and ignore the advice from the ks-kit crew.

My test site is here...test site.

I hope RealMac starts to take all of this more seriously. (I know there are taking it seriously, but this really is in need of “disaster relief” kind of handling).

Echo, put succinctly, sucks big time. And that’s being generous. I can get it to work, but it’s very slow delivering content, very awkward in implementation, very “rich” in unnecessary advertising of its own goods, and more.

About 5 days ago I went back (once again) to RapidBlog. RapidBlog currently works with Disqus. And Disqus, I’ve found, is an absolute delight to work with. They are fantastic! If RealMac want to continue to “support” JS-Comments then okay. But really RealMac should be considering additional options. And Disqus appears to be first rate. My guess is their people would be quite happy to work with the RealMac people.

I love Rapidweaver, and I really understand that RealMac is not responsible for the mess over at JS-Comments. But this complete screw up continues to reflect poorly on RealMac as well. I think if Real Mac was able to provide some commenting-system options then the problems would likely go away. There are likely other services as good, even better, than Disqus. But for years and years now Real Mac has been wedded to HaloScan-JS-Comments. Surely it’s time to think outside of that very old and dis-functional box.