Drupal 4.4.0 release candidate

By Dries on 1 Mar 2004 at 22:00 UTC

We are pleased to announce that the first Drupal 4.4.0 release candidate is available. A list of the major changes can be found in the CHANGELOG file. Right now most things are wrapped up, so we'd like you to help polish this release and help iron out final issues: your comments on the stability, correctness and performance of this release candidate are more than welcome!

You can download the latest release candidate at http://www.drupal.org/drupal/drupal-4.4.0-rc.tgz.

This package is rebuilt twice a day, so make sure to download a fresh copy every now and then to get the latest bug fixes. For now, no new features or functionality will be added. Only bug fixes, documentation updates and small usability improvements will find their way into the release candidate and thus into the final Drupal 4.4.0 release. When Drupal 4.4.0 is released, upgrading from the release candidates to the final version should be a breeze.

Installation and upgrading

For instructions on installing or upgrading Drupal, please consult the installation documentation and the instructions carried out by the update.php script. For the most trouble free transition, it is recommended that you first upgrade existing installations to Drupal 4.3.0, Drupal 4.3.1 or Drupal 4.3.2.

Also, please take note that several documents (e.g. INSTALL, CHANGELOG, etc.), modules (e.g. import module) and themes (e.g. UnConeD and Marvin) have been renamed or moved to the contributions repository. It is recommended that you (temporarily) remove these files before you run the upgrade script.

Developer information

Developers should be aware that custom themes and modules for Drupal 4.3.0 need to be updated to work with Drupal 4.4.0. If you maintain a theme or module in Drupal's contributions repository, this is the perfect time to make sure your code is up to date. A list of changes with Drupal 4.3.x can be found in the Module developer's guide and Theme developer's guide.

The DRUPAL-4-4 CVS branch will be created soon so we can pick up active development on new features. In the meantime all Drupal contributors are encouraged to focus on the pending bugs as well as the documentation.

Update, March 6, Dries: I just created the DRUPAL-4-4 branch meaning that the HEAD branch is opened up again for development. The Drupal 4.4.0 release will be pulled from the newly created DRUPAL-4-4 branch after it have proven to be stable.

Update, March 14, Dries: please remind that the DRUPAL-4-4 branch is available for use in the contributions repository. If you have updated your module/theme to work with Drupal 4.4.0-RC please branch appropriately. Updated themes and modules are available from http://drupal.org/project/releases/4.4.

Comments

4.3.2 xtemplate to 4.4.0?

randybrown commented 2 March 2004 at 00:39

I'm using the 4.3.2 version of the xtemplate theme with a 4.3.2 install. If I update to 4.4.0, what changes will I need to do prior to the system working again? Or will 4.4.0 work with the 4.3.2 xtemplate until I get time to update to the 4.4.0 version fo xtemplate?

Thanks.

Pedalopolis :: Pedal Power in the Miami Valley

Drupal 4.4.0 Xtemplate theme

Dries commented 2 March 2004 at 18:14

The Xtemplate theme still works as illustrated here on drupal.org, though it has been subject to significant changes since Drupal 4.3.0. If you haven't modified your local copy, the Xtemplate theme should continue to work after the transition to Drupal 4.4.0. Nonetheless, you'll want to revisit the Xtemplate's configuration page to ensure everything is still configured properly.

500 Error Still in 4.4.0.rc

ti commented 2 March 2004 at 02:16

This bug I reported (and mathias fixed via a patch) for the cvs version of Drupal 4.4.x is still present in the downloaded version of Drupal 4.4.0.rc. The patch still works to fix it, though. Just thought I'd let you guys know about it.

404 handling

Dries commented 2 March 2004 at 18:18

While that patch might fix with your specific problem, it is not the proper solution. I won't commit that in its current state.

(It looks like you are mixing up 404s and 500s: 404s are 'page not found' errors, 500s are 'internal server errors'.)

status codes

bertboerland commented 2 March 2004 at 19:06

see also the status codes in brief or the full rfc (2616)

--
groets

bertb

--
groets
bert boerland

My observations

joe lombardo commented 2 March 2004 at 10:24

As always, thank you for developing a phenomenal system! To help get this released, i've installed and tested it locally. Here is a running log of what I found.

The update.php tells me to make a few changes to my database directly, but then running the update scripts seems to try the same changes.. and fails. (1)
My theme, a modified interlaced theme doesn't work. This makes viewing the update pages impossible without editing the database. The instructions might need to say, "change the administrators theme preference to 'chameleon' before starting the upgrade process."
I always forget to log in as admin before starting to upgrade and find myself disabling the check in the update.php file. To fix, I should probably start drinking herbal teas.
I am getting an error while trying to login (2), that appears to be theme related.
old themes, ie. marvin and unconed, still in the themes directory will throw errors. Administrators should be told to remove unwanted themes.
chameleon is a pretty theme :-)
What modules take advantage of the new file api?
The breadcrumb trail and the URL path don't always match.
I think the feature making it possible to add context-sensitive help to all pages is great.

(1) - user error: Duplicate column name 'throttle'
query: ALTER TABLE system ADD throttle tinyint(1) NOT NULL DEFAULT '0' in C:\Program Files\Apache Group\Apache\htdocs\includes\database.mysql.inc on line 97.

ALTER TABLE {system} ADD throttle tinyint(1) NOT NULL DEFAULT '0'
FAILED

(2) warning: init_theme(): Failed opening '' for inclusion (include_path='.;C:\Program Files\Apache Group\Apache\;C:\php\pear;C:\php\') in C:\Program Files\Apache Group\Apache\htdocs\includes\theme.inc on line 51.

Joe Lombardo | joe@familytimes.com | FamilyTimes Online Journals

patch ?

felixz commented 2 March 2004 at 14:05

You guys going to provide a patch from 4.3.2 ?
I dont mean it is neccessary for the release candidate but for final release ?

I made a few changes and i am going to need help to merge them with new drupal code.

Felix Zaslavskiy
felix[at]bebinary.com
http://www.zaslavskiy.net/

Drupal 4.3.0 to Drupal 4.4.0 patch

Dries commented 2 March 2004 at 18:30

We've not been providing patches in the past but I could create one for you. Of course, if you're familiar with CVS, patch or diff you could easily create one yourself. The problem with such patches is that they are rather large. For example, not taking into account the new themes and modules, a diff between Drupal 4.3.0 and Drupal 4.4.0 makes for a 925K patch (55 files changed worth 6152 insertions and 6547 deletions).

Well if its just for me maybe

felixz commented 2 March 2004 at 20:19

Well if its just for me maybe its not such a good idea.
I can certainly use diff to generate a patch.

I thought if others request it then it may be a good thing.

Felix Zaslavskiy
felix[at]bebinary.com
http://www.zaslavskiy.net/

Another unfixed bug

eap1935 commented 2 March 2004 at 19:01

Permissions for viewing a user's blog are still broken in the RC. i.e. in the RC, when viewing a user's profile, the appearance (or not) of the "view recent blog entries" link depends on the "maintain personal blog" permission of the user viewing the profile, not of the user whose profile is being viewed. This is not correct.

This is addressed in http://drupal.org/node/view/5965, and needs to be fixed in the user_access() function of user.module. image.module and other modules that display links in user profiles are also affected.

I played around for about half an hour and couldn't find anything else obvious. Looks good.

Oh, except one thing. I use the blog module quite a bit, and one thing I've noticed is that when viewing a particular user's blog, the breadcrumb does not include a link to all blogs. There's just a link home. I think the breadcrumb should include a link to all blogs, but I've never bothered to submit a bug report. Small thing, but hey, you asked.

birthdate

deekayen commented 4 March 2004 at 10:45

I don't know what version drupal.org is running, but I noticed a bug in the birthdate display for my account. If I click the my account link after I login, I see October 24, 1980 as my birthdate, which is incorrect. I clicked edit account to fix it and it had the correct birthdate, October 25, 1980. The page that displays the account info is one day off.

You probably need to change y

killes@www.drop.org commented 5 March 2004 at 19:48

You probably need to change your personal time zone setting.

--
Drupal services
My Drupal services

Same birthdate problem

jcosters commented 25 March 2004 at 13:20

I'm running 4.4.0-rc and am having the same problem: birthdate is shown 1 day off while it is set right in my account settings.
The timezone in my account is the same as the global site timezone.

I've added a bug report about

Boris Mann commented 27 March 2004 at 03:14

I've added a bug report about this.

Problem with links & xtemplate theme

davidm commented 6 March 2004 at 00:39

Hi,

I have a number of sites that put a lot of different categorizations on each resource. I notice that for some reason this makes it impossible to click on leading links, starting with username and sort-of until the last line of links, in the node header when it is displayed. This problem manifests in tested browsers including IE 6 and Galeon/Mozilla, although I'm told not for Mac users using IE or Firefox (but with the Epiphany browser.. must be a Gecko version thing).

I have reduced the problem down to its core with latest CSS from the 4.4 RC at http://www.zooid.org/~vid/drupal-css-cantclick/. Without the CSS, the links are all clickable. http://www.zooid.org/~vid/drupal-css-cantclick/canclick.html ...

Is anyone else seeing this problem and is there a solution, besides reducing the number of links? I am not a CSS crafter, and wouldn't know where to jump into the Drupal dev to try to fix this.

Thanks!

David

Theme specific or not?

Dries commented 6 March 2004 at 10:11

David, I notice you are using the pushbutton template. Can you reproduce this behavior with say, a chameleon theme or with the default xtemplate template? Either way, it is better to create a bug report for this. Thanks.

Still happens with default xtemplate, not with chameleon

davidm commented 8 March 2004 at 01:05

Yes, it does. In fact, I had noticed this problem in xtemplate/the last release of Drupal (4.3).

I'll file a bug report... I already put some work into using xtemplate/pushbutton as a base.. but is the easiest solution to use Chameleon instead?

i fingered it out

heather commented 8 March 2004 at 03:10

that's going to happen with any theme you try because the problem lies not in the CSS- it lies in the HTML.

the problem is the span tag used to wrap the taxonomy list. span is an in-line element. you'll notice, if you look at your examples closely- you can click on any link that is not 'stacked' under or over another. if there is a link below, you can't click it. try resizing the window to see what i mean.

you'll have to use a div tag for that purpose.

and if you don't want it to act like a block element, try using
display: inline; in the taxonomy class.

hope that helps.

Great!

davidm commented 8 March 2004 at 03:19

Thanks for figuring this out, I hope it can be applied to the CVS version now as I'd like to stick with an xtemplate base.

David

Thanks

Robert Castelo commented 8 March 2004 at 10:41

Well spotted Heather, thanks.

David, have you created a bug report for this problem?

I'll submit a patch for xTemplate default/pushbutton this evening, if no one beats me to it ;-)

---- The Pushbutton Template Test Experience ---->>

------------------------------------------
Drupal Specialists: Consulting, Development & Training

Robert Castelo, CTO
Code Positive
London, United Kingdom
----

Worked For Me!

JoeCotellese commented 7 March 2004 at 03:51

Great Job Guys! I upgraded from 4.2 without any difficulties. I even migrated my site to an Xtemplate base theme. It was much easier then I expected.
www.clearstatic.org

worked for me too

cel4145 commented 7 March 2004 at 15:42

Same here. I took my my personal blog, cyberdash.com, and upgraded from 4.2 to 4.4.0-rc. I also took the theme design which was not xtemplate and ported it to xtemplate. The changes to xtemplate certainly made this very easy and also enhanced some of the things I could do with the design.

Great release!

Clean install upgrade

RobCamp commented 7 March 2004 at 14:56

Decided to try an upgrade on a clean install. Initial install performed by Cpanel/Fantastico script to 4.3.2 Before installing I went in and removed themes marvin and unconed.

3 problems encountered:

1) Doing a mass over-write of files also over-writes the conf.php file in the includes directory. I always wondered Drupal was storing DB usernames and pw's - now I know. Unfortunately, the Fantastico script uses a different user naming style to allow for the shared hosting environment AND it creates random passwords that cannot be looked up elsewhere afterward. Once I overwrote the conf.php file (yeah, I know, back-up first) the username and password were history.
Advice - remind people who are upgrading to ESPECIALLY back up the conf.php file, or don't include it at all, as it doesn't seem to have changed from 4.3 to 4.4 anyway.

2 and 3 - Got the same problems as Joe Lombardo #1 and #4. #1 didn't cause any problems - no harm no foul. #4 went away as soon as I went into config and activated the Chameleon and Xtemplate scripts, and made Chameleon the default.

Now - have to check what kind of taxonomy display possibilities there are. I really wish that either:
1) The forums module would properly display entries that appear in 2 or more nodes (when the taxonomy is defined as "multiple") when displaying its taxonomy
or
2) The taxonomy module would work like the forums page display and show the child nodes.

Time to play a bit...

Rob

Follow-ups on Taxonomy

RobCamp commented 7 March 2004 at 17:46

You can see the following on my playground account at:
http://germancarclubs.com/autos (no need to create a user ID - anonymous should see it too)

There is an overlap between using the taxonomy module and the forum module that will cause confusion with users:

Start by going to
http://germancarclubs.com/autos/forum
If you then select Porsche 1.1, and then either of the two messages there, you will of course see the contents of the message.

Now notice the links across the bottom of the message. You see BMW1.1 AND Porsche 1.1 because the message was added to both terms when it was created. Let's put that problem aside for a moment though because:

When a user clicks on either of the links (porsche 1.1 or bmw 1.1) they are taken to the TAXONOMY page view of the terms (not the forum page view).

Here the breadcrumb path is handled differently, particularly if you try to go up a level. Because the term BMW (or Porsche) has no messages of its own, it is simply a blank content area - unlike it wsa in the forum page module where child terms were also displayed.

This will confuse users.

Ideally, the Forum term tree page would be updated to work off the term_node table so it would select all the nodes for each term, instead of reading a single value NID from teh forum table. Then the forum node display could be updated to have each node point to the forum term display page for that term, and everything would be in sync.

I know this problem was in previous versions as well - my guess is that no-one is going to consider this a bug to 4.4 - but maybe it coudl be a feature list item for a future release OR someone will create an alternate form of the forum module to address it.

Rob

Named anchors in nodes still not working

cheema commented 8 March 2004 at 06:12

Outside of Drupal I use named anchors in a single document like this:

<a HREF="#A1">This is a test</a>

<a NAME="A1">Testing 123</a>

And they work. Under Drupal however they dont.

When I hover my mouse over one of the links I see that it is pointing
to: http://hostname/drupal/#A1 when it should be pointing to:
http://hostname/drupal/node/view/11#A1

It also seems that other people are seeing the exact same problem
without a resolution. See:

http://drupal.org/node/view/2880 and

http://drupal.org/node/view/4213 (last comment on the page)

Base URL

Dries commented 8 March 2004 at 08:11

This is due to the fact that Drupal uses a base URL. Links should be relative to the base URL, not to the active or current URL.

This is very annoying

anarcat commented 24 March 2004 at 17:27

Indeed, this is a big problem when you want to create anchors using filters where you don't have access to the node data. I implemented a footnotes filter that needs to use #stuff anchors, and I needed an horrible hack where I access $_GET['q'] in order to get the proper url. The hack also doesn't work on alias pages. Is there a better way to do this?

Emitting links

Dries commented 24 March 2004 at 18:54

You can emit proper links/anchors using Drupal's built-in url() or l() functions. These functions take care of differences between Apache and IIS and adapt to the value of 'clean URLs'-setting.

theme

rakhmat commented 8 March 2004 at 07:18

i have just set up my site Footprints of my life, using RC 4.4.0 drupal , and i want to change how it look ,:? what file do i have to use or change?

Documentation

Dries commented 8 March 2004 at 08:16

This is covered briefly in the INSTALL.txt and the theme developer's guide. To switch theme or to configure your theme, head on to administer > configuration > themes.

Administrator theme configuration

Reko commented 9 March 2004 at 18:53

Hi,

I think you should change the theme configuration page so that the 'default' option is a >select< dropdown box like before, not a radio option spread across entries...

I've had an eye on Drupal for some time, and it really does stand out where the other CMS's don't - absolutely bloat free.

I've just installed 4.4.0RC, and apart from the theme interface, it really looks great.

Good luck with Drupal 4.4.

Oh, and one piece of advice: Drupal is great because it's so bloat free, unlike all those other CMS's out there - let's keep it like that.

I'm not saying anything you've done anything to make it bloated, but watch out, you have to be careful - or you might, and suddenly realise it when it's too late.

secret is in the cache

duntuk commented 11 March 2004 at 02:39

the increasing trend now is caching, i.e. making static pages out of dynamic (which is updated at specific time intervals, instead of on each request)...

as a result, in the near future even the most bloated CMS or Portal systems will be as fast as static pages...

so it's gonna get interesting...

Bloated CMS Speed

Brian@brianpuccio.net commented 11 March 2004 at 03:05

I don't think blaoted CMS'es will ever be fast. I think they will become bigger and heavier, which is fine for people with an online community of 5 on a shared server, but for something that scares to a signifcant userbase, the blaoted CMS will die. This is where Drupal will shine.

How to enable "Book" link in blocks or Primary/Secondary links

Donovan commented 14 March 2004 at 08:38

How does one go about adding/enabling a "Books" link like the one in Drupal 4.3x? The only visible link to books seem to be the links to pages that are published. I want to have a "Books" link that will create a page with links to all books -- just like in v4.3x. I have searched for a solution, but cannot figure out how to do this. I have tried both the 4.4 RC1 and Drupal CVS. Any help is appreciated.

"It always seems impossible, until it is done."
- Nelson Mandela

A problem with book navigation

joel_guesclin commented 16 March 2004 at 08:35

This seems to be due to a bug. I notice that in my list of blocks there is one called "book navigation". However, despite the fact that I have it checked, nothing of the kind appears...

Help would be appreciated on this

Book navigation block

Dries commented 16 March 2004 at 09:25

The 'book navigation' block will only show up when looking at a book page (through the book module). Try visiting http://yoursite/book/ or http://yoursite/book/nid where nid is the node ID of a book page.

Which I guess solves the problem mentioned above...

joel_guesclin commented 16 March 2004 at 14:00

If Donovan goes to http://yoursite/book then this will produce a list of books - which seems to be pretty much the same as in 4.3. In order to get this appearing like it used to in 4.3 I have found the only thing to do is to set the theme to Xtemplate and then use "edit primary links" and stick the URL in there. This seems rather a backward step though, to have to fiddle around like this rather than just have the link there by default.

Going to http://yoursite/book

Donovan commented 17 March 2004 at 06:07

Going to http://yoursite/book (in my case http://donovan-dillon.name/home/book --temporary URL) results in:

"error 404: File not found
The document you requested is not found."

I ultimately followed Dries' recommendation to use the Marvin 2K XHTML template in order to get a 4.3-like link set at the top of the page. This works as advertised, and the book navigation block does appear once a book is selected. This works reasonably well; however, what I would prefer to see is the following:

(1) Book Navigation block initially displays a list of all books (this would be identical in operation to the Blogs block which displays a list of all Blogs)
(2) When a book within the Book Navigation block is selected/clicked, the block then behaves as a book navigation aid (per the current design)
(3) Ideally, only "public" Books are displayed in #1 above -- this might require a "public/private" option on the create content/book page form

Is this doable? Is it possible to modify the Book Navigation Block code to affect this operation? Drupal 4.4 is awesome, but I believe these changes would enhance it even further.

Donovan.

"It always seems impossible, until it is done."
- Nelson Mandela

Here's a hack solution for chameleon

joel_guesclin commented 18 March 2004 at 09:50

Actually, I liked the old Marvin theme (very clean) and wanted to use the new Marvin theme in Chameleon (very fast). But where had my nice links menu gone? This menu allowed me to go direct to books, events, and also static pages whose link I could define.

Well, I've frigged about a bit and discovered that in chameleon.theme there is a function called chameleon_page, and in that function there is a line that reads:
$output .= theme("breadcrumb", drupal_get_breadcrumb());

If you replace this with:
$output .= theme("links", link_page());
then you get your links back...

Might help

Thanks Joel. I tried your su

Donovan commented 20 March 2004 at 20:42

Thanks Joel. I tried your suggestion, and it worked .. sort of. The links are back -- on every page except the home page! Any suggestions on how to remedy this?

"It always seems impossible, until it is done."
- Nelson Mandela

theme_page()

Dries commented 21 March 2004 at 07:20

Put that code in the _page() function of your theme, just above the code that prints the breadcrumb trail.

Thanks Dries. This worked li

Donovan commented 21 March 2004 at 17:50

Thanks Dries. This worked like a charm after a bit of experimentation to figure out that I needed to place the $output .= theme("links", link_page()); statement outside of the if (..) statement.

"It always seems impossible, until it is done."
- Nelson Mandela

This works great with Chamele

Donovan commented 22 March 2004 at 01:18

This works great with Chameleon; however I prefer the layout and look of the default Xtemplates theme, but would like to get the links back. How would I accomplish this same effect with the Xtemplates theme? I looked for similar code (i.e., "the code that prints the breadcrumb trail.") but found none. Any suggestions are appreciated.

"It always seems impossible, until it is done."
- Nelson Mandela

Check the patch I submitted

shane commented 23 March 2004 at 23:15

I submitted a patch to the XTemplate theme that fixes this. The patch creates a new XTemplate template hook called "{menu_links}" which when placed somewhere in the *.xtmpl file will call output the original Drupal Menus. See:

http://drupal.org/node/view/6518

For more details. I personally commented out the "secondary links" in my *.tmpl file and replaced it with the "menu_links" call.

v/r
Shane

Thx Shane. Now, I searched t

Donovan commented 25 March 2004 at 04:47

Thx Shane. Now, I searched the site really hard to avoid asking this newbie question, but I could not find the answer. So here goes: I applied the patch using SSH (Putty) and received an error. The executed command, and error message are:

u36103342:/kunden/homepages/38/d97894505/htdocs/home > patch -p0 -u < xtemplate.theme-menu_links_0.patch

patching file themes/xtemplate/xtemplate.theme

Hunk #1 FAILED at 171.
1 out of 1 hunk FAILED -- saving rejects to file themes/xtemplate/xtemplate.theme.rej
u36103342:/kunden/homepages/38/d97894505/htdocs/home >

What does this mean, and how do I resolve it? For what it's worth, my Drupal installation is hosted on a 1and1.com server.

Thx,

Donovan.

"It always seems impossible, until it is done."
- Nelson Mandela

Next Link on Book Module

Jhef.Vicedo commented 25 June 2004 at 11:10

Im having a problem on the url of the next navigation of the book module.

If the current book page has no direct child, the url of the next navigation is any parent on that level or should i say that tree upward.

So, when I browse that tree, I am just circling around it and not able to go to the next of the next level.

jhefmv [at] gmail [dot] com
Work smarter, not harder!

Image.module

dokks commented 15 March 2004 at 12:09

So far the 4.4 RC is working wonderfully on my system. I removed the old install and installed from scratch into a new DB. The intention was to recreate any conent.

The only issue I have encountered is no image support. Isn't about time this became an integrated part of Drupal?

The Ravens Myst at the White Tower

True dat

Euan-1 commented 16 March 2004 at 03:15

Hell yeah!

I third

ti commented 16 March 2004 at 15:39

Dokks, I made a wishlist of three things that Drupal should do out of the box. One of them is image handling.

Highlight the instuctions about deleting themes (UnConeD, etc)

voipfc commented 17 March 2004 at 03:37

Hello Dries,

It seems that your instructions to delete some of the themes is being overlooked by a lot of upgraders, myself included.

I suggest you highlight that section in bold or in red so they are not overlooked

Regards

Bug using localization

joel_guesclin commented 18 March 2004 at 12:43

I have the locale module switched on. Everything going fine until I tried creating a static page. It all seems to work ok, except that I get this message across the top:
user error: You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near 'FROM locales WHERE string = 'Home'' at line 1
query: SELECT lid, FROM locales WHERE string = 'Home' in C:\Apache\Apache2\htdocs\drupal-cvs\includes\database.mysql.inc on line 97.

When I switch off the locale module, the message goes away.
The only page I get the message on is the static page when I go to look at it.

Look forward to seeing a fix...

yes, i noticed it too. it's a

merlimat commented 19 March 2004 at 09:39

yes, i noticed it too. it's a bug because of the
SELECT lid<b>,</b> FROM locales WHERE string = 'Home'

looking at the locale.module it seems that the query should be SELECT lid, COUNTRY_CODE ...
so maybe the language code isn't set by default.
Another thing: is it possible to take the default language for the user from the browser language info?

Matteo Merli

Internationalization

joel_guesclin commented 24 March 2004 at 12:43

The Internationalization module has something like this, recognition of the browser language...

bugs in queue and "edit account" ?

NFW-1 commented 19 March 2004 at 10:19

When I (using my "administrator" account) go to accounts and choose an account to edit, the name on the account is always "administrator."

When I (as admin or a regular user) go to the submission queue and pick an item, I'm taken to a page that shows two copies of the submitted item, with a comment form below.

Are these bugs?

Thanks...

Are you using Mozilla?

moonfire commented 19 March 2004 at 15:28

I had this problem when I accidently said "fill in forms" or "passwords" (I can't remember) in mozilla, netscape 6, and galeon. Basically, the work around is to not save passwords/form values on a drupal site. In a perfect world, they would change the name of that field so it wouldn't autopopulate through those. But since I never submitted a bug, I don't deserve to complain. :)

Search function problem

Donovan commented 22 March 2004 at 01:24

I have noticed that the 4.x.x/CVS Search function only returns matches to User names. That is, the only time the function returns a match is when I am searching for a user name; but never for other text anywhere on the site. I don't know if this is a bug, or if there is a configuration option that I might have missed.

"It always seems impossible, until it is done."
- Nelson Mandela

Fresh install of 4.40 RC error

fredb86 commented 24 March 2004 at 17:30

Did a new install of 4.40 RC. Everthing appears to function ok, but I get this error when I submit articles:

user error: Access denied for user: 'username@localhost' to database 'mydrupaldatabasename'
query: LOCK TABLES sequences WRITE in /www/mydrupalsite.org/drupal/includes/database.mysql.inc on line 97.

Running FreeBSD and Mysql 4.0.18 and PHP 4.3.3 CGI

That isn't a Drupal error

lineman commented 25 March 2004 at 11:56

user error: Access denied for user: 'username@localhost' to database 'mydrupaldatabasename'

You need to give your database user LOCK/UNLOCK priveledges for that database. There is a workaround for this, but the LOCK feature is important so that you don't have tables getting written to by multiple people at the same time. If you run a site that more than one person will be submitting content, you will definitely want to give your database user this priveledge.

usability notes & review

anarcat commented 26 March 2004 at 15:26

I installed the RC with a non-geek friend and I have a few notes to tell about the current interface. This applies to 4.4rc, but I doubt it will make it in the release, so this might be better implemented in 4.5.

Having Adrian's install module builtin Drupal and working is critical. Right now, installing Drupal is near to impossible for non-geeks and quite hard for people used to it. The main reasons:
1. You need to modify a PHP file with obscure parameters and syntax (for newbies), even though the INSTALL file documents this well. The install module should take care of this.
2. You need either shell access or phpMyAdmin to create the database. I think this is solved by the install module.
3. Installing contribution modules is pretty hard: not only do you need to install the module in the proper place (modules/foo.module or modules/foo/?), but you also need to use the hack above (shell or PMA) to load the custom table for the module. I also think this is solved by the install module (if it's not, it should be).
In the taxonomy administration: "To delete a term choose "edit term". To delete a vocabulary, and all its terms, choose "edit vocabulary"." This sounds *so* wrong. There should be a delete button. I don't feel like reading a whole paragraph when I'm looking for a delete button. To delete a term, I'd naturally choose a link named "delete term", not "edit term". I think there are a few places like this in Drupal where "delete" is hidden in "edit", very annoying.
There is no clear way of getting rid of the "welcome message" that shows up on the frontpage when no node is published. The message should say that it will disappear when content is published to the frontpage.
Language issues: it's not clear at all how to install a new language in Drupal. I have the advantage of having another Drupal installed where I could steal the locale dump, but in general: .po file or SQL dump? How would a newbie install *that*?? (What's the status on .po support in Drupal anyways?)
Creating a user in the admin interface doesn't hide the password.
The administration menu is deep and complex. "Administer"? "Configuration"? All the same to me. I have a hard time understanding why the modules configuration (in admin/system/modules/node) is apart from the module's *settings* (in admin/node). This is confusing and hinders usability IMHO. I would drop "configuration" menu altogether and at least bring the modules, blocks and filters menus to toplevel. I would also move upwards all the modules configuration stuff. So the workflow would be:
1. enable a module "foo" in admin/modules
2. configure the module *only* in admin/foo (maybe admin/modules/foo would be acceptable here, *but not both*!!!)
3. enable the relevant blocks in admin/block
4. enable the relevant permissions in admin/user/permissions
The thing is: if the menu gets too deep, it's too hard to look for a particular setting. *I* know where to look, since I've been using Drupal for over a year, but someone installing Drupal for the first time would have a hard time figuring all this out.
Having "hover-expanded" menus would be nice too.

All this didn't strike me as much as last night when I scrambled to install Drupal in the least time possible, trying to explain what I was doing along, with a newbie. Should I make feature requests out of this?

great observations

ax commented 26 March 2004 at 18:19

i agree, more or less, with all of them. and yes, please make this feature requests (or tasks?) to not forget about them.

Install Scripts

RobCamp commented 26 March 2004 at 21:31

Has anyone ever inquired into how the Cpanel group makes the installers for its Fantastico themes ( http://www.cpanelthemes.com/fantastico.php )? That's how I installed Drupal the first time, and it was smooth as silk. Their installer is a two-step process, the first setting up the files, the second creating and pre-populating the database. If anyone has contacts into the Cpanel team there might be some good insights on how to make an easier installer.

Rob

Message on frontpage

Steven commented 26 March 2004 at 22:29

"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."

Come again? :)

l()-function adds on incrementally(?).

gynther commented 28 March 2004 at 11:15

Hi.

I've just upgraded our LUG-site from 4.2-rc to 4.4-rc and overall it works great. However the navigational links supplied by Drupal gets extra data 'tagged' on for each page you visit. It's kindof hard to explain but if you go to http://web.karlstadunix.nu and navigate using the 'Forum topics' block you'll see what I mean.

I'm kindof new to this so if there is anything I have missed to read please point it out to me. Any help in this matter is greatly appreciated.

//Christian Gundersson
http://www.karlstadunix.nu/

Works without clean URL:s

gynther commented 28 March 2004 at 13:56

I tried turning off clean URL:s and the navigation worked. So somehow the cleaning of urls never resets the data from before. Anyone else having this problem?

//Christian Gundersson
http://www.karlstadunix.nu/

Installation issues with 4.4rc

BryanPflug commented 29 March 2004 at 20:51

Just made a run at upgrading from 4.3.2 to 4.4. Ran into a few minor issues detailed below. Would submit these as issues via create content -> issues but pick list does not yet allow submission of issues under 4.4rc (seems like a chicken and egg problem for release candidates). Please clarify where you want these submitted in future release announcements. In the meantime, here are my findings:

Ran update script for database, but instructions had confused me – Based upon the way they were written, I thought I had to manually add fields bootstrap and throttle to system table, which I did in advance of running the script. Appears that script then attempted to do this as well, and generated errors when it failed. However, the rest of the upgrade steps appear to have worked, so hopefully this won't cause problems
I uploaded the source over an existing directory. As a result, gworks was still in the directory structure. When I then tried to first run Drupal after the upgrade, I got an error. I deleted the gworks theme and that cleared things up.
My custom site logo now has a red border. Not immediately apparent where to change this - using xtemplate system, and css logo style doesn't appear to have changed. Not an HTML expert, and this is making for a really UGLY site at the moment. Suggestions?
My block settings were all on the right for 4.3.2, now on the left. Easy to change, but thought you should know, as some will probably whine about this.
Had to re-enter the default email value under configuration main page. Not sure why, but thought you should know, as I just stumbled on this, and it may cause problems if people stop getting some notifications due to this but don't know
I had a value for 'mission' under the previous release. This did not carry over under xtemplate but it still exists under the main configuration screen. Seems like there should be one place to enter this or people will be confused. I know I am.

Nevertheless, not bad for first run at this.

Articles

nazadus commented 4 April 2004 at 00:01

In version 4.3.2 I was able to get to page that had the latest additions and listed the possible categories to select, which would contain my information. How do I get to this in 4.4.0?

-----------------
"Our greatest glory is not in never failing but in rising every time we fall." -- Confusious