Forum Replies Created

Viewing 15 replies - 31 through 45 (of 3,008 total)
  • Plugin Author Doodlebee

    (@doodlebee)

    yes, there’s a discussion about this in the post previous to this one. There’s something fishy going on with updating the plugin. For some reason, every time I’ve tried to update the plugin, the SVN is taking my changes (i can see them taking in terminal), but in the repository, it seems only half the changes are coming through. I do not know why. (I just tried it again – and yet again, it’s still sending out files that are REALLY old, and only updating/removing/adding half the stuff that should be in there.) I’m still trying to get to the bottom of this.

    In the meantime, you can download it here:

    https://brassblogs.com/downloads/jquery-expandable-comments.zip

    Plugin Author Doodlebee

    (@doodlebee)

    I still don’t understand what’s happening. I just tried to update it again, and it’s still only updating half the files. I have no idea what’s going on here.

    In the meantime, use these files (I know they work, since I just tested them out myself):

    https://brassblogs.com/downloads/jquery-expandable-comments.zip

    I’m still trying to get to the bottom of this – it’s bordering on ridiculous now.

    Plugin Author Doodlebee

    (@doodlebee)

    Look, ma – another attempt. Sorry again! (apparently, I’m persistent!)

    Plugin Author Doodlebee

    (@doodlebee)

    See, now I look like a dork, because I kept trying to repost. Apologies!

    Plugin Author Doodlebee

    (@doodlebee)

    ert. ignore this. WordPress is having some issues with posting this morning.

    Plugin Author Doodlebee

    (@doodlebee)

    Sorry – as I mentioned in the email, I’m still having a couple of issues with the SVN – it keeps trying to upload only part of the plugin for some reason.

    For you (and anyone else who is having this issue), I’ve uploaded a zip to my server, and here’s the link to the download of the zip file I’m trying to upload to SVN (and get into the repository). It’s a band-aid – I know – but at least it’s one that works until I get this SVN stuff sorted.

    Download jQuery Expandable Comments 1.2

    I’m going to go ahead and mark this as “resolved”, because it *will* be resolved – and you all will be notified once it is (because your back end will tell you that an upgrade is in order!)

    Thanks for your patience!

    Thread Starter Doodlebee

    (@doodlebee)

    Well, right now, I’m using it on a site for a client, and he has one page with hundreds of articles split into individual categories Each post is only part of *one* category, so it shows the title with the category description belonging to that category under it. I would *guess* that if a post belonged to multiple categories, then the post would just show up, repeated, under the next category? I don’t know. Right now it’s working perfectly fine, though. I think what you’ve got there would work perfectly well. (in my case, though, I’m using the shortcode multiple times, because the client has something separating each category, so I’ve got a shortcode in place for each one so I can pop that thing in between them)

    I *do* think it would be nice to be able to add a class for the category name. I just tried using the catlist_class, and it didn’t apply the class anywhere – I don’t know if that’s a bug or what (but I worked around it) but anyway… hope that helps somehow!

    Thread Starter Doodlebee

    (@doodlebee)

    Nevermind. Figured it out.

    In the template file that you copy to your theme file (in the plugin, it’s under templates/default.php), you just need to add the following after the “Show Category Link” part:

    $lcp_display_output .= category_description( $this->catlist->get_category_id() );

    Bang. Description shows up.

    Thanks anyway!

    Plugin Author Doodlebee

    (@doodlebee)

    How very weird… did the file get deleted from your copy? it should be in the “js” folder in the plugin.

    ETA: Apologies. I am having a FUN time with the system lately. Apparently, the respository updated some, but not all, of the plugin files. That is so bizarre. (I just downloaded what the repository is handing out, and it’s NOT the correct files)

    I’ll give uploading the correct files a shot again – hopefully it works this time.

    Plugin Author Doodlebee

    (@doodlebee)

    Thanks Matt ?? I appreciate the review.

    Can I ask you: what would make it more intuitive? I’ve been swamped with work lately, so I haven’t been able to update the plugin for 3.7 yet, but I’m slowly working on it. maybe I can work something in with the next release. Do you think dropdowns would work better? That might work. The only issue is if you want it to work on a particular page – for example, a custom post type. if you just added “post-new.php”, then it would appear on ALL post types, but if you want it to show up only in the “dogs” post type, you have to put in “post-new.php?post_type=dogs”. That could get really cumbersome with a dropdown. (but perhaps a dropdown selection with an optional input field for additional info? I don’t know – thinking off the top of my head with only half a cup of coffee in me right now ?? )

    I’d love any suggestions for improvements. Thanks!

    Plugin Author Doodlebee

    (@doodlebee)

    I don’t understand what you mean about it “being in the same format”?

    the “div” option doesn’t work with my plugin. I’ve tried many times to get it going with “divs”, but it typically ends up breaking the site for reasons I haven’t been able to figure out. (I’m actually working in a new version *now* – to be released with WordPress 3.7 – that will hopefully have the “div” option enabled, but it’s been a long-time issue for me to get that sorted.) That’s why your only choices are “ol” and”ul”.

    You *can* change it, but note that, when you do, in your comment layout callback, you need to add in an extra “</div>” tag at the end to close out what it opens. But to add it in, ust pop in:

    case: 'div':
    	echo "<span class='replylink'><span class='show'>" . $options['show_replies'] . "</span>\n</span>\n";
    	echo "<div class='children'>\n";
    	break;

    in the top, and a corresponding </div> in the bottom section. But again, you’ll have to add in an extra closing div tag at the end of your comment callback, or the site layout will break.

    Also note that if I don’t get the “div” format working by 3.7, if you update the plugin, these changes will be wiped – so be sure to save it as another filename so you can refer back to it if I update it without this fix. (which is possible, because I’ve been trying to get the div option to work for several versions, to no avail. it’s a headbanger, for sure. I’d love it to work, too – because I prefer the nested divs over lists, myself.)

    Plugin Author Doodlebee

    (@doodlebee)

    Hi,

    sorry – WordPress doesn’t email me when someone leaves a support question here.

    What do your error logs say? What other plugins did you have activated? Theme? It most likely wasn’t my plugin (it possible, but it’s been pretty well tested), but a conflict with something else (the “blank white page” is the tell there). Your error logs would tell you exactly what it was that happened. Do you have that?

    Plugin Author Doodlebee

    (@doodlebee)

    Thanks! I like the tooltip idea – that’s a good one. I’ll have to put that in the next release. My instructions for the Instructions are huge, I know – but I feel it’s better to over-explain than under. ??

    No, it’s here.

    Plugin Author Doodlebee

    (@doodlebee)

    As I said in the support thread, it does not alter your comments extensively. It simply adds a link and a class to trigger the show/hide functionality. Out of over 3,000 downloads, you’re the only one who’s had this problem of “completely breaking the site”. I asked you a couple of times what other stuff you were using (so I could have the opportunity to see if there was another problem we both weren’t aware of, and give me the opportunity to fix it so others could benefit – and as you can see from my history, I am *excellent* in offering support for my plugins), but you didn’t say.

    Glad you found another plugin to suit your needs, but I still stand by the fact that my plugin does NOT mess up your site, and I still have yet to see any evidence from you to that effect, other than your say-so. If you’d be so kind as to give me the opportunity to try and fix whatever problem you’re having (so others who want to use my plugin can benefit from the fix) that would be appreciated, but to leave a bad review without even giving me the chance to do so leaves me with the only option of defending myself.

Viewing 15 replies - 31 through 45 (of 3,008 total)