Make it all compatible

Thats the idea.

Test Polylang to any bugs and create admin feature like Codestyling Localization connected to translations repository.


Frontend works perfectly. Unfortunately Admin stays always en_US.  that may be caused by missings at ClassicPress install, or error (elsewhere misfunctionality) of Polylang. It’s worth to make it  Front/Back Translation switched and all translation phrases edited by new module like Codestyling Localization.

Then I see it as a perfect system.

If connect new admin feature with some translation repository (based on plugins repository) Could create ClassicPress so powerful tool to reach out point “friendly software with easy multilanguage solutions”. All this features with Polylang deactivated in bundle is my kind of wish to Santa.