Drupal 4.7.x

Hi All.

I have installed ePublish and have created some terms under a new vocabulary, "Issue." I then created an Edition and placed several pages and blogs underneath it. My pages have one of the taxonomy terms attached to them, so I would think that when I view my current issue, or go to it directly, I would see all of the "articles" already in view like a newspaper.

Instead I get just a list of headlines. :(

I have tried it with and without adding headlines in that section of the admin page. Without headlines, I get a blank page.

i've enabled upload.module and i use a file field in my form.
when i submit the form the file doesnt gets uploaded!!
i dont know wat's the reason.. can any one help???

thanx,
Charles.

I'm looking for module that make possible vote on users profiles. Is there anyting like that? Thanx for answers.

David

Hello, my problem is,
When i turn on user pictures in settings and in themes for some of the node types like forum and story its ok
but when i dont need user avatar or user picture in poll node type, I have this: files/pictures/picture-1.gif
how to remove this file path ?

New user here, but have searched docs and forums for the last 2 hours and still can't find the answer to this. In the administer>menus section, there is no option to disable create content...just enable and reset are available options. There is no need for visitors to see this option since I only allow admins to post content. However, logged in as admin or not logged in at all, "create content" comes up in the menu. I either want to make it come up only when an admin is logged in (like the "administer" link) or not come up at all and just point the browser to the node/add URL directly.

Because it might be useful to have conditional text possibilities in Drupal, I'll try to describe such a scenario; possibly inspiring others. Given time I might develop a conditional text module myself, but it will take a while, as there's still a few skills I need to acquire.

Text might be made conditional to documents intended for different audiences or media. Imagine you were writing general documentation about Drupal, and needed to discuss Drupal forms. There's quite a difference in the way forms are handled between versions prior to v 4.7 and subsequent versions. So two books are required, but tracking changes manually between the two different books is error-prone, time-consuming, and laborious.

Imagine conditional text working in a Drupal environment as follows:

Most of the text is common to both documents, and remains unaltered.

Text conditional to v4.7 is selected (somehow, not very relevant, lots of possibilities) and high-lighted with a pleasant green tint. Similarly text unique to v4.6 is high-lighted as a pleasant red.

Near Preview / Submit are check-boxes labelled 'v4.7' and 'v.4.6'; Each box include/excludes the conditional version from rendering upon Preview/ Submit.

Another checkbox toggles the colored high-lighting on or off, at render-time.

In terms of mark-up, the selections are simple spans, supported by a style-sheet.