-
Notifications
You must be signed in to change notification settings - Fork 142
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug: cant edit values in a tile that has child tile(s) #4383
Comments
@adamlodge I've merged in a fix for this. I still have to do a little more investigation to see why this problem occurred, so don't close this ticket right away. |
… official_master * 'master' of https://github.com/archesproject/arches: (23 commits) Update loading mask message style Update instruction panel fix overflow on MSM default page, update status instructions download all concepts in a collection for the mobile app, re #4499 Update pre-release testing script Update pre release script. removes uneeded classes, adds active-sub class behavior erases comments new search icon left nav-bar lints Enforces card order in the MSM and persists that order to the mobile app. Also fixes card dirty state issues. re #4487 Update status message fix child cards not being added to the mobile survey, re #4472 Add message for completed, inactive survey Only shows active survey message when a survey is active on the server. re #4357 Notifies user why some features of the MSM are immutable once a survey has been synced. re #4401 Start update to survey status details Locks users and groups if a survey has been synched. re #4383, #4396, #4401 Fixes to user order so that dirty state does not persist once a user reverses their chanages to the user list. Locking critical mobile-survey properties once a survey has been synced. re #4383, #4396, #4401, archesproject/arches-collector#329 ...
meets requirementr |
This may not yet work as expected: when I try to add data to a newly added node in an existing node group, the changes don't get picked up and the |
By "existing node group", do mean existing node group instance/tile? Just
trying to replicate properly.
…On Sat, Feb 23, 2019, 6:51 AM Vincent Meijer ***@***.***> wrote:
This may not yet work as expected: when I try to add data to a newly added
node in an *existing node group*, the changes don't get picked up and the Save
edits button does not appear.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#4383 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJPDa-ROGlqNQpgkoOHW5a_oHWLy2Vcrks5vQVVmgaJpZM4Zo_Ar>
.
|
Yes exactly that :) So in the resource editor I added some data to a few nodes in the same node group (resulting in a node group instance, if I understand the vocabulary correctly). Then in the designer I added a new node to the node group. Subsequently in the resource editor I tried adding a value to the newly added node. This resulted in the 'Save edits' button not appearing. |
meets reqt |
if this is fixed, it should be closed |
@adamlodge I just tested this and it worked fine for me in the latest. |
To reproduce:
System will hang
https://app.zenhub.com/files/49451058/37fe3517-a282-41f9-9afb-07f68fee87b3/download
The text was updated successfully, but these errors were encountered: