Hello, it seems you have JavaScript turned off or you are using and old browser. Hikari WebSite uses JavaScript to implement some of its features, but JavaScript is not required to browse it.

If you are willingly disabling JavaScript, I assure I'll do my best to not force you to enable it, building unobstutive and responsible JS code that do not block your Usability in this site.

 
   

Collapse comments 36 comments to “Hikari Titled Comments” | Comments RSS | Top

  1. 1
    flag Windows Seven Mozilla Firefox 3.6
     

    hh

    gravatar Comment by pedram3000 (http://www NULL.pedram3000 NULL.com):
    Monday, 8 Mar 2010, at 1:39:35 PM, 4 years, 4 months ago | # |

    marketingghhh

    Collapse nested comments
  2. 2
    flag Windows Seven Mozilla Firefox 3.6
     
    gravatar Comment by ikalangita:
    Friday, 19 Mar 2010, at 6:11:14 AM, 4 years, 3 months ago | # |

    I Love these comments with flags

    Collapse nested comments
    1. 3
      flag Windows XP Mozilla Firefox 3.5.8
       

      Titles & Flags

      gravatar Comment by Hikari:
      Friday, 19 Mar 2010, at 10:53:15 AM, 4 years, 3 months ago | # | replying ikalangita |

      research

      Yeah, I prefere titles, but I like these flags too ^-^

       

      To have flags and titles, together with Titled Comments you must use Hikari Enhanced Comments plugin too :).

      information

      Collapse nested comments
  3. 4
    flag Mac OS X Safari 525.28.3
     

    Having problems with integration

    gravatar Comment by Kontrive Media (http://kontrive NULL.com):
    Wednesday, 19 May 2010, at 1:25:29 AM, 4 years, 1 month ago | # |

    This looks like a great plugin, however I am experiencing issues adding the function for adding the comment title. I was able to get the code inserted for the form however. Everything gets hung up with wp-comments-post.php.

    The basic comment information is being added but it appears that the title is not being stored, nor can I access the titles. Lastly when I view my comments it is only showing a list of comment that are supposed to have titles. The originally stored comments are no longer accessible.

    I am using a basic install of 2.8.4 with very minimal ( to no) customizations. Please help, I hope its a simple fix. Thanks.homepage

    Collapse nested comments
    1. 5
      flag Windows XP Mozilla Firefox 3.5.9
       

      name attribute

      gravatar Comment by Hikari:
      Wednesday, 19 May 2010, at 12:15:24 PM, 4 years, 1 month ago | # | replying Kontrive Media |

      homepage

      Hello.

       

      I’ve visited your site and indeed you have a "Subject" field on your comment form. But it’s using a name="subject" attribute.

       

      For the title field to work, it must have name="hikari-titled-comments", if possible id="hikari-titled-comments" name="hikari-titled-comments". It’s the name attribute that the browser uses to set the parameter’s name that’s sent to the server, and it’s the parameter’s name that is used by the plugin to gather the comment title.

       

      Try changing your input’s name and id and see if it works :).

      research

      Collapse nested comments
      1. 6
        flag Mac OS X Safari 530.19
         

        Here is the testing site

        gravatar Comment by Kontrive Media (http://www NULL.kontrive NULL.com):
        Wednesday, 19 May 2010, at 12:45:40 PM, 4 years, 1 month ago | # | replying Hikari |

        Thanks for your reply, however the website where I have this installed is : http://kmbackup.com/hello-world (http://kmbackup NULL.com/hello-world)
        The comment field has already been applied but I am experiencing the same issues as I mentioned previously. I hope that clarifies everything.marketing

        Collapse nested comments
        1. 7
          flag Windows XP Mozilla Firefox 3.5.9
           

          working tests

          gravatar Comment by Hikari:
          Wednesday, 19 May 2010, at 1:26:58 PM, 4 years, 1 month ago | # | replying Kontrive Media |

          information

          Ok, in that site it’s right :D

           

          Let’s try a few tests then.

          1. Do you see the Comment Title metabox in comment editing page? That’s a plugin-core direct relation and the metabox should be there without any theme interaction, I think it’s the easiest way of know the plugin is working.
          2. When you edit this metabox’s input text and updates the comment, is the title updated in the editing page?
          3. In comments list admin page, do you see comments titles?

           

          If these don’t work, then there’s something wrong with plugin installation. I never tested it with WP 2.8.4, but I don’t see anything stopping this version to work.

           

          Try totally deleting plugin files and reinstalling it, see if you can get admin interfaces to work with comment titles, and when it works then you see if theme is properly customized.

           

           

          Your theme is very customized and it has some strange code, it doesn’t seem to have space in each comment for its title. Make sure you are using hkTC_comment_title() function on it to print titles.

          research

          Collapse nested comments
          1. 8
            flag Mac OS X Safari 525.28.3
             

            Plugin in not working

            gravatar Comment by Kontrive Media (http://kontrive NULL.com):
            Wednesday, 19 May 2010, at 3:12:18 PM, 4 years, 1 month ago | # | replying Hikari |

            homepageI just tried uninstalling the plugin. When this happens I have full functionality of my edit-comments.php. When the plugin is activated again. I lose the ability to manage the comments. In addition, there is no title that displays in the interface.

            After installing the upgrade to 2.9.2 it appears that everything is working now. Not sure why that makes a difference but everything looks perfect after the upgrade. Thanks for all of the great plugins. I hope this others find this plugin and support issue helpful.

            Collapse nested comments
            1. 9
              flag Windows XP Mozilla Firefox 3.5.9
               

              2.9 required!

              gravatar Comment by Hikari:
              Wednesday, 19 May 2010, at 5:01:00 PM, 4 years, 1 month ago | # | replying Kontrive Media |

              Ahh!!!

               

              Hikari Titled Comments requires Wordpress 2.9!! It uses comments metadata and this features isn’t available in 2.8!

              Really sorry, I should have noted when you said 2.8.4 but forgot about it! Normally my plugins require 2.8, but this one requires 2.9!

               

              If you use the plugin on 2.8, everytime it tries to access comments metadata it breaks WordPress, because the function/database doesn’t exist.

               

              I plan adding PHP and WP version checks to all my plugins, once it’s done they’ll just inform that current version isn’t supported and shutdown graciously :)

               

              Sorry again for my mistake, and tnx for testing 2.9 and fiding the problem!

              information

              Collapse nested comments
  4. 10
    flag Windows Seven Internet Explorer 8.0
     

    Automatic Subject in replies: RE:XXXX

    gravatar Comment by Eugene (http://diaped NULL.soe NULL.udel NULL.edu/):
    Sunday, 11 Jul 2010, at 2:06:25 AM, 4 years ago | # |

    Dear Hikari–

    Thanks A LOT for your very useful plugin! I have two questions for you:

    1) Is it possible to pass parent subject to the reply. For example, if the parent comment has subject "Test", the reply automatically has subject "RE: Test" (and the user can change it, if the user wants);

    2) Is it possible that when a user edits a comment, the Subject text field appears above rather than below the comment body?

    Thanks!

    Eugene

    Collapse nested comments
    1. 11
      flag Windows XP Mozilla Firefox 3.6.6
       

      Requests

      gravatar Comment by Hikari:
      Sunday, 11 Jul 2010, at 2:49:48 AM, 4 years ago | # | replying Eugene |

      Yeah I also love it :D

       

      1) That can be done… but it’d need to be a request for a new feature. And I’m damn busy, I already have pending requests and I’ll be out of home for a few weeks, and IDK what will happen later… maybe my time in PC will be 0 for some months.

       

      And also, I don’t see much real need for that feature. Comment titles would get underused if we have a lot of Re: titles. It’s better if each comment has its own, unique, title, ppl would even be discourage to set a real title if a Re: one is already there. For replying comments pointing to the comment they are replying, we already have threaded comments feature that deals with it.

       

       

      2) I’d really love if that was possible, indeed I wanted title field to go below URL field.

       

      But that’s not possible :( Only way to add new fields to pages like Edit Comment is to use metabox, and plugin metaboxes are forced to go below core ones. Since I developed Hikari Titled Comments I worked further on metaboxes and maybe that’s possible with some hacking. I’ll try to do it and enhance the title field in the future :)

       

       

      Past months I was dedicated to develop plugins I needed and last month I was publishing some of them. I have a lot of enhancements to do on all of them, I’ve been learning a lot and oldest plugins are outdated and their code isn’t top quality. I have a lot of things to do, and time is getting rarer. But I’ll do it :)

      Collapse nested comments
      1. 12
        flag Windows Seven Internet Explorer 8.0
         

        Validation of the title form

        gravatar Comment by Eugene (http://diaped NULL.soe NULL.udel NULL.edu/):
        Monday, 12 Jul 2010, at 12:32:04 AM, 4 years ago | # | replying Hikari |

        participate

        Thanks, Hikari, for your reply. I use discussions for teaching for more than a decade and automatic refiller of title is a very good idea for human interactions. I wonder if you can share your idea how to do that — major steps — and I can try to develop it myself and share if I'm successful. What do you think?

        By the way, I just want to share that I managed to add validation of the title form. First, I added the plugin "Comment Validation " from http://bassistance.de/wordpress-plugin-comment-validation/ (http://bassistance NULL.de/wordpress-plugin-comment-validation/)  and then I added

        class="required"

        to the comments.php description of the title text input:

         <input type="text" name="hikari-titled-comments" id="hikari-titled-comments" size="152" tabindex="4" value="" class="required" /> 

        It's very simple and works really well. This prevents people to leave empty title…

        participate

        Collapse nested comments
        1. 13
          flag Windows XP Mozilla Firefox 3.6.6
           

          Possibilities

          gravatar Comment by Hikari:
          Monday, 12 Jul 2010, at 3:40:11 AM, 4 years ago | # | replying Eugene |

          Nice! Tnx a lot for the required feature! :D I’m gonna take a look on it later! I don’t want it in my site (I don’t like blocking comment creation), but I wanted to implement it and didn’t know how!

           

           

          For implementing the Re: feature, you must find out the comment parent, to know its title. That can be done getting its parent using the field $comment->comment_parent then processing it as you want.

           

          The problem is how to do it, since Wordpress’ threaded comments feature allows comment form to move freely among comments… If JavaScript is disabled it’s easy, on every request to reply a comment you get the desired parent and create the default title. But when it’s done by JavaScript you must do it by JavaScript too, and comment-reply.js doesn’t support hooks.

          I’ve had the need to execute custom code when comment form is moved and I’m gonna develop hooks for that code allowing anybody to hook its events, but I didn’t have time to develop it yet and when it’s done I’ll still have to create a patch suggesting the enhancement, pray for them to accept it and still wait the patch be committed… I doubt that will be finished in 2010 :(

           

          Currently, the title input field is responsibility of the theme, Hikari Titled Comments only captures submitted form and verifies if it has the title parameter. So it would still require a new function to print possible default titles inside the input, and require themes to be updated to use that function.

          Wordpress 3.0 brought the new function comment_form(), making Core build the comment form, with options to add new fields to it, that will make it possible for any plugin to add custom fields without theme intervention, in themes that support Core’s comment form. But of course I still need to learn the new feature, implement it, and themes must be updated to use comment_form().

           

           

          Another option is, when a comment is created, set its default title when none is provided. That’s much simpler, but it may be intrusive creating titles that commentator didn’t provided. Some forum engines do that, but they allow poster to edit his post after being created… Wordpress doesn’t allow commentator to edit a comment after it’s sent. Anyway, the feature can be provided and each site admin choose to use it or not.

           

          The function postingComment() handles comment creation, if a title is provided it creates the metadata, and if none then it does nothing. It’s a matter of adding an else statement and setting a default title based on $comment->comment_parent. That’s by far the easiest solution.

           

           

          The problem is that in a few hours I’ll leave home and only be back on saturday, to stay only until sunday and leave again. And IDK what will happen after that, so I’ll be unable to update the plugin in the near future and even unavailable to approve and reply comments in middle of week.

           

          But I’ll be back, someday ^^

          Collapse nested comments
  5. 14
    flag Windows Seven Internet Explorer 8.0
     

    Old-fashioned threaded discussion forum on WordPress

    gravatar Comment by Eugene (http://diaped NULL.soe NULL.udel NULL.edu/):
    Tuesday, 13 Jul 2010, at 9:54:27 PM, 4 years ago | # |

    Dear Hiraki and everybody–

    Thanks for the encouragement and useful info. I cannot believe myself but I've managed to solve the problem and designed successfully passing subject from the parent posting. Even more, in the process I developed an Old-fashioned Threaded Discussion Forum on WordPress — my initial goal. Granted, my solution is probably VERY "dirty", local, and opportunistic. My main way of designing was to try to turn emerging problems into opportunities for my overall design of an Old-fashioned Threaded Discussion Forum on WordPress  and I've learned a lot. Before presenting my "saga" (that ran yesterday into 3am), let me provide several disclosures:

    1) My overall goal was to develop an Old-fashioned Threaded Discussion Forum on WordPress that still used by many forums including by Microsoft. I use webs for teaching and my experimentation shows that these "messy" forums fit the best human ecology of communication when people can in charge of changing themes.;

    2) I'm very new in php, WordPress, and MySQL. My very light programming background is in MS SharePoint, JavaScript, and MS SQL server.  thatandaannnnnnddddkkkkaaakk

    3) I wonder if my "quick-and-dirty" solution is based on exploitation the theme I use — "Prosumer 1.9.1 " that supports thread and nested comments. I do not how much one can generalize it to other themes. Also, I'm sure that my solution is not elegant and probably laughable for a professional. But it works.

     

    Step1. By placing the cursor on the comment Reply links, I have notice that the variable Replytocom passes the Comment ID. As little as I know PHP, I now that it is very easy to pass variable via link using $_GET['replytocom']; statement. However, the problem was that when I click in the Reply link, for some reason the link with the Replytocom variable did not appear in the URL address window and thus, the statement did not work.

    Step2. I have notice that when I deleted the <div id="respond" class="comform"> statement from comment.php, the Reply link appeared in the URL and I could pass the Replytocom variable to php variable $replyID that I created $replyID=$_GET['replytocom']; — placed it just above the script initating the Reply input area in comment.php. Deleting the statement above created the new problem: the Reply input area was always on the bottom of the page and not after the parent comment to which it would be a reply. I spent some time searching for a solution until I realized that it was blessing for my overall goal of creating Threaded Discussion Forum rather than a problem (see Step 4).

    Step 3. As soon as, I got the parent comment ID in the $replyID, I could place it in Hikari’s beautifully desinged input field for his Subject text window (that he calls "Comment Title". Here is it:

    <strong>Subject</strong> (*required field)
    <input type="text" name="hikari-titled-comments" id="hikari-titled-comments" size="130" tabindex="4"
    	value="<?php if($replyID!=""){ printf('RE: '); printf(hkTC_comment_title($replyID)); } ?>"
    	class="required" /> stttt stst. H.tI
    

    I want to apologize to Hikari and the whole community because I had to destroy some of Hikari’s script, namely:

    <?php if(function_exists('hkTC_comment_title')){
    	// ...[kept script]
    } ?>
    

    I did not know how to embed my new php script into overall php script created by Hikari (I like that he set to check if his plugin exists!). Probably it is very easy but it is above me now….  

    Please, notice that I added "RE: " to the parent subject as in Old-fashioned Threaded Discussion Forum (and emails) it is done. I also used the conditional statement if ($replyID!="") { (see the script above) to add the parent comment's subject ONLY when the Reply link is hit. 

    Step 4. I suddenly realized that the fact that the Reply input window remains always at the bottom of the page was good, not bad. I did not like how it was below all nested postings so a user may be confused and not see well the original comment that he or she was replying anyway. However, when the Reply input window is down, how can the user see the parent comment? Since I kept the parent comment ID in the $replyID variable I started learning WordPress function syntax, which is VERY user-friendly and intuitive, to create the parent comment posting. I decided to include the parent comment' Subject, Avatar, Author, Date, Time, and Text:

    <h3><a id="post"></a><?php comment_form_title( 'Leave a Reply', 'Leave a Reply to %s' ); ?></h3>
    <?php if($replyID!=""){
    	printf('<blockquote><h4>'); printf(hkTC_comment_title($replyID)); printf('</h4>');
    	echo get_avatar($comment, 52);
    	printf(comment_author($replyID)); printf('</strong> wrote on ');
    	printf(comment_date('l, F j, Y', $replyID)); printf(' @ ');
    	printf(comment_time('H:i:s', $replyID));
    	printf(': <br />'); printf(comment_text($replyID)); printf('</blockquote>');
    }
    ?>
    <div class="cancel-comment-reply">
    	<small><?php cancel_comment_reply_link('<strong>[Cancel Reply]</strong>'); ?></small>
    

    It worked great!

    Step 5. Finally (but it took me some time!), the remaining problem was that after a user clicks Reply, the focus of the page remained where the parent comment was and did not go to the Reply input windows, located on the bottom of the page. Actually, Reply link had this ending: Replytocom=XXX#respond (where XXX is the parent comment ID). The bookmark #respond did not work after I cut the <div id="respond" class="comform"> statement. Initially I wanted to use this bookmark to pointed it for the Reply input windows at the bottom of the page BUT for some reason, unknown for me, it did not work leading to problems with the script. I suspect that it is used by some hidden scripts. Anyway, I decided to create a new bookmark that I called "post" for thebeginning of the Reply input windows:

    <h3>
    	<a id="post"></a>
    	<?php comment_form_title( 'Leave a Reply', 'Leave a Reply to %s' ); ?>
    </h3>
    

    Then I decided to capture the URL of the page, updated the new bookmark #post and reload the page:

    <?php
    function selfURL(){
    	$s = empty($_SERVER["HTTPS"]) ? ""
    	: ($_SERVER["HTTPS"] == "on") ? "s"
    	: "";
    
    	$protocol = strleft(strtolower($_SERVER["SERVER_PROTOCOL"]), "/").$s;
    	$port = ($_SERVER["SERVER_PORT"] == "80") ? ""
    	: (":".$_SERVER["SERVER_PORT"]);
    
    	return $protocol."://".$_SERVER['SERVER_NAME'].$port.$_SERVER['REQUEST_URI'];
    }
    
    function strleft($s1, $s2){
    	return substr($s1, 0, strpos($s1, $s2));
    }
    
    $replyID=$_GET['replytocom']; $nurl=selfURL()."#post";
    
    if($replyID!=""){
    	echo '<META HTTP-EQUIV="refresh" CONTENT="0.5; URL='.$nurl.'"> ';
    }
    ?>
    

    Folks, do not be scared by this script that I stole from the Internet! I googled on "Getting the current full URL in PHP" and on "Reloading The Page". I placed this script just before the script above.

     

    And that is it. I also use the Collapsible Comment Plugin to make my forum.

    I hope that I did not bored you with my "saga" and solution that people who are interested in Old-Fashioned Threaded Discussion Forum on WordPress can use…

    Eugene 

    Collapse nested comments
    1. 15
      flag Windows XP Mozilla Firefox 3.6.6
       

      Wordpress as a forum

      gravatar Comment by Hikari:
      Sunday, 18 Jul 2010, at 2:39:52 PM, 3 years, 12 months ago | # | replying Eugene |

      feedback

      wow that was epic! :P

       

      I didn’t fully understand what you did, but I’ll try to help…

       

      Step1: where’s that link? probably it’s using JavaScript to move the comment form instead of sending a request to the server, and in that case of course PHP won’t receive it and page won’t reload. That’s what I said, the same thing may be done by JavaScript or PHP, so we’d need to implement it twice… or disable comment-reply.js.

       

      Step2: <div id="respond"> is a Wordpress standard and can’t be removed. It’s the div that surrounds the comment form, and id="respond" is used by comment-reply.js to find the comment form and move it.

       

      Instead of removing the div, you should just not enqueue comment-reply.js and it would work ;)

       

       

      Step3: As I said, title input field is currently the theme’s responsibility. The code I provided is just a suggestion on how to do it and can be changed as needed. Testing if plugin functions and classes are available before using them is a "design pattern" that we should always follow ;)

      You could do the following to implement your code:

      <?php if(function_exists('hkTC_comment_title')){ ?>
        <h3>Comment Title</h3>
        <input type="text" name="hikari-titled-comments" id="hikari-titled-comments" tabindex="4" value="<?php
          	if(!empty($replyID)){ hkTC_comment_title($replyID, 'RE: ');
          ?>" />
      <?php } ?>
      

       

      Note that hkTC_comment_title() already echoes the title and returns nothing, so you don’t need to and shouldn’t echo/print that function. It also has more parameters that you can use to make its use more confortable.

       

       

      Step4: that’s really a problem, I think Kubrick is the father of moving comment form to the end of a comment, below all its nested comments, and not immediately below the comment that’s being replied.

       

      When Threaded Comments was added to Wordpress Core and the feature was implemented in Kubrick, it seems their idea was to put comment form in the place the created comment would go. That highlights and valorizes the Threaded Comments feature, but it confuses commentators that are more interesting in just commenting, and not see how geek is the feature.

      They get confused when comment form is moved, and it’s much more useful to have the replying comment on sight then seeing where their new comment will go when created. When using a reply feature, we wanna see the comment we’re replying, we’re not worried with the site layout and where our comment will live its life.

       

      The reply link is generated by the function comment_reply_link(). It receives an array as parameter (seeing on the code now I remember that Kubrick doesn’t implement comments markup, it just uses Wordpress Core’s, so it’s Core’s fault), and one of possible parameters is 'add_below', that has the HTML id that will be used to put comment form.

      I won’t explain it in details, but you can just create an area in the bottom of your comment layout and give it an id, add this id to comment_reply_link()‘s parameters and comment fom will start being moved below the comment it’s replying to, above all nested comments, and not at the very bottom of the comment and below all nested ones. You can test clicking reply links in my site and you’ll see the effect, I implemented it properly on my theme ;)

       

      Step5: like I said, #respond is Wordpress standard and must be present in all comments areas. You broke the standard, had problems because of it and had to hack stuff to fix it. Never do that, you’ll end up with more problems in the future :P

       

       

       

      Having a forum in Wordpress is very desired. phpbb has a feature that we can create blogs and each post automatically creates a topic in the forum area where visitors can comment and talk, but post and topic are in separated areas and just link each other. There’s also another forum engine that treats first topic post (the op) as the main text and all subsequent posts as comments to it, and even leaves the op in top of all pages of the topic.

      ppl that have a lot of comments wanna merge them all together, having commentators talking as if they were in a forum, with the post and all its features being the op and comments as remaining topic posts. I’ve even seen commentators calling Wordpress sites as forum because of the amount of comments.

       

      I’ve never admin a forum, but maybe bbPress or buddyPress has features that can enhance "comments as forum posts", replacing comments to forum posts and effectively turning Wordpress posts into forum topics. If they don’t have, that feature should be implemented, with real threaded posts as we have threaded comments and so on.

      I’ve been working on enhancing comments features to make them more post-like while keeping comments’ strictier security. Titled Comments is one of these features, Hikari Enhanced Comments has a package with a few more, and I have some more features to implement and publish. Recently I updated my theme to show commentators info (country, OS, browser and handheld).

       

      With all these features together it would just be a matter of designing a proper theme with a layout that would ressemble a forum to have a real "Wordpress as a forum" look & feel, or having a forum managed by Wordpress! :D

      Collapse nested comments
      1. 16
        Windows Vista Mozilla Firefox 3.6.10
         

        Check Out the SEO Super Comments Plugin

        gravatar Comment by David Law (http://www NULL.google-adsense-templates NULL.co NULL.uk/wordpress-theme-talian-with-adsense-and-seo-optimisation NULL.html):
        Tuesday, 11 Jan 2011, at 10:31:36 PM, 3 years, 6 months ago | # | replying Hikari |

        Interesting thread. Just started playing around with your plugin to incorporate it into my premium theme (Talian 5, though I'm rebranding the name in the next update).

        I've got your plugin working in my next version (just on my development server) and have been using a customised version of another plugin called SEO super Comments (by Vladamir Provolic: he makes some really good plugins) and been trying to pull the comments titles into the output of the SEO Super Comments output. No joy so far, can't seem to pull anything directly from the commentmetadata table!

        My customised version (heavily hacked and only works with Talian) use the first X number of words from the comment as the title element of the comment post. What I want to do is take the comment title from your plugin as the title element for the comment posts created by the other plugin and after reading this thread it kind of fits in with what you were discussing.

        I linked to the Talian support page which includes over 400 comments. If you look at the bottom of reasonable size comment you'll find a link to the comment posts. I'm going to try to pull together your comment title on those pages along with the RE: concept above.

        Will drop a comment if I get it working. When I release the next version will be using it on the site I linked to and will have thousands of Talian theme users potentially using it (will have it as an on/off option rather than on by default).

        Your comment editor wouldn't let me paste some text I copied from a PHPMyadmin window. Got a security warning so typed it. Same issue with select all the text of this comment and copy, in FireFox used Edit >> Copy to copy the text (like to keep a copy of my comments on others sites: really sucks when you type something and a browser crashes or a spam filter deletes your comment :-)).

        David

        Collapse nested comments
        1. 17
          flag Windows Server 2003 Mozilla Firefox 3.6.13
           
          gravatar Comment by Hikari:
          Tuesday, 11 Jan 2011, at 11:40:45 PM, 3 years, 6 months ago | # | replying David Law |

          Interesting dude, I’m happy my pluing is being useful.

           

          Keep us updated about your progress. Unfortunately I've been low on time and can't help you in your project, but I hope you are succeeded.

           

          You can use the function hkTC_get_comment_title($comment) to retrieve a comment's title, then process the string as you like.

           

          gl :)

          marketing

          Collapse nested comments
          1. 18
            Windows Vista Mozilla Firefox 3.6.10
             
            gravatar Comment by David Law (http://www NULL.google-adsense-templates NULL.co NULL.uk/wordpress-theme-talian-with-adsense-and-seo-optimisation NULL.html):
            Wednesday, 12 Jan 2011, at 11:05:48 PM, 3 years, 6 months ago | # | replying Hikari |

            participate

            I got it working as I wanted, see it in action at http://www.stallion-theme.com/stallion-seo-theme-comment-title-feature (http://www NULL.stallion-theme NULL.com/stallion-seo-theme-comment-title-feature)

            There's a test comment (quick review of your plugin) uses the comment title as the title element etc.. for the output of the SEO Super Comment plugin.

            Haven't tried to code in the re: concept yet, might not in hindsight as will add RE: to the title element of those comment pages which has no SEO value.

            Sent you a backlink from the above page and left your copyright info intact with the plugin file.

            BTW speaking of links, you should look into removing nofollow from your site and any plugins you develop, nofollow deletes link benefit. I noticed a fair number of nofollow links on your site (have a FireFox extension that puts a line through nofollow links, an SEO consultant thing:-))

            David

            feedback

            Collapse nested comments
            1. 19
              flag Windows Server 2003 Mozilla Firefox 3.6.13
               
              gravatar Comment by Hikari:
              Friday, 14 Jan 2011, at 9:12:02 PM, 3 years, 6 months ago | # | replying David Law |

              feedback

               

              Very nice, I loved your theme. I suggest, instead of using paragraph with strong, use a header element, it's more Semantic.

              It would be interesting to add Re: title for new comments. I personally wouldn't use it but it seems some sites would benefit from it.

               

              I also verify nofollow links, indeed I have a yet-to-be-published plugin that highlights it, but it doesn't matter because my plugin obfuscates all links. My idea is in the future, when I have the time, develop a JavaScript plugin that would make all links marked as nofollow to open in another tab. If you notice, my posts are XHTML 1.1 valid (ols posts aren't, and a couple plugins make all pages not valid, but my theme is and my posts are, I'm making new content be so that when I have the time to fix the issues I won't have to bother with new posts…), so I can't use target=blank on them, that's why I wanna replace this feature by a JavaScript implementation.

               

              It's sad I need to have a cheap full-time job to live, I wanted to dedicate 100% to Wordpress and software development in general, I'd earn much more money if this activity could be a stable job.

               

              But gl in your project, tell me if you finished it and if you want I can add the future to my plugin :)

              Really sorry for not being of much help.

              marketing

              Collapse nested comments
              1. 20
                Windows Vista Mozilla Firefox 3.6.10
                 
                gravatar Comment by David Law (http://www NULL.google-adsense-templates NULL.co NULL.uk/wordpress-theme-talian-with-adsense-and-seo-optimisation NULL.html):
                Friday, 14 Jan 2011, at 11:00:24 PM, 3 years, 6 months ago | # | replying Hikari |

                 

                I went with strong on the markup so very little SEO benefit was used on the comment titles. Ideally headers (H*) which have SEO value would be left entirely down to the site owner, whether to add content to them. Although some think strong has SEO value, I'm not convinced and it it does will be minor relative to headers. Suppose I could use a style to give them no SEO value at all (probably will now).

                Nofollow is a major problem for WordPress users, each nofollow link no matter how it's generated wastes link benefit.

                I noticed the nofollow links in your links widget, each one wastes link benefit, then there's all the nofollow attributes added to comment links!

                I've solved the problem in my theme, I use form button styled like text links. also use various WordPress filters to remove nofollow links from comments etc… The only nofollow links my theme hasn't removed are those added by the site owner (I assume you added the rel attribute via the links menu) and fully formed HTML links in comments. I use a filter that blocks WordPress converting a link with no HTML into an HTML link, so that solves some of them, but not the fully forme dones. On my sites I remove them manually because they waste so much link benefit.

                Few weeks back managed to persuade one of the WordPress developers to remove the nofollow attribute from the Reply to comment links, so in WordPress 3.1 that will be millions of nofollow links removed from WordPress sites. One week later found a theme level solution as well :-)

                I have a lot of theme customers using autoblog plugins (automated blogs from Amazon content etc…) and they generate a lot of affiliate links which are nofollow. Javascript is the way to go for hiding them (what I do with next release of my theme).

                It's more than possible to make a living from WordPress, I have a business online (SEO consulting), but also make money from using WordPress which would be enough money to give up a day job and the WordPress money is more a hobby than something I do to survive from.

                David

                Collapse nested comments
                1. 21
                  flag Windows Server 2003 Mozilla Firefox 3.6.13
                   
                  gravatar Comment by Hikari:
                  Sunday, 16 Jan 2011, at 1:30:35 PM, 3 years, 5 months ago | # | replying David Law |

                  Header has no SEO value. It's about Semantic.

                   

                  And look closer, all these links are obfuscated. They exist only when JavaScript creates them, so whether or not nofollow is in them, search engines can't see them :) My intention is really to not allow search engines to see those links, only humans on browsers should be able to indentify their URL.

                  Just read how I do it: Hikari Email & URL Obfuscator

                   

                  I was making some good money from Wordpress consulting, but it's not reliable, anytime I can stay long time without any client and no money. A stable job here pays me very low but the money is always coming, and in some time I'll try to get a bigger salary.

                  research

                  Collapse nested comments
                  1. 22
                    Windows Vista Mozilla Firefox 3.6.10
                     
                    gravatar Comment by David Law (http://www NULL.google-adsense-templates NULL.co NULL.uk/wordpress-theme-talian-with-adsense-and-seo-optimisation NULL.html):
                    Sunday, 16 Jan 2011, at 7:39:57 PM, 3 years, 5 months ago | # | replying Hikari |

                    information

                    Headers almost certainly have SEO value, I've ran hundreds of SEO tests over the past decade and though headers are a difficult one to test, the tests suggest they have value.

                    I had a look at the obsfucator plugin page and if it works sounds interesting, I use a bit of advanced javascript and CSS to hide affiliate links etc… from search engines, but it does mean a percentage of non search engine visitors don't see the links (they just see the anchor text). I don't know of a 'good' way to show javascript hidden links to real visitors without using cloaking. I just incorporated the javascript into my theme as have alot of people using it who autoblog.

                    Are you using the obsfucator plugin on this site? I used Chrome with Javascript turned off (saw your message about javascript being used on the site etc…) and when viewing source there are standard html links with nofollow attributes which if Google sees them the way I see them they delete link benefit.

                    Unless you are using some form of search engine specific cloaking (which is generally a bad idea to serve Google someting your other visitors don't see) it looks to me like javascript isn't acting on the links.

                    Links to look at:

                    Twitter, Posts feed, comments feed, comment reply links and links related to comments (author link etc…).

                    These all have nofollow links (there's a lot of them) that are deleting your link benefit!

                    I'll takea look at your plugin, see what it does as if it works would be something to work alongside autoblogs potentially.

                    Take a look at any page under http://www.google-adsense-templates.co.uk/ (http://www NULL.google-adsense-templates NULL.co NULL.uk/) with comments and check out author links, they are form buttons, Login links are form buttons as well. I have URLs like the the one I just pasted above not being converted to links (stays as text) and have turned nofollow off links of full html links within comments off and then delete any added by visitors. This way I can still add full clickable links from comments that aren't nofollow and if a visitor adds a link I'm happy with I won't replace it with the text version of a link. It's all dealt with at theme level.

                    There are no nofollow links on my sites and I create quite a lot of sites with affiliate links off them and wouldn't send a link to an affiliate.

                    BTW you are having the same issue I had with my theme on sites with deep threaded comments, the width of the comment becomes quite narrow. I had to reduce the padding/margin of each comment to fit more in. You have quite wide margins between the threaded comments.

                    David

                    Collapse nested comments
                    1. 23
                      flag Windows Server 2003 Mozilla Firefox 3.6.13
                       
                      gravatar Comment by Hikari:
                      Thursday, 20 Jan 2011, at 10:00:04 PM, 3 years, 5 months ago | # | replying David Law |

                      homepage

                      Well my plugin obfuscates links pretty well. They are built by JavaScript when available and by CSS when not, and I don't see spammers and search engines doing the mess to build them in the near future. For visitors with JavaScript enabled, unobfuscated links have all features of normal links…

                      I just forgot to say (or you didn't read it plugin info fully :P ), internal links don't need to be obfuscated so they aren't by default. Just try searching for links pointing out of my site (and a few that I whitelisted) and you'll see them working. It's easier to just try the plugin with your own tests. Of course I'm using it on this site, I developed it just to be used on my sites! :D

                       

                      My point is that links I don't want search engines to see doesn't matter having nofollow, because they aren't seen at all. And links I don't obfuscate are as I want them to be.

                      Are you saying that adding nofollow to internal links isn't good? I don't remember adding nofollow to them, but as I've read it's irrelevant. I use a lot of internal links in my texts, because I make posts about a subject and then everytime I talk about that subject I just link back to that post, and use relevant keyworks on the link text. These links I'm sure aren't with nofollow because I use my Hikari Internal Links to build those links.

                       

                      I just suggest you to not add those features to a theme, making them "theme level". Themes are meant to be visual only, oriented to build HTML. Any feature not visual related should be implemented in a plugin. Wordpress offers enought filters to allow plugins access relevant content and change them.

                       

                      And yeah, I allow 10 nested levels in this site, and threads like this one get very deep. But I also had already the need to go up some levels to keep replying, so I can't reduce the nesting level. And I also like the current padding/margin because nestings must be evident in threads with many mixed comments.

                      The problem is that I designed my theme on a 1680×1050 monitor, and now most of the time I use it in a 1600×2560 monitor so my theme is optmized for large monitors. And I want it like that, because I hate themes that don't take benefit from high resolutions. It's just not so confortable for narrower monitors, but for them the plugin still lets sidebars to be hidden ;)

                      homepage

                      Collapse nested comments
  6. 24
    flag Mac OS X Mozilla Firefox 3.6.8
     

    bug?

    gravatar Comment by iamkalabaw:
    Sunday, 25 Jul 2010, at 4:14:43 AM, 3 years, 11 months ago | # |

    research

    i noticed that after activating this plugin, comments do not appear instantly on the page. a refresh is needed before comments appear. is this a bug?

     marketing

    Collapse nested comments
    1. 25
      flag Windows XP Mozilla Firefox 3.6.6
       
      gravatar Comment by Hikari:
      Sunday, 25 Jul 2010, at 6:12:08 PM, 3 years, 11 months ago | # | replying iamkalabaw |

      information

      I doubt it, I see no reason for comments not appearing.

       

      Most often the plugin works only in its metadata, it does no modification over original comment’s content. Only place where it modifies some core comment data is in edit-comments.php, where titles are appended in the begining of their comment_text.

       

      I see no reason why a comment would stop appearing. But if you have any guess of what may be happening give me some clues and I’ll try to fix :)

      research

      Collapse nested comments
  7. 26
    flag Windows XP Mozilla Firefox 3.6.10
     

    date

    gravatar Comment by ahmet:
    Thursday, 14 Oct 2010, at 1:05:52 PM, 3 years, 9 months ago | # |

    homepage

    Dear We celebrate your job, thanks but

    we want add auto closed  comment date not a

    Comment Title / Subject

    commenters wll be choose their own comment close or delete times.

    how we can entegration with your plugin

    thanks for your reply

    Regards

    Collapse nested comments
    1. 27
      flag Windows XP Mozilla Firefox 3.6.10
       
      gravatar Comment by Hikari:
      Thursday, 14 Oct 2010, at 8:57:20 PM, 3 years, 9 months ago | # | replying ahmet |

      Tnx :)

      I suppose you are talking about my Titled Comments plugin, so I moved it here.

       

      Your request is out of the scope of this plugin. You’d need a way to pick a date (JavaScript can handle that), find out how comments are closed then create a cronjob to do that when the time comes.

       

      But hey, comments aren’t closed separately, it’s posts that are closed for new comments. Wouldn’t you me thinking about allowing commentators to edit their comments for some time then block the feature?

      Collapse nested comments
      1. 28
        flag Windows XP Mozilla Firefox 3.6.10
         

        thanks quick reply

        gravatar Comment by ahmet:
        Friday, 15 Oct 2010, at 5:49:46 AM, 3 years, 9 months ago | # | replying Hikari |

        information

        Dear Hilkari,

         

        very simple

        How

        commenters wll be choose when close their own comments.

        Regards

        Collapse nested comments
        1. 29
          flag Windows XP Mozilla Firefox 3.6.10
           
          gravatar Comment by Hikari:
          Friday, 15 Oct 2010, at 3:39:16 PM, 3 years, 9 months ago | # | replying ahmet |

          participate

          ok, but what do you mean with a closed comment?

          By default commentators can't edit their comments after submit, so what exactally changes when a comment is closed?

           

          Anyway, I've said how to implement the date and how to submit and store it, and how to execute some action when that date arrives. Now it's a matter of implement the "comment closing" feature :)

          participate

          Collapse nested comments
          1. 30
            flag Windows XP Mozilla Firefox 3.6.10
             

            one day / there day / one week / one mounth ...

            gravatar Comment by ahmet:
            Monday, 18 Oct 2010, at 11:17:28 AM, 3 years, 8 months ago | # | replying Hikari |

            can be choose comment owner.?

            Collapse nested comments
            1. 31
              flag Windows XP Mozilla Firefox 3.6.10
               
              gravatar Comment by Hikari:
              Monday, 18 Oct 2010, at 9:37:53 PM, 3 years, 8 months ago | # | replying ahmet |

              Well, yes. You can use a JavaScript datepicker or some combos to let user set a date, then pass it in comment form and capture it with a plugin :)

              Collapse nested comments
              1. 32
                flag Windows XP Mozilla Firefox 3.6.10
                 

                how

                gravatar Comment by ahmet:
                Tuesday, 19 Oct 2010, at 3:23:25 AM, 3 years, 8 months ago | # | replying Hikari |

                CAN U PREPARE * FOR US ?

                Collapse nested comments
                1. 33
                  flag Windows XP Mozilla Firefox 3.6.10
                   
                  gravatar Comment by Hikari:
                  Tuesday, 19 Oct 2010, at 5:59:25 PM, 3 years, 8 months ago | # | replying ahmet |

                  I still didn't understand what exactally you wanna do to each comment for closing it… and I never worked with JavaScript datetime.

                   

                  If you wanna hire me we can talk in ICQ or MSN or another IM software to explain me in details what you want to accomplish, and I search for a JavaScript solution. Otherwise I apologize but I won't develop your request in the near future :(

                  feedback

                  Collapse nested comments
                2. 34
                  flag Windows XP Mozilla Firefox 3.6.10
                   
                  gravatar Comment by Hikari:
                  Wednesday, 20 Oct 2010, at 11:50:56 PM, 3 years, 8 months ago | # | replying ahmet |

                  I added you in my msn but didn't see you online, I also mailed you in the email you use in comments and also no answer

                  Collapse nested comments
  8. 35
    flag Windows XP Mozilla Firefox 3.6.12
     

    thank you

    gravatar Comment by duncan (http://www NULL.ubunifucapital NULL.com):
    Thursday, 2 Dec 2010, at 6:05:30 AM, 3 years, 7 months ago | # |

     hi there,
    thanks for all the great info on your site.i was using joomla for my site http://www.ubunifucapital.com (http://www NULL.ubunifucapital NULL.com)
    but i am thinking of switching to wordpress.i am looking for any information i can find on wordpress
    thanks for all the helpful infomarketing

    Collapse nested comments
    1. 36
      flag Windows XP Mozilla Firefox 3.6.12
       

      tnx!

      gravatar Comment by Hikari:
      Thursday, 2 Dec 2010, at 5:28:42 PM, 3 years, 7 months ago | # | replying duncan |

      participate

      hehe tnx :)

       

      But I barely have time to maintain my plugins. I wanted to add tutorials teaching stuff that I learn while developing. I hope when I have my theme and my plugins finished I’ll have some more time to spend building content!

      feedback

      Collapse nested comments
Leave a Comment

Comment Title / Subject


Experimental:

I've started testing a new comment editor to make commenting easier. It requires JavaScript enabled to work. If you have any problem with it, just click the Source button and it will be shut off.

Comecei a testar um editor novo nos comments. Ele precisa de JavaScript pra funcionar. Se vc tiver algum problema ao usar ele, é só clickar no Source e ele vai ser desativado.

 

XHTML: You can use the following tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <strong> <em> <blockquote cite=""> <q cite=""> <cite> <code lang=""> <pre lang="" class=""> <tt> <del datetime=""> <strike> <ol> <ul> <li> <p style="" class=""> <span style="" class=""> <h1> <h2> <h3> <h4> <h5> <h6> <sub> <sup> <i> <u>

 
 
 
homepage
research