Hello @dzoladz,
Thank you for your contribution. Alas, I've merged it too quickly.
The problem with the links comes from the localePath function, inadvertently introduced during the translation system update and that should not be used.
Your modification thus causes the new link to be http://localhost:59599/http://localhost:59599/<jobId>
The localePath function is generally used on the ezPAARSE interface (it builds the links by adding the locale or not depending on the language). in this specific case, the http://localhost:59599/<jobId> url is wired to the API and doesn't need to know the language used on the interface.
@wilmouths Thank you for the explanation and for removing the unnecessary localePath function. I'll pull down the changes to master and rebuild my container this morning.
Reverts ezpaarse-project/ezpaarse#103
Hello @dzoladz, Thank you for your contribution. Alas, I've merged it too quickly. The problem with the links comes from the
localePath
function, inadvertently introduced during the translation system update and that should not be used. Your modification thus causes the new link to behttp://localhost:59599/http://localhost:59599/<jobId>
The
localePath
function is generally used on the ezPAARSE interface (it builds the links by adding the locale or not depending on the language). in this specific case, thehttp://localhost:59599/<jobId>
url is wired to the API and doesn't need to know the language used on the interface.Bests.
@wilmouths