kelson
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: [Plugin: Twitter Tools] Duplicate digests on scheduleI’m consistently getting only one post per day now. It seems to be getting built at the time I set in the config, but scheduled for 11:59 pm instead of published immediately.
Before, when I was getting multiple posts per day, they were all being scheduled for 11:59 pm on the day they were built. So the duplicates that were generated after midnight ended up scheduled for the following night.
Forum: Fixing WordPress
In reply to: [Plugin: Twitter Tools] Duplicate digests on scheduleIt looks like the patch worked for me too. Just one post last night, though it was posted at 11:59 instead of the time I’d selected, 11:30.
Forum: Fixing WordPress
In reply to: [Plugin: Twitter Tools] Duplicate digests on scheduleWell, I installed Twitter Tools 1.5.1 yesterday. And right now, I have 20 posts scheduled for tonight, all of which are identical to last night’s post but show today’s date.
So upgrading didn’t fix it.
Possible interactions: I’m using both WP-Super-Cache and WP-Widget-Cache. Let me know if you need a full list of plugins I have running.
Forum: Plugins
In reply to: [Plugin: Twitter Tools] Twitter tools tweeting when old posts are savedI ran into the same issue with the stable version, but it seems okay with 1.5 beta 3. Of course, the beta has other problems.
Forum: Fixing WordPress
In reply to: [Plugin: Twitter Tools] Scheduled postsThis seemed to work with the stable version, but has stopped working with 1.5b3. It just doesn’t seem to be sending the tweet on scheduled posts.
Forum: Fixing WordPress
In reply to: Flash uploader with Flash 10I did a little digging, and found this: http://trac.wordpress.org/ticket/6979
It looks like Adobe removed a feature that the uploader depended on.
Forum: Plugins
In reply to: [Plugin: WP Super Cache] Allow tighter permissionsGlad to hear it! Thanks!
Forum: Fixing WordPress
In reply to: post_date_gmt is always 0000-00-00This problem started showing up when I turned on XCache about a week ago. There were about 5 or 6 posts that I noticed weren’t showing up in my feed reader, and looking at the feed they were dated Dec 31 1969. (Oddly, the most recent one wasn’t affected.) Checking out the DB showed them with zeroed-out gmt dates, which I manually fixed.
I’ve applied the patch, and will keep an eye on the DB to see if that takes care of it.
I did have a couple of other posts that weren’t published, but for some reason showed post dates matching the modification date. This, interestingly, resulted in the dashboard telling me that I had one scheduled post, but producing an empty list when I tried to list them.
Forum: Plugins
In reply to: [Plugin: WP Security Scan] What’s with the empty updates?Thanks!
Forum: Plugins
In reply to: [Plugin: WP Security Scan] What’s with the empty updates?Just to clarify, I don’t mind frequent updates, as long as there are actual substantive changes and I can see what’s new before downloading the files.
An “update now!” notice when the only thing that’s changed — literally — is the version number is just adding noise to a critical administration process.
Forum: Plugins
In reply to: [Plugin: WP Security Scan] CAUTION: SCREWED-UP MY BLOG!I’d suggest clarifying the version/error hiding in the plugin docs and descriptions. Right now, they seem to suggest that activating it as-needed is sufficient.
Forum: Plugins
In reply to: Supercache rewrite rules incorrect if blog not at top levelThanks for the response.
I’ve got RewriteBase set to /journal/. If I understand mod_rewrite correctly, this removes /journal/ from the beginning of $1, which would be why the second half of each expression doesn’t match. In theory, setting the RewriteBase to / (and adjusting all the other rules accordingly) might clear up the path within the cache directory.
But that still leaves the path to the cache directory, both for the conditional and for the rewrite. The conditional is bound to ${DOCUMENT_ROOT}, which won’t get changed by RewriteBase.
I think the reason RewriteBase doesn’t add /journal/ to the target is it looks like an absolute path rather than a relative path. I tried setting it to redirect to wp-cache/… instead of /wp-cache/…, and it seems to work (with the RewriteBase set to /journal/)
(I’m still a bit of a novice at mod_rewrite, though. I tend to study the manual while I try to do something, get it in place, then forget until the next time.)
Forum: Developing with WordPress
In reply to: Supercache installed, not serving pagesIs your blog at the top of your domain (i.e. at http://www.example.com/) or is it in a subdirectory (i.e. at http://www.example.com/blog/)?
If it’s in a subdirectory, it might be the problem I ran into with the rewrite rules assuming that your blog is at the top.
Forum: Fixing WordPress
In reply to: Showing posters usernamesEach user’s profile has a “Display name publicly as…” option where you can choose between the username or some combination of first and last name.
Forum: Fixing WordPress
In reply to: XML-RPC Response Parsing Failed ERRORThis is almost certainly the same problem I had here with PHP 5.2.2. There’s a bug in that version with XML-RPC.
Workaround: add the following line at the beginning of WordPress’ xmlrpc.php file, right before the first reference to $HTTP_RAW_POST_DATA:
$HTTP_RAW_POST_DATA = file_get_contents("php://input");(In theory it should be fixed in the next version of PHP.)