I'm using your excellent 1-2-3 magic package and it works fine, but I have one small question.
I've been working on a site for quite a while now, and now I've created a live site so I installed Umport on both development and production.
When I do an export on development, and right after clicking on "Analyze" also on development, I get a few changes like renaming a few properties and moving them to other tabs.
But, shouldn't the "Analyze" give me 0 modifications when both Export and Analyze are executed on the same solution within seconds ?
Yes and no... The "Property XXX sort order will be updated" is to be expected. The reason behind this is, that Umbraco does not necessarily enforce its own sort order on properties, but often simply rely on the creation date (or property ID to be exact) of each property to calculate the sort order. Obviously this won't work when synchronizing between different databases, so Umport enforces a strict sort order in the export XML, and thus you'll see these updates when you analyze changes on the source environment.
The other changes on the other hand should not show. I suspect some recently introduced caching is causing this. I've been working on a new release of Umport that should counter this (and add some nice new features), but time is not my friend these days. I'll get around to it eventually.
Out of curiosity, do you get these unexpected changes if you touch the web.config before exporting and again before analyzing?
I've just released the next version of Umport for Umbraco 7.2+ (Umport version 1.720.1.2). If you're using 7.2, try installing this new release and see if that changes anything.
We've had similar issues due to the fact that properties (AFAIK) don't have a GUID or similar that works across environments, so Umport performs som heuristic mapping of properties based on name and alias.
Which means that it can get tripped up when properties on a doctype have the same name, even though their aliases are different. Which is the case for e.g. Header [slideHeader] and Header [reviewsHeader] in the screenshot above. If you rename them to Slide header [slideHeader] and Reviews header [reviewsHeader] I'm pretty sure the problem will be solved.
But Kenn, can the heuristics be improved to handle this case better? Perhaps taking into account which property a tab is on, since duplicate property names are usually spread across different tabs (e.g. for a multi-lingual solution)?
Changes if I try to import right after export ?
Hi Kenn
I'm using your excellent 1-2-3 magic package and it works fine, but I have one small question.
I've been working on a site for quite a while now, and now I've created a live site so I installed Umport on both development and production.
When I do an export on development, and right after clicking on "Analyze" also on development, I get a few changes like renaming a few properties and moving them to other tabs.
But, shouldn't the "Analyze" give me 0 modifications when both Export and Analyze are executed on the same solution within seconds ?
Hi!
Yes and no... The "Property XXX sort order will be updated" is to be expected. The reason behind this is, that Umbraco does not necessarily enforce its own sort order on properties, but often simply rely on the creation date (or property ID to be exact) of each property to calculate the sort order. Obviously this won't work when synchronizing between different databases, so Umport enforces a strict sort order in the export XML, and thus you'll see these updates when you analyze changes on the source environment.
The other changes on the other hand should not show. I suspect some recently introduced caching is causing this. I've been working on a new release of Umport that should counter this (and add some nice new features), but time is not my friend these days. I'll get around to it eventually.
Out of curiosity, do you get these unexpected changes if you touch the web.config before exporting and again before analyzing?
-Kenn
It doesn't really change anything.
I still see a line like this:
Property Header [slideHeader] alias will be updated to header
Hi again.
I've just released the next version of Umport for Umbraco 7.2+ (Umport version 1.720.1.2). If you're using 7.2, try installing this new release and see if that changes anything.
-Kenn
Nice update :)
But it still shows some modified properties.
Venturing a guess here:
We've had similar issues due to the fact that properties (AFAIK) don't have a GUID or similar that works across environments, so Umport performs som heuristic mapping of properties based on name and alias.
Which means that it can get tripped up when properties on a doctype have the same name, even though their aliases are different. Which is the case for e.g.
Header [slideHeader]andHeader [reviewsHeader]in the screenshot above. If you rename them toSlide header [slideHeader]andReviews header [reviewsHeader]I'm pretty sure the problem will be solved.But Kenn, can the heuristics be improved to handle this case better? Perhaps taking into account which property a tab is on, since duplicate property names are usually spread across different tabs (e.g. for a multi-lingual solution)?
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.