Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • resolved. our particular problem was pretty basic: modified wp-config.php changing this line from true to false:

    define(‘DISALLOW_FILE_MODS’,false);

    was this resolved? We have just done a new install and while default site functions and can login w/ our initial (administrator role) account, we have no “Add new” buttons on the plugin or theme admin pages. Is there something we have missed in terms of file permissions, etc.

    Thread Starter elink

    (@elink)

    Okay – got new release. The {+exif:Subject+} gives me what I need. Thanks much. Consider closed.

    See the second tab (“ARSLS Program”) at this location.

    I included some variants to see result of href. I could never get the {+xmp:subject+} to give me what I needed.

    The challenge is getting consistency in the source application that is doing the jpg meta data (reminds me of tannenbaum – “the great thing about standard is there are so many to choose from”)

    Thread Starter elink

    (@elink)

    Thanks. Problems solved. But then I decided to change approach – namely want all needed info stored in originating (JPG) meta data rather than using admin menus to set values — and this of course has led to more confusion.

    I wrote a simple program to invoke the exif_read_data (based on manual example) on my image file (e.g. phone, radio image in prior post url). The output is:

    /opt/wordpress/wp-content/uploads/products-radio.jpg:<br />
    Image contains headers<br />
    FILE.FileName: products-radio.jpg<br />
    FILE.FileDateTime: 1483725849<br />
    FILE.FileSize: 12460<br />
    FILE.FileType: 2<br />
    FILE.MimeType: image/jpeg<br />
    FILE.SectionsFound: ANY_TAG, IFD0, THUMBNAIL, EXIF, WINXP<br />
    COMPUTED.html: width="141" height="130"<br />
    COMPUTED.Height: 130<br />
    COMPUTED.Width: 141<br />
    COMPUTED.IsColor: 1<br />
    COMPUTED.ByteOrderMotorola: 1<br />
    COMPUTED.UserComment: bullhorn<br />
    COMPUTED.UserCommentEncoding: ASCII<br />
    COMPUTED.Thumbnail.FileType: 2<br />
    COMPUTED.Thumbnail.MimeType: image/jpeg<br />
    IFD0.ImageDescription: 2<br />
    IFD0.Software: www.inkscape.org<br />
    IFD0.PixelUnit: <br />
    IFD0.PixelPerUnitX: 1128<br />
    IFD0.PixelPerUnitY: 1128<br />
    IFD0.Exif_IFD_Pointer: 2230<br />
    IFD0.Title: Radio<br />
    IFD0.Keywords: products<br />
    IFD0.Subject: radio<br />
    IFD0.UndefinedTag:0xEA1C: <br />
    THUMBNAIL.Compression: 6<br />
    THUMBNAIL.JPEGInterchangeFormat: 4378<br />
    THUMBNAIL.JPEGInterchangeFormatLength: 1687<br />
    EXIF.UserComment: ASCIIbullhorn<br />
    EXIF.UndefinedTag:0xEA1C: <br />
    WINXP.Title: ?????<br />
    WINXP.Keywords: ????????<br />
    WINXP.Subject: ?????<br />
    

    From above I want to map :

    IFD0.Title: Radio<br /> –> to title query argument in my href string
    IFD0.Subject: radio<br /> –> to pageslug query argument in my href string
    COMPUTED.UserComment: bullhorn<br /> –> to icon query argument in my href string
    IFD0.ImageDescription: 2<br /> –> for image order in the gallery.

    I have tried various mappings and shortcode arguments (am invoking via do_shortcode within my custom page.php script) and haven’t succeeded in getting example (radio) title,icon, and order mapping correctly. Here is latest incarnation:
    [mla_gallery attachment_tag="products" orderby={+exif:ImageDescription+} order=ASC mla_link_href="{+site_url+}/?pageslug={+slug+}&parent=products&title={+exif:Title+}&icon={+image_alt+}" columns=5 mla_margin=0.25%]
    with the following mapping:
    meta mapping

    Thread Starter elink

    (@elink)

    the original query string used single letter keywords, e.g., ?s=XXX&y=WWW&t=MMM When I changed the (all?) keywords to something more verbose (parent=XXX) then it worked. wonder why?

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