CMS Made Simple Forums

Hello,

I've been upgrading a number of the sites I look after to cms 1.9.3 and I'm noticing some issues with apparently changed behaviour regarding page aliases and the cms_selflink tag.

Prior to the 1.9.x series some pages may have been created, despite my advice to the contrary, with a page alias like:
This would be accessible with a cms_selflink like:
It now appears that the case must exactly match within the cms_selflink tag or the link won't be created correctly. For this to work the tag must be;
Surely cms_selflink should still work regardless of the case within the page param? I can easily reproduce this on cms 1.9.3 with all the latest updates applied.

For some sites I look after this is a show-stopping bug preventing upgrades because after the upgrade half the links would disappear or stop working...

Can anyone confirm?

Thanks,

Mark.

Hello again,

So nobody have an opinion on this?

Let me restate it: If the case of the page or href param in a cms_selflink tag doesn't exactly match the case of the page alias then that page will not be found or the link will not be made.

Surely the case of the text used in a cms_selflink should be irrelevent? It no longer seems to be and it also appears to have changed in a very recent version(1.9.x) of cms.

I very much doubt that I'm the only one experiencing this issue? Is it a bug? Expected behaviour? Try it for yourselves, it seems quite wrong to me.

Can anyone comment on this? Even if to tell me I'm completely wrong!

Cheers,
Mark.

This hasn't come up before as most let the alias auto generate do it's job, but yes it is a bug that has been addressed in 1.9.4...

Hello,

Thanks for the information, I'll hold off upgrading the affected sites until 1.9.4 becomes available.

Cheers,
Mark.