Hi
I realise that "anonymous user" has to have Node access ticked to be able to see anything.
But then they can see everything. We have real "members" who have gone through an
accreditation process. I would like to be able to allow unregistered visitors
to see the homepage, and read "stories", but not to be able to access the "forum",
or at least
some other way to allow members to choose whether a posting is for members-only or
for public viewing (and I thought making "forum" private and "story" public would be
I know there is implementation into xtemplate to have user avatars, but I'm wondering if anyone has ever tried implementing node avatars instead? What I want to do is if I post in a specific node it will have a specific icon/avatar for it on my front page when it posts. So basically like a topic icon/avatar. Thus each of my nodes would have a different icon/avatar depending on the node I posted to.
I have two sites that are being handled by drupal, with different databases. The work find without any problems. They each have seperate config files and seperate databases, but share the same drupal directory. I set up a third, and when its active the second site gets all it's links rewritten with the domain of the third site.
I don't understand. Please help.
The weird thing is the last site is not affected. . .
I have a site that uses flexinode types to add some contents. One of the fields is an image. There are a lot of content (and images) added normally. But last time, a user uploads an image (directly adding a flexinode), and the path seems to be the same that other previous image that was on the server. So the previous node associated to that image now shows this other image. If I upload again the first image, then is ok for the first, but overwrites for the second. Etc.
Within Administer - Themes, I clicked Configuration and it said:
warning: mkdir(files): Permission denied in /Users/john/Sites/drupal-cvs/includes/file.inc on line 77.
The directory files does not exist.
I guess this means that Drupal cannot create a new folder that it wants to,
and may be due to higher folders not having the correct permissions
though I'd think the installation should have sorted that?