Open ajplopez opened 5 years ago
thanks @ajplopez. I'll wait for a few votes to see if this is wanted by more users - shouldn't be a big deal ;)
This comes up regularly with clients. Any chance this is easy or easier now in the newer UI, recent versions of 2sxc? Its one of those simple, obvious things that we really need. Thanks!!
Get it some more votes and we'll prioritize 😉
Just as a side-note: you could probably also just create a regex to solve this, requiring file:xxx That would at least prevent links etc. being added
As a developer, I always want my non-technical content editors to have the simplest editing experience in which it's hard for them to make mistakes. Often that means limiting their abilities on editing. I've run into an issue every once in a while where my content editors will hotlink to other domains when I really need them to simply upload an image through drag and drop. One of the problems that can occur with hotlinking is that the image resizer doesn't work because the file isn't local.
I'm submitting a ... [x] feature request / wish issue
...about
[x] edit experience / UI [x] admin experience UI
Current behavior When you create a Link field in a content type, you can choose Default Dialog, Show Page Picker, Show Image Manager, Show File Manager, Show Adam. While these guide the users to make decisions, it still allows them to type mostly anything they want into the field. That means they can hotlink to other domains.
Expected behavior As a 2sxc developer, I wish there was an extra toggle below or beside Show Adam that forced the user to use ADAM and not allow them to type in the fields.
Minimal reproduction of the problem with instructions Go to edit a content type that has a Link field and try typing into the field. You're allowed to type anything you want. Even though you may have settings making the field required, or Custom File Extensions, or show the buttons and menus, the user can still bypass the field essentially.
What is the motivation / use case for changing the behavior? I want to force my relatively non-technical content editors to upload images and not hotlink to other domains.
Please tell us about your environment: Multi-portal instance on DNN 9.3.1. Currently 2SXC 9.32.1. We have many content different content editors - some who update regularly, some less regularly.
Anything you would like to add