Hi Julio,

I apologise for my late response, I've been very busy. Regarding the upgrade from 1.3 to 2.0, I've just checked the code for v1.3 and I doesn't appear to save the data in the way I thought, I'm really sorry about that.

If you can wait until tomorrow I can get some code over to you which should store your data in the correct place ready for the upgrade?

I'll send you a tweet once its been uploaded

Regards

Richard

Hi Richard

Sorry about the delay but I just managed to get the 4.5.2 version up and running. Any advice on keeping the existing AutoTag data?

Regards

Julio

Julio,

I did send you a tweet, perhaps you didn't get it. But I've uploaded a code snippet which will help you port the tags over. I would however do this on a dev environment first, as although I have tested it, your setup might be slightly different. The code I've written can be dropped into a unit test or a usercontrol and run from there

Let me know if you have any problems

Rich

Hi Rich

Thanks for this.

Just to double check the steps we will follow to run the update:

• Install AutoTags 2.0 (without removing 1.3)
• Create a new AutoTags dataType using usercontrols/opencalaisautotag/autotags.ascx
• Add new property called "GrailTechTags" to document types using the new dataType
• Run update snippet to copy tags from existing code to new code?

Also, we're running the site on IIS6 / 4.5.2 / .NET 4

Best regards
Julio

Hi Julio,

Your plan makes sense, although there might be a problem with DLL names which would cause the older dataType to fail. 

My suggestion would be to run the snippet code first and test that the correct tags exist in the database either by looking at the cmsTags & cmsTagRelationship tables or by using the umbraco tagslib xslt extention. I'd then back the DB up and then install the new dataType.

If you could let me know how the upgrade goes I'd be really interested to find out

Thanks

Richard

Hi Richard

So far so good except for the disappearing tags bug reported here. We have exactly the same issue, tags work when saving but on re-saving they dissappear. This happens on both save and publish actions.

Any suggestions are welcomed.

Best regards
Julio

Well I'm pleased the upgrade is going well. Sorry to hear about this disappearing tags issue. What browser are you using?

So far on IE8, FF3.6, Chrome on Win7 Pro 32 & 64 bit and XP Pro

In all cases existing tags are removed. Can't see any client side errors, they simply vanish.

I'm planning to keep a copy on another field but if there is any easier way it would be appreciated

Thanks for your help

Regards
Julio

Update on this: if a page is published from the tree, the tags are kept. It's only when clicking on the publish icon on the toolbar thate they are wiped out

I'll try and have a look at this tonight. Is it just the publish or is it save as well?

It happens on both publish and save... unless you click again on any of the tags. Also, this happens when you go to another page, then go back to the page with the tags. It doesn't matter if you edit anything else, the only way to keep the tags is to click on them or publish from the tree (including publishing the parent page with "include children" ticked).

It would be interesting to see if anyone else is experiencing something similar?

Regards

Julio

I might be wrong, but judging from your description it sounds like its actually working as intended. Take a look at Darren's screen cast, but there are a few things you might be missing.

Suggesting tags will do only that, suggest them. By default the tags will have a grey background which means they're suggestions only. If you want to actually select the tag you will have to right click on that tag which will turn it green. Alternatively there is a property in /config/OpenCalaisAutotag/autotags.config, "SelectTagsAutomatically" which if you set to true will create the tags as "chosen" by default. Changing the config file will require an App Pool restart.

If you have done these then if you could provide a screendump then I'd be greatful

Regards

Richard

Hi Richard

We're saving the "green" tags and they're being kept as long as the page is published form the tree

1. Suggest and choose tags works OK

2. After saving the tags are in place

3. If we go back to the page and save or publish, tags are removed

4. The settings for the tags are:

I've managed to replicate this problem. I'll try and look at this tonight

Hi Richard

serialiseTags();

has done the trick indeed

Thanks a lot for your help

Regards
Julio

is working on a reply...