All my TVs (pickers, file upload, text fields) appear on the NP form as expected but any changes are not reflected on the actual resource. No errors are being thrown either. On the other hand the default system fields like 'content' and 'summary' work fine.
The TVs have the correct template access settings and belong to the proper resource groups so I'm not sure where else to look for problems.
Todd
Can you change and save those TVs in the Manager?
If you give the font end user rights to the Manager, can they log into the Manager and edit and save those TVs?
Yes, editing TVs from the manager does work.
For dev purposes only, the Member user group uses the default Admin Policy so they are able to login to the Manager and yes, edit the TVs from the back-end.
Todd
What version of MODX are you using?
Are the TVs listed in the &show property?
Revo 2.3.2
Yes they are. The TVs appear as expected in the NP forms, they just won't update, even for an admin (sudo) when editing from the front-end.
I assume if it were a permissions problem I wouldn't be able to edit the TVs from the Manager (I can). The whole ACL/permissions thing is still a bit like voo-doo to me.
[ed. note: todd.b last edited this post 11 years, 9 months ago.]
Todd
Do you have &stopOnBadTv=`1` in the NP tag? (it's the default). That should alert you if there's a TV that isn't connected.
I don't know what to suggest. If a sudo user can't save them, it shouldn't be a permissions problem and if you can save them in the Manager, it's probably not mod_security. Do all the TVs contain MODX tags by any chance? If so, it might be an issue with the allow_tags_in_post System Setting.
You do have the latest version of NewsPublisher, right?
The new version converts tags from this format
to this format when NP is loaded.
{{tag . . . }}
It converts them back again on save. If there are MODX tags in the TV values and they still look like the first example in NewsPublisher, that would be a clue. If you can't save a TV with no tags in its value for the resource you're editing, that's not the problem.