kelson

Edit: Never mind, at first I just looked at the beginning & end of that thread and it didn’t seem to apply, but the middle looks like the same issue.

I’ve checked back from time to time and I still can’t get the new version to sync with my Amazon S3 buckets on either of two blogs. I keep going back to the previous version because I don’t have time to troubleshoot. There’s no error message, it claims it’s synced, and there’s nothing in the website error log, but the files never arrive at Amazon.

Is there something I should be looking for? Some trick I should be using?

Thank you, I appreciate it!

On top of that, the new version flat-out won’t work with Amazon S3 because I can’t set the bucket it uploads to. I reported the problem using the form, but I haven’t heard back from them after two days.

It’s a good thing WP.org keeps archives of older versions.

I just ran into this too. If you can’t set it in php.ini or .htaccess, you can add the following line to your wp_config.php file and it seems to work:

ini_set(‘date.timezone’,’America/Los_Angeles’);

Replace “America/Los_Angeles” with the appropriate time zone from https://www.php.net/manual/en/timezones.php

Yes, I’m seeing it too, on three sites with different sets of plugins. The last IE9 preview displayed it just fine, but the beta shows exactly the same behavior you’re seeing.

I haven’t taken the time yet to investigate whether it’s a bug in IE9 or a deliberate change.

Some follow-up:

First, I tried rolling back to Twitter Friendly Links 0.4.3 and re-enabling WP Super Cache, and it appeared to work normally again.

Second, I think I’ve found a workaround for the problem. I’ve upgraded back to 0.4.4, and added the following line to the list of URL strings that WP Super Cache will avoid caching:

^/[0-9]+/?$

I’m just using the numeric short link with no prefix, so this ends up matching it with or without a trailing slash. People with different patterns for the short link will need different patterns to match here.

It does still redirect from https://example.com/1234 to https://example.com/1234/ (adding the trailing slash) for some reason, but https://example.com/1234/ is redirecting to the actual post. So it’s at least working even though there’s an extra redirect step in the middle.

*whew* Finally had a chance to try 3.0.3, and it seems to work fine! Thank you, Alex, for all the updates!

As for the <b>completely different issue</b> that johnbakeronline and dazzlindonna have…remember that you have to upload the carrington-mobile-(version) folder into your themes directory. I don’t think automatic update/install will do that, so you’ll probably need to use FTP.

I installed 3.0.2 and it’s back to the original problem again.

PHP Fatal error: Call to undefined function cfct_comment_list_class()
in path/to/wp-content/themes/carrington-mobile/comments/pings-loop.php

And I mean really back to the original problem, because when I remove that call from comments/pings.php, I end up with

PHP Fatal error: Call to undefined function cfct_comment_class() in /path/to/wp-content/themes/carrington-mobile/comment/ping.php

And if I remove that reference, the page finishes loading, but the pingbacks don’t actually show the linked site.

It’s like it’s just been reverted back to 3.0, except with everything in carrington-mobile instead of wp-mobile. Even the partial fix from 3.0.1 is gone (since 3.0.1, if I uploaded those missing files, actually worked).

I’ve installed 3.0.1, and now comments don’t work at all. I just get “error loading comments-loop 209”.

I see that comments-loop.php and pings-loop.php aren’t in the 3.0.1 archive.

If I upload those the files from the 3.0.0 archive, comments work again, but then I’m back to the original PHP error with pingbacks until I remove that call to cfct_comment_list_class(). After that, pingbacks finally display okay.

I’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.

It 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.

Well, 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.

I 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.

This 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.