• Resolved seanalansnyder

    (@seanalansnyder)


    I’m using PostX Pro to add Category Image and Category Color, which adds 2 custom meta values (ultp_category_image, ultp_category_color) to any Taxonomy for-which it is enabled. Having PMDM enabled for that same Taxonomy prevents the display/GUI for editing these PostX meta values from working properly.

    I don’t know if the problem is PostX or PMDM.

    Steps to replicate:

    1. Install both PostX Pro and PMDM.
    2. Activate PMDM, then go into PMDM Settings.
    3. Enable the checkbox for all Taxonomies (or at least the Taxonomy you will be using to test)
    4. In PostX Settings > Taxonomy Image & Color, make sure those same taxonomies you enabled in PMDM Settings are also enabled for Image.
    5. Edit a Taxonomy Term, Attempt to change Taxonomy Image, then Save/Update.
      • You will see that your image change has NOT taken effect.
    6. GO into PMDM Settings again, UNcheck the checkbox next to that taxonomy you are using?for testing.
    7. Edit that same Taxonomy Term, change Taxonomy Image, then Save/Update.
      • You will see that your image change has been properly?retained.

    My guess is that PMDM is overwriting whatever image setting is set using the PostX Add/Remove Image buttons with the OLD value when I save/Update that Taxonomy. even though I haven’t edit any of the PMDM Terms within the Term Metadata Manager panel itself. I’ve suggested to PostX developers to force a full page reload (instead of relying on Ajax partial rewrite of page) to force PMDM to read new values, but I’m not sure if that is THE right solution.

    Is there a way to have PMDM’s metadata values take precedence ONLY if they were actually edited using PMDM’s Term Metadata Manager “edit/delete” functions?

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WpExpertPlugins

    (@gandhihitesh9)

    Hello?@seanalansnyder

    Thanks for the reporting the issue.

    We will defiantly look into that and let you know.

    Best Regards,
    WpExpertPlugins

    Plugin Author WpExpertPlugins

    (@gandhihitesh9)

    Hello @seanalansnyder

    We have resolved the issue. Please update the plugin and test it. If the issue persists, let us know.

    Best Regards,
    WpExpertPlugins

    Thread Starter seanalansnyder

    (@seanalansnyder)

    Thanks!
    I’ve just updated and confirmed that v1.4.0 of PMDM appears to have resolved the issue.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.