Forum Replies Created

Viewing 15 replies - 46 through 60 (of 74 total)
  • Thread Starter Jon Hardison

    (@jonhardison)

    I hear you. Truth is it probably isn’t just a setting. Notifications have been a problem consistently since day one. I finally started getting notifications of comments but could only ever get it to work via the associated business page. So if I wasn’t sitting in Facebook all the time or didn’t enable email notifications for business page comments I’d never know. In some case (when I was really busy) I might not get back to an FB user for a month or two just because I didn’t know they’d left a comment. Even when I got it all working it didn’t work all the time. Facebook would block comments for no reason so I’d constantly have to check the moderation screen to see what was gummed up in there. Keep in mind, if it does get blocked you get zero notifications…

    Here’s my problem with this: Facebook comments on your site do a great job of increasing interactions. I’ll give it that. But it does a terrible job supporting your interactions with commenters. I liken it to starting out with one support line in your office. Not all the people that need support are going to get through, but those that do will be helped. Now add a new phone system that will allow everyone to get through but will only right 30% of the time. You basically are building bad support into your operation, y’know what I mean? FB Comments turned out to be the same as a phone system that only rings 30% of the time.

    We’re a design firm so this is a big deal for us. You, however, might have an entertainment site or something where this isn’t as big a deal… Point is, in our experience, if you rely on comments to provide a service or to spur on actual conversation, you’re taking a big risk relying on FB comments.

    I wish you luck. It’s been a long time since we messed with this so it might be better now. Can’t be sure. ??

    Thread Starter Jon Hardison

    (@jonhardison)

    I didn’t ever find a solution. Honestly, I just gave up. Truth is Facebook is just making too many changes too fast for this to be a safe system to use. The JetPack commenting system that lets commenters use their FB or Twitter creds to comment seems to be the ‘happy’ medium for us. Of course that’s only true when Jetpack isn’t slowing everything to a crawl. ??

    Sorry I can’t be more helpful. We’ve been playing with various FB comments implementations for many years. I think Facebook just makes it too hard.

    Thread Starter Jon Hardison

    (@jonhardison)

    I wish I could. This site isn’t public yet (of course). It will be in another day or two, but for the moment I can’t…

    I have found that it is working on a few other sites running 3.8 though so it’s not a problem with WP.

    Thanx a bunch for the help though. I’ll close this one.

    Thread Starter Jon Hardison

    (@jonhardison)

    Have you tried it? Is it working for you in WP 3.8?
    I haven’t needed to do this in a while, but now that I do it stinks not being able to get it working.

    Thread Starter Jon Hardison

    (@jonhardison)

    Hey there! Thanx for the quick reply. All cache is clear the class entered was “hide” and another I tried to simply “nophone”. I also tried them with the period for giggles but that didn’t work either.

    I’ve checked both the li and the lower a for it and nothing. ??

    Thread Starter Jon Hardison

    (@jonhardison)

    Man you’re good. ??
    We’ve applied the update across the impacted sites and the issue is resolved.

    Thank you SO much!

    I’d love an answer to this question too, although I think I already know what it is. ??

    If I understand all this correctly, you won’t be able to do this. The problem is once you log-in via SSL via the main domain, that log-in won’t work on unencrypted subdomain admin pages. You’ll just be forced to log-in again as your SSL cert is probably only setup for the main domain.

    The rightest way I’ve been able to find for dealing with this issue includes two things.

    The first is grabbing yourself a copy of the WordPress HTTPS plugin which does a great job of keeping all this really clean and simple on multisite install.

    The second thing is (and don’t hate me) to purchase a Wildcard SSL Cert. They’re expensive, but will work with all your subdomains, so you can use WP HTTPS to manage how each site is to use the cert.

    Also keep in mind that you’re going to want to be sure that your domain mapping plug-in is setup to leave admin pages in the subdomain instead of using the option to access them within the mapped domain [example: https://subdomain.domain.com/wp-admin vs https://domain.com/wp-admin%5D

    I’d love to be wrong though. ??
    Wildcard Certs are like $350 a year!

    Best of luck.

    Thread Starter Jon Hardison

    (@jonhardison)

    Update again:

    I pulled this plug and use SEO Facebook Comments to see if I could figure out what was going on. The comments left using Firefox someone were send to the WordPress internal commenting system? Does that make any sense?

    It doesn’t to me, but I thought I’d share.

    Thread Starter Jon Hardison

    (@jonhardison)

    Update:

    Now I’m at a total loss. LOL!

    If comments are made in EI, Safari or Chrome they should up in those browsers. But if a comment is made in Firefox it only shows up in Firefox.

    This makes no sense.

    Me too. Had this plug-in working perfectly and it suddenly stopped. ??
    I think this is why the original guys gave up on it. FB keeps changing stuff for no reason.

    Anyways, add me (with several sites) to the folks having this issue.
    Jon-

    Okay, that worked! Thank you webeida!!!

    One thing though: When I got the notification of your solution the strangest thing happened. The line to add was completely different.

    'si-contact-form/si-contact-form.php', // Fast Secure Contact Form

    Don’t know what happened there. ??
    Thanx again though.

    Same here! It’s not doing it on all my sites, but I’ve found two where this is a problem. Removed the shortcode, turned a few things on and off… Still doing it.

    Thought it might be a conflict with the RAW HTML Protector… Nope! Still doing it. Any ideas?

    This is a session problem with AJAX.

    All you should need to do is enable SSL on your BuddyPress specific pages like Activity, Members, Sites, Groups, etc. and everything should start working just fine.

    Edit each of your BuddyPress created pages and check both options in the HTTPS option on the left. If you don’t see HTTPS on the left just click Screen Options in the upper-right of your dash while editing the page and enable HTTPS.

    I had this same issue and fought with it forever. It was a pretty simple fix. ??

    Just had the same issue. I know it would be horrible to post another product in here, but it seems support goes largely unanswered so…

    What plug-in worked for you without producing this dreaded error? Erroring Dashes everywhere would love to know. ??

    Thread Starter Jon Hardison

    (@jonhardison)

    Thanx SmartDesi9n. Yeah, we can across that one too, but had no luck ith it. Really hoping we can get this resolved soon. As you can see, the site owner is getting pretty frustrated, and after all my picking I can figure out what’s causing it. ??

Viewing 15 replies - 46 through 60 (of 74 total)