Problem: Sublanguage & Ecwid Shopping Cart – 404 error

Hello, thanks for feedback!

Unfortunately “Sublanguage” cannot be used with “Ecwid Shopping Cart”: this plugin is not using the WordPress standards API for content edition and url rewrite. Sorry!

Hi @gioweb and @max345,

Thanks for the report. We’re looking into the issue now.

@max345,

What exact WordPress APIs did you refer to? What in our plugin do you think makes the alternate-language pages on the site to respond with 404? Thanks for your help.

The problem is not just the 404 problem you’re referring to. Your plugin use a very custom ajax-based interface to edit products. It is impossible for a plugin to add multilanguage functionalities without doing specific code.

The 404 happens because the rewrite rules are regenerated on every page and overwrite extra rules added by Sublanguage for handling translations (I think they should only be regenerated on admin side, for performance reason).

Thanks for the response. Please see my comments below.

> The problem is not just the 404 problem you’re referring to. Your plugin use a very custom ajax-based interface to edit products. It is impossible for a plugin to add multilanguage functionalities without doing specific code.

All of the products data in Ecwid is stored in the cloud, so there is no store posts or pages in WordPress your plugin could “multilang”. We understand that —
Ecwid is by design a SaaS solution, so an extra functionality would need to be added to your plugin to work with the Ecwid APIs. That would be cool, of course, if you can do that (we can provide the APIs to you), but again — within the scope of this issue, this is OK that the product/categories are not translated here.

So, the main issue we see here is those 404 errors because they make the site not usable and we want to fix that.

> The 404 happens because the rewrite rules are regenerated on every page and overwrite extra rules added by Sublanguage for handling translations (I think they should only be regenerated on admin side, for performance reason).

Can you elaborate on this a bit? Does Ecwid plugin (when enabled) prevents yours from creating the necessary rewrite rules?

We understand that Ecwid is by design a SaaS solution, so an extra functionality would need to be added to your plugin to work with the Ecwid APIs. That would be cool, of course, if you can do that (we can provide the APIs to you)

Sure, I will think about that.

Can you elaborate on this a bit? Does Ecwid plugin (when enabled) prevents yours from creating the necessary rewrite rules?

Actually my plugin generate custom rewrite rules every time the rules are “flushed” (by WP or by any plugin), your plugin does exactly the same. The difference is my plugin only do this when flush happens on admin side. This is because generating theses extra rules use a lot of logics. But your plugin force a flush on every front-end page, so the rules are regenerated without my extra rules… I could easily change my plugin to allow the regeneration to happen on front-end, but I don’t want because I think doing this will slow things. And I care a lot about performances.

Problem solved by ecwid team. Thank you all!

Thanks for your help, @max345.
And thank you @gioweb for reporting the issue and connecting us!