prevent problems for URL parameter that do no exist in Post model

[mjauvin]

A page with the following URL using the BlogPost component will generate an SQL query error when switching locale since the rainlab_blog_posts DB table does not have a field calld category:

url = "/post/:slug/:category?"

[LukeTowers]

What other params would there be to be translated other than slug? Why not just explicitly translate slug and nothing else?

[mjauvin]

I wanted to leave place for extensibility, if someone adds fields to the blog model, for example

[LukeTowers]

Shouldn't they just extend the event themselves in that case?

[mjauvin]

would adding a new handler that adds the missing fields work? I have doubts...

[LukeTowers]

I have doubts about the original theoretical use case behind the original implementation, can you provide me a concrete example where someone would be using arbitrary columns from the DB table as URL params that they would also want translated?

[mjauvin]

I can't. I don't mind changing it to only use the slug parameter as you suggested.

[LukeTowers]

LGTM! @bennothommo I'll leave it to you to merge so I don't screw up the release process.

[mjauvin]

I submited the requested changes @bennothommo

[bennothommo]

Thanks @mjauvin.