CommentLuv Support for Fixing the Errors Caused by Https Links

CommentLuv: How to Fix the Errors Caused by Https Links

Fixing Several CommentLuv Errors

CommentLuv is a popular WordPress plugin that unfortunately hasn’t been updated lately.

More and more bloggers switch their blogs to https. But CommentLuv doesn’t like these links. And it displays errors in some specific cases.

I can hear you saying that you didn’t switch to https yet, so CommentLuv works fine for you.

No, it doesn’t. So keep reading, this article is useful also for you.

After I moved this blog to https, I identified two CommentLuv errors:

1. An error occurred on my blog when someone tried to comment.

2. An error occurred on any other CommentLuv enabled blog when I tried to comment – irrespective of whether that third party blog was http or https.

Now let’s see the errors and how to fix ’em.

Error #1: The Plugin Doesn’t Retrieve Commenter’s Last Blog Post

So I switched this blog to https, then I logged out and I tried to comment as if I was you, one of my readers.

Instead of the latest blog post related to the blog I filled in the Website field, this error message was displayed:

“It appears that you are offline or another error occured contacting the API url, have you set it to use www or missed the www off the api url?? Check the technical settings and add or remove www from the api url.”

Very misleading. As if it’s the commenter’s fault.

I tried to fill in another blog address. Got the same error no matter what blog address I filled in the Website field. Obviously not the commenter’s fault, the problem was with this blog.

Solution No. 1: Changing CL Settings via WordPress Dashboard

So I checked CommentLuv settings and I discovered how to fix the problem. Go to Settings >> CommentLuv, and on that settings page you’ll find a link named “Click to open technical settings.”

Click that link. An extra table will open on the same page. Look for the section “API URL”:

Example of CommentLuv Settings

On your blog, instead of my domain name will be yours:

Well, add the letter “s” after http:

Then click the button “Save Settings.” That’s it. Problem solved. The commenters with http blogs will be able to comment and have their latest blog post displayed with the help of CommentLuv. What about the commenters with https blogs? See the next error!

Comodo SSL Certificates

Note #1: After I switched to https, I didn’t want to use a plugin for redirecting all http pages to the correspondent https pages. A big NO for using yet another plugin! So I did the redirection using the file .htaccess.

If you use a plugin for the redirection, maybe it will also change the setting above. Maybe – I just don’t know. But if that plugin doesn’t make the change and you still get the error shown above, now you know how to fix it.

Note #2: If you didn’t migrate your blog to https, then this error doesn’t appear on your blog. Don’t change the setting.

Solution No. 2: Changing CL Settings via cPanel

Update July 11, 2017: I’ve just discovered that under some circumstances, on some blogs the change of settings mentioned above is shown to the owner of the blog (to you) but it’s not actually made in your WordPress database. In such a case the error isn’t fixed.

You need to make the update manually in your WordPress database.

Go to phpMyAdmin from your cPanel and look for the table wp_options. Search that table for the row that has this option_name:

commentluv_options (if you have installed a free CommentLuv version) or
cl_premium_options_commentluv (if you have installed a premium CommentLuv version), as appropriate.

Then click the link Edit from that row and look for this code:


(in your case, there will be a link specific to your domain, and instead of X you’ll see a figure that corresponds to the number of characters of that link)

Add the letter s to that link (https instead of http) and replace your X by X+1 (because you added one character to the link; btw, do the math, don’t write +1 in that code). Then save the changes. That’s it.

Error #2: Commenter’s Https Link Is Assessed as Incorrect URL

Irrespective of whether your blog is http or https, the commenters who post a https link in the Website field of your comment area will get this CommentLuv error:

“Please use http:// in front of your url.”

As if https links are bad or incorrect.

That’s an inappropriate error message caused by poor coding or bad judgement from the developer’s side.

If the commenter adds http in front of the URL (in front of the https link) nothing good will happen.

If the commenter replaces https by http, then the plugin will work. But making such a replacement is a non-sense, and some people won’t do it. Because they may think that it’s something wrong with your plugin. And they are right…

The real fix is for the blog owner to update CommentLuv.

Warning: The following fix refers to the latest free version of this plugin, i.e. CommentLuv 2.94.7 and to the latest premium version, i.e. CommentLuv It may or may not work on other versions. I didn’t check their source codes.
Update June 9, 2017: While the download link from WordPress Plugin Repository still includes in the URL, someone who had access to developer’s account has changed at least one file from that version: commentluv.js. Once opened, that file reveals this first line: // commentluv 2.92.8. Therefore that file isn’t the last version. If you didn’t update your plugin at the right time, do NOT do it now. This change is very fishy!

You will have to modify the following file from the folder js of your CommentLuv plugin:

commentluv.js (if you have the free version)

commentluv-premium.js (if you have the premium version)

Find this piece of code:


and modify it as follows:


The original piece of code says something like this: “If the first seven characters of the URL aren’t http:// then display the error message.”

My modified code says: “If the first seven characters of the URL aren’t http:// and the first eight characters aren’t https:// then display the error message.”

Note #1: I split the codes on more lines only for the sake of you seeing clearly the difference between them. I also marked the difference using a yellow background. The actual code for the free version isn’t split like that on more lines. Copy the yellow code and insert it in the original code between ‘http://’ and )

Note #2: In order to be on the safe side, before making any code change do this: make a copy of the original file that you’re going to edit. Name it commentluv-original.js

After you edit the file commentluv.js (or commentluv-premium.js, as appropriate), see if the problem is fixed. If it isn’t fixed, then:

a) you made a mistake or
b) you’re using a CDN (content delivery network) or a cache plugin.

If you’re using a CDN or a cache plugin, clear your cache or turn them off and see if the problem is fixed. If it’s still not fixed, then you made a mistake.

If you cannot identify the mistake, go back to the initial plugin: delete the modified file, then revert the file commentluv-original.js to the original name commentluv.js (or commentluv-premium.js, as appropriate) and upload it to the folder js.

To Your Blogging Success!
Adrian Jock

P.S. If you’re not 100% sure that you understood any of the solutions presented here, please feel free to ask your questions using the comment area below.

P.P.S. Update July 12, 2017: Ask simple questions though. If you’re not a very tech person and you need a detailed step-by-step help, sorry, I can’t afford to do it for free anymore. You’ll need to pay for my time. FYI, the time required to fix a problem depends also on your skills and knowledge. I won’t request your passwords and do the actual job. You’ll have to do it yourself based on my written instructions.

Time & Action-Based Autoresponders. Landing Pages. Webinars
GetResponse is head and shoulders above the rest. I call it my email marketing secret weapon!” – Neil Patel, Kissmetrics
Start your GetResponse free trial now!
Adrian Jock's
Internet Marketing
Tips & News
Wanna improve your internet marketing skills in order to make more money online? Subscribe to my newsletter. Period!
Bonus: my list of free tools and resources that I use in order to run this blog and all related activities ;)

51 thoughts on “CommentLuv: How to Fix the Errors Caused by Https Links

  1. Fantabulous, Adrian!

    I’ve been having these errors on sites I try to comment on and leave my linky. It’s so annoying that I stopped trying. The blog owner also has made me feel like it was my issue, not the plugin. Sadly enough, Andy isn’t well enough to update the plugin in any longer. I wish someone would take it over because I did like using CLuv. However, with no update in the foreseeable future, I discontinued using it.

    So happy that you took the time to tweak the coding. You know I’ll be passing this along so others can tweak theirs too!

    Thanks Adrian!

    1. Thank you for your comment and social media shares, Bren!

      I doubt that someone will be able in the near future to release a formal update. Since Andy’s site is down, I guess the assumption that he didn’t sell the site and the plugin is quite correct. Therefore the plugin is still his product and only he can formally release an official updated version :(

      1. Does anyone know how to reach Andy to get his permission to have someone else update the plugin? I had hoped that he would turn it over to someone if he wasn’t up to dealing with it anymore. Now I wish I had tried to talk to him about that sooner.

        The free version says open source. Does that mean someone could fork and update it? The premium version we would need him to give us permission. Before they stop working or have security issues, maybe we should collectively do a crowdfunding effort to either update or replace them?

        I don’t know about the rest of you, but I would hate to lose CommentLuv and without the GrowMap anti-spambot (GASP) functioning the spambot comments were overwhelming my site. GASP exists because I was getting over 1000 comments PER DAY. As soon as I installed it, that dropped to ~40 which means ~960 were being left by bots. I can’t live without it.

        If anyone wants to discuss this, I’m game. I even have the domain we can use to explain the status and figure out what to do next.

        1. Hi Gail. I don’t know how to contact Andy or whether that’s still possible or not ;)

          Updating the software – for the free version – can be done technically. But after that, distribution isn’t that easy anymore.

          You need (legal) access to Andy’s WordPress Plugin Repository account. Otherwise there will be confusions.

          There might also be legal implications if someone modifies the software and distributes it without Andy’s permission by using the name of CommentLuv. I don’t know, I’m not a lawyer.

          Maybe the best solution is for someone to create a new plugin based more or less on CL.

          1. I suspect that we can update the free plugins, but would have to upload the new versions into a different plugin repository account. That would mean that only someone doing a search could find them and not someone looking at updates on the existing plugin.

            The premium plugin, though, I suspect would be more problematic to update without express permission from Andy. I used to DM him on Twitter, but he deleted that account. I’ve tried messaging him on Facebook (no response) and LinkedIn (no response). So either he doesn’t feel up to answering or just doesn’t wish to do so.

    2. Hello Adrian

      I also had this issue commenting on blogs, I figured it was “operator error” and simply cut bait and rain. It’s nice to know that there is a fix, even if I’m not well versed in this. I’m going to send this out on Twitter and hopefully we can spread the word.

  2. Thanks so much for this, worked perfectly.

    One note, when I copy pasted into my commentluv.js file I got curly apostropines. Don’t know if that would cause problems, but I changed them.

    1. You’re welcome, Paul. I don’t know whether the curly apostrophes displayed by the font I use may cause problems or not, but it’s good that you changed them. To be on the safer side, I updated the post and I used another font for the codes. Thanks for your comment!

  3. Thanks Adrian, I fixed it – I believe. I followed the instructions. When I was first told by some of my readers about the error, I turned off the Gasp and then turned it back on and it worked. But they didn’t have the https in front of their urls either. I hope you can test it out for me. Thanks for this post Adrian. It’s too bad this plugin won’t get updated :(

    1. You’re welcome, Lisa. Yes, it’s too bad that this plugin won’t get updated. I rarely comment on blogs that don’t have it enabled. When I comment I like to kill two birds with one stone, and it cannot be done without CL.

  4. Adrian,

    Thanks for the heads up on this issue! I had no idea that people with https where having issues leaving blog comments. I think I’ve updated everything correctly and appreciate the advice.

    I didn’t realize that the Comment Luv plug-in wasn’t going to be updated. Is there another program that is similar or is it okay to continue to use it?


    1. Hi Amy,

      I checked both your blogs and I noticed that you didn’t make the correct update. You addressed the error #1 that wasn’t related to your blogs while you didn’t address the error #2 that is displayed by your blogs. The result is that now CL doesn’t work anymore on your blogs.

      You weren’t supposed to address the error #1, see the last paragraph (Note #2) from that section of the article: “If you didn’t migrate your blog to https, then this error doesn’t appear on your blog. Don’t change the setting.”

      So change back that technical setting. The other error (#2) is displayed on your blogs ;)

      The answer to your questions:

      1) unfortunately there’s no similar plugin available;

      2) I still use CL on this blog, but I can’t tell you to do the same. That’s because it’s not recommended to use plugins that weren’t updated for a long period of time.

      1. Thanks yet again for the heads up! I appreciate all of the help you’ve given me over the last few years. So I fixed the first, but will have to wait until later to do the second. I remember it being a bit more complicated and need some baby free time!
        I wish there were another product on the market to use. I love the concept of CL, but am concerned about using a plugin that isn’t updated. I’m just not technically proficient enough to be able to fix issues.

        1. You’re very welcome, Amy. Fixing the second error is more complicated indeed and you need basic tech knowledge, it cannot be done by everyone. So read the instructions carefully and ask me questions if you don’t understand something.

  5. Adrian, thanks for sharing. This was a very useful article for me.

    I found several issues regarding the comments on my blog. One of my readers complained I didn’t enable Commentluv, but actually I did. I don’t know why Commentluv didn’t release an update for such a long time.

    Thanks for sharing, by the way. It seems my problem was solved with the help of this article.

    1. Hi Ashley, I have checked the blog post that you indicated and I noticed that actually you didn’t fix the error #2 mentioned in my article. I inserted my blog address in your “Website” field and I got the error rendered by the original plugin – that means that you didn’t make the change I mentioned in the article.

      What change or changes have you made? If you remember the changes you made, then revert the things back and make the changes I recommended, not something else ;)

      1. Hi Adrian,

        Thank you for your quick response! You’re right- I’m not sure what happened, but I didn’t complete #2 changes. I had definitely completed #1. Now I have made the changes you recommend for #2 error. Unfortunately the plugin is no longer pulling in the latest post for the commenter, but the ugly code is gone. It’s probably something I did! This is super frustrating!

  6. I am using the free version and I can’t find the file to change the code. Where is that js file?

    The one that you refer to when you say: You will have to modify the following file from the folder js of your CommentLuv plugin:
    commentluv.js (if you have the free version)

    1. The latest free version of CL has the following five folders: css, images, js, lang, and videos.

      The folder js includes the file you have to modify: commentluv.js

  7. Hello Adrian, Good guide for fixing the CommentLuv errors. However, I have some different question. We are thinking to migrate to HTTPS from HTTP. I read that you have redirected your pages from HTTP to HTTPS through htaccess file. So can you please explain how can we redirect all our pages from HTTP to HTTPS from htaccess file without much hassle?

    1. Hi Amit. First of all, before redirecting the pages from http to https, you need an SSL certificate. Otherwise there’s no point in making the redirection. For the moment, your blog doesn’t seem to have such a certificate. The https versions don’t exist.

      After you get that certificate, you need to find out what kind of hosting you have. Then you can search on Google for the appropriate code that you need to add to your .htaccess file.

      1. Be aware that there are 2 .htaccess files on your server, at least in my case. The one in public_html I believe was the right one. I wasted a bunch of time on that because no one in support or anywhere else told me.

  8. Hi Adrian
    Just a note. I love Comment Luv, but on some of my blogs when I comment
    and use the url to them run into that error code.
    Please get in touch with me when it is convenient.
    Can also contact me at Artagene on Facebook for a quick connect!

    cURL error 6: Couldn’t resolve host ‘’
    Hover your mouse here to see the data that CommentLuv got back from your site..

    1. Hi Cararta,

      That error appears when you misspell your URL. %20 in a web address is the correspondent of a blank space. If you spell the address correctly, without an empty space at the end of the address, then that error doesn’t appear anymore.

      Usually such a misspell cannot appear when you actually write the URL. It appears when you copy and paste it from a file or something similar, and there is an additional space after the actual URL.

      If you copy and paste that misspelled address into a browser, nothing wrong happens, the browser removes the empty space. But if you copy and paste it on systems that use cURL (that’s a software) then cURL doesn’t correct YOUR mistake and returns that error #6.

  9. Adrian

    Thanks for your good tutorial.
    But when I install & test commentluv plug-in, It’ still not working.
    When I test myself, it shows recent posting list & seems working perfectly.
    But when I click post comment button, it only post my comment itself. Last post link is gone :-(
    Do you have any idea to fix this problem?
    Thanks in advance!


    1. Hi Chad,

      It’s difficult to hep someone if that someone doesn’t provide all details about his of her problem ;)

      But here’s a hint that may help you: it looks like you downloaded CL very recently. If you downloaded it from WordPress site, then go back to my article and read “Update June 9, 2017.”

  10. Woah! Thanks for the help. I had some issues on my website that caused my users not being able to upload a comment after I installed the commentluv plugin. Now I know how to fix it. Great explanation and thanks again.

  11. Thanks for this post. I have tried your step but at the end I decided to uninstall the plugin because too much hassle and too technical.

    So, that’s one thing I have to sacrifice for the sake of SSL.

  12. Hello Adrian

    I’m trying to follow your advice, by adding the http to my blog URL in commentluv blogs. I have not been able to get it to work, would adding certificate help? I have not purchased them for my 2 blogs since I’m not engaged in ecommerce.

    1. Hi Michael,

      1) The visitor of a CL blog (that’s you) cannot modify anything from that blog (including the plugins). The owners of these CL blogs have to fix the issues. That’s why my article is not addressed to visitors (even if they are bloggers themselves) but it’s addressed to the bloggers who installed CommentLuv on their blogs.

      Conclusion: since you haven’t installed CL on your blogs, the article isn’t addressed to you, but to the owners of the CL blogs you visit.

      2) In addition, the article refers to the errors rendered by CommentLuv when the commenters have a https link. Since your links aren’t https, nothing from this article applies to you.

      3) When you posted your first comment from this page (the 6th comment starting from the top of the comment area), you inserted a correct URL and CL worked fine. See the comment you posted as a reply to Bren’s comment thread (btw, adding your reply to another commenter’s thread when your comment isn’t related to that thread… is wrong. Don’t do it again).

      When you posted your second comment from this page (right above the reply I’m writing right now), you inserted in the Website field a URL that starts with a double http:// This is a bad address that doesn’t exist and as a consequence CL didn’t work and didn’t display your latest blog post under your comment.

      A correct address includes only one single http:// (for sites without SSL certificates) or https:// (for sites with SSL certificates) and then the domain name follows. If you add one more http or https, that’s a bad address and nothing works. So… saying that you followed my advice is wrong. I didn’t recommended anywhere to use a double http://

      4) You said, ” I have not purchased them for my 2 blogs since I’m not engaged in ecommerce.”

      SSL certificates aren’t only for ecommerce sites. Visit your own sites using Chrome, the most popular desktop browser. You’ll see what the browser displays to the visitor on the address bar: NOT SECURE. It may be understood by your visitors as “Run away! You’re in danger!” If you don’t like to lose visitors for this reason, get SSL certificates for your sites, even if your sites aren’t ecommerce sites. As you can easily see, that’s what I did ;)

  13. Thanks for this Adrian. I just made the changes and I’ll try it out.

    FYI: In cPanel I had to enable “View Hidden Files” in order to find the CommentLuv plugin folder & .js file. This was within wp_content\plugins\commentluv

  14. I uninstalled Commentluv sometime ago as the spam comments that it encouraged got overwhelming. As a commenter who has gone https I often get the error notice, I also have a mass of 404 redirects pointing back to me from commentluv …. any views on how to fix these or where to redirect to? Thank you

    1. Hi Catherine,

      When you comment on a CommentLuv enabled blog, the link that is displayed on that blog is a proper link that points back to one of your blog posts.

      After such a comment is approved, if you change your blog link structure, then of course that the link displayed by CommentLuv on that blog is not working anymore.

      However, this issue is not related in any way to CommentLuv or to this article. It’s your fault. If you change the link structure without making any proper redirection to solve the issue of the backlinks posted everywhere on the Internet (including but not limited to the CommentLuv blogs you commented on), then of course that these backlinks aren’t working anymore.

      If I misunderstood your comment and it’s somehow related to this article, let me know.

  15. Hi I don’t think that I have changed my blog structure and there are masses …. will set about redirecting them … just where?!

    1. This conversation is off-topic and it will not continue here. In order to understand your problem, send me by email several examples of such links posted on CommentLuv blogs that now don’t work anymore.

  16. The code for fixing submitted urls with https should use logical OR. In the code example it uses logical AND.

    Should be:

    if(url.val().toLowerCase().substring(0,7) != 'http://' || url.val().toLowerCase().substring(0,8) != 'https://'){

    1. Why? Because you say so?

      Check the first comment under this article. Bren’s comment. She has a http site. CommentLuv worked fine, right?

      Then check Kimsea Sok’s comment under the same article. He has a https site. CommentLuv worked fine again, right?

      Anyone, including you, can see that my solution implemented on this blog works fine. So what’s your point? Just trolling?

  17. Really useful post Adrian, actually I have a problem as a commentator using commentluv. When I comment somewhere, instead of my latest post appearing via commentluv , it appears a comment section, you can probably see this in my comment here. Let me know if you have any idea why this is happening…

    Thanks in advance

    1. Hi Kostas,

      Here’s how CommentLuv works in order to display the latest blog post: CommentLuv uses a third party piece of software that calls your blog and then CommentLuv displays the pieces of information received from your blog. Exactly like a RSS reader.

      CommentLuv cannot and doesn’t alter in any way the information received from your blog. What CommentLuv displays is what CommentLuv gets from your blog.

      Here’s an experiment made several minutes ago: I wanted to add to my sidebar the feed of your blog in order to see what happens. I used the widget RSS from my WordPress dashboard. The result was this: the widget wasn’t displayed because of this error…

      RSS Error: WP HTTP Error: cURL error 28: Operation timed out after 10000 milliseconds with 0 bytes received.

      I checked your feed manually and I didn’t see anything weird. However, it’s obvious that your blog has a problem and that problem isn’t related to CommentLuv or to WordPress RSS widget. Unfortunately I don’t know what the problem of your blog is.

    1. You’re welcome, Kostas. You changed the blog from the field Website and the consequence was that CommentLuv worked fine this time. The problem is caused by that first blog not by CL – as I already emphasized in my previous comment ;)

  18. Hey Adrian

    I’m still confused about this if I’m a trying to leave a comment and the blog owner has not fixed the plugin what can I do to ensure the links work?

    1. Hi Michael,

      You can contact the blog owner and let her or him know about the issue. Only the blog owner can fix the issues.

      Alternatively, if you try to comment using your https blog (the one you used in your comment above) and you see the error #2 mentioned in my article (“Please use http:// in front of your url”), then you can follow that wrong instruction from that error message and use the http version of your site. Your blog has proper settings and will redirect the visitors from the http version to the https version of your blog.

      Please note that using the http version doesn’t mean to add http in front of your https link. It means to replace https by http.


      – http version:
      – https version:

  19. Yeah, I just sort of stumbled onto this while commenting on another blog. I entered my website with https and just happened to click on the comment luv checkbox and got the error message you’re talking about. Nice to see it working here with https. Too bad it looks like the plugin has been abandoned and probably won’t ever get updated.

  20. Thanks so much ADRIAN for posting this guide. My domain is SSL installed and it was installed when I bought the domain before I started the wp site. So it wasn’t a migration from http to https. I have been facing Error #2 with a message “Please use http:// in front of your url”
    I have done the option 2 instructions but it still doesn’t work. The funny thing is when I was commenting on your blog my latest post showed up but on other commentluv blogs no.
    Please, may you help me?

    1. Hi Josephine,

      1) I checked your blog and when I added my site to the appropriate place from the comment area of your blog… everything worked fine. The error #2 didn’t appear anymore, my latest blog post was displayed.

      2) It’s not funny the fact that you still get the error #2 when you comment on other CL blogs (except for my blogs and several other blogs that implemented my solution). It’s normal. The owners of these blogs that you tried to comment on must correct the error as per my instruction, otherwise any of their commenters (including you or me) will get that error.

      When you corrected the error on your blog, you didn’t also correct the error on all the CL blogs from the world. Obvious, right? That’s why when someone comments on your blog, now everything is fine, but when you try to comment on another blog the error appears on THAT blog you try to comment on. The owner of that blog didn’t correct the error yet, and the obvious consequence is that you see the error when you try to comment.

      To fix this problem, there’s nothing you can do but to let the owners of these blogs know about the problem and ask them to fix it according to my instructions. It’s not your fault, it’s theirs.

      1. Thanks, ADRIAN for the reply really appreciated.
        It is good to know that is not my blog. I will check with the other bloggers and see if they are willing to fix theirs too.
        Thank you.

Comments are closed.