-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
[Feature request] For Views, Move the Photo/Icon assignment to View Management #1724
Comments
Needs sponsoring, so added to #2107 and will close unless someone contributes or sponsors this. |
We're reopening because new features in 12.02 would benefit from this. |
iJungleboy
added a commit
to 2sic/2sxc-docs
that referenced
this issue
May 28, 2021
iJungleboy
added a commit
that referenced
this issue
May 28, 2021
It's now implemented that you can
|
Note: also related to #2430 |
Is it still only PNG or will it detect JPG too? |
Any pic should work. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
[x] feature request
[x] edit experience / UI
[x] admin experience UI
Current behavior
To assign an icon/image to a View, right now you create a PNG and name it identical to the .cshtml file. This causes the icon/image to show automatically in the Change Template (View) UI.
Desired behavior
When in Admin/Views and editing the view, you should be able to use the well-established 2sxc pattern of having a field for this and adding/assign an image to use as the icon for the view. Nicer still if it supported PNG, JPG, GIF, SVG, and others.
The current method is hacky and tedious and breaks easily as projects evolve. It prevents ending up in production situations that look clunky and unplanned because the current method for assigning/providing these UI elements is not obvious or intuitive.
Environment: n/a
2sxc version(s): requesting based on 9.42
Browser: all/any
DNN: all, Language: any/all
IMHO this would have huge ROI for agencies like us creating customized, highly effective client-managed CMS scenarios.
The text was updated successfully, but these errors were encountered: