Post installation

One of the requirements for the site we're building is to restrict access to the "full text" of a custom node to just the "teaser" unless the user has permission to see the "full text". In otherwords, an anonymous (or basic) user would be able to view/read the teaser - but not the complete content unless they logon (or upgrade) their account to have "premium" access. This restriction should apply to both users visiting the site directly with their browser as well as receiving a "feed" of the content.

Here's the way it looks to someone who has been wrestling with Drupal for a few weeks.

Development is way out ahead of the production (which makes documentation almost impossible). For the poor person who wants to use the system for an organization where users are using it for mission critical functionality it's a nightmare. This has been stated elsewhere and is often met with the response of hey why don't you contribute.

This is a chicken or egg situation whereby people who are attracted to core features of Drupal but are not coders are in a very difficult postion when it comes to contributing documentation clarity. Not sure if the egg is trying to catch up with the chicken or vice versa but it hides the positive work done on Drupal and the modules under a curtain of obscurity and insider knowledge.

At this point in what appears to be well 'logged' (as opposed to 'documented') development it is obvious Drupal is leaving a wake of disappointed, frustrated, and discouraged people who really wanted to use it. I'm not ignoring those of you who are using it to good advantage, but from the list of 'broken' and hobby sites (including developers sites) in the example site list there is a lot of room for improvement.

Each issue I run into, and many are simply lack of understanding on my part, leads me to a confusing array of terminology and choices about versions, matching modules, and patches. If the production version is held in such low esteem by the developers that most are encouraged to use the in progress version (I'm still not clear about 'head,' vs. CVS -- well I know *some* meanings of the term).

I was trying to get taxonomy terms to show up consistently on a page and meant to disable taxonomy_menu and unselected taxonomy module by mistake.

Now, as one might imagine I'm f*d. I figure there must be a place in the code where you can reselect it, but the gui interface to admin modules is broken as are most other areas. Seems like the site depends on taxonomy module pretty heavily so it's odd that it can be unchecked, or maybe it is only f*d up because the taxonomy_menu is on and there is no taxonomy...

Hi, I'm a total newbie with drupal and have been playing with it for the past 3 days.
I'm building a site for an artist cooperative group, with a very tight schedule (and budget, of course). Trying to keep things as simple as possible, with straightforward navigation and content relationships.
I'm having trouble getting past the initial learning curve, and a little confused with all the information I've been digging from the documentation and forums...
More specifically, I'm having a hard time creating the navigation as I need it to be (getting taxonomy to translate into navigation, menus, submenus, etc), and in the dark as to what theme to use as a basis to customize the site's look, since each theme implementation seems to work with different subsets of modules. I just know I would rather have one that uses templates and/or with strong use of css (xtemplate and interlaced are the ones I've been playing with).

The navigation structure is as follows:

I have been trying to set up a dropdown menu in a block with links to taxonomy URLs such taxonomy/page/or/34. The menu works fine with Mozilla and Firefox but with IE it works once, then starts adding taxonomy/page/or to the url so that I end up with something like taxonomy/page/or/taxonomy/page/or/taxonomy/page/or/53 and an error in database.mysql.inc. The form includes the following select element (spaces added around the square brackets):

select name="menu" onChange="location=document.jump.menu.options [ document.jump.menu.selectedIndex ] .value;" value="GO"

I need to set the order of items that show within a taxonomy term area. I am using taxonomy_menu module with drupal 4.3.2.

When a taxonomy 'term' is clicked I see the items (nodes?) that are associated with that term but they seem to show in most recent order. I want to be able to order them independent of chronological sequence. I would rather not have to put letters or numbers on the items within a term, but is there a way to use the 'weight' system at the level of files/stories/posts within a term?