-
Notifications
You must be signed in to change notification settings - Fork 648
Feature Request: Multilingual #173
Comments
Yes, multilingual ist a important feature in these days, also for smaller sites. |
Meanwhile, it is possible to create a language file for themes ? |
I agree making pagekit natively multilingual is essential. It would be an extra reason to replace Wordpress by Pagekit. |
+1 |
I'll take a look at the code and see if it is easily implemented. I'd like this feature, too. |
Would be really neat thing to be integrated. Without this, CMS'es are more like "US ONLY" thing for me. So I +1 for this :) |
A CMS without multilanguage support is not a CMS. |
I'm taking a look at what would be required to make this happen. Is anybody else working on this? I'm not familiar with Symfony, but I use Laravel so it's shouldn't be too bad. Should we open up a new branch for this? |
To make this happen, several things need to happen: Visitor side:
CMS side:
|
User friendly language negotiation:
|
Markus, I agree, the only correction is that the client language/locale list is an array:
Now, let me figure out what type of effort it would be. Do you have any tips? I'm new with Symfony, but not with PHP so I'll just start hacking into my fork. |
Storing of translations:
|
Chris, I'm using Symfony very rarely but I'm sure the translation infrastructure isn't very different from other frameworks. Personally I prefer using the gettext adapter. Introducing i18n / translatability into a whole CMS is not a small task. Subtasks IMO are:
That's all I can think of at the moment. Just a brainstorm because I like the idea of pagekit and I have some experience with translating large infrastructures. |
Markus, I agree that it is not a small task. I want to tackle one subtask, if possible. I just need to find out where to start. The translation adapter is already in the code from what I can see, although I've created a issue regarding date formatting fallback. |
I can't understand this feature request... On pagekit already exist localization and content are translatable using what mark said "gettext", using .po files which exist many po editor like poedit or online https://localise.biz/free/poedit the function name is _() and there is @trans() function for view files. Which part of pagekit should be translatable? Content of pages and blogs? Not sure if this is required by cms core, also WordPress does not support a bilingual or multilingual blog out-of-the-box. There are however Plugins developed by the WordPress community which will allow you to create a multilingual blog easily. This can be the same for pagekit. Maybe there is something other that is not translatable which I missing? |
Yes, I want translated content and I think it is a mayor shortcoming of Wordpress that it is not native multi-lingual. I don't use it any longer for multi-language sites. The plugins are either not user-friendly or they make the pages load slow. |
It should also do browser locale detection and serve up the proper language of the content. To do this, we would need to add a locale code field for the posts. |
In our experience, yes it is good to detect users language, but for example in my country 60% users use browser in english, but language is lithuanian. so we separate language by slug. ALso in-core multi-language would be good because of search modules or something like this. We currently are using PyroCMS with custom multi-lang support. For us multi-language is not only the translated cms buttons or something. Thanks Jaroslav |
@tastymousehub I understand now. I found this topic on roadmap here: http://www.pagekit.com/roadmap They seem integrate this feature but only in Future, after releasing 1.0.0 in first quartar of 2015. For now maybe someone will prepare an extension for this. I agree with mark who suggest how to handle this:
|
Guys, you really need to prioritize multi-language functionality. Like nearly all other platforms, you've left it as an afterthought, and it's gonna get messy. While I'm here, I also want to share that your URL structure needs to steer clear of filler words like "page," "post," "category," etc. These are really a nuisance for SEOs and site owners who want to migrate to a new platform but retain the organic ranking they've worked so hard and spent so much money to achieve. I wouldn't even look at yet another CMS that doesn't support custom URLs and multi-language functionality. |
👍 |
2 similar comments
👍 |
👍 |
@88kbbq you are right! :+1 |
We released the Pagekit Beta today. I close this issue because the code base completely changed. Please open a new issue if it still exists. |
Great news Sascha, I'll check it out. Cheers! Kevin On Thu, Sep 10, 2015 at 11:47 PM, Sascha notifications@github.com wrote:
|
But does the new pagekit support multilingual sites? |
+1 |
8 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
+1 |
I help create multi-language version |
What now? Do u do this? |
It's on the roadmap: https://pagekit.com/roadmap . So the developers are aware of the fact that the community would love to see this feature. |
+1 |
2 similar comments
+1 |
+1 |
+999999999 |
+1 |
CMS is incomplete without multilanguage. This feature is required nowdays. |
since at least 2014 people request this as probably #1 user request |
Maybe need contribute? |
For us, its feels like Pagekit is Dead :( There is a huge potential but nothing is moving.... |
Are there any news to Pagekit? It seems it is really dead! |
Get over with it, go learn WordPress, nothing is important for clients except WP. They are asking to build CRM on Wordpress, B2B solutions and so on. PHP world was infected with WP parasite. You either go with WP or learn another programming language or maybe wait until this stupidity ends. |
Well, I better go for OctoberCMS. Wordpress is a mess and will stay a mess! |
+1 |
+1 👍 |
This thread from 4 Aug 2014 is the main reason why I didn't install Pagekit even on localhost server. If something change here, I try 😄 |
In the meantime we started to built an own CMS which bases on pros from many other CMS (fast, lightweight, with additional basics like multilanguage) and we are near to publish it publicly. |
Hi Eichi, sounds interesting. How can we stay informed about this new CMS? |
It is really hard to build a MULTILANG feature for 100 DEVELOPERS ??? This is OPEN SOURCE software boys!!! IF YOU NEED SOMETHING, YOU CAN BUILD IT!! Happy coding... |
Making pagekit natively multilingual would be great.
Eventually, setting up a dedicated language manager extension would be interesting so it would give us the possibility to manage translatable content.
Also if do not need it, we could remove the extension and fallback to a monolingual site.
The text was updated successfully, but these errors were encountered: