{"action":"created","issue":{"url":"https://api.github.com/repos/modxcms/revolution/issues/3494","labels_url":"https://api.github.com/repos/modxcms/revolution/issues/3494/labels{/name}","comments_url":"https://api.github.com/repos/modxcms/revolution/issues/3494/comments","events_url":"https://api.github.com/repos/modxcms/revolution/issues/3494/events","html_url":"https://github.com/modxcms/revolution/issues/3494","id":26694517,"number":3494,"title":"Tv's Input Option Values Leftovers","user":{"login":"gOmp","id":442790,"avatar_url":"https://avatars.githubusercontent.com/u/442790?v=3","gravatar_id":"","url":"https://api.github.com/users/gOmp","html_url":"https://github.com/gOmp","followers_url":"https://api.github.com/users/gOmp/followers","following_url":"https://api.github.com/users/gOmp/following{/other_user}","gists_url":"https://api.github.com/users/gOmp/gists{/gist_id}","starred_url":"https://api.github.com/users/gOmp/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/gOmp/subscriptions","organizations_url":"https://api.github.com/users/gOmp/orgs","repos_url":"https://api.github.com/users/gOmp/repos","events_url":"https://api.github.com/users/gOmp/events{/privacy}","received_events_url":"https://api.github.com/users/gOmp/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/modxcms/revolution/labels/enhancement","name":"enhancement","color":"90BEF2"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2011-01-15T21:55:06Z","updated_at":"2015-01-12T17:04:16Z","closed_at":null,"body":"gOmp created Redmine issue ID 3494\r\n\r\n{Didn't know to which category assign this}\r\n\r\nWhen setting up a TV we can fill in an input option values as inline content, options separated by `||` , by bindings, delimiters and so...\r\nThe problem is when for example we save the TV with some chosen option across the different resources when adding/editing them,\r\nAnd afterwards when we want to edit the TV's input option values, and remove an option that we used already somewhere in our resources,\r\nThen it would show this removed-option at those resources even that we removed it from being an option, it would still be there but as a *blank label.\r\n\r\nSo generally speaking it doesn't update the input option values. and we left with a *blank leftovers.\r\nIt's because when rendering the values for the TV's in the Back-end Resource Page it takes the values of the TV's from `[[+PREFIX]]site_tmplvar_contentvalues` Table, and this values isn't always fit to what we set(changed) to be the options of the particular TV.\r\n\r\nI Think that it would be much better if while rendering the tv input in the manager, to cross-check if the stored values are those who appears as part of the `Input Option Values` so if we change our input option values/or deleting a resource/chunk/whatever-filled as an option, you don't need to go and update the tv all across your site to avoid those ugly blanks.\r\n\r\nI suppose it's a known behavior (if so, then why?), or is it a bug?\r\n\r\n\r\nA little note: * Blanks appear when using check boxes, In other types (e.g. `DropDown List Menu`) it's just outputs on the front-end the option we saved and removed.\r\n\r\nas described here:\r\nhttp://modxcms.com/forums/index.php?topic=59700"},"comment":{"url":"https://api.github.com/repos/modxcms/revolution/issues/comments/69604523","html_url":"https://github.com/modxcms/revolution/issues/3494#issuecomment-69604523","issue_url":"https://api.github.com/repos/modxcms/revolution/issues/3494","id":69604523,"user":{"login":"OptimusCrime","id":2326278,"avatar_url":"https://avatars.githubusercontent.com/u/2326278?v=3","gravatar_id":"","url":"https://api.github.com/users/OptimusCrime","html_url":"https://github.com/OptimusCrime","followers_url":"https://api.github.com/users/OptimusCrime/followers","following_url":"https://api.github.com/users/OptimusCrime/following{/other_user}","gists_url":"https://api.github.com/users/OptimusCrime/gists{/gist_id}","starred_url":"https://api.github.com/users/OptimusCrime/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/OptimusCrime/subscriptions","organizations_url":"https://api.github.com/users/OptimusCrime/orgs","repos_url":"https://api.github.com/users/OptimusCrime/repos","events_url":"https://api.github.com/users/OptimusCrime/events{/privacy}","received_events_url":"https://api.github.com/users/OptimusCrime/received_events","type":"User","site_admin":false},"created_at":"2015-01-12T17:04:16Z","updated_at":"2015-01-12T17:04:16Z","body":"I am pretty sure this is known behavior and there are no better ways to do it.\r\n\r\nIf they implemented a way to \"listen\" to changes, they would have to analyze the changes and figure out what value was altered. How should be done if multiple values were added instead? Should they be changed to that or left alone?\r\n\r\nI am pretty sure there is no easy way to fix this issue. And it is well known."}}