Forum Replies Created

Viewing 15 replies - 16 through 30 (of 118 total)
  • Plugin Author Norbert

    (@norbusan)

    Good to hear, so I can mark the topic as resolved. Thanks for coming back.

    Plugin Author Norbert

    (@norbusan)

    Thanks a lot!

    Plugin Author Norbert

    (@norbusan)

    Hi,

    I am really surprised about all that. I have added new debug code to PiwigoPress_get.php and I see the following DEBUG output in the source code:

    <!-- DEBUG pwg_get_contents: calling wp_remote_get fullurl = https://laneb.re/photos/ws.php?method=pwg.images.getInfo&format=php&image_id=2395 -->
    <!-- DEBUG long output of json from your server -->
    <!-- DEBUG pwg_get_contents: calling wp_remote_get fullurl = https://laneb.re/photos/ws.php?method=pwg.images.getInfo&format=php&image_id=2390 -->
    <!-- DEBUG again long output of json from your server -->
    <!-- DEBUG pwg_get_contents: calling wp_remote_get fullurl = https://laneb.re/photos/ws.php?method=pwg.images.getInfo&format=php&image_id=2398 -->
    <!-- DEBUG <html>
    <head><title>503 Saturation Requetes</title></head>
    <body bgcolor="white"> ...

    That means that the first and second request worked, but not the third.

    I am using nothing else but WordPress’ builtin wp_remote_get($fullurl); so I would be surprised that something is wrong here.

    I cannot do anything more than that, something on your server side is blocking the requests.

    Plugin Author Norbert

    (@norbusan)

    The problem is again the rate limiting. But since the HTML code is generated on your server, the rate limiting is surprising.

    It is definitely not a problem in piwigopress.

    I can only see two possible sources of the problem:

    * You are blocking/rate limiting access from *your*own* server. In this case you need to fix the blocking.

    * The other idea I have is a caching system (keeping pre-generated hmtl pages to speed up delivery). In this case, if the caching was done of a bad html page, no new one will be generated.

    Did you start using some caching system recently?

    Can you verify that the server that generates the HTML code (i.e., running the wordpress installation), has *unlimited* access to the photo site?

    Norbert

    Plugin Author Norbert

    (@norbusan)

    Bummer, that was rubbish and broke the site. Please get a new version from github, or remove one of the two dots in the “..”, that should have been only “.” (two times) (mixing lua with php, bad).

    Sorry, thanks.

    Norbert

    Plugin Author Norbert

    (@norbusan)

    Hmm, I think just allowing me to access your site will not fix anything. Every client watching your blog site will be hit by the rate limit.

    Are you limiting the access to all pages, or only to some?s

    Can you *again* download the piwigopress.php from the github site and replace it on your server. I have now added DEBUG statements (printed in the *SOURCE* only via <!-- DEBUG ... ->) that should help.

    Thank

    Plugin Author Norbert

    (@norbusan)

    Ok, found the reason. THere seems to be a rate limiting going on on your site.

    When debugging the response I see:

    <html>
    <head><title>503 Saturation Requetes</title></head>
    <body bgcolor="white">
    <center><h1>Saturation Temporaire</h1></center>
    <center>Si vous etes le webmaster du site concerne, merci de contacter le support technique de votre hebergeur.</center>
    <center>Il semble qu'un probleme technique individuel au contenu que vous hebergez existe.</center>
    <hr><center>Serveur Web</center>
    </body>
    </html>

    So this is a problem with your web server rate-limiting the access I guess. Can you disable this? At least when it comes from your site?

    Norbert

    Plugin Author Norbert

    (@norbusan)

    Ok, I can reproduce this here with

    [PiwigoPress id=2398 url='https://laneb.re/photos/' class="img-shadow" lnktype='none']

    I get a warning: Notice: unserialize(): Error at offset 0 of 409 bytes in /home/norbert/Debian/Piwigo/piwigopress.git/piwigopress.php on line 122

    I will investigate, but I am currently on a business trip with intermittent internet connection. I will try to find out the reason.

    Thanks

    Plugin Author Norbert

    (@norbusan)

    Can you please send me the text of the used shortcodes. There seems to be a problem in the generation. The source code cotains several

    <div id="Photo-2395-la" class="PiwigoPress_photoblog"><!-- PiwigoPress Started --></div><!-- PiwigoPress Ended -->

    Can you please get the following piwigopress.php from https://raw.githubusercontent.com/norbusan/piwigopress/master/piwigopress.php and (after making a backup) replace yours with that one. It should print some debugs.

    The problem is that $response = pwg_get_contents( $url . 'ws.php?method=pwg.images.getInfo&format=php&image_id=' . $id); does return some kind of error.

    Thanks

    Plugin Author Norbert

    (@norbusan)

    Interesting. Especially the case that within the actual post only one or two images are shown.

    Can you check the server logs for some error messages? This is purely a PHP thingy, since the shortcodes are expanded on the server.

    Can you also check the generated *source* code (html). There are normally some code surrounding the images.

    Please send me a link to a blog entry where there should be at least 3 or more photos, and where at the moment only 1/2 are shown.

    Thanks

    Plugin Author Norbert

    (@norbusan)

    Hi Christopher,

    thanks for the screenshot and the information, but could you provide an example shortcode that I can try out to see what is going on?

    Is your theme a home-made or publicly available?

    Thanks

    Norbert

    Plugin Author Norbert

    (@norbusan)

    Seems that this is resolved.

    Plugin Author Norbert

    (@norbusan)

    I have released a new version 0.3 that allows for parsing of all kind of lat, lon formats, practically everything that is halfway decent.

    Please try 0.3 and see if that works for you.

    Thanks

    Plugin Author Norbert

    (@norbusan)

    Hi Matt,

    I will see that I can adapt the code to support the conversion, too.

    All the best

    Norbert

    Plugin Author Norbert

    (@norbusan)

    Indeed, it seems the documentation needs changing. The Google location coder is used, and it returns for your location “N50°19 43.91, W004°11 41.78” the wrong position. Try it out at: https://developers.google.com/maps/documentation/javascript/examples/geocoding-simple

    The problem is that the google geocoder does not support DMS format, and so geocoding it generates slightly wrong results.

    For reference see https://stackoverflow.com/questions/18793273/gps-coordinates-and-google-api-v3

    I have opened an issue (bug report) at the github package of the project to remind me either to fix the documentation, or manually convert DMS format to decimal, see:
    https://github.com/norbusan/slick-google-map-plugin/issues/9

    For now I recommend feeding in decimal coordinates.

    Hope that helps

    Norbert

Viewing 15 replies - 16 through 30 (of 118 total)