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?
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | createcontentbyblock_translatable_ingroup.patch | 380 bytes | mlncn |
| #3 | creategroupcontent.png | 17.41 KB | Christefano-oldaccount |
| #2 | createcontent.png | 14.61 KB | Christefano-oldaccount |
Comments
Comment #1
douggreen commentedThe 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...
Comment #2
Christefano-oldaccount commentedThe 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.
Comment #3
Christefano-oldaccount commentedAttached 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.
Comment #4
Christefano-oldaccount commentedThe "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.
Comment #5
douggreen commentedOk, I get it...
Comment #6
GregoryHeller commentedWhile 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)
Comment #7
mlncn commentedHere's a patch, that simply makes them translatable. You could localize them to nothing if you want now.
Comment #8
douggreen commenteddoh - 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.
Comment #9
douggreen commentedComment #10
douggreen commented