support

support@drupal.org

7912 discussions

css for autocomplete?
by Laura Scott 20 Apr '06

20 Apr '06

Hi, I've run into a strange problem where the autocomplete drop-down for freetagging on node/add/foo is actually behind the rest of the page elements. In other words, the form labels and fields are on top of the drop-down display. If the fields are opaque, then the drop-down disappears behind the body textarea. I'm not a js adept. I'm trying to figure if the drop-down has css class or id designations I can use to do something like bump the z- index -- or something! I tried to discern what's in the autocomplete javascript, and guessed at an autocomplete class, but adding .autocomplete stylings to the style.css file hasn't seemed to provided any solutions. Thanks. Laura Drupal 4.7RC2 Custom phpTemplate theme Laura Scott President laura(a)pingv.com pingVision, LLC 4450 Arapahoe Ave, Suite 100 Boulder, CO 80303 www.pingv.com 303.415.2559

2 2

Re: [support] 4.6.5 to 4.7RC3 upgrade: successful, but front page is default until users log in
by Kobus Myburgh 18 Apr '06

18 Apr '06

Yes - you can't create "your own account" when you're already logged in. That is the way it is, although personally, I'd prefer that it rather goes to your account instead of that error. As for your problem - you've checked all ideas I had, and that didn't work, so you've obviously got a problem I have not encountered yet, but let's try one last thing: clear your browser's cache and/or view with another browser. If that doesn't help, then I am sorry - hopefully someone else can help who had different scenarios... :-) Regards, Kobus >>> talltim(a)gmail.com 4/18/2006 2:44:27 PM >>> > Something else you can check is caching. Clear your database's cache > table and see if that solves anything? Did that too, with no luck. Also, when I try to "create the first account", I get an access denied at http://sitename.com/user/register. I get this message even when I'm logged in as user 1. Tim -- [ Drupal support list | http://lists.drupal.org/ ]

2 2

Re: [support] 4.6.5 to 4.7RC3 upgrade: successful, but front page is default until users log in
by Kobus Myburgh 18 Apr '06

18 Apr '06

Tim, Something else you can check is caching. Clear your database's cache table and see if that solves anything? Regards, Kobus >>> talltim(a)gmail.com 4/18/2006 2:28:36 PM >>> > I think #2 is your problem. > > HTH > > Kobus Thanks for the reply. I checked the Access Control permissions and node access is enabled for anonymous users so I don't think that's the problem. I'm wondering if it's something to do with Aggregator 2 which I haven't yet re-installed. -- [ Drupal support list | http://lists.drupal.org/ ]

2 1

Re: [support] 4.6.5 to 4.7RC3 upgrade: successful, but front page is default until users log in
by Kobus Myburgh 18 Apr '06

18 Apr '06

Hi, Tim, Here are a few things you can check: 1. That your content is actually promoted to front page (which it seems it is) 2. That your "anonymous user" can actually see content. I think #2 is your problem. HTH Kobus >>> talltim(a)gmail.com 4/18/2006 2:10:21 PM >>> I upgrade from 4.6.5 to 4.7.3 and it seems to have been successful. However, visitors to the site see the default message: "Welcome to your new Drupal-powered website. This message will guide you through your first steps with Drupal, and will disappear once you have posted your first piece of content." This message disappears when users log in. It does not disappear when I post content - the content appears as normal but, on logging out, the default front page appears again. How can I make Drupal realise that it's not a new install? Is there an entry in the database somewhere that I can edit manually? Thanks, Tim -- [ Drupal support list | http://lists.drupal.org/ ]

2 1

4.6.5 to 4.7RC3 upgrade: successful, but front page is default until users log in
by Tim Vaughan 18 Apr '06

18 Apr '06

I upgrade from 4.6.5 to 4.7.3 and it seems to have been successful. However, visitors to the site see the default message: "Welcome to your new Drupal-powered website. This message will guide you through your first steps with Drupal, and will disappear once you have posted your first piece of content." This message disappears when users log in. It does not disappear when I post content - the content appears as normal but, on logging out, the default front page appears again. How can I make Drupal realise that it's not a new install? Is there an entry in the database somewhere that I can edit manually? Thanks, Tim

1 0

func l() or Project Module - Extraneous Data in URL
by Gary (Lists) 18 Apr '06

18 Apr '06

With still plenty of errors, and confusion as to why there is no documentation for the project module, I have gotten the module to a usable state (so long as I don't make projects public, since I'd have to support users when I have no support myself). The one remaining error which I've just discovered is that the Download link for projects points to: /?q=assets/releases/<file_item> Which is completely broken and should be: /assets/releases/<file_item> But the only thing that I've been able to find in the 'project.inc' file is: $links[] = l(t('Download latest release (%version)', array('%version' => $release->version)), $release->path); The value $release->path gets set in the file 'release.inc', here: $dir = dirname($path); and then, transferred to: $release->path = $path; And then later, in the same file ('release.inc'), a Drupal function is called, passing that data: if ($release->path) { $output .= '<small>Download: '. l(basename($release->path), $release->path) .'</small><br />'; } So...if I go and edit the function l(), then that will screw everything else. But it appears that it's getting some bad data in two places, as shown here. What's different about 'project.module' that I would get back this "/?q=" value, and that be wrong? Where should I look to fix this last item before I try to personally use this wonky module? -- Gary

2 2

Project Module - Directory Choices
by Gary (Lists) 15 Apr '06

15 Apr '06

As an aside (and a chide), I think that no module should receive the right of distribution if that module does not contain a community-verified set of documentation. If the author can't explain, then Drupal shouldn't endorse it by delivering it. I have spent 4.5 hours, with 14 open browser tabs to the Drupal site, and I have finally actually gotten the project module to do something. Of all the issues reported and requests for help on the site, there are scant few usable replies, and loads of frustrated folks. (I recently read a review where the author said something like "I'd rather use separate dedicated tools than Drupal's well-meaning but under-delivered modules." While I don't quite agree, I do understand the perspective and the level of frustration that can mount when moving from order to chaos...and freedom. ;) So...now...I've edited the PHP to discover that I can add filetypes (a good thing) and generally it's working, and I have gotten a few dummy projects in place for testing But...I have a few "now I'm working" kinds of questions. Since each individual recipe of modules leads to wildly varying results, let me outline my set-up as it is currently (generally) working: filemanager.module path = assets/files + project.module release path = releases [Yes, gentle reader, you must use trial and error to know that this is relative to the above. No documentation exists.] This also means that actual release path = assets/files/releases issue path = issues [Yes, here we get some clear information that this directory is relative to the 'filemanager' path. A clue that we now must rely on trial and error to determine the 'release' path.] + attachment.module [See more below.] Okay, so now when I place dummy "0.0.zip" files in the releases directory, and update the project releases, the new releases show up appropriately and all seems well. BIG QUESTION: Editing a project shows a list of Attachments, which can be 'hidden'. But this is only if items were created by using 'Attachment'. Is there no similar listing for 'releases' (which were placed manually, and then auto-updated)? It seems strange that I should be able to hide any Attachments, but not be able to hide any Releases. (Also, attachments and actual releases seem like they should live in the same place, a project-specific directory...?) If I use the 'Attachments' button, so that my users can actually upload files, then the do not get updated in the release auto-update. I have experimented with setting the Content Type 'Project' to __disallow__ attachments, but then there is no project release upload ability. So, will I need to provide FTP access to every user, into the same directory!? (I am considering using the FTP.php class to build quick upload system.) Can someone help me reconcile whether I should be using the Attachment (I want that, it's great for the ReadMe.txt file) privilege for the Project Content Type? Must I make my own way for users to submit their releases to this buried directory [ assets/releases ]? What part of this, after this many hours, am I now missing? I feel so close to having it make sense to me, which means it might make sense to a user. Thanks for any guidance. -- Gary P.S. The 'Issues' page -- at Drupal, too -- has the same link on every project: Support Forums with a link to 'forum/18' Is this not configurable? If there __is no forum for support__ for this project, why is the link there? I have nothing at 'forum/18', yet the link still appears. (Users are taken to a blank forum page.) Further, why is the link the same, since I'm looking at a project-specific page, and why is it not the support link provided in the project's entry record? (I don't want to run support forums for everyone else's projects, but I'm happy to link _to_ their support set-up.)

1 0

Drupal 4.7.0 RC2 available
by Steven Wittens 15 Apr '06

15 Apr '06

The second release candidate of Drupal 4.7 is now available. 55 more issues have been fixed since RC1. No known critical issues remain, so unless new major problems arise, this will be the last release candidate before Drupal 4.7.0 final. Please test this latest release, so that 4.7.0 will be a trouble-free ride for everyone. If you maintain a contributed module or theme, now is definitely the time to ensure your contribution works with Drupal 4.7. The Module Upgrading Guide and Theme Upgrading Guide contain a list of all required changes. Make sure there are no last-minute changes that you missed. Drupal 4.7 RC2 can be downloaded at http://drupal.org/files/projects/drupal-4.7.0-rc2.tar.gz. More info at: http://drupal.org/drupal-4.7.0-rc2 Steven Wittens

3 2

Drupal 4.7.0 RC3
by Steven Wittens 15 Apr '06

15 Apr '06

... is out. More info at: http://drupal.org/drupal-4.7.0-rc3 Steven Wittens

1 0

Project Module - Tabs Appear for Each Category?
by Gary (Lists) 14 Apr '06

14 Apr '06

Living intensely with Drupal for 8 hours per day, for a couple of weeks, can really be a joy and struggle. Luckily, the struggles are mostly my own at this point. I've installed the Projects module, and I have -- and wish to remove -- the tabs for every category that I've defined (elsewhere). I can not seem to find a configuration option to turn off these tabs for which there are no projects. This page's URL is <http://accidentaltechie.org/dru/?q=project>, so you can see what I want to remove. I do not understand why no other taxonomy vocabulary shows up there, although others are defined to be applicable to the 'project' node type. These are the taxonomy vocabularies that I have defined, and you can see that each of the three has been set to be applicable to the 'project' node type, but only the first one (Mac Scripting) is delivering its terms to the project page. === My vocab settings... Mac Scripting actionfeed, personal blog entry, book page, forum topic, page, poll, issue, project, story AppleScript (edit term) -- Smile (edit term) ECMA-JavaScript (edit term) FileMaker (edit term) Python (edit term) Smile (edit term) Topics actionfeed, personal blog entry, book page, forum topic, page, poll, issue, project, story Peeves (edit term) Site News (edit term) Web Software personal blog entry, book page, forum topic, page, poll, issue, project, story, topic Drupal (edit term) Thanks in advance for any pointers. (I did read the issues page for the module, and I did not see anything that seemed relevant to this question. I did find a patch that is described as: Here's a patch implementing the second approach. We introduce a configuration option where admins can choose, for each project type,... but I don't think that's what I need...or is it?) -- Gary

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

support