Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable all fields to be moved to any manager tab/panel using form customization #16701

Open
SnowCreative opened this issue Feb 3, 2025 · 3 comments
Labels
feature Request about implementing a brand new function or possibility.

Comments

@SnowCreative
Copy link
Contributor

Feature request

Summary

Currently, only TVs can be moved into any editing panel using form customization. Standard fields are fixed to particular tabs/panels.

Why is it needed?

This limits the flexibility of designing custom editing interfaces.

Suggested solution(s)

Set up the standard fields just like TVs in form customization, so that a specific tab and order can be assigned.

I'm sure this is a big request, requiring significant updating to the code, but it sure would enhance the "creative freedom" of MODX!

@SnowCreative SnowCreative added the feature Request about implementing a brand new function or possibility. label Feb 3, 2025
@modxcommunity
Copy link
Collaborator

This issue has been mentioned on MODX Community. There might be relevant details there:

https://community.modx.com/t/resource-edit-panel-how-to-move-fields-from-one-region-to-another/8287/2

@SnowCreative SnowCreative changed the title Enable all fields to be moved to any panel using form customization Enable all fields to be moved to any manager tab/panel using form customization Feb 3, 2025
@smg6511
Copy link
Collaborator

smg6511 commented Feb 3, 2025

@SnowCreative - Hey Michael - Totally agree that this would be great. It is, however, unlikely to happen until the next-gen MODX is developed. This will likely involve a major re-write of the back end (especially if it moves to a REST or other architecture) and definitely a new front end. Ext JS will almost certainly be out, unless Sencha does a complete 180 on their licensing policies. Even if they did, I suspect folks might prefer moving to a declarative framework (such as React) instead of the more imperative, config-based Ext JS.

There's a lot of hating on Ext, but there's something to be said for 2011-12 tech (the ancient 3.4 version we're stuck with) that still manages to run our front end here in 2025 without too many issues (issues directly a result of the framework and not of our usage of it).

@SnowCreative
Copy link
Contributor Author

I figured that might be the case. Sadly, I expect it will be many years before any next-gen version is developed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Request about implementing a brand new function or possibility.
Projects
None yet
Development

No branches or pull requests

3 participants