support November 2006

support@drupal.org

39 participants
43 discussions

Re: [support] Change to home page location
by Metzler, David 10 Nov '06

10 Nov '06

Are all the pages in the drupal site going to have /home in front of them or was the idea that only the entry page of drupal needed a to be at /home? You shouldn't need (nor would I recommend) two copies of the drupal distro files. The /files permissions problem is probably because it's root and it's looking for mysite.com/files when you want it to find mysite.com/home/files or the other way around. The permisssions error may just be indicating that the file doesn't exist? If all drupal content needs to be accessed from mysite.com/home then I'd recommend that you only keep the copy there. Also, this may be slightly different depending on whether clean urls are enalbed or no.... Dave ________________________________ From: support-bounces(a)drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Halter, Shari Sent: Friday, November 10, 2006 11:21 AM To: support(a)drupal.org Subject: [support] Change to home page location I have a site, call it mysite.com. My site lives in the following directory on a Debian linux server: /export/devhome/mysite.com/htdocs. Drupal was installed here. It ran fine. Administration deemed, after the site was in place, that site home page needed to be changed to http://mysite.com/home <http://mysite.com/home> , rather than http://mysite.com <http://mysite.com> . (The URL MUST appear exactly this way) So I made a directory, /home, under htdocs. [I've been told by our sysadmin that Apache mod_rewrite, symbolic linking and other server redirect methods wouldn't work]. My home page would initially not run here (complained first about includes, then modules) so I had to make a separate copy of mostly everything (includes, modules, misc, etc. everything except for database) in htdocs and duplicate it in /home. It now works fine, from both locations. The $base_url was left, in sites/mysite.com/settings.php, as http://mysite.com <http://mysite.com> . Questions/issues: 1. Is it really necessary to have those Drupal files in both locations (htdocs and htdocs/home)? 2. My "Administer" -> "Settings" page in Drupal is complaining that it no longer has access or permissions in the /file directory, despite my having used chmod 755 . to adjust permissions on the directory and the files within. Thanks, Shari Shari L. Halter Web Programmer, Corporate Services Thornton Tomasetti 51 Madison Avenue New York, NY 10010 T 917.661.7800 F 917.661.7801 D 917.661.7970 SHalter(a)ThorntonTomasetti.com <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> The information in this email and any attachments may contain confidential information that is intended solely for the attention and use of the named addressee(s). This message or any part thereof must not be disclosed, copied, distributed or retained by any person without authorization from the addressee. If you are not the intended addressee, please notify the sender immediately, and delete this message. <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

1 0

Re: [support] Multi Site Question . . .
by Michelle Cox 10 Nov '06

10 Nov '06

On 11/10/2006 7:39:19 AM, Jason Flatt (drupal(a)oadae.net) wrote: > I have not done so for one reason: what happens if I have a site that is > using a module that gets abandoned or > doesn't get upgraded in a timely > manner? And with multi-sites and the potential to have several sites on a > single installation (like > 20), there's > a good likelihood that on a major > upgrade (like from 4.6 to 4.7 or 4.7 to 5.0), I will have more than one > such > module. Upgrading is one reason that I'm considering splitting up my multi site. I have 3 sites running off a multi site. One of them I want to bring to 5.x within a few months after release. The other two really don't need to be upgraded as long as 4.7 is still supported. The only real advantage I've found to multi site is security updates only need to be applied in one place. I'm not sure that benefit outweighs the pain of being forced to upgrade all sites at once. If you do decide to do multi site, and you only have one or two out of the 20 that you don't want to upgrade because you're waiting on a module, you could always split those off of the multi site until they are ready to be upgraded. Michelle

5 7

Multi Site Question . . .
by Jason Flatt 10 Nov '06

10 Nov '06

I currently have in place several sites using Drupal with immediate plans to do more in the near future. Because of the way I have configured my server, most of those sites have their own installations. I have thought many times about moving them all into a single installation for ease of maintenance, but I have not done so for one reason: what happens if I have a site that is using a module that gets abandoned or doesn't get upgraded in a timely manner? And with multi-sites and the potential to have several sites on a single installation (like > 20), there's a good likelihood that on a major upgrade (like from 4.6 to 4.7 or 4.7 to 5.0), I will have more than one such module. I really see only three options: 1) don't upgrade any site until the modules are all current -- not really practical for abandoned modules, 2) uninstall the offending module(s) and live without it(them) -- also not practical if it turns out that it(they) are key to the site, and 3) upgrade and/or maintain the module(s) myself -- also not necessarily practical if we're talking several modules and free time being at a premium. I think for me the only option that makes any sense (other than not combining all the sites into a single installation, which may turn out to be the best option) is option #3. Does anyone else have any words of wisdom to offer? -- Jason Flatt http://www.oadaeh.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

technical support chat
by Mohammed Al-shar' 04 Nov '06

04 Nov '06

hello everyone. your recommendations are always appreciated. this time I want to provide a technical support chat inside of my drupal powered-website, so that users chat with one of the technical support ingineers in my company. I don't want the users to be able to chat with each other, but only with the technical support persons. what is the best way to do it? module(s), combos, etc. Regards, Mohammed al-shar'

2 1

RewriteRules and Multisites
by marcob 04 Nov '06

04 Nov '06

I've searched in Drupal forums and on the net, but couldn't manage to get this solved: How to redirect each multisite "mysite.com" to it's respective "www.mysite.com" ? I tryed many RewriteRules: RULE 1: RewriteCond %{HTTP_HOST} !^www\.site1\.com$ [NC] RewriteRule ^(.*)$ http://www.site1.com/$1 [L,R=301] RESULT: all my sites are redirected to "www.site1.com" ------------------------------------------------------------------------ --------------------------- RULE 2: RewriteCond %{HTTP_HOST} !^www\.site1\.com$ [NC] RewriteRule ^(.*)$ http://www.site1.com/$1 [L,R=301] RewriteCond %{HTTP_HOST} !^www\.site2\.com$ [NC] RewriteRule ^(.*)$ http://www.site2.com/$1 [L,R=301] RESULT: Too many redirects occurred trying to open “http://www.kiteatlas.com/”. This might occur if you open a page that is redirected to open another page which then is redirected to open the original page. ------------------------------------------------------------------------ --------------------------- RULE 3: RewriteCond %{HTTP_HOST} ^www\.[^.]+\.com$ [NC] RewriteRule ^http://www\.([^.]+)\.com/$1 [L,R=301] RESULT: Nothing happens. Site addresses are not redirected in any way apparently. ------------------------------------------------------------------------ --------------------------- Please, could anyone suggest a RewriteRule (Cond) that redirects ALL multisites to their corresponding www. address? I swear I will make the reply into a Handbook page ;) Cheers, Marco

2 2

$base_url problems on cocomment and notifications
by Michael Angeles 03 Nov '06

03 Nov '06

Cocomment is formatting my links oddly. My settings.php file has base url as: $base_url = 'http://urlgreyhot.com/personal'; Links being set by cocomment, reference $base_url, but are sending the links in the form: http://urlgreyhot.com/personal/personal/comment/reply/2661 You see how personal/ is in the URL twice. Notifications module is sending its links that way too. Any idea where this might be getting confused? Thanks, Michael

1 0

(no subject)
by Zen Seeker 03 Nov '06

03 Nov '06

I don't mean to be a bug, but I am curious as to why I don't get any acknowledgment to this question. I know everyone is very busy. I am trying to use the proper protocol for addressing this issue. The following is an issue I posted at drupal.org. I've tried to be as specific as possible. If I'm not clear, can someone let me know what other details you might need? As always, thanks in advance for all assistance. I put this out in the forums, but it got overlooked. Didn't know if I should put it here, but taking a chance that maybe someone else might have this problem. I am playing with the 5.x beta with my custom theme. It is here on a temp site: www.memoryflix.biz. I have inserted the new primary link code in the page.tpl.php file. I have graphic tabs in the header for the primary links. It took some fiddling to get them, along with the background image, in the proper position. I used bluemarine page.tpl.php as the basis for the theme. Everything looked good in 4.7.4, as here: www.lifeonilife.com. My only problem is the tabs are now spaced too far apart. I have another theme that is doing the same thing. Looked fine in 4.7.4, but now there are spaces between the tabs. From that theme, it seems it's the size or padding or margin of the button_over image, but nothing in the css that I change is squashing the space. I even dropped the background image to a 1px width. I realize that the new primary link code is using navlist. My css has navcontainer. I tried changing all the navcontainers to navlist and that really messed things up. So I left the new code as is and put it in I just want to get rid of the spaces. I didn't want to put this in as an issue because I THINK it's got to be the css, although that hasn't changed from the 4.7.4 installation. I'm a newbie who has discovered custom theming and Dries' post said newbies could contribute to the testing of 5.x beta. I'm definitely in the "dangerous" category. I lived life as a tester for six years, testing against Oracle databases and SAS. Never want to see that life again, but I'll gladly volunteer to test if anyone wants to give me some use cases, or I can just try and break things myself! Thanks in advance. Just wondering if anyone has had time to look at this. I did install antique_modern theme and it has the same problem. If someone could just give me a little direction, I'd appreciate it. Looks like it's any theme that has tabs for primary links. Thanks again.

1 0

Re: [support] Upload pictures directly from node (not from EDITpage)
by Metzler, David 02 Nov '06

02 Nov '06

Sorry to say that there are no modules that I'm aware of (and I'm aware of a lot of them) that do what you're asking. I'd try and make contact with the maintainer of the image tabs module to see if that's something that could be incorperated. YOu may or may not have success, but it's always worth a try. Or, if you're a developer yourself. Start looking at image tabs to see if it can be customized. Dave ________________________________ From: support-bounces(a)drupal.org [mailto:support-bounces@drupal.org] On Behalf Of marcob Sent: Thursday, November 02, 2006 12:05 PM To: support(a)drupal.org Subject: [support] Upload pictures directly from node (not from EDITpage) Howdy, i followed the support list for some time, but this is my first post, so first of all my big up to all the people who use their for making Drupal a better place :) My support question: Upload pictures directly from node (not from EDIT page) can anyone tell if there actually is a way to let users upload/attach images to posts (nodes) directly from the node page? Now all (?) the image modules require users to go through the EDIT form. What i mean instead is the very classic/basic "upload an image" field *directly* on node page. The closest thing i found is the Image_tab.module: it adds an "add images" tab to the desired nodes. Still i reckon the easiest thing for users is the upload form on node page. Also the module is still cvs and not finalized for 4.7 yet and quite buggy... Please, any hint greatly apreciated! Cheers, Marco ++++++++++++++++++++++++++++++++++++++++ David, thanks for replying! Img_assist (image assist) module is provides the functionality, but its still from the edit page. Can't really answer your question without knowing: 1. What would you want drupal to do with the images attached to a node? In what way are they attached? If you don't have an editing context, how would drupal know where to put the image on the page? basically what i need is that users should be able to upload pictures they might have related to particular nodes. They should find an *upload image* field directly on the node page, or alternatively there could be an "add images" tab, similarly to what image_tab tryes to do, that links to a page that allows them ONLY to upload pictures. The images they upload are then attached to the node and displayed on the node's page togheter with other similarly submitted pics (a kind of "node gallery") 2. What is the problem with doing this on the edit page? i don't want all users to be able to actually *edit* the whole node, but i want them to be able to only upload pics. 3. Have you thought of this problem on other ways? Are you trying to create a gallery (there are modules for that), or are you trying to publish a page, or upload an image for use within a page? is not a real standalone pictures gallery (a la image.module, or shazaam.module). It is more a collection of pictures related to each specific node, submitted by different users. 4. Are you familiar with the wysiwig editors used in drupal such as tincymce? These may offer features that you're looking for. wysiwigs act always from the back of the nodes ( from the *edit* page) so they are not suited for what i am looking for. Hope this is bit more clear ;) Thanks for any help! Marco

1 0

Upload pictures directly from node (not from EDITpage)
by marcob 02 Nov '06

02 Nov '06

Howdy, i followed the support list for some time, but this is my first post, so first of all my big up to all the people who use their for making Drupal a better place :) My support question: Upload pictures directly from node (not from EDIT page) can anyone tell if there actually is a way to let users upload/attach images to posts (nodes) directly from the node page? Now all (?) the image modules require users to go through the EDIT form. What i mean instead is the very classic/basic "upload an image" field *directly* on node page. The closest thing i found is the Image_tab.module: it adds an "add images" tab to the desired nodes. Still i reckon the easiest thing for users is the upload form on node page. Also the module is still cvs and not finalized for 4.7 yet and quite buggy... Please, any hint greatly apreciated! Cheers, Marco ++++++++++++++++++++++++++++++++++++++++ David, thanks for replying! > Img_assist (image assist) module is provides the functionality, but > its still from the edit page. Can't really answer your question > without knowing: > > 1. What would you want drupal to do with the images attached to a > node? In what way are they attached? If you don't have an editing > context, how would drupal know where to put the image on the page? basically what i need is that users should be able to upload pictures they might have related to particular nodes. They should find an *upload image* field directly on the node page, or alternatively there could be an "add images" tab, similarly to what image_tab tryes to do, that links to a page that allows them ONLY to upload pictures. The images they upload are then attached to the node and displayed on the node's page togheter with other similarly submitted pics (a kind of "node gallery") > 2. What is the problem with doing this on the edit page? i don't want all users to be able to actually *edit* the whole node, but i want them to be able to only upload pics. > 3. Have you thought of this problem on other ways? Are you trying to > create a gallery (there are modules for that), or are you trying to > publish a page, or upload an image for use within a page? is not a real standalone pictures gallery (a la image.module, or shazaam.module). It is more a collection of pictures related to each specific node, submitted by different users. > 4. Are you familiar with the wysiwig editors used in drupal such as > tincymce? These may offer features that you're looking for. wysiwigs act always from the back of the nodes ( from the *edit* page) so they are not suited for what i am looking for. Hope this is bit more clear ;) Thanks for any help! Marco

1 0

Re: [support] login problems
by Metzler, David 02 Nov '06

02 Nov '06

My best guess is that session support is not configured properly in PHP 5. You can check this with a simple php script containing the following. <? session_start(); phpinfo(); ?> Look to make sure session support is enabled. Debugging this is highly dependent on which version of web server you're running, and how php5 is installed. Some things to look at: Examine PHP.ini settnigs to make sure that the sessions settings are being stored in a directory that the apache user has access to (can create files, etc.). Dave -----Original Message----- From: support-bounces(a)drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Leo Burd Sent: Thursday, November 02, 2006 6:10 AM To: support(a)drupal.org Subject: [support] login problems Hello there, I've just installed PHP 5 on my server and now I'm having login problems. My Drupal site is asking me to login again for each page that I go to in my site. It is as if it's "forgetting" information about the current logged in user. If I keep logging in, the site seems to be working just fine. What to do? Thanks in advance, Leo -- [ Drupal support list | http://lists.drupal.org/ ]

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

support November 2006