Improving the editor: business logic for permissions
Has there been a major change to the API that the editors use (with the demise of cartouche_old)?
I'm really annoyed at no longer being able to "work around" permission issues by using cartouche_old, so I'm contemplating a deep-dive into the WME javascript to come up with another workaround. Assuming they're still implementing the permissions business logic in the editor (and allowing essentially a free-for-all at the raw web services interface), it should be possible to come up with a more intelligent permissions mechanism using an extension.
Anyone looked into this?
On the other hand, I'm just about to cross 200K edits-- is that still the threshold for loosening the shackles?
I'm really annoyed at no longer being able to "work around" permission issues by using cartouche_old, so I'm contemplating a deep-dive into the WME javascript to come up with another workaround. Assuming they're still implementing the permissions business logic in the editor (and allowing essentially a free-for-all at the raw web services interface), it should be possible to come up with a more intelligent permissions mechanism using an extension.
Anyone looked into this?
On the other hand, I'm just about to cross 200K edits-- is that still the threshold for loosening the shackles?
Re: Improving the editor: business logic for permissions