C W (VYSO)

It’s interesting to note that the Disqus plugin has not been updated for more than five months. I’m an administrator on a news website that is about to add a comments system, and I’m discouraged by the fact that a number of users seem to be having serious problems with Disqus and WordPress 3.1.2.

I have no compelling stake in any particular system, but the slow development of Disqus compared to alternatives such as Livefyre and Intense Debate comes as a surprise to me.

Either way, sticking with 1.9.3 means I don’t have to change anything. ?? I can’t see any new features in version 2 that actually add functionality (as opposed to merely change functionality) so I’m happy to stay in the past until such time as the old version breaks. Thanks for the tips, though.

(1) My own theme, but it uses fairly conventional positioning techniques. Am I right in suggesting that you altered the positioning method for the edit overlay in the latest version? (I haven’t looked very closely, but I notice that version 2 now has a fee-loading-edit class that uses absolute positioning).
(2) Cheers. I’ll still be using the previous version for the meantime though: means I don’t have to poke around inside the plugin.
(3) The “previous plugin” would be the previous version of Front-end Editor. I’ve downgraded and it’s working perfectly.

Use a different plugin, is my advice. It seems to be completely useless if your theme has anything that makes it structurally different to one of the default WordPress themes. Plugins show up in random locations and they’re hard to align properly because there’s no customisation available.

Hi Chris, I used var_dump to diagnose, and it turns out the problem was in the authentication. So I downloaded the twitteroauth library directly from github, re-uploaded the files and now it seems to be working.

Not sure precisely what was wrong with the twitteroauth.php packaged in the plugin download: I noted that the twitteroauth.php in the plugin was about 50 bytes larger than the one I downloaded from github, but didn’t check for the precise differences. But whatever it was, it fixed the problem.

Thanks for all the help!

Yep, it does have that message. Thanks for the suggestion: I’ll have a poke through the code this morning and see where that takes me.

I don’t doubt that there’s a way to get it to work, but I’m pretty sure it’s got nothing to do with the general site/WP setup. I’ve now tested it on three servers – our main site plus two other places – that I know allow connections with Twitter. Just to make sure, I used fresh installations of both WordPress 3.0.1 and 3.0.4, and I tried installing them both in the root and in a sub-directory.

Still nothing’s happening – which suggests either that there’s a setup problem which coincidentally exists on all of those servers and installations, or there’s something a bit deeper at play. I’ll continue to try things out: everything else about this plugin is working great, but it’s the Twitter integration that I really need. ??

Actually, spoke a bit too soon. I tested this out on a host that I know allows outgoing connections – other plugins that post to Twitter from WordPress, like WordTwit, work just fine – but no updates have been sent to the Twitter account that I selected.

[I set up the live blog on a WordPress page (https://www.mediaspy.org/report/live-blog/) and it should have been sending tweets to https://twitter.com/cyrilwashbrook.]

Working like a charm now – great plugin!

Just one suggestion while I’m about it: it’d be good to have the ability to customise the tweets sent out through the plugin. I know that I could just go into Twitter and post my own tweets, but it would be a neat feature nevertheless as sometimes the first 139 characters of a live blog post aren’t going to be completely coherent on their own (or I might want to post only the first 80 characters of a particular post).

Must be the latter, as Twitter’s up. Thanks – I’ll look into it.

Sorry to double-post but I can’t edit again. I’ve switched to TwentyTen and it turns out it’s specific to my theme. However, I haven’t the foggiest idea how to correct the problem now that I know it’s something to do with the theme…

EDIT: Gee my face is red. Turns out it was a rogue entry in my functions.php file. ??

I have the same problem: all the images are there, but the search box is non-functional. I haven’t installed any new plugins or anything. It was working fine until very recently, and then the problem just randomly sprung up.

I’ve also attempted to deactivate/reactivate plugins, just to be sure. But none of them seem to be responsible: even when all the plugins were deactivated, the same failure occurred.

It wasn’t anything to do with the theme – ’twas an issue with some files getting corrupted during the copy. We cleared out the files and did another copy and it worked out fine. ?? Thanks for the reply, though.

Hi Frederick,

I’m not using it directly in my theme. I’m using wp-load.php in an external file, in order to display WordPress headlines on a non-Wordpress page. Best practice or not, it’s what a lot of sites do to call on their WordPress content in a directory other than the one in which their WordPress installations are placed. W3 Total Cache didn’t have a problem with this until the last upgrade.

It’s also a fixable problem, because every time I manually flush the page cache, all the headlines show up properly. I just don’t know what setting I should modify so that it flushes without my having to do it manually.

I don’t mean to bump this thread, but I can’t find an “edit” button so I’ll have to make a new post.

I have determined that this problem is definitely being caused by W3 Total Cache. I recently made substantial modifications to my home page (not my WordPress home: the site index, in which I’ve included wp-load.php). I then uploaded the version. Yet despite the fact that a new file had been uploaded, the old index page was still inexplicably showing.

I solved this problem instantly by manually flushing W3 Total Cache. Suddenly, the new page showed up.

This is obviously not an ideal situation: I’m not around to manually flush the cache every time one of my writers publishes a new article. What setting in W3TC could be causing this page to fail to update?