Routing broken?

[stefandoorn]

It seems that in the current version (dev-master) adding routes doesn't function. The adding itself functions, but afterwards accessing a page does not work. It works if the static content has the same 'name', but I don't think that's how routes are meant :)

Reproduce:

• Add static content with name 'test'
• Add static content with name 'test123'
• Add route with name 'test-test' and link with static content 'test'
• Access /test-test - returns 404 (expected 200)
• Access /test123 - returns 200 (expected 404)
• Now rename static content 'test' to have name 'test-test'
• Access /test-test - return 200

Or, am I using this feature totally wrong? If so, I have no clue what Routes is supposed to do then.

[michalmarcinkowski]

The Route entity is not used on the frontend at all right now. The pages are resolved by internal name of static content mypage.com/internal-name-of-my-page.

[stefandoorn]

Ah ok.. so basically for now the routing option is obsolete? It would be nice to have it :)