Gary_Petersen

I back up my databases weekly and started having a similar problem yesterday. I don’t get the SSL error message, but a login unsuccessful exception message, shown below.

I’ve verified the user name and password are correct and that I can log into the Dropbox website using them.

[2012-10-10 2:26:12 am] — Initiate transfer to dropbox
[2012-10-10 2:26:12 am] — Instantiate new DropboxUploader()
[2012-10-10 2:26:12 am] — files loop: /home2/countrykeepers/public_html/kjv/wp-content/wpTimeMachine-content-files.zip >> /KJV >> wpTimeMachine-content-files.zip
[2012-10-10 2:26:13 am] — error w/ S3(): exception ‘Exception’ with message ‘Login unsuccessful.’ in /home2/countrykeepers/public_html/kjv/wp-content/plugins/wp-time-machine/includes/DropboxUploader.php:90
Stack trace:
#0 /home2/countrykeepers/public_html/kjv/wp-content/plugins/wp-time-machine/includes/DropboxUploader.php(74): DropboxUploader->login()
#1 /home2/countrykeepers/public_html/kjv/wp-content/plugins/wp-time-machine/includes/wpTimeMachineSwitch.php5(30): DropboxUploader->upload(‘/home2/countryk…’, ‘/KJV’)
#2 /home2/countrykeepers/public_html/kjv/wp-content/plugins/wp-time-machine/includes/wpTimeMachineCore.php(812): require(‘/home2/countryk…’)
#3 [internal function]: wpTimeMachine_init(”)
#4 /home2/countrykeepers/public_html/kjv/wp-includes/plugin.php(403): call_user_func_array(‘wpTimeMachine_i…’, Array)
#5 /home2/countrykeepers/public_html/kjv/wp-admin/admin.php(151): do_action(‘settings_page_w…’)
#6 /home2/countrykeepers/public_html/kjv/wp-admin/options-general.php(10): require_once(‘/home2/countryk…’)
#7 {main}
[2012-10-10 2:26:13 am] — Transfer not completed

Any ideas? Thanks, Gary

The issue is fixed with version 1.9.99 that was just released today.

FWIW, since updating to WordPress v3.3, CTRL-Backspace works for me in Internet Explorer v8 and Firefox v8.0.1, but not in Chrome v16.

Alex, I uploaded the updated plugin and it allowed me to successfully create and save a test post following the steps I outlined earlier in this thread. I was also able to post to Twitter using the plugin, though I did have only it activated. One thing you’ll want to update in the final release, the version number of the plugins (as shown on the plugins page in WordPress) did not change when I loaded the test versions.

Alex, I don’t see a way to provide information to the WordPress Help Center without also providing them money. Here’s what I found on my system, which is running WordPress 2.9 with Akismet 2.2.7 the only other active plugin (and Hello Dolly and the Twitter Tools suite the only other installed plugins).

With all of the Twitter Tools plugins deactivated, if I create a new post, type Testing in the post header and body, then click Save Draft, the post saves just fine.

If I then move that draft post to the trash, activate only the main Twitter Tools plugin (leaving the Twitter Tools – Bit.ly URLs, Twitter Tools – Exclude Category, and Twitter Tools – Hashtags plugins deactivated), create a new post with Testing in the post header and body, and click the Save Draft button, I get the “Your attempt to edit this post: “Testing” has failed. Please try again.” error message. When I re-navigate to my weblog (not using the browser Back button), I find the post saved as a draft but with only the post header field filled. The body is empty.

I can edit that draft post, type Testing in the body, click the Save Draft button again, and the post saves without error.

The Twitter Tools settings are:

– Enable option to create a tweet when you post in your blog? Yes
– Tweet prefix for new blog posts: New blog post
– Set this on by default? No
– Create a blog post from each of your tweets? No
– Create a daily digest blog post from your tweets? No
– Title for daily digest posts: My Tweets for %s
– Create a weekly digest blog post from your tweets? No
– Title for weekly digest posts: Twitter Weekly Updates for %s
– Order of tweets in digest? Oldest first (chronological order)
– Category for tweet posts: General
– Tag(s) for your tweet posts: twitter
– Author for tweet posts: gary-petersen
– Exclude @reply tweets in your sidebar, digests and created blog posts? No
– Tweets to show in sidebar: 5
– Create tweets from your sidebar? Yes
– JS Library to use? jQuery
– Give Twitter Tools credit? Yes

Disabling the Twitter Tools plugin restores the blog to normal performance.

Thanks for the plugin and your help in fixing this issue. Gary

Alex, the advice I took away from the thread you linked to was to disable your plugin, Twitter Tools. Doing that appears to correct the issue on my weblog, but (obviously) removes the function the plugin provides.

I couldn’t tell if the issue was that something in WordPress 2.9 was now broken or if the interaction between WordPress 2.9 and Twitter Tools 2.0 is what is amiss. Do you know what the issue is?

I appreciate your plugin, Alex. It is useful to me when I’m visiting my company’s headquarters, where I often don’t pay for Internet access in the hotel and our work network blocks Twitter. I can still update my Twitter account via my weblog and your plugin.

Thanks, Gary

My one remaining site showed the update as available this morning. It updated quickly and without issue, just as the other two sites had. Just 12 hours later. Go figure.

I normally work on the sites using Firefox, by the way. Clearing the cache and restarting Firefox didn’t change the behavior at all. Neither did loading the site in Internet Explorer.

Very cool. Thanks.

I’m just now exploring widgets and that helps a lot.

Thanks, Michael, though I’m not sure I follow the logic. I think that is saying that if you don’t check any category, the post gets written to the default category. But if you check another category, the post will get written to the checked category, but not also to the default category.

I’ve not had any issue with lost posts. Thanks again for pointing that out. I didn’t find it when I first started searching.

One additional piece of information, since upgrading, the list of post categories off to the right of the writing window now includes categories from my list of links. That used to not be the case.

You may also need to clear out your browser cache after the upgrade to WordPress 2.1. On my system, many of the WYSIWYG icons didn’t display after the upgrade until I did that.

It turns out that I didn’t have access to the database in a way that I could repair the table, as suggested. Since comments weren’t allowed on this weblog (announce only), that table was pretty much empty any way, so I deleted the table that was missing then re-created it manually, using another of my weblog tables as a template.

All is well now. Thanks for the help.

Not completely Greek! ?? I’ll give that a shot and see what happens, after backing up again. Thanks.

macmanx, I had done replaced the wp-blog-header.php file with the updated one from that link, but just a day or two ago, so maybe it hasn’t flowed all the way through Bloglines yet.