Date bug on 1.4.5

_______________________________________________
Emacsweblogs mailing list
Emacsweblogs <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/emacsweblogs

Strange behavior with wordpress

_______________________________________________
Emacsweblogs mailing list
Emacsweblogs <at> nongnu.org
https://lists.nongnu.org/mailman/listinfo/emacsweblogs

Symbol's function definition is void: caddr

Hi,

I was able to get weblogger to work after the initial setup, however
after the first session and logout I'm unable to re-connect. I've
completely removed the settings and reinstalled weblogger using ELPA and
after a re-install it works fine in the same way: first login works but
subsequent logins are foiled.

Peter

The following is the error:

Symbol's function definition is void: caddr

This is the content of my .emacs file:

; This buffer is for notes you don't want to save, and for Lisp evaluation.
;; If you want to create a file, visit that file with C-x C-f,
;; then enter the text in that file's own buffer.

;;; This was installed by package-install.el.
;;; This provides support for the package system and
;;; interfacing with ELPA, the package archive.
;;; Move this code earlier if you want to reference
;;; packages in your .emacs.
(when
      (load
       (expand-file-name "~/.emacs.d/elpa/package.el"))
    (package-initialize))

;;; This was installed by package-install.el.
;;; This provides support for the package system and
;;; interfacing with ELPA, the package archive.
;;; Move this code earlier if you want to reference
;;; packages in your .emacs.
(when
      (load
       (expand-file-name "~/.emacs.d/elpa/package.el"))
    (package-initialize))
(custom-set-variables
    ;; custom-set-variables was added by Custom.
    ;; If you edit it by hand, you could mess it up, so be careful.
    ;; Your init file should contain only one such instance.
    ;; If there is more than one, they won't work right.
   '(weblogger-config-alist (quote (("default" "http://<blog
url>/xmlrpc.php" "<login>" "" "1") ))))
(custom-set-faces
    ;; custom-set-faces was added by Custom.
    ;; If you edit it by hand, you could mess it up, so be careful.
    ;; Your init file should contain only one such instance.
    ;; If there is more than one, they won't work right.
   '(default ((t (:inherit nil :stipple nil :background "white"
:foreground "black" :inverse-video nil :box nil :strike-through nil

format-time-string: Symbol's function definition is void: caddr

Hi,

I have setup weblogger.el to work with my locally hosted wordpress blog 
but i seem to only be able to log in once before I start getting the 
following error:

Wrote /home/peter/.emacs
Contacting host: locuscor.homedns.org:80
Reading [text/xml]... 13k of 13k (100%)
Reading... done.
format-time-string: Symbol's function definition is void: caddr
Contacting host: locuscor.homedns.org:80
Reading [text/xml]... 170 bytes of 160 bytes (106%)
weblogger-api-blogger-edit-template: Wrong type argument: 
char-or-string-p, nil
format-time-string: Symbol's function definition is void: caddr

My .emacs file looks like this:

;;; This was installed by package-install.el.
;;; This provides support for the package system and
;;; interfacing with ELPA, the package archive.
;;; Move this code earlier if you want to reference
;;; packages in your .emacs.
(when
     (load
      (expand-file-name "~/.emacs.d/elpa/package.el"))
   (package-initialize))

;;; This was installed by package-install.el.
;;; This provides support for the package system and
;;; interfacing with ELPA, the package archive.
;;; Move this code earlier if you want to reference
;;; packages in your .emacs.
(when
     (load
      (expand-file-name "~/.emacs.d/elpa/package.el"))
   (package-initialize))
(custom-set-variables
   ;; custom-set-variables was added by Custom.
   ;; If you edit it by hand, you could mess it up, so be careful.
   ;; Your init file should contain only one such instance.
   ;; If there is more than one, they won't work right.
  '(weblogger-config-alist (quote (("default" 
"http://locuscor.homedns.org/wordpress/xmlrpc.php" "<<login>>" "" "1") 
("patojo_local" "http://localhost/wordpress/xmlrpc.php" "<<login>>" "" 
"1")))))
(custom-set-faces
   ;; custom-set-faces was added by Custom.
   ;; If you edit it by hand, you could mess it up, so be careful.
   ;; Your init file should contain only one such instance.
   ;; If there is more than one, they won't work right.
  )

Thanks for any assistance!

Peter

Re: Weblogger issue with Wordpress 3.0.1

_______________________________________________
Emacsweblogs mailing list
Emacsweblogs <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/emacsweblogs

Weblogger issue with Wordpress 3.0.1

Hi,

I've discovered Weblogger.el yesterday and i have an issue when
fetching posts from my Wordpress 3.0.1 blog.

My current version of Emacs is 23.2.1.  My current version of
Weblogger is the launchpad one.

When i type weblogger-setup-weblog i got an error 500 after typing the
configuation name and the saving of the parameters.

The debugger buffer show this log:

[...]  Saving file /home/jpec/.emacs...  Wrote /home/jpec/.emacs
Contacting host: www.julienpecqueur.com:80 Reading [text/xml]... 25k
of 25k (100%) Reading [text/html]... 677 bytes of 669 bytes (101%)
Reading... done.  xml-rpc-request: Error 500

The xml request wich give error is (log from the xmlrpc.php.log file
on the server):

<?xml version="1.0" encoding="UTF-8"?> <methodCall>
  <methodName>metaWeblog.getRecentPosts</methodName> <params>
    <param>
      <value>
        <string>1</string> </value>
    </param> <param>
      <value>
        <string>my_user_was_here</string> </value>
    </param> <param>
      <value>
        <string>my_password_was_here</string> </value>
    </param> <param>
      <value>
        <int>20</int> </value>
    </param> </params>
</methodCall>

When i try this xml request with curl on my server, i got a 500 error
too.

What's wrong?

--

-- 
Julien Pecqueur (JPEC)

Site:      http://julienpecqueur.com
Email:     jpec <at> julienpecqueur.com
PGP:       B1AA2389 (GNUPG)
IRC:       jpec (irc.freenode.net)
StatusNet: http://identi.ca/jpec

Powered by Archlinux - Keep it simple stupid !

_______________________________________________
Emacsweblogs mailing list
Emacsweblogs <at> nongnu.org
http://lists.nongnu.org/mailman/listinfo/emacsweblogs

Wordpress and timezone differences

Tonight, I finally had a chance to look at the timezone problems
people are having with WordPress and weblogger-el. 

I was able to confirm that if you set your WP installation to your
timezone, you have to then offset your weblogger-el posts by the same
amount in the opposite direction.

That is, since I'm in GMT-4 and I set my timezone in WP to GMT-4, I had
to set the timezone in my weblogger-el post to be GMT+4.

Why?

From a little googling (e.g http://www.makeyougohmm.com/20070125/4178/)
I found that other people are having similar problems with WP and
timezones.  It looks like WP isn't really treating time properly.

I think I'll be adding a customization so that you can tell weblogger-el
to the appropriate timezone for your blog.  It looks like this is what
has to happen to work around a WP bug.

I could be wrong in how I understand this problem, though, so I'm
interested in your feedback.

Thanks,

Mark.

--

-- 
http://hexmode.com/

Embrace Ignorance.  Just don't get too attached.

Re: Weblogger bugs (WordPress, Emacs 22, Linux)

J. David Boyd wrote:

> Michael Stutz <address <at> hidden> writes:
> 
> >
> > First, I'm still encountering the time error that has been reported
> > before (bug #29277): the time shows correctly in Emacs, but when posted
> > to WordPress it appears as four hours earlier.
> 
> 
> The fast way I've found to get around this is to remove the - from in
> front of the 0400 time zone value.
> 
> I noticed my time was off, so I started playing around, and removing the
> '-' gives me the correct time.

Are you sure it's the correct time? When I take out the dash the posts
are exactly 12 hours behind---so posting at 4pm (16:00) will give the
post a timestamp of 4am earlier that day (04:00). (Posting now at 10am
makes a post at 10pm last night.)

Taking out the -0400 altogether will set the time for 8 hours previous.

The way to set the correct time, at least for me, is to change it to
-0800. But that too has a problem---when I make a post with the time at
-0800 the post is always made at the current time, but it's listed as
"scheduled" for that time and it never appears in the blog. This happens
even if I first change the date to some time in the past!

Weblogger bugs (WordPress, Emacs 22, Linux)

I'm enjoying weblogger.el, which I'm using with WordPress, and would be
happy to volunteer with testing---I think a few tweaks could be easily
made (like supporting tags and categories) that would make it much more
practical to use.

I've also found a few bugs in the latest available files (weblogger.el
version 1.4.5 timestampped <2010-03-11 01:49:36 mah> and xml-rpc.el
version 1.6.9a). I sent a bug report about a week ago but also want to
send a mail here and describe what's going on:

First, I'm still encountering the time error that has been reported
before (bug #29277): the time shows correctly in Emacs, but when posted
to WordPress it appears as four hours earlier.

The other bug is that the body text is sent to Wordpress with soft
linefeeds. This doesn't work. What happens is that if you have Emacs set
up with a normal fill column (like 70), and auto-fill-mode as I imagine
most people do, your post buffer will look nice in Emacs, but when it
appears on WordPress the end of lines for each line will have been
treated like a hard carriage return, so the wordwrap will be off and
you'll have to go in (with the WordPress editor) and manually take out
every newline. The post text needs to be sent without any word wrap or
fill at all.

I saw this problem mentioned on
http://ciju.wordpress.com/2008/06/06/twiddling-with-webloggerel-emacs-wordpress/
but I tried applying his hooks and they didn't work. (What he does is
turn on longlines-mode before editing an entry, and then turns it off
before publishing it.)

How would you remove all soft newlines from the text of a buffer
before publishing it? That's the way to do it. I tried setting the fill
column to a value like 0, 99999, -1, but these did not work.

xml-rpc infinite loop

Hello Mark,

This call seems to loop forever:

  (xml-rpc-method-call "http://paste.pocoo.org/xmlrpc/" "pastes.getRecent" "4")

The returned http buffer contains the correct result but xml-rpc seems
to fail to parse it.

Leo

Re: I made weblogger-el to support Windows Live blog API

[Ccing emacsweblogs]

Haojun Bao <baohaojun <at> gmail.com> writes:

> First thanks for the great weblogger-el!

Your welcome.  I apologize for my late reply.

> I made some changes to weblogger.el and xml-rpc.el to make it support Windows
> Live blog, which is basically based on metaWeblog. Hope you find it
> useful.

Thank you.  Its because people like you test this out on different
platforms that I can continue to improve weblogger.el and xml-rpc.el.

>>> without these changes, the wrong APIs will be called, blogger.*
>>> instead of metaWeblog.*
>
>>> This patch is dirty, I think it will break blogger for
>>> metaWeblog. How can I make a better solution?

I note that the Windows Live weblogs have RSD headers that specify MetaWeblog.  The best way
would be to use RSD to determine what to do with a particular weblog.
Right now, it uses a MT-native call (mt.supportedMethods) to see what is
supported.  Obviously, if you implment MetaWeblog but mt, this will
fail.

Because of that, I'm not going to use the patch to weblogger.el.  But it
is clear that RSD should be my first priority for weblogger.el.

If you would like to try to tackle it (since I'm not sure when I will be
able to), I could help you out.

> -		      (when mt_keywords
> -			(cons "mt_keywords"   mt_keywords))
>>> This doesn't make sense, mt_keywords as a symbol is defined nowhere,
>>> and Elisp report error

Thanks for point this out.  Obviously I didn't test that.

>  <at>  <at>  -1456,9 +1454,9  <at>  <at> 
>  	   (cons "url"           (message-fetch-field "X-Url"))
>  	   (cons "title"     (or (message-fetch-field "Subject")
>  				 weblogger-default-title))
> -           (cons "categories" (vconcat (or (message-tokenize-header
> +           (cons "categories" (car (list (or (message-tokenize-header
>                                              (message-fetch-field "Keywords") ", ")
> -                                           weblogger-default-categories)))
> +                                           weblogger-default-categories))))
>
>>> From your latest xml-rpc, I guess you are trying to make xml-rpc
>>> array a real elisp vector here, right? but it's not working yet, so I
>>> made the above changes. 
>
>>> "categories" parameter need to be an array of strings, and from
>>> xml-rpc comments, an array in xml-rpc is a list, not a vector in
>>> Elisp.

Ok, I'm going to assume this is working and I'll use your patch here.

>  <at>  <at>  -567,8 +567,13  <at>  <at> 
>            (result nil))
>        (while l
>          ;; iterate
> -        (setq elem (car l)
> -              l (cdr l))
> +        (cond 
> +         ((listp l)
> +          (setq elem (car l)
> +                l (cdr l)))
> +         (t
> +          (setq elem l
> +                l nil)))
>
>>> Live Space will send xmlns attribute which is like (xmlns . "http://w3c/scheme")
>>> and it's not a list proper, so your old code will report error when
>>> (car "http://w3c/scheme")
>
>>> This fix is also dirty, because after this, what used to be (xmlns . "http://w3c/scheme")
>>> will change to (xmlns "http://w3c/scheme"), without the DOT in
>>> between. Hopefully it does not cause any harm. 

Hrm… I'm not sure about this.  It'll take some testing.

>  <at>  <at>  -609,7 +614,7  <at>  <at> 
>                             url-http-response-status 200))
>                 (result (cond
>                          ;; A probable XML response
> -                        ((looking-at "<\\?xml ")
> +                        ((looking-at "\\(\357\273\277\\)?<\\?xml ")
>
>>> Live Space is ``dirty'', it will send a utf-8 head \357\273\277
>>> (0xfeff or sth. like that) before the <?xml.
>
>>> I wonder if these (attributes and utf-8 header) are allowed by the
>>> xml-rpc spec, since other clients like blogtk has no issue supporting
>>> Live Space

This is probably a short-coming of Emacs HTTP support and this isn't the
right place to fix the problem.

Thanks for your contributions and putting effort into tracking this
down!

Mark.

--

-- 
http://hexmode.com/

Embrace Ignorance.  Just don't get too attached.