can you confirm what version of usync you have installed (you can see this on the usync dashboard tab in the developer section).
also , do you have contentedition installed ?
usync doesn't know about all custom property types, but if Mr N Picker works in a similar way to the standard multinode picker it's probibly only a config change to get usync working with it.
I've had a look but i can't recreate this, just with usync stuff. usync saves, exports and imports Mr N Picker properties, on doctypes, and when content edition is also installed it happy saves exports them.
It doesn't be default map them - because out of the box, it doesn't know that Mr N Picker is storing content ids.
Luckily it is quite easy to tell usync about it. Just add the following to uSyncCore.Config
To make usync map the IDs that are stored in the datatype (so the root nodes). add the following to the <mappings> section
if you now save the data type, usync will put mapped paths into it's config so you can move them between sites, and if you save the content that uses the nPicker, it will replace the ids with guids so when you move the content toanother site it will map them.
this however doesn't explain what's happening for you, because without these mappings, usync will just leave the values alone, so on a single site nothing should change (assuming the usync files on the disk haven't been copied over from an old set or another site)
Mr n picker U sync
After save - saved nodes dissapear General Umbraco 7 Hi
Umbraco version 7.4.2 Mr N picker version 1.1.0
I have some troubles with the Mr N picker.
When i save the items it saves and it shows up: enter image description here
After 10 - to 15 minutes it dissapears, the values are still in available, but i can´t se the selected items.
Hi
I have a post here in mr Npicker forum https://our.umbraco.org/projects/backoffice-extensions/mr-n-picker/general/76412-after-save-saved-nodes-dissapear
If anyone sees this, i think it is related to u sync project.
I will test some more to see if i´m right.
René
hi,
can you confirm what version of usync you have installed (you can see this on the usync dashboard tab in the developer section).
also , do you have contentedition installed ?
usync doesn't know about all custom property types, but if Mr N Picker works in a similar way to the standard multinode picker it's probibly only a config change to get usync working with it.
Kevin
Hi Kevin
Tanks for your reply
Here is the information about Usync
(uSync.BackOffice 3.1.1.740) (uSync.Core 5.3.1.740)
I thought the content edition is included in usync.
Here is the settings from uSyncBackOffice.Config
Aarrgh! damned editor :-(
Here is an image from the config file for usync
Hi
I´m pretty sure it is when i set it to auto in the backend.
Then it somehow delete the type of the picker.
So next time i render the page i gat an error or no picker shown.
Hi
I've had a look but i can't recreate this, just with usync stuff. usync saves, exports and imports Mr N Picker properties, on doctypes, and when content edition is also installed it happy saves exports them.
It doesn't be default map them - because out of the box, it doesn't know that Mr N Picker is storing content ids.
Luckily it is quite easy to tell usync about it. Just add the following to
uSyncCore.Config
To make usync map the IDs that are stored in the datatype (so the root nodes). add the following to the
<mappings>
sectionto get usync to map the IDs inside the content (assuming you are using content edition) add the following to the
<ContentMappings>
sectionif you now save the data type, usync will put mapped paths into it's config so you can move them between sites, and if you save the content that uses the nPicker, it will replace the ids with guids so when you move the content toanother site it will map them.
this however doesn't explain what's happening for you, because without these mappings, usync will just leave the values alone, so on a single site nothing should change (assuming the usync files on the disk haven't been copied over from an old set or another site)
Hi Kevin
Tank you for your answer.
I have found out what was wrong.
It´s my own fault.
I published the site trough visualstudio to a local server, and changed the webconfig connectionstring via the web.release.config.
But there was an error, so it did not change the connection string, and used the same server.
This has caused the problems, every time i opened the deploy version it would reset the other :-(
Happy weekend René
No worries.
it's allowed me to add the config for Mr N Picker to the core config files, in the latest release.
So now this will just work for people who install Mr N Picker with usync.
:-)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.