Forum Replies Created

Viewing 15 replies - 301 through 315 (of 3,008 total)
  • Thread Starter Doodlebee

    (@doodlebee)

    No, I don’t, sadly. I just made the changes and popped the SQL file back in. We were using Gravity Forms, so I know several of the items were on those (there’s something like 7 forms on the site for various purposes), but there were some other fields that had my email address in there. I know _options was one of them. But I do recall that there were a couple of spots where the email address was within a serialized array – and it wasn’t part of the plugins.

    Thread Starter Doodlebee

    (@doodlebee)

    yeah, that’s what’s getting me. it’s one of the first things I do when I hand a site over, is change that email address to theirs in the settings. Yet I’m still getting all the notification emails.

    I don’t know, maybe it’s the older sites then – because the one’s I’m getting are from clients I did sites for quite a while ago (and they don’t update. Some of them, I don’t think they even use the site anymore – and I can tell – especially with the comments – that these are spam stuff coming through.)

    I just know the last site I finished (which was last week, and it’s 3.3.1), I *did* do a database dump and removed my email address from *everywhere* save my own profile – and I’m still getting user registration notifications. I just got three this morning (and one of the guys lost his password already. LOL)

    Could it be that I’m getting them because I’m an *administrator* on these sites? that’s something I’ve never looked into – if notifications just go to admins (no matter how many there are)? If that’s what it is, then maybe there’s some way to have it set to notifications go to just the *one* email address, not *all* admins….

    Plugin Author Doodlebee

    (@doodlebee)

    Well, if I had a link to the site you’re having an issue with, that would be a start. I can take a look at the source code and see what’s being put out. But additional goodness would be seeing if you’re using a callback in your template files (“bb_list_comments(callback=somefunction');”), and if you are, your functions.php file so I can see what the function is putting out. But something of that length, you’d have to email me. So if you *do* have a callback function in your template files, look for it and pop *just that function* over here and I’ll take a peek at it, too.

    If it helps (and you want to try and troubleshoot a bit on your own) I had this setup on my site, and I had to change my list output from a div style to the default list style – that was the quick fix.

    Plugin Author Doodlebee

    (@doodlebee)

    Actually, I just tested it on a 3.3.1 site, and it works just fine. “Show/Hide Replies” link appears (at the bottom of the post that has replies) and it toggles when you click it.

    The only thing that makes it not work properly is if you have a callback function for your comments in your functions.php file (and you’re calling it in your bb_list_comments() call). The bb_list_comments will not override the function you have in place for customizing your own comments layout. But without knowing what code you’re using, I can’t troubleshoot why it’s not working for you. (but it certainly works with default comments, no callback function) It’s most likely a class you’ve added to your callback that’s interfering.

    Also, you don’t indicate if you tried deactivating other plugins first. Another plugin could be conflicting. (honestly just saying “it doesn’t work” doesn’t provide much to go on in figuring out what the issue is. Without more information, I can’t help you.) but yep – it still works!

    Plugin Author Doodlebee

    (@doodlebee)

    Before you vote for it as broken (I’m assuming you’re the one who did that?) could you give me the opportunity to fix the problem? And as a side note, it’s only been tested up to 3.1.4 – you’re running it on 3.3.1. It would have been nice to get some kind of bug report before it was marked as “broken” without having the opportunity to check out the problem and fix it, and update it for the current version (which it hasn’t yet been tested in, and is noted as such.)

    Then something must be wrong, because I was (properly) using “get_the_title()”, and I was within the Loop (but only the “if(have_posts())” part), and the filter refused to work until I switched it to “the_title()” and moved it after the “while(have_posts()): the_post();”

    I do know the_title is just a wrapper for get_the_title, but my “get_the_title” certainly didn’t work (even after being placed after “the_post();”) – I *had* to switch it to “the_title();” before it would work. Believe me, I tried not to edit my code *too* much to mess up what I was doing with other pages! 🙂

    Thread Starter Doodlebee

    (@doodlebee)

    Awesome! You are my hero of the day (granted, it’s the end of the day, so this title will officially carry over to tomorrow!). I could have sworn I tried that before, but it didn’t work – then I realized I was using the esc_attr() stuff. You’re not. It works fine!

    I made a few edits, and this is the final code I came up with:

    [Code moderated as per the Forum Rules. Please use the pastebin]

    it works *wonderfully*. I’m happy-dancing like crazy. I do still need to sort out the visual editor issue, but since most people I do this stuff for (including me!) never use it, I’m not too concerned about it.

    Thanks SO much!

    Actually, I found out why it’s not working for me. I have some conditionals in regards to my header, and changing the title for “theme_my_login” ONLY works if you’re using <?php the_title(); ?>

    In my case, my code was using echo get_the_title(); instead of the_title(); and “Theme My Login” ignores the get_the_title() function.

    so if it’s not working for you, be sure you’re NOT using get_the_title() as I was. (and for the record, that’s not something that shows my theme isn’t “coded properly.” Just the plugin doesn’t use/acknowledge the get_ thing.)

    Just thought I’d pop this note in here, because I finally got it to work after getting rid of the get_ part of things.

    ETA: it also has to be *after* the while(have_posts()) part of the loop. So now I have to do some configuring so my conditionals for the page title don’t get all messed up, since mine is after if(have_posts()), so the title only gets shown once. (Not the login title, of course, but if I move the whole conditional *after* the while part, then the title will show up in my blog for every post – and I don’t want that! 🙂 )

    Thread Starter Doodlebee

    (@doodlebee)

    Oh sweet! I’ll give that a shot 🙂 I appreciate it. And I didn’t even think of residuals – I’ll look into that. Thanks for letting me know!

    Thread Starter Doodlebee

    (@doodlebee)

    Actually, I found a workaround. Instead of creating a query, I redid it so it simply takes the string in the URL and does get_userdatabylogin(). So if the string isn’t an actual user’s login name, it goes to 404.

    Thanks anyway!

    Thread Starter Doodlebee

    (@doodlebee)

    Fixed the bug. Added this to my functions.php file:

    // "Back to Directory" link goes to the wrong spot. this fixes it.
    add_filter('kws_gf_directory_backlink', 'link_to_member_directory');
    function link_to_member_directory($entryback) {
    	return str_replace('login', 'directory', $entryback);
    }

    (for anyone that may want to know, it was linking to the “login” page, but I wanted it to link to my “directory” page.)

    Hope it fixed it permanently… but we’ll see!

    Thread Starter Doodlebee

    (@doodlebee)

    Plugin Author Doodlebee

    (@doodlebee)

    That’s because to “view post,” you’re viewing it as if it’s a regular post on the front end of the site. The plugin is meant to be viewed on the back-end only. Since it’s a custom post type, the settings I’ve put in for it are *meant* to disable it from viewing and indexing (therefore giving access publicly) on the front end of the site, which is why you’re getting a 404… It doesn’t exist to be viewed on the front end.

    You can change that if you like, but unfortunately I’m currently on vacation for the holidays at the moment, and I’m responding from my iPhone… I don’t actually have access to my files to tell you exactly where to change this. But off the top of my head, I know it’s in the main file (instructions.php) and you want to look at the “register_post_type” function, and look att he array variables to set it to it’ll be indexed, etc. But keep in mind, if you do this, when the public does a search, these posts will appear in the search results.

    Another alternative would be to create a 404 page template with a condition that will allow you to see the custom post type, using possibly your current_user_can() status as an admin and a custom query to view the post from the front end, but that would also require a bit of plugin editing since the custom post type is set to *not* be queryable. (I’d also rather test that put first, actually, which I can’t do until I get back to my office.)

    I do not ever intend for the posts you create to be found on the front end of the site, so this isn’t something I ever plan to “fix,” since it’s really against the grain of the actual intended use of the plugin. If you want your posts to display on the front end of the site, there’s plenty of other plugins out there that will create custom post types for that purpose. However, if it’s a feature that you think would be helpful to you as an administrator (to be able to see the post before you publish) I can look into the possibility when I return from vacation (in early January) and give it a go at testing it out to be sure it doesn’t affect other important features. Alternatively, I can just look into removing the “View this post” button… That’s actually something I’ve never really thought about, to be honest!

    Forum: Hacks
    In reply to: Plugin update gone wrong?
    Thread Starter Doodlebee

    (@doodlebee)

    …aaaaand nevermind. Of *course* immediately after I post this, I figure out what happened. When I copied the standard readme.txt file (and ‘ported my stuff into it) I forgot to change the template’s “=== Plugin Name Here ===” to my plugin’s name. Changed it, uploaded it, and BAM it all works now.

    Duh.

    Thank you for your time.

    Plugin Author Doodlebee

    (@doodlebee)

    Blitz, this is covered in the readme file.

    Try looking at the “How to Use” section.

Viewing 15 replies - 301 through 315 (of 3,008 total)