App-org2wp
3 results

 view release on metacpan or  search on metacpan

README  view on Meta::CPAN 

19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
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 

178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
    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 

31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
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 

156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
 
_
    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 

703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
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 

867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
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 

53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
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 

390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
=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>



( run in 1.268 second using v1.01-cache-2.11-cpan-49f99fa48dc )