Drupal is up and running but how do I ...?

(How to) create a 'collaborators' section?

Hi everyone,

I recently finished an installation of Drupal (4.6) for a client with the following sections:

  • news (nodes classified by taxonomy)
  • (future) events (nodes classified by taxonomy + location.module)
  • report of past events (same as events, lets past 'future events' in when desired)
  • image gallery (acidfree.module)
  • plus some semi-static pages, contact form, newsletter and recomended links

The contents and user management are run by a single person, so I only needed 3 roles: common user (let's them add comments to the nodes), editor (my client) and administrator (myself).

Now my client wants to add a new feature/section: collaborators. It will be some friends of her and won't be posting very often. That means she will probably be posting the nodes in their name. But on the visitors side it'll be seen as a new category, where they will be able to see:

  • last collaborators' nodes (ordered from newer to older, showing name and maybe avatar of each node)
  • all nodes by one collaborator (ordered from newer to older)
  • each collaborator personal page (=c.v., =resume)
  • (not necessary but an xtra would be) the list of collaborators

I've thought of creating the new role 'collaborator', including their personal profile and letting them post when logged in (my client could have the list of collaborator users/passwords, then log in for them, then post). I've thought of Organic Groups module (og.module) as well as of profile.module, but none of them helped me to achieve it all. On top of it I want to keep it SIMPLE. I think a different (3rd) approach could be using the features included in tha basic Drupal installation, such as the 'user's blog' (I don't let common users to have their own blog, but I would allow collaborators to do so) and 'my account' (for personal collaborator info).

I'm stuck at different points and at different approaches to the problem (see for example http://drupal.org/node/70887) but I really think it could be simpler than all of what I've tried till now, so I would love to have any suggestions from you, whether have developed some similar section before, or see it clear just from my post.

How to do this with views?

I am trying to make view generated pages (listing posts by taxonomy terms from different vocabs) the top level links of the site, but apparently the url has to be in the form of 'dir/dir'. Supposing I stick to 'view/taxonomy', should I then alias it *again* to get something like www.domain.com/find, where find is the top level link?

TinyMCE- by design or bugs?

Returning to TinyMCE after a long time, I found that when you first set it up, you need to assign at least one role with the necessary tinymce permissions *before* creating a profile. This is fine, but since I am uid1, shouldn't this happen automatically? This seems contrary to the way core and contrib modules generally function where uid1 always has all the permissions (I recollect another contrib module that did something similar, but I don't remember its name).

Show $tabs only to certain roles.... HOW?

Hi there!

I´ve the mysite.com/search link and when users get there, there is this search form, with the "advanced search" link.
The $tabs appears both to authenticated and annonymous users, and it says "cases" and "content", were "content" is the default. My problem is that I don´t wan´t unregistered people to search within the "cases" tab.
Is there a way to avoid that appearing?

Inside the page.tpl.php file there is the generic $tabs...

Block Content In Node

I know i've seen this somewhere before, but what module/code would I use to put a specific block content (EX: USER POINTS BLOCK) inside of a node.

Thanks in advance,

Nick

i18n: both translations of node promoted to front page appear for one language, but not other

Hi all

After much searching here, I have got most of my dual language site working - thanks everyone! However, just come across an odd problem. I create a story (in english) and promote it to the front page. I then create its translation (in french) and promote that to the front page. When I go to the english front page (/en or /en/node) I see that story, no problem. But when I switch to french via the language switcher or by typing in /fr or /fr/node, I see the french translation AND the english translation.

Pages

Subscribe with RSS Subscribe to RSS - Post installation