WordPress.org

Support

Support » Plugins and Hacks » [Resolved] [Plugin: WPGPlus] Failing for German users

[Resolved] [Plugin: WPGPlus] Failing for German users

  • Received comments on Google+ that this is failing for German users.

    Warnings being thrown:

    Warning: DOMDocument::loadHTML() [domdocument.loadhtml]: htmlParseEntityRef: expecting ';' in Entity, line: 60 in ..../wordpress/wp-content/plugins/wpgplus/gplus.php on line 72
    
    Warning: DOMDocument::loadHTML() [domdocument.loadhtml]: htmlParseEntityRef: expecting ';' in Entity, line: 60 in ....wordpress/wp-content/plugins/wpgplus/gplus.php on line 72
    
    Warning: DOMDocument::loadHTML() [domdocument.loadhtml]: htmlParseEntityRef: expecting ';' in Entity, line: 60 in ..../blog/wordpress/wp-content/plugins/wpgplus/gplus.php on line 72
    
    Warning: DOMDocument::loadHTML() [domdocument.loadhtml]: Input is not proper UTF-8, indicate encoding ! in Entity, line: 64 in ..../blog/wordpress/wp-content/plugins/wpgplus/gplus.php on line 72
    
    Warning: DOMDocument::loadXML() [domdocument.loadxml]: Input is not proper UTF-8, indicate encoding ! Bytes: 0xC4 0x6E 0x64 0x65 in Entity, line: 1 in ..../blog/wordpress/wp-content/plugins/wpgplus/gplus.php on line 139
    
    Warning: Cannot modify header information - headers already sent by (output started at ..../blog/wordpress/wp-content/plugins/wpgplus/gplus.php:55) in ..../blog/wordpress/wp-includes/pluggable.php on line 866

    Maybe an issue with how Google+ gets encoded in German? Some other characters in the stream which make the xml loading fail?

    http://wordpress.org/extend/plugins/wpgplus/

Viewing 15 replies - 16 through 30 (of 65 total)
  • John: The cookies file is not updating with new test posts I’m publishing.

    Plugin Author John Eckman

    @johneckman

    @ari and @herb37

    Is the cookies.txt in the wpgplus directory zero length, or does it have a size?

    I just release a 0.7 version with more debugging in it, but I think the issue may be with permissions on the cookies.txt file – delete the one that came with the plugin and it should create a new one next time you publish something.

    Huh? If I delete the cookies file (which did have text in it) and publish a new post, a cookies file is not auto created.

    Plugin Author John Eckman

    @johneckman

    Well that’s a problem.

    wpgplus uses cURL and needs to be able to write to and read from the cookie.

    I can look at trying to change how the cookie file gets created.

    In the meanwhile, can you create a blank cookies.txt and set its permissions to 644?

    Plugin Author John Eckman

    @johneckman

    ari – what does your debug.txt say after you delete the cookies file and then try to publish again?

    @john,
    I have created a blank cookies.txt and set the permission to 644.
    After publishing a post, there is a cookies.txt with a lot of text and figures.

    The debug.txt now has more content than this morming (using the developer version).
    But nothing is published to G+

    Herb and I are in the same boat.

    If I delete cookies.txt, then recreate it and set permission to 644, then publish a post, the cookies file is populated from libcurl but nothing is published to G+.

    Debug file is updated with:

    2012-02-19 00:47:59 : publish_to_gplus running, included wpgplus.php
    2012-02-19 00:47:59 : publish_to_gplus running, postID is 7874
    2012-02-19 00:47:59 : wgplus_safe_post_google running, post_url
    2012-02-19 00:47:59 : wgplus_safe_post_google running, username is xxx
    password is yyy
    2012-02-19 00:48:01 : wgplus_safe_post_google running,  past log in
    2012-02-19 00:48:04 : wgplus_safe_post_google running,  past update
    2012-02-19 00:48:04 : publish_to_gplus done running

    Does the debug file also need to be perm 644? It’s 604 right now.

    @ ariherzog,
    I guess we have the same problem.
    Starting with a clean cookies.txt I got:

    # Netscape HTTP Cookie File
    # http://www.netscape.com/newsref/std/cookie_spec.html
    # This file was generated by libcurl! Edit at your own risk.

    .m.google.com TRUE /app/plus TRUE 631152000 MEX EXPIRED
    accounts.google.com FALSE / TRUE 1392695430 GAPS 1:ukBLWL_POMsBzlY8qG_sG9QQrMzuoQ:zJLJ7j7hDIgmqfEv
    accounts.google.com FALSE / TRUE 0 GALX vKWrnjy9Ztk
    .google.com TRUE / FALSE 1345434630 NID 56=0asdB_oWFfOfR-c4mC4z08lKAzqdH4sc69XnIdGUkNs5Xa1VKSpUKbg8a5oesJpQN4Xpdoo2DUHg29QTRYlfWekXrNyrx-FZ-cPeKRN5QfYCcWVSjwh0dcEGh2D1mewK5TfRwhyK3SLA5I6WTI2h3kcOoK3aOws
    .google.com TRUE / FALSE 0 SID DQAAANAAAAD8Ht8QK9Zz0aaUbYtfuuRqpaeMZJqIFUyL2IAyQZNwgMO2y50jMQDYWmH6GvguM_dUyKMGKPQAB6vJDIIKKn7uj9IfvBjErRUrwxuD4sB5i3ZFaYkwGwKw_IuWrICZzd6hGTi48687o4tq0IClXg0dUpGK67UjJRnDBRbMt3IYKNAysyzDe6fEaHUyo8Yv_P8ZpBYjxuGoamx9U-D1WB-t7X0mejriNheonh2kiWo4OnyAttsZnEe55Af6EkwkuBFEbyH_g7r8hj6d2gME4POc
    accounts.google.com FALSE / FALSE 0 LSID s.DE:DQAAANIAAAABFOntCufs411AMUfrUVI8eT9_X3nhA9s2ZbNYGNBef3I3PF7YEZskHtJTvTZsqsUfxnwUhEGEBGUbUVg7vag7nMHhBF9ltmXQ_A3WuJvFLP1jQprBfpWoz2D0FfQrI0Ud1lhL3gN-vpiNxb7OmWRKyJN0rHWXihIPxJexG94VLaEwOwieyYysHsJybydFrLDoxD072G88tLHQcogEYl9nlF3OCme0odIdJaiiZFvJ2_iJt8TMbTX2xOEp0urC4ntwHmw1LDNcbmaRwlCMFbGXyCew1_XtyeWB16EpVjVTTw
    .google.com TRUE / FALSE 0 HSID Att_mzo_8Zq-AIYeI
    .google.com TRUE / TRUE 0 SSID AXgz5bXqhB0C4YME9
    .google.com TRUE / FALSE 0 APISID QLlingzyeifjdufs/ASf7XwmoMr4wmYs_3
    .google.com TRUE / TRUE 0 SAPISID sLVhZ4_fYyb1TQLy/A9_Af2jFopCFLziv7

    and for the debug.txt

    2012-02-19 03:50:29 : publish_to_gplus running, included wpgplus.php
    2012-02-19 03:50:29 : publish_to_gplus running, postID is 131
    2012-02-19 03:50:29 : wgplus_safe_post_google running, post_id is 131
    2012-02-19 03:50:29 : wgplus_safe_post_google running, username is schmidt.herb@googlemail.com
    password is xxxxxxx
    2012-02-19 03:50:30 : login data posted
    2012-02-19 03:50:30 : status code was 200
    2012-02-19 03:50:30 : wgplus_safe_post_google running, past log in
    2012-02-19 03:50:35 : Getting form for posting
    2012-02-19 03:50:36 : Got form, status was 200
    2012-02-19 03:50:36 : and base url is https://m.google.com/app/plus/x/qg1ric49ghcp/
    2012-02-19 03:50:37 : Posted form, status was 200
    2012-02-19 03:50:42 : wgplus_safe_post_google running, past update
    2012-02-19 03:50:42 : publish_to_gplus done running

    Both files have the permission 644

    Nothing was published to G+

    Plugin Author John Eckman

    @johneckman

    So the cookie looks good, and so long as the cookies are getting text filled in then the permissions are ok. (The permissions being wrong would prevent any text from being added to the cookie).

    However, I’m still not seeing any specific error in the debug logs.

    @ari – your debug log posted above is from the older version – can you update to 0.7 and try another post?

    @herb37 – the statuc codes it is showing are 200, meaning “OK” – in other words, no error.

    I was hoping we’d see some other statuses, which would tell us something else was wrong – but I’m not seeing any.

    Are you entering something in the “Message for Google+ post: (use google+ markup)” box before you publish?

    Are you writing posts in the regular post edit screen?

    I’ve just checked in another development version newer that 0.7 – which outputs the whole response from Google+ to the form post – this one will create a much larger debug file, but should help us solve this mystery.

    Please do get the development version from wordpress.org/extend/plugins/wpgplus/download/ and install it, and share the debug output with me.

    (If you don’t want to post it publically here, as it might contain sensitive info, you can email it to me – eckman.john -at- gmail.com.

    @john,
    I am writing the posts in the regular post edit screen, without enabling the Wysywig-editor.

    I didn’t enter something in the “Message Box”.
    Regards
    Herbert

    @john,
    I have sent an eMail via gmail to You.
    Herb

    Plugin Author John Eckman

    @johneckman

    Herbert – the new development version (newer than 0.7) does more debugging, including capturing what post-text it is trying to post.

    Since we’re getting 200 OK status codes, looking at what is actually being posted and the full response from Google is the only way to try to find out what is happening.

    I upgraded to 0.7. Same as before: Post publishes, but no publish on G+. (I assume it should be automatic.)

    Debug data:

    2012-02-19 17:37:26 : publish_to_gplus running, included wpgplus.php
    2012-02-19 17:37:26 : publish_to_gplus running, postID is 7881
    2012-02-19 17:37:26 : wgplus_safe_post_google running, post_id is 7881
    2012-02-19 17:37:26 : wgplus_safe_post_google running, username is xxx
    password is yyy
    2012-02-19 17:37:30 : login data posted
    2012-02-19 17:37:30 : status code was 200
    2012-02-19 17:37:30 : wgplus_safe_post_google running,  past log in
    2012-02-19 17:37:35 : Getting form for posting
    2012-02-19 17:37:36 : Got form, status was 200
    2012-02-19 17:37:36 : and base url is https://m.google.com/ServiceLogin
    2012-02-19 17:37:37 : Posted form, status was 404
    2012-02-19 17:37:42 : wgplus_safe_post_google running,  past update
    2012-02-19 17:37:42 : publish_to_gplus done running
Viewing 15 replies - 16 through 30 (of 65 total)
  • The topic ‘[Resolved] [Plugin: WPGPlus] Failing for German users’ is closed to new replies.