Hola.
I read the post titled Does not work with Nodecomment module but I don't use the Nodecomment module, although the patches would indicate that it may have solved my problem, I'm not sure as I'm not a php or drupal guru.
Anyway, since upgrading to drupal 6.16 the add comment link on my stories and pages have disappeared and both that link and the read more link have disappeared from the "front page".
Changing back to Garland, the links reappear.
Inspect the element (chrome, firebug both) and the relevent <ul> are empty apart from classes.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | no_comments.jpg | 80.83 KB | datakid |
Comments
Comment #1
datakid commentedIn the posting mentioned above, there is talk of a patch against the 6.x-2.x-dev branch.
I am using this in a production site, so would prefer not to use the -dev build.
Regardless of this, the patch provided in that link talks about it being "patch for latest 6.x-2.0-dev". From what I can tell, the last -dev release for 6.x-2.x was done in May '09 and the last stable being in Dec 09. This confuses me. Does it mean that the patch won't work on the stable?
Should I be using the (older) -dev and applying the patch to that?
cheers
Comment #2
datakid commentedOn a fresh install I patched against the stable 6.x-2.0 version of the theme, using this patch, and it works a treat.
So, despite not wanting to fsck up a production install too much, I performed exactly the same patch on it, but I'm still not seeing the links and they are still rendered empty in the code...any more ideas?
Comment #3
datakid commentedSee attached image for what I'm seeing in inspect element
Comment #4
datakid commentedOkay, problem solved.
I'm not quite sure what happened, but these are the steps that fixed it:
1. Apply path listed above to stable 2.0 theme
2. Go to theme settings page
3. add a prefix and suffix to the add comments and read more links (and save...)
4. refresh page - boom! there they
5. Remove prefix and suffix in settings (and save)
6. refresh page - still there.
I presume this means that I had somehow corrupted my settings file.
Comment #5
pcdonohue commentedFor folks using a sub-theme, you may also want to check out http://drupal.org/node/708068
What's weird is that I didn't start noticing this behavior until a week after I had upgraded.