Call Support:Direct: (214) 420-1337Toll Free: (877)
Monday through Friday 8 a.m. to 6 p.m. Central
We created a configuration property for a widget where we want to be able to have end users update without having to edit the page and configure the widget.
We created a vm for the user to enter a property value and then we call $core_v2_widget.SetStringValue to save the property value. This works so long as the user is logged into the site.
When the user logs out, browser is restarted, the saved value is no longer there.
We're running Telligent 7.5. Is this a bug? or is this by design? Also, is there a work around, so that we can persist the value for the widget?
It's part bug, part by design.
The by-design part is that only users who have access to enter page edit mode can do so. And those users see the 'Edit' link in the header.
It's a little ambiguous, but .SetStringValue() is only intended for setting context-specific defaults for when a user *does* open the widget's configuration. It's not designed to support actually updating/persisting those values for the widget. And the fact that it *appears* to do so is the bug. It appears to, but it's only updating the cached configuration of the widget, which may or may not be user-specific per the widget's definition. A bug is now logged internally to investigate securing these Set methods.
Unfortunately, there isn't currently a supported way to enable adjustment of widget configuration values by users without actually using the widget configuration UI.
Thanks for the response!
Telligent Systems, Inc. ©2013, All Rights Reserved