Hi Ismail

That did it! Thanks a lot. I tought a rebuild of my project would be enough. -> And now to some XSLT refactoring :-)

Now this is really weird.

It actually didn't quite fix my problem. It seems like everytime I publish, republish or manually delete my umbraco.config, to have a new one build up, only some of my xml is created in the new scheme. Other nodes are in the old scheme, so I have <TextPage... and <node... living together in the same xml.

Any idea how that is possible?

anyone?

Simon,

Is your site in its own app pool and are all the permissions correct?

Regards

Ismail

Hi Ismail

The solution is running on my localhost (XP IIS 6, so only one website at a time). I changed it from running "Medium (pooled)" application security to "High (Isolated)". Also I overwrote all of my folder permissions to give ASPNET full control. This seems to have done the trick. 

I would normally have done one change at a time, so I could have decided if just one of them did the trick. Unfortunately I didn't here, but I'm pretty sure it was the application security setting, that did it, as I think I had the permissions correct on beforehand. 

Any idea, why this happens? Is my publishing process being interrupted, because it doesn't get enough resources when publishing, and why does this result in "old" xml scheme?

Thanks a lot Ismail!

Simon,

Do idea but i have seen publishing issues where stuff seems to be published but doesnt when permissions are not correct. I have been caught out before where i have assigned permissions but not propogated down.  I have found through experience with things not publishing or css/ xslt not saving or timeouts and yellow screen of death to be either incorrect permissions or site not in own app pool.  In your case as its iis on xp app pool will not be issue.

Glad to have helped.

Regards

Ismail

Thanks Ismail!

I'd thrown you some High Fives, if I had only had the karma to do it :-) (umbraco forum understood)

I am having similiar problems, I just used XSLTUpdater and I set UseLegacyXMLSchema to false but nothing seems to work. I then changed the setting back to true and everything works fine even if the converted XSLT file is being used. Please help!

Hi,

I am also  having this problem after upgrading from 4.0 to 4.5.2.

Even though I have this line in umbracoSettings.config

<UseLegacyXmlSchema>false</UseLegacyXmlSchema>

The umbraco.config file is still being generated using the old schema.

I can restart the web server, touch the web.config, delete umbraco.config, and nothing works.

Any ideas?

Thanks,

Daniel

I am having this on a couple of sites, and I can't track it down at all; like Daniel, restarting, touch web.config, delete umbraco.config and republish - nothing works. Any ideas?

I ended up having to rebuild the site in the new version rather than upgrading it. Luckily it was a smaller site and the only one I needed to upgrade. There probably is a solution for the problem, I just couldn't find it and it was just quicker to rebuild it.

Thanks,

Daniel

It's looking that way for me, too, although first I'm going to try an upgrade to 4.5.2 on a mirror :o(

You have to publis the top level nodes in the content tree (including childnodes). Not the 'republish entire site' option, but the 'publish' option on the nodes on level below the root.

And after that, you have to republish the entire site...

See: http://our.umbraco.org/wiki/reference/xslt/45-xml-schema/switching-between-old-and-new-schema

@Martin van de Hoef : Oh my God, you have saved me from an early grave. That did the trick!

is working on a reply...