You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Trying to use static files like in 2.x and it appears the static file field is not showing, as well as the tabs not working for settings, resource groups, etc. So I can't revert the resource type back to anything else.
Step to reproduce
Make a new static resource.
Observed behavior
Expected behavior
We should see a static resource file path, and the ability to change tabs. I looked into the html and they are not rendered at all, so it's likely not that the tabs don't work, but that they have nothing to show.
Environment
MODX Cloud - MODX 3.0.4 , FRED (latest) , some light manager customization.
The text was updated successfully, but these errors were encountered:
neoneddy
added
the
bug
The issue in the code or project, which should be addressed.
label
Jan 11, 2024
I can't reproduce this issue with a clean installation of MODX 3.0.4.
Probably the manager customization or an installed extra causes the issue.
Can you try to figure out, what exactly breaks the UI?
So I can't revert the resource type back to anything else.
Try changing it directly in the database. In the Table modx_site_content, set the column class_key back to MODX\Revolution\modDocument.
Bug report
Summary
Trying to use static files like in 2.x and it appears the static file field is not showing, as well as the tabs not working for settings, resource groups, etc. So I can't revert the resource type back to anything else.
Step to reproduce
Make a new static resource.
Observed behavior
Expected behavior
We should see a static resource file path, and the ability to change tabs. I looked into the html and they are not rendered at all, so it's likely not that the tabs don't work, but that they have nothing to show.
Environment
MODX Cloud - MODX 3.0.4 , FRED (latest) , some light manager customization.
The text was updated successfully, but these errors were encountered: