Solution Redesign
Closed this issue · 1 comments
We're changing the approach to use a one post per language mode. Tis is inline with other solutions such as WPML or Polylang. The change comes from a need to convert an existing system, which uses one of these solutions. By keeping the same design we facilitate migration.
Why not use any of the existing solutions?
We're planning to be leaner and focusing on support for some plugins used by our clients. Not that others can't be supported, but these will be our main focus. Also, we hope to test and change things according to what is best from a performance stand-point. If we ever find a bottleneck that can be solved with a change to a different design we'll rectify the existing solution at the time.
What needs to be done now?
- Reuse most of the configuration and interface modules.
- Create a database schema for language information (one for posts and another for terms).
- Correct queries to include
INcondition with the respective tables.
This has already been done. We'll open a new issue to track cleaning the old code as some things might be useful.