Edit: sorry some of this was a bit redundant to earlier posts... I got a call while writing it and forgot to refresh to check new posts before submitting.
I believe what you are describing isn’t a behavior associated to whether a container is visible or not, rather a global config setting for friendly URLs. It determines whether the URL builds a virtual path based on the tree or if it is always ’flat’, that is the friendly alias title appended directly to the base URL. The relevant setting in the Evo system config is ’Friendly URLs > Use Friendly URL alias path’.
That said, I haven’t had a chance to use Revo since beta but at the time it had an equivalent config setting (System Settings > Area:Friendly URL > Use Friendly Alias Path (key = use_alias_path)). If it isn’t still available I imagine you could achieve the same result with some tweaks to the .htaccess file.
Aha. In tinkering with Revo, I had not found that particular setting. If I can use that setting to get Revo to generate the same paths as Evo, then thelast obstacle is cleared and I can work on upgrading.
So, any idea when an automated tool might be available for this? I’m not looking forward to porting 257 pages by hand, especially seeing as how many of them use galleries and other relatively complex content.
You might check out Provisioner. I believe it will allow you to transfer resources.
Actually, I think it might be possible now to export the site_content table and import it into Revo (but I’d back up the site first).
