Posted by mcduarte2000 on February 1, 2010 at 10:48am
6 followers
Jump to:
| Project: | Drupal.org webmasters |
| Component: | Localize.drupal.org |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
It would be useful to have this 2 extra permissions for administrator roles in localize.drupal.org:
- Publish a page node without offering the possibility for commenting (on my case, people are commenting on the dictionary page, which I would prefer to keep clean, as commenting on dictionary words should be done on the specific word node);
- Have the option to keep some nodes on top of all others.
Comments
#1
It was posted on the wrong section. New post:
http://drupal.org/node/702448
#2
#3
You can move existing issues, please do not submit new ones.
#4
+1 for the latter idea: Have the option to keep some nodes on top of all others.
I have been using l10n-server-your_lang_code tag to distinguish posts: Those which should be posted on the dashboard page (frontpage) of the language project, and others which don't have to. Nodes categorized as the latter still were accessible on the node listing page of the project. In this way, I could explicitly show most important posts to people who have just joined or who have just logged in.
But with the l.d.o. update done on March 17, 2010 (GSM +0900), the dashboard page and the node listing page were merged into one dashboard page, and all nodes are now listed on that page. So, when more new nodes are added, some important posts such as FAQ or translation guideline will be sent to the back (2nd page or later).
Please add some feature to allow us to choose some nodes and to keep them on the dashboard page.
#5
Hm, maybe we can use og_user_roles to grant you node admin permissions within the group you manage. /thinking
#6
kind of Node Queue or Flags functionality will be very useful and therefore appreciated. Or, just "Sticky" tag may work.
#7
Yes, as soon as we can make og_user_roles properly work again (run soon enough), we can easily grant node administration permssions to apply inside a group I imagine.
#8
Any news on this? I would really like to see an option to make a node sticky.
#9
I found an interim solution and would like to share it with other group maintainers.
On the top page of your translation group (*1), there is a link "Edit group" at the bottom of the right side bar.
Click it and you will see the organic group's group node edit page for your group. At almost the end, there is a text area which is titled as "Welcome message" or something similar.
In that text area, you can use <ul>, <li>, and <a>, with more tags. By using these tags, you can manually create a list of links to most important nodes on your group.
An example can be found at Japanese group.
Please note that it will take some time before the change takes effect on the page for anonymous users, due to (probably) caching.
*1 In Japanese group's case, the URL address is http://localize.drupal.org/translate/languages/ja . Please replace "ja" at the end of the address with appropriate language code of your language.
#10
Subscribing. Both features would be very helpful.
#11
This is now made possible. Any group member who has the "translation community manager" role in the group (edit member roles to grant this to people) can now administer nodes and comments under your group. This role also grants the possibility for the users to grant these roles to others. I hope this is a desired combination.
#12
Automatically closed -- issue fixed for 2 weeks with no activity.