Thread

When doing a simple exp:comment:entries tag with dynamic set to “no”, it causes a sql query error.
Removing the dynamic variable remedies the error but then breaks the page as it doesn’t return results (obviously).

The error is as such

Error Number: 1052
Column ‘comment_date’ in field list is ambiguous

SELECT `comment_date`, `comment_id` FROM (`exp_comments` c, `exp_comments`) JOIN `exp_channel_titles` ct ON `ct`.`entry_id` = `c`.`entry_id` WHERE `c`.`status` = ‘o’ AND `c`.`channel_id` IN (‘9’, ‘5’) AND `ct`.`status` != ‘closed’ AND `c`.`site_id` IN (‘1’) AND (`ct`.`expiration_date` = 0 OR `ct`.`expiration_date` > 1315293869) ORDER BY `comment_date` desc LIMIT 15

Filename: modules/comment/mod.comment.php

Line Number: 475

The problem is in “(`exp_comments` c, `exp_comments`)”

The comments table is being called twice, which causes a duplication of the comment_date field and hence the error.

I’ve temporarily overcome this by keeping the comment module’s model from 2.2.2 but using the mcp, mod and upd files from version 2.1.1. This is not ideal however as I’m not certain wether this breaks other functionality or will cause other issues down the line.

There is clearly a bug in the new mod.comment.php file which needs to be corrected expediently.

afrihost,

Welcome to the Forums! I’m sorry you’ve run into this. I’m going to try and replicate on a local install to verify that is is a bug. Thanks for bringing this to our attention.

Cheers,

Hi Dan and afrihost,

Is this the same comment pagination error that’s in the bug tracker?
https://support.ellislab.com/bugs/detail/16389/

Afrihost, does the fix listed in the bug report work for you?

-Aaron

Thanks Aaron.

That does look like the bug in question afrihost. Can you replace your EE2.2.2. comment module files and try applying the patch supplied in the bug comments and let us know if the issue persists.

This has fixed this error yes.

In the meantime I have noticed another issue since migrating from 2.1.1 to 2.2.2.

All the pagination links are now broken - they produce urls such as “/&per_page=N15” and “/&per_page=P25” instead of just the N15 or P25 that used to define the pagination URL. Obviously the URLs above do not work - unless of course the “&per;_page=” is removed but that’s manual per url and we can’t exactly tell our customers to do that.

Hi, afrihost -

In system/expressionengine/config/config.php, have you modified enable_query_strings?

Can you let us know what that line says?

Thanks!

That line was set to true for some reason (strange) - have set to false and the issue is resolved

Hi afrihost,

Glad to see you’re all squared away now.

Please don’t hesitate to post again in the future as needed.

Thanks,

Mark