Not sure what to do here. I was developing on my local machine and two days ago moved everything to my hosting account to work out the inevitable bugs in porting. Today I noticed that my comments and flag abuse links below content were no longer there (my 5-star ratings widget was however). The first thing I did was to go back and check my localhost version and sure enough neither link was there either! Thought I might be going crazy and just hallucinated having installed/configured these modules so went into phpAdmin and checked the comments table. Sure enough there it was with all the comments I'd put in while testing that module.
Regarding the comments module, I totally disabled it, wiped the table and reenabled/reconfigured it. Nothing. Totally removed the flag and flag abuse modules, reinstalled and nothing. Even went as far as downloading the abuse module and configuring it (I'm in production/beta right now), but even IT doesn't show up. Thought that just possibly those modules might have been having a conflict with the google adsense banner I have displaying below 5-star/comment/flag, however after removing that and repeating all the above still nothing. In don't even get the "reset flags" option as admin! I'm just about positive I have everything configured correctly, but am open to suggestions on this point also.
Also, I went into comments setup and configured the comment submission form to display below the content instead of on another page. When I did this I went back to my content and the form showed up. it's just the LINKS to "Comment on this article" and "Flag as offensive" that aren't showing up. What I don't understand is why the 5-star module is still functioning correctly but comments/flag abuse and the abuse module will not work!
On my local machine I'm running Ubuntu with WAMPP and PHP that comes with that module (5.x). My webhost is also running Apache (don't know the version) and PHP 5.x. My Drupal install is 6.13. The paths are different between localhost and webhost, but I'm getting the same results from both.
Um... anyone?
Comments
Comment #1
fblevins commentedMy apologies for the double-post. I guess my provider got slow and I clicked twice? Dunno...
Anyway, an update on this issue (dealing specifically with the comments issue, i figure that if I can get this fixed it may automatically fix the flags problem as well):
With comments set to display the comments editor below the post I can add comments and reply to them and they show up fine. Went back and set it to display on a different page and the comments I'd entered stayed but still no link to submit a new comment below the node (should be next to the 5-star widget).
I currently have the flag module set up to require an explanation of why the content is being flagged. Am going back in and take this off and see if it makes any difference.
Comment #2
fblevins commentedOk. I set up a vanilla install on a new database and the comments link IS showing up, so it must be something I've done. On my (localhost) site I have the following modules enabled:
Content
Content Permissions
Content Taxonomy
Content Taxonomy Autocomplete
Content Taxonomy Options
Content Taxonomy Tree
Number
Option Widgets
Text
Chaos Tools
Page Manager
Views content panes
Comment (of course)
Contact
Database logging
Help
Menu
Path
PHP filter
Profile
Search
Taxonomy
Update status
Upload
Delete content and users
Devel
Performance Logging
Flag
Hierarchical Select
Hierarchical Select Content Taxonomy
Hierarchical Select Flat List
Hierarchical Select Menu
Hierarchical Select Taxonomy
Hierarchical Select Taxonomy Views
Image
Image assist
Advanced help
FCKeditor
Hierarchical Select Taxonomy Filter Block
IMCE
Pathauto
Taxonomy Manager
Token
Transliteration
User Delete
Mini panels
Panel nodes
Panels
JQuery Update
Wysiwyg
Bonus:Panels
Views
Views UI
Could one or more of these modules be causing a problem with the add comment link displaying properly? I hate to make an issue of this but have looked everywhere I can think of both online and in my own installation and can't come up with a resolution! If I've left any necessary information out of these posts that might help just let me know and I'll get it for you.
Comment #3
fblevins commentedAfter about 1.5 days I found the problem in a template redirect I had in place for a custom node header element. It was a booger to find though.