I do agree AJAX request is best approach, and that is how I am doing it in numerous other locations. I just needed a fix for this one instance as it would have been a lot more work to refactor the modal to use AJAX for the select list, then it was to implement the refresh of the initial modal when the secondary modal executed a save.
I was able to resolve this using the existing
_resetUserSpecificPermissions()
in _PermissionsModal.js
as an example, tweaking it to my specific need!
I have a modal that has a select form field in it that is populated from the database; it also has a button that opens another modal where the user can add a new record to the database, once they add the record I need to refresh the modal that has the select so that the newly created option appears in the select list.
The select list is populated using a ViewBag parameter that is set in the Controller, thus the need to "refresh/reload" the modal window (to get the newly added record)
is there a "refresh" or "reload" method for the first open modal?
Considering renaming "MPA" to something else, any ill effects anyone can think of?
TIA! :)
Just asking - I rubber duckied my way to the solution :)
ModalManager - getModalId() and jQuery to modify the css.
$thisModal = $('#' + _modalManager.getModalId()).find(".modal-content").css({ "width": "900px", "margin-left": "-10px" });
Is there a quick way to adjust the modal width for the modalManager? Didnt see any options for width in ModalManager.js, wondering if it could be accomplished easily via jQuery but the Modal_ + (Math.floor((Math.random() * .... + new Date().getTime(); seems a bit difficult to "key" off of...
Thoughts appreciated as always!
Hmmm, in my continued reading it appears Settings Manager uses Cache, maybe extending OU to have settings is the correct route.
Appreciate others input...
Organizational Units work great for segregating users however I need to further extend it so that OU's can have "settings". I looked into the Setting Manager and it'd work great if I didn't need a UI for the site admin to manage the "OU Settings".
So... should I get the source code and extend OU's to have "settings", or should I go the route of creating an UI for creating static (saved to db) settings that are then used to create settings in the settings manager on application initialization.
Thoughts?
Org. Unit X (Customers)
Setting 1 (locale zone fee) Setting 2 (group discount for instance)
TIA! :D
<cite>hikalkan: </cite> One reason can be customErrors should be "On" in for web.config file.
That was the culprit, thank you sir.