Recently Browsing 0 members
No registered users viewing this page.
Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:
This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
I am using the translation function (either $this->_() or __()) within a module that responds to AJAX API calls - there isn't really a page that is being served.
When I supply a string with an apostrophe, e.g.,
__('Book \'em danno') It is formatted as
Book 'em danno
Is there some way to prevent output formatting when retrieving strings using the translation functions?
Each page in processwire has a name and a title.
When I create a new page and give it a title, the name is created automatically.
That name creates the URL of that page.
This works great for English sites.
However, for international users this doesn't work as nicely.
If I create a new page and give it a title that's not in English, then the name field is left blank and I must write a "fake" title in English.
I work with sites in Arabic and in Hebrew and this is the biggest difficulty I see when working on non English sites with Processwire.
Even for an experienced user, this is an annoyance every time.
For comparison, in WordPress I can have multilingual titles and URL's out of the box.
This is an advantage WordPress has when it comes to international users.
I would like to see this change, and perhaps help bring this change.
What would it take for Processwire to support multilingual URL's and page names?
What would be the best route to achieve this?
I'm in the process of building an internal tool using ProcessWire for my team to write and manage Agile user stories. (It actually started out as a quick prototype, but you know how things go with ProcessWire, I kept going for a few hours and suddenly had a pretty full-featured system. )
The way we do user stories, we have a story ID, such as "OP100", and then a title, such as "As an admin, I want to upload a PDF to attach to a user's account." I have these as separate fields, with the latter being the actual page title.
These titles can get somewhat long, however, and can change throughout the lifecycle of a user story, breaking links from Pivotal Tracker. Ideally, I'd like to just use the story ID as the name / URL, so instead of "/as-an-admin-i-want-to-upload-a-pdf-to-attach-to-a-users-account/", the page would just be "/op100/".
Further complicating this is that the story ID is optional (since a story can start out as just a concept that turns into an actual story later). So my ideal workflow would actually be one where the title creates the URL initially, but once there is a story ID, the URL changes to that (or even better, aliases to that).
One more related thing I'm hoping to do is to concatenate the story ID and title in the admin. Any ideas on how to do this?