support February 2006

support@drupal.org

67 participants
78 discussions

Re: Post to front page only for certain roles?
by Alison 19 Feb '06

19 Feb '06

Nevermind. We found it. admin/node/configure/types/story It states clearly that anyone with administer nodes permission can override. Now if only everyone would answer their own questions. Alison

3 2

Post to front page only for certain roles?
by Alison 18 Feb '06

18 Feb '06

The queue module doesn't seem to support this. We have already put all admin/front page posts into the node type story but that doesn't change that there is a promoted to front page checkbox on every node. I don't care that it's there - I just don't want the posts to end up on the front page. Alison

2 1

offline Drupal Handbook
by Amit Karpe 18 Feb '06

18 Feb '06

Hi all, From where I can donwload offline Drupal Handbook ? I don't want to connect all time see Handbook . Or go on saving all pages . I want it in pdf or html form . Where do I get ? Thanks in Advance -- Amit. ______________________________________________________ param vaibhavam netum etat swaraashtram samrthaa bhavatwaashishaa tebhrusham || Bharat Maata Ki Jay ||

3 3

admin->access control
by VJ 18 Feb '06

18 Feb '06

Hi, I have around 25 roles and 20 modules. The interface is very hard to use (too wide, too long) Has anyone done work on a different interface for access control? If I wanted to get a seperate page for each role, how would I achieve that? Can a more practical display be achieved just using css? (considering the table is hardcoded) Thanks, V

3 3

What is difference of Theme and engine and template
by Amit Karpe 18 Feb '06

18 Feb '06

Hi , I am using box_cleanslate_smarty theme . But I am very new to this world . I do not have clear concepts of Theme and engine and template . Where I can find good material ? After googling I got this things . http://drupal.org/node/11774 http://drupal.org/book/export/html/509 Thanks in advance -- Amit. ______________________________________________________ param vaibhavam netum etat swaraashtram samrthaa bhavatwaashishaa tebhrusham || Bharat Maata Ki Jay ||

3 2

Re: [support] massive blog hosting
by dondi_2006 17 Feb '06

17 Feb '06

> 1) Install Drupal. > 2) Enable the "blog" module and "comment" module. (admin/modules) > 3) Give "edit own blog" permission to whichever class of users you want > (admin/access). > 4) Configure comments to your preference (admin/comments). > > All users with that permission now have a blog/uid path that is their > personal blog. RSS feed is created automagically. Comments can be > moderated or not, require logging in or not, threaded or not, etc. But will the users (and the blog posts they create under this Drupal configuration) have the same pingback and trackback capabilities and facilities available under WordPress or any other "Blog-only" software? I asked similar questions a couple of weeks ago, even on the forums, but frankly I haven't understood yet if and how much Drupal-generated pages can behave like "standard" blog pages, as in: *) be just as quickly and transparently seen/indexed by Technorati and other blog-oriented search engines *) provide to non geeks visitors the same buttons/links as WordPress to trackback their comments on their blogs to my pages, have a permalink, etc... *) ping by themselves pingomatic and similar services Thanks, D.

8 11

RE: [support] Contact info in an event
by Metzler, David 16 Feb '06

16 Feb '06

Yep, those are the two ways. Use flexinode to create content information within the event posting, or to use the user profiles to store the information upon registration. We've sort of decided to do the latter for a similar site, because that way you're not "always asking the user" for their contact infoatmation every time they post. If you're planning on allowing anonymous content, then you'd have to go with the flexinode option. Dave -----Original Message----- From: support-bounces(a)drupal.org [mailto:support-bounces@drupal.org] On Behalf Of David Grant Sent: Wednesday, February 15, 2006 1:33 PM To: Drupal Support Subject: [support] Contact info in an event I am creating a drupal site for a non-profit, and all their events seem to require contact information. http://www.davidgrant.ca/baldingfordollars/event/2006/02/01/list/all/all /28 What is the best way to incorporate the contact information? Create a drupal user and provide a link to that user? Or should I provide a flexinode field for the phone number and person's name...? I just want some ideas, as a new drupal user. Thanks, David -- [ Drupal support list | http://lists.drupal.org/ ]

1 0

Contact info in an event
by David Grant 16 Feb '06

16 Feb '06

I am creating a drupal site for a non-profit, and all their events seem to require contact information. http://www.davidgrant.ca/baldingfordollars/event/2006/02/01/list/all/all/28 What is the best way to incorporate the contact information? Create a drupal user and provide a link to that user? Or should I provide a flexinode field for the phone number and person's name...? I just want some ideas, as a new drupal user. Thanks, David

2 1

simplenews problem
by Laura Scott 15 Feb '06

15 Feb '06

I posted an issue on this, but I'm still not certain that this is a bug or a configuration problem. We have a site that is working well, except that the newsletters are not emailing out. All other email functions are working, including registration, new password, notification, contact and banner stats emails. But the newsletter emails do not send. The nodes are saving. The email addresses are there in the database table. If I edit the sent status to posted but not yet sent, the node seems to go into an email mode in that the status of the newsletter is displayed on the admin page as being in the process of being sent. After a cron run or two, the status changes to sent. Yet nobody receives any emails. No errors show up in the watchdog. Any ideas what the problem might be? This is the latest tarball of simplenews for 4.6. Thanks! Laura

1 0

Re: [support] New Install Problem: Access Denied
by Jason Flatt 15 Feb '06

15 Feb '06

Kory, you should keep these queries in the support list. There may be others with the same question, it saves bandwidth to answer the question for multiple people one time, and you are likely to get your answer sooner with multiple people seeing it. On Sunday 12 February 2006 10:57 am, Kory Hamzeh wrote: > Jason, > > Thank you for your help. I have one more question that I was hoping you > can help me with. > > I want to setup multiple drupal sites using different subdirectories > instead of domain names or IP addresses. For example, my main drupal > site right now is http://dilligaf.avatar.com. I want to create another > independent site with the root address of > http://dilligaf.avatar.com/site2. > > I know I need to create a config directory in > sites/dilligaf.avatar.com.site2/ and put seetings.php there, but what do > I put in http://dilligaf.avatar.com/site2 directory? There must be at > least an index.php there. Normally, that directory would simply be a sym. link to the parent. > Also, do I need to create a separate MySQL database? I thought I could > use the $db_prefix, by using a different prefix for each site, but when > I do that, I end up with a blank page (I also did a symbolic link of the > root html directory to the site2 directory). If I remove the $db_prefix, > I end up back at the main site (this is with the symbolic link). And > obviously, if I remove the symbolic link, I get an HTTP page not found > error since the site2 directory is empty. There are a couple of ways to handle this, and it depends on what your objectives are. You could use separate databases for each site or you could use a shared database. Also, shared databases could be anything from all tables shared to 1 table shared, depending on your needs. Mostly, I guess the real determining factor would be how much of the two sites are going to have in common. If there will be lots in common, then share the database and use the prefix. If there is a necessity to have something in common (like user accounts), then share the database. If there is a lot of differences and nothing really required to be shared, then I think it is easier to keep the databases separate. I frequently make mistakes on my shared database environment, and it is more time consuming to maintain. I'm sure that if there is anyone with differing opinions, they will add to the discussion. I did some searching through the Drupal Web site and was unable to find a page that explains how to do a shared database, so I'll post what I did here. I have one site that is into two parts: 1) public, and 2) private. For the public or main part, I have this in it's settings.php file: $db_prefix = "public_"; For the private part, I have this in it's settings.php file: $db_prefix = array("default"=>"public_", "accesslog"=>"private_", "blocks"=>"private_", "cache"=>"private_", "forum"=>"private_", "poll"=>"private_", "poll_choices"=>"private_", "remindme_node"=>"private_", "remindme_term"=>"private_", "signup"=>"private_", "system"=>"private_", "watchdog"=>"private_"); When I created the database, I did so with the prefix of public_, then I copied the various tables that the private site needed and changed their prefixes. So, for each table listed in the private settings.php file, I have both a public_ and a private_ prefixed table, but for each table not listed, the default prefix of public_ is used. I hope that's not too confusing to understand. -- Jason Flatt http://www.oadae.net/ Father of Six: http://www.flattfamily.com/ (Joseph, 13; Cramer, 11; Travis, 9; Angela; Harry, 5; and William, 12:04 am, 12-29-2005) Linux User: http://www.sourcemage.org/ Drupal Fanatic: http://drupal.org/

2 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

support February 2006