ASP.net
Awesome
Learn
Forum
Buy
Demos
Sign In
☾
☀
Switch to
Dark
Light
Mode
this site works best with javascript enabled
Ask Question
Problem with nest editing (button click always shows popup)
Title:
B
I
{code}
?
Hi, I used the code from the examples (sources from the demo-download) and can't get the nest grid editing to work. Everytime I click on the e.g. create button a popup appears with my view. In the source the popup is rendered as jq ui element at the bottom of the page, not within the grid. Any ideas what I could have missed? @Html.InitCrudForGridNest("Jobarticles", "InstalljobsManage") <div class="bar"> <button type="button" onclick="utils.nestCreate('Jobarticles', 'createJobarticles')" class="awe-btn mbtn">Create</button> </div> @(Html.Awe().Grid("Jobarticles") .Mod(o => o.PageInfo().ColumnsSelector()) .Url(Url.Action("GridGetArticleItems", "InstalljobsManage", new { id = Model.Id })) .Height(0) .Groupable(false) .Tag(new {cont = "place"}) .Nests( new Nest { ButtonClass = "editnst", GetFunc = "utils.loadNestPopup('editJobarticles')" }, new Nest { ButtonClass = "delnst", GetFunc = "utils.loadNestPopup('deleteJobarticles')" } ) .Columns( new Column { Bind = "Id", Header = "#", Width = 70 }, new Column { Bind = "ArticleQty", Header = "Qty", Width = 50, Sortable = false }, new Column { Bind = "ArticleName", Header = "Name", Sortable = false }, new Column { Bind = "ProviderName", Header = "Provider", Width = 80, Sortable = false }, new Column { Bind = "TrackingNo", Header = "Tracking", Width = 160, Sortable = false }, new Column { Bind = "SerialNo", Header = "S/N", Width = 160, Sortable = false }, new Column { Bind = "ActivationCode", Header = "Cluster/Act.", Width = 160 }, new Column { ClientFormat = GridUtils.EditGridNestFormat(), Width = 50 }, new Column { ClientFormat = GridUtils.DeleteGridNestFormat(), Width = 50 })) I even traced through the js code but can't find the place where the ui object is actually created to change that behaviour. Best regards M
Save Changes
Cancel
Martin Strojek
asked at 02 Aug 2016
check if you have something like this in your site.js or utils.js and if it's called on document ready: return awem.inlinePopup(o);... this should be called via utils.init() compare your layout.cshtml with the min setup demo
at 02 Aug 2016
Omu
You saved my day! The init-call was missing, thanks a lot for the fast reply + solution!
at 03 Aug 2016
Martin Strojek
Answers
please
Sign In
to leave an answer
By accessing this site, you agree to store cookies on your device and disclose information in accordance with our
cookie policy
and
privacy policy
.
OK