App-org2wp

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN

    work after some update. "org2wp" uses the same format as "org2blog", but
    instead of being an Emacs package, it is a CLI script written in Perl.

    First, create "~/org2wp.conf" containing the API credentials, e.g.:

     ; use INI (IOD) format for this file
     proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
     username=YOURUSERNAME
     password=YOURPASSWORD

    Note that "proxy" is the endpoint URL of your WordPress instance's
    XML-RPC server, which can be hosted on "wordpress.com" or on other
    server, including your own. It has nothing to do with HTTP/HTTPS proxy;
    the term "proxy" is used by the XMLRPC::Lite and SOAP::Lite Perl
    libraries and "org2wp" simply uses the same terminology.

    You can also put multiple credentials in the configuration file using
    profile sections, e.g.:

     ; use INI (IOD) format for this file
     [profile=blog1]

README  view on Meta::CPAN

        of certain level will be regarded as a single blog post.

    *   post_password => *str*

        Set password for posts.

    *   proxy* => *str*

        Example: C<https://YOURBLOGNAME.wordpress.com/xmlrpc.php>.

        Note that "proxy" is the endpoint URL of your WordPress instance's
        XML-RPC server, which can be hosted on "wordpress.com" or on other
        server, including your own. It has nothing to do with HTTP/HTTPS
        proxy; the term "proxy" is used by the XMLRPC::Lite and SOAP::Lite
        Perl libraries and "org2wp" simply uses the same terminology.

    *   publish => *bool*

        Whether to publish post or make it a draft.

        Equivalent to "--extra-attr post_status=published", while

lib/App/org2wp.pm  view on Meta::CPAN

work after some update. `org2wp` uses the same format as `org2blog`, but instead
of being an Emacs package, it is a CLI script written in Perl.

First, create `~/org2wp.conf` containing the API credentials, e.g.:

    ; use INI (IOD) format for this file
    proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
    username=YOURUSERNAME
    password=YOURPASSWORD

Note that `proxy` is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on `wordpress.com` or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the <pm:XMLRPC::Lite> and <pm:SOAP::Lite> Perl libraries and `org2wp` simply
uses the same terminology.

You can also put multiple credentials in the configuration file using profile
sections, e.g.:

    ; use INI (IOD) format for this file
    [profile=blog1]

lib/App/org2wp.pm  view on Meta::CPAN

_
    args => {
        proxy => {
            schema => 'str*', # XXX url
            req => 1,
            description => <<'_',

Example: `https://YOURBLOGNAME.wordpress.com/xmlrpc.php`.

Note that `proxy` is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on `wordpress.com` or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the <pm:XMLRPC::Lite> and <pm:SOAP::Lite> Perl libraries and `org2wp` simply
uses the same terminology.

_
            tags => ['credential'],
        },
        username => {
            schema => 'str*',

lib/App/org2wp.pm  view on Meta::CPAN

work after some update. C<org2wp> uses the same format as C<org2blog>, but instead
of being an Emacs package, it is a CLI script written in Perl.

First, create C<~/org2wp.conf> containing the API credentials, e.g.:

 ; use INI (IOD) format for this file
 proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
 username=YOURUSERNAME
 password=YOURPASSWORD

Note that C<proxy> is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on C<wordpress.com> or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the L<XMLRPC::Lite> and L<SOAP::Lite> Perl libraries and C<org2wp> simply
uses the same terminology.

You can also put multiple credentials in the configuration file using profile
sections, e.g.:

 ; use INI (IOD) format for this file
 [profile=blog1]

lib/App/org2wp.pm  view on Meta::CPAN

a single blog post.

=item * B<post_password> => I<str>

Set password for posts.

=item * B<proxy>* => I<str>

Example: CL<https://YOURBLOGNAME.wordpress.com/xmlrpc.php>.

Note that C<proxy> is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on C<wordpress.com> or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the L<XMLRPC::Lite> and L<SOAP::Lite> Perl libraries and C<org2wp> simply
uses the same terminology.

=item * B<publish> => I<bool>

Whether to publish post or make it a draft.

Equivalent to C<--extra-attr post_status=published>, while C<--no-publish> is

script/org2wp  view on Meta::CPAN

work after some update. C<org2wp> uses the same format as C<org2blog>, but instead
of being an Emacs package, it is a CLI script written in Perl.

First, create C<~/org2wp.conf> containing the API credentials, e.g.:

 ; use INI (IOD) format for this file
 proxy=https://YOURBLOGNAME.wordpress.com/xmlrpc.php
 username=YOURUSERNAME
 password=YOURPASSWORD

Note that C<proxy> is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on C<wordpress.com> or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the L<XMLRPC::Lite> and L<SOAP::Lite> Perl libraries and C<org2wp> simply
uses the same terminology.

You can also put multiple credentials in the configuration file using profile
sections, e.g.:

 ; use INI (IOD) format for this file
 [profile=blog1]

script/org2wp  view on Meta::CPAN

=item B<--help>, B<-h>, B<-?>

Display help message and exit.

=item B<--password>=I<s>*

=item B<--proxy>=I<s>*

Example: `https://YOURBLOGNAME.wordpress.com/xmlrpc.php`.

Note that `proxy` is the endpoint URL of your WordPress instance's XML-RPC
server, which can be hosted on `wordpress.com` or on other server, including
your own. It has nothing to do with HTTP/HTTPS proxy; the term "proxy" is used
by the <pm:XMLRPC::Lite> and <pm:SOAP::Lite> Perl libraries and `org2wp` simply
uses the same terminology.


=item B<--username>=I<s>*

=item B<--version>, B<-v>