We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 9207 ☆ A M B ☆
    • 2,475 Posts
    What’s the purpose of having content types and content dispositions for WebLinks? Does changing these settings actually affect anything? E.g. saying http://google.com/ is a download doesn’t make it suddenly downloadable. Are there plans to simplify the manager page for this? As it is, methinks it is confusing to users to have excessive controls on that form that essentially do nothing.

    I think this starts driving at similar conversations re "Resource Types" where there could be custom icons and custom manager pages for each type of resource...
      • 17499 ☆ A M B ☆
      • 872 Posts
      I second that.

      Today, one of my coworker demoed me a WP extension called magicfields that allows the exact same behaviour as modx TVs, but also allowed to create in 2 clicks custom page/post type, with custom view (table listing or direct edit for single page) and unlimited custom fields...

      If the fields side is already covered by MODx, i have to say that custom UI easy definable is huge plus on the side of WP. And the fact that not even one line of code was necessary to actually have the UI working on the admin side is quite powerful.

      Custom Resource Type + TV attached to specific Resource Type instead of TV can bring MODx to the next level.
        • 9207 ☆ A M B ☆
        • 2,475 Posts
        I agree... WP’s architecture is so simplistic, and it might ugly to customize certain areas of the manager with it, but at least it’s possible.

        I think I’ve mentioned this already to you, lossendae, but my Custom Content Type Manager plugin for WordPress does most of what Magic Fields does and more:
        http://code.google.com/p/wordpress-custom-content-type-manager/

        MODx has the solid architecture to support this type of manager customization, so I’d love to see it implemented and made more easily customizable, related to this feature request:
        http://bugs.modx.com/issues/4842