Comments on: Wordpress wp_list_comments()

By: Jennifer

Jennifer — Thu, 11 Mar 2010 04:44:17 +0000

So I was testing this out to see if maybe something changed in the latest version – I had a test wordpress setup – and just dumped the mycomment function in the functions.php file and got the same error you did. But what I realized is that I had actually placed it BELOW the close php tag just above it… ie. the function looked like this before I put the new code in:
…last function in functions.php actually is printing something to screen…

And right here is where I dumped my function…

do you see the problem? (the php file is close just above where I put my function… so in that last line, I had to remove the close php:
NEW FUNCTION GOES HERE..

That may not have been the same problem you're having – but you never know. It's just funny that it gave the same response you describe. Otherwise, once i fixed that, everything worked fine…

By: KDesign

KDesign — Thu, 11 Mar 2010 04:05:10 +0000

Hi, thanks for the tutorial. I'm having problems though that I can't seem to find an answer to on the web.

When I follow the example in the Codex http://codex.wordpress.org/Template_Tags/wp_list_comments#Comments_Only_With_A_Custom_Comment_Display, as you've done in your article, I keep getting an error message after updating functions.php.

It says: Parse error: syntax error, unexpected '}' in /home4/popsicl2/public_html/wp-content/themes/magadine12/functions.php on line 26

Have you ever had this problem? I'm not sure where the problem would be seeing as I copied and pasted everything exactly, and I don't know if there are other files I should be looking at besides comments.php and functions.php. My functions.php file doesn't even have any other code in there besides this custom callback one.

Any help would be much appreciated! And if it helps, I'm using version 2.9.2. Thanks.

By: Cenay : Wordpress Blogging Coach

Cenay : Wordpress Blogging Coach — Tue, 26 Jan 2010 02:32:15 +0000

Interesting. I am working with a new theme that I believe BREAKS the silly comments. I am hoping this information will help me find the dang thing.

Implemented the new updates to the functions.php file first, along with the new call in my themes comments.php file. The interesting part is that bypasses the HTML to standard HTML didn't fix it.

Guess I am going to have to break down and buy the PHP debugger I have been eyeballing and trace where it goes wrong.

Thanks for your insights and help.

By: Scott H

Scott H — Mon, 04 Jan 2010 22:45:04 +0000

The code block you provided for functions.php is missing the php start tag at the beginning and a php end tag at the end of the code.

I'm guessing WP ate them up

By: Scott H

Scott H — Mon, 04 Jan 2010 22:17:41 +0000

Thanks for saving the day again.

I'm working on a new WP install after not having done one in a while and I'm finding WP's hide the html code from the kids attitude pretty annoying.

By: Gerrit Fries

Gerrit Fries — Sun, 29 Nov 2009 00:55:55 +0000

Thanks a lot! I am building my own blog right now – so this was nice tip to use my own gravatar function (which stores image on my server) on comments.

By: Jeff

Jeff — Wed, 06 May 2009 04:51:13 +0000

The new comment features in 2.7 make a lot of things easier but you're so right in that it's now a freakin' pain to get rid of the "says"…

By: Mark Jaquith

Mark Jaquith — Fri, 01 May 2009 08:05:05 +0000

The reason for no ending is for threaded comments, where the child comments have to be within the parent list item. If you close it here, WordPress won't be able to create a valid ol/li tree.

By: Upgrading Your Comments Area in Wordpress 2.7 | Addicott Web

Upgrading Your Comments Area in Wordpress 2.7 | Addicott Web — Fri, 06 Mar 2009 20:35:12 +0000

[...] Code for functions.php (from Scriptygoddess) [...]

By: zakkap

zakkap — Sat, 28 Feb 2009 21:44:55 +0000

hey great post – the wordpress codex has so little information about this. you explained it clearly. and who is wordpress to tell us that we "shouldn't need to change" the HTML.