Fixed #018337: REST index missing module repository activation

[nfrp]

No description provided.

[oms]

On 2nd thought, would it work for you @nfrp, if you included the module list setup directly in your controller, as to not enforce the coupling between eZModule and the newer rest endpoint?

[lolautruche]

I think the eZModule activation is needed since it appears to be quite common (I had this issue a couple of times on custom REST controllers and the problem is quite confusing...)
So I'd vote for the merge :)

[nfrp]

@oms @lolautruche i also believe that making content creation from REST transparent should help here. This patch makes it transparent. The patch itself is maybe not the best way to do it, but on the principle i think the feature is important.

[andrerom]

After some though I think I would vote -1 myself. rest is ment to be used with public api eventually, so when it is this patch will be removed thus breaking all code that relies on it, better to break early during development then break during upgrade possible on prod.

[nfrp]

Now that we moved ahead on creating the PHP API, was there any move on the subject ? In other words, can we make available a temporary solution for people to use the REST api in W mode ?

Cheers guys,

[andrerom]

See comment above, if people want to use the old "api" then they it is safer that they do as much old api init code in their own code as possible as that init code will not be part of rest api 2.0 witch uses public api.

[nfrp]

Ok for the low-quality workaround.

I would recommend updating the various tutorials with this instruction. It cost me some debug time to figure-out what went wrong, we should help other developers not waste this time. The old API will still be used for some time until the brand new PHP + REST API is released & stable, and people will want to make mobile applications in the meantime.