Posted by Christefano on November 6, 2007 at 8:55am
| Project: | Create Content Block |
| Version: | 5.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | douggreen |
| Status: | active |
Issue Summary
I'd like to use this on sites that use OG but don't actually have OG content types called "groups". Is it possible to make the menu items translatable?
Comments
#1
The menu items are the "Human Readable" content type names from admin/content/types. These are not language translatable AFAIK. Is that what you are asking for. Please elaborate...
#2
The menu has items like "Story (in groups)" and "Poll (this group)" but some of sites have OG group content types named "clubs" and "teams" instead. The parts I'd like to translate are the "in groups" and "this group" strings in the select menu -- or remove them entirely.
Here's a mockup of my ideal "create content" block.
#3
Attached is a mockup of my ideal "create group content" block. The variables are placeholders for OG's group home page type and the OG group's name, and I hope they make sense.
#4
The "Create content" and "Create group_node->type content" text displayed at the top of these imaginary blocks would hopefully be translatable with the locale module.
#5
Ok, I get it...
#6
While i can certainly see the benefit of using the site's name for the og enabled content type, I can see a problem when the site has two og enabled content types (for example clubs and teams)
#7
Here's a patch, that simply makes them translatable. You could localize them to nothing if you want now.
#8
doh - i didn't "get" the simplicity of the bug report, that these two strings weren't being translated. I went ahead and added t()'s to both the group strings (not quite Benjamin's patch, but I gave him credit for it anyway's :) I'm leaving the issue open because I'd still like to implement some of the options discussed above.
#9