I'm trying to fetch a post from a blog and receiving the message that my dialog tool is at v8 while my plug in is at v5 - anyway to remedy this problem without having to use svn?
Jose
On 12. Feb 2007, at 07:17, Jose Villalobos wrote:
I'm trying to fetch a post from a blog and receiving the message that my dialog tool is at v8 while my plug in is at v5 - anyway to remedy this problem without having to use svn?
Your dialog tool is at v8 because you already did use svn.
Either svn up your support folder checkout or remove it.
I deleted the support folder exactly as told but now when trying to fetch the post but now its giving me the following: usage:dirname path /users/~/library/app.../support/bin/tm_dialog: line 5: /tm_dialog_v5: No such file or directory.
Thanks for the help, Jose
On 2/12/07, Allan Odgaard throw-away-1@macromates.com wrote:
On 12. Feb 2007, at 07:17, Jose Villalobos wrote:
I'm trying to fetch a post from a blog and receiving the message that my dialog tool is at v8 while my plug in is at v5 - anyway to remedy this problem without having to use svn?
Your dialog tool is at v8 because you already did use svn.
Either svn up your support folder checkout or remove it.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 12. Feb 2007, at 17:28, Jose Villalobos wrote:
I deleted the support folder exactly as told but now when trying to fetch the post but now its giving me the following:
You *deleted* it? Sure you didn’t *update* it? Cause the tm_dialog_v5 was something I added earlier today.
Best to delete it. If you do update it, you will also need to checkout the PlugIns folder.
Well, I believe I did delete it but I saw the file in there (I'm assuming because tm regenerates those files on restart) so I deleted those files for good measure and now I'm seeing another error message on fetch post.
{ /usr/lib/ruby/1.8/xmlrpc/client.rb:535:in `do_rpc': HTTP-Error: 302 Found (RuntimeError) { from /usr/lib/ruby/1.8/xmlrpc/client.rb:409:in `call2' { from /usr/lib/ruby/1.8/xmlrpc/client.rb:399:in `call' { from /Applications/TextMate.app/Contents/SharedSupport/Bundles/ {Blogging.tmbundle/Support/lib/metaweblog.rb:31:in `getRecentPosts' { from /Applications/TextMate.app/Contents/SharedSupport/Bundles/{Blogging.tmbundle/Support/lib/blogging.rb:547:in `fetch' { from /Applications/TextMate.app/Contents/SharedSupport/Bundles/{Blogging.tmbundle/Support/lib/blogging.rb:546:in `popen' { from /Applications/TextMate.app/Contents/SharedSupport/Support/lib/progress.rb:{11:in `call_with_progress' { from /Applications/TextMate.app/Contents/SharedSupport/Bundles/{Blogging.tmbundle/Support/lib/blogging.rb:546:in `fetch' { from /tmp/temp_textmate.hQ0EzC:3
For the record, I'm trying to fetch from a WP blog hosted by wordpress.com. On second thought, I think the bundle might not work for this kind of blog, but I'm really not sure.
Thanks, Jose
On 2/12/07, Allan Odgaard throw-away-1@macromates.com wrote:
On 12. Feb 2007, at 17:28, Jose Villalobos wrote:
I deleted the support folder exactly as told but now when trying to fetch the post but now its giving me the following:
You *deleted* it? Sure you didn't *update* it? Cause the tm_dialog_v5 was something I added earlier today.
Best to delete it. If you do update it, you will also need to checkout the PlugIns folder.
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On 12. Feb 2007, at 17:53, Jose Villalobos wrote:
Well, I believe I did delete it but I saw the file in there (I'm assuming because tm regenerates those files on restart) so I deleted those files for good measure and now I'm seeing another error message on fetch post.
{ /usr/lib/ruby/1.8/xmlrpc/client.rb:535:in `do_rpc': HTTP-Error: 302 Found (RuntimeError)
I believe this indicates that the end point URL you configured gave an 302 error.
For the record, I'm trying to fetch from a WP blog hosted by wordpress.com. On second thought, I think the bundle might not work for this kind of blog, but I'm really not sure.
I seem to recall having read that, yes. But haven’t tested it though. It does work with WordPress in general (the software, not their hosted solutions)
-
Allan Odgaard -
Jose Villalobos