Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter lrissman

    (@lrissman)

    Okay some more info… seems this is a bug introduced in wordpress 3.3. http://core.trac.wordpress.org/ticket/19722

    In essence I’ve been digging into the GUID stored for the post created for each of the image attachments. In short, if you upload via wordpress or Eazyest, the protocol you are using in the admin panel at the time of the upload (or discovery in the case of Easyest) is stored in the GUID for that post (attachment).

    Ie, HTTP/HTTPs.

    Now, it seems that wordpress does a bit of a substitution if you load up the thumbnail/attachment from a http session when uploaded with HTTPS (or vice versa) and then puts in the incorrect path.

    I am going to test a few theories for workarounds as I cant imagine using wordpress without at least SSL login (to prevent cleartext password transmission).

    Thread Starter lrissman

    (@lrissman)

    Okay, I know I said I wouldnt troubleshoot further but I hit the next hurdle and found some more interesting information.

    Here goes, I replaced WordPress HTTPS Plugin with this guide: http://codex.wordpress.org/Administration_Over_SSL
    (In essence add define('FORCE_SSL_ADMIN', true); to your wp-config.php).

    Now here is the crux.
    If the photos are discovered via a HTTPS admin session, they are viewable if you view the page with HTTPS, Not HTTP.

    If the photos are discovered via a HTTP admin session, they are viewable if you view the page with HTTP, not HTTPs.

    So, clearly there is an issue with the discovery script in Eazyest Gallary and storing paths for only HTTP or HTTPs. And seems that when you access the page via the other protocol, it defaults to wp-content/upload instead of what it should be.

    Oups…

    Thread Starter lrissman

    (@lrissman)

    Okay.. so i reinstalled from scratch… backup, install, test, restore, backup install test restore… Exciting day… but fruitful.

    So… situation:
    1) install clean wordpress 3.6.1.
    2) install Eazyest Gallery
    3) create folder
    4) add photo to folder using wordpress/Eazyest Gallery
    —-
    at this point we are clean and working fine
    —-
    5)Install WordPress HTTPS plugin
    6)Activate plugin
    7)Enable “Force SSL Administration” in HTTPS Plugin
    —-
    At this point we are now broken
    —-
    8) click on Eazyest Gallery in the admin panel
    9) Eazyest Gallery will now scan for new pictures and find an additional duplicate and identify it as missing. And add it with a file-last-modify date instead of the upload date. Details of that photo show the same path as the original, but when viewed through the page, the path is wrong as in my first post.

    ——
    At this point I will backup my install, start fresh and find a replacement for the plugin “WordPress HTTPS” and I don’t intend to debug further unless I come to another problem. If somebody would like to debug more, let me know and i can spin up an instance.

    Not resolved, but at least repeatable and avoidable.

    Not 100% in my quick testing. It displays photos just fine; however, if you click the gallery link, it tries to open it as a photo then closes itself. If you click the gallery link again, it opens to the page showing your folders.

    So, close, but not quite 100%.

Viewing 4 replies - 1 through 4 (of 4 total)