Forum Replies Created

Viewing 9 replies - 1 through 9 (of 9 total)
  • There’s one that is called, I think, Enable Media Replace that I use on https://dancinglight.photos

    MLA is a real powerhouse, but it won’t touch things outside its own domain. Of course, with WP, it’s often hard to tell where to look to accomplish something.

    Hey, sh^t happens! I find Mr Lindgren’s stuff to be quite well thought out, it’s the overwhelming amount of functionality that I usually fail to understand. I think I’ve barely scratched the surface, myself. I only found 1 actual bug, which was quite subtle, all other errors have been operator errors on my part. Plus, his support is surreal (I mean that in a good way!)

    Thread Starter wesm

    (@wesm)

    Ah, OK, Thanks. So I should use the title, i.e., the “friendly name” for the term, not the slug. I used the slug because I read elsewhere that that was what WP used for matching, but I don’t recall if it was taxonomy, custom fields, or what.

    Do you mention this fact in the doc somewhere? Possible I missed it, but the doc is huge (and sort of dense).

    I see there is a delimiters field in the Taxonomy term mapping. I assume that is so you can specify multiple terms, e.g., “night,urban”. My suggestion about the path was that you introduce an optional path delimiter for hierarchical terms. Of course, that would complicate the database query, not so nice for doing tree- or graph-based searches.

    Thread Starter wesm

    (@wesm)

    Here is the mapping, in the EXIF/Template Value field of the Edit Rule dialog:
    template:([+xmp:Iptc4xmpCore.IntellectualGenre+])

    It’s the same image as earlier, here, and the caption dump technique shows a genre of astrophotography.

    When I list my “Genre” taxonomy on the dashboard, I see terms:
    Name Slug
    astrophotography astrophotography-2
    Night night
    — Astro Photography astrophotography

    The first one in the list shouldn’t be there, it wasn’t before I executed the rule, which I did by clicking the “Execute” link under the rule in the rule table.

    As far as proper scope, I note that Attachment Category is a hierarchical taxonomy 🙂

    • This reply was modified 8 years, 4 months ago by wesm.
    • This reply was modified 8 years, 4 months ago by wesm.
    Thread Starter wesm

    (@wesm)

    Well, actually it didn’t match terms in the incoming images to a predefined hierarchical term; it created the same term at the top level, assigning it a different slug. Specifically, I had created the genre taxonomy, a top-level term called “night” and a child term of night called “astrophotography”. The incoming image was tagged with “astrophotography” for the genre. MLA created the top-level “astrophotography” term. I executed the rule from the dashboard, not on image upload, although I wouldn’t imagine that would make a difference. So this seems like a bug to me.

    What would be interesting would be able to define a path, like night/astrophotography in the xmp metadata, and have that match to the nested child term. That way, I could have the same term appear in different hierarchies.

    • This reply was modified 8 years, 4 months ago by wesm.
    Thread Starter wesm

    (@wesm)

    Follow up: I figured out that my new taxonomies show up in the list box on the right-hand column under the IPTC/EXIF tab, so I could edit the rule there.

    And running the rule does create new terms, as desired.

    However, it misses hierarchical terms, and assigns them as top level terms.

    Is there a workaround for this? Is there a way I can tag the original image to preserve hierarchy in taxonomies?

    Thanks!!

    Thread Starter wesm

    (@wesm)

    Yes, thanks, that was a typo. I meant xmp:Iptc4xmpExt.LocationCreated.0.Sublocation
    Close this ticket if you like.

    Thread Starter wesm

    (@wesm)

    Followup: {+xmp:Iptc4xmpCore.0.Sublocation+} does what I want …. anonymous nested structure, I guess. PHP is so un-wonderful.

    Thread Starter wesm

    (@wesm)

    Cool. I solved some of this puzzle by doing your caption trick with this magic key:
    [mla_gallery attachment_tag=”Panoche” mla_caption=”{+xmp:Iptc4xmpCore.IntellectualGenre+}”]. Found the “magic” key by looking at the Photoshop raw data panel of the File Info.

    Here’s a link to the published image … this is my “junk” site where I do experiments, so nothing is organized 🙂
    Image

    Hosting page:
    Page

    However, I am having difficulty getting access to fields inside structured data, such as LocationCreated … The ‘.’ notation isn’t working, and when I look at the raw xmp data in photoshop, I see one or more subcontainers around the fields I want to access.

    Wes

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