By Kjartan on

The Drupal project has released version 4.3.1 of its open-source content management platform today. There are no new features in this installment, just fixes bugs from the 4.3.0 release.

Drupal: powerful, modular and extensible

Drupal is a full fledged platform for web applications: its flexible, modular architecture can host virtually any type of dynamic website, as is easily adapted to specific needs.

All modules and themes that work for 4.3.0 will work with 4.3.1.

Fixes and changes in 4.3.1:

  • Fixed broken link in forum module.
  • Fixed broken usernames in 'Who's new' block.
  • Fixed error messages not being shown.
  • Fixed incorrect link title in watchdog module.
  • Fixed invalid XHTML in poll.module.
  • Fixed leftover debug statement in story module.
  • Fixed menu glitch in book module.
  • Fixed non-ANSI SQL query in path module.
  • Fixed typo in cloud module.
  • Fixed bug #2617: editing user information does not work.
  • Fixed bug #3900: PostgreSQL problem with locale module.
  • Fixed bug #4055: Added missing break statements.
  • Fixed bug #4080: comments shown against wrong node.
  • Fixed bug #4323: Renamed 'Content-length' to 'Content-Length.
  • Translation fix: made the word 'permission' translatable in the system module' help text.
  • Translation fix: the date in the calendar block could not be translated.
  • Translation fix: the ping module's help text was translated twice.

About Drupal

Since its start in December of 2000, Drupal has grown into an industrial strength dynamic web site platform which allows an individual or community of users to publish, manage and organize a variety of content, Drupal integrates many popular features of content management systems, weblogs, collaborative tools and discussion-based community software into one easy-to-use package.

As an open source software project maintained and developed by a community, Drupal is free to download and use. The source code is available at:

http://drupal.org/drupal/4.3.1/drupal/drupal-4.3.1.tar.gz

Drupal is written for PHP version 4.1 or newer and supports a variety of databases including MySQL, PostgreSQL and MSSQL. More information on Drupal is available from the main Drupal developer site, drupal.org. For a complete list of features, please see the official CHANGELOG.

Comments

hystrix’s picture

hystrix commented

I assume since there are no database changes we can upgrade by simply copying the updated files over the previous versions?

It would seem as though the previous method of update.php as referenced in the Upgrading from Drupal 3.00 to 4.00 and later versions book is no longer relevant to 4.3.x minor upgrades... ?

I apologize if this is mentioned elsewhere, I only installed 4.3.0 a couple of weeks ago.

Anonymous’s picture

(not verified) commented

One would assume I could just log into the web server and pull up the update.php script. But what of my includes/config.php? Should I upgrade it?

I just completed the setup (and I'm quite pleased BTW) however, the doc portion of the site is missing update instructions for the 4.3.x line.

killes@www.drop.org’s picture

killes@www.drop.org commented

There is no need to change anything in your conf.php file. To avoid replacing it with the standard version when upgrading, you should rename the file do e.g. my.site.com.php.

--
Drupal services
My Drupal services

Anonymous’s picture

(not verified) commented

Thanks. I've been looking forward to the fixes :-)

tdebruyn’s picture

tdebruyn commented

Since I have installed my drupal based web site in

web_server/drupal-4.3.0

How do I copy the files from 4.3.1 over before using the upgrade.php script?
The only obvious way I see is, on my PC :

home# tar -zxvf drupal-4.3.1.tar.gz
home# mv drupal-4.3.1 drupal-4.3.0
home# tar -zcvf drupal-4.3.1.tar.gz drupal-4.3.0
home# scp drupal-4.3.1.tar.gz $web_server
home# ssh $web_server
web_server# tar -zxvf drupal-4.3.1.tar.gz
web_server# mv drupal-4.3.0 drupal-4.3.1

I guess this would work, but I don't see this as a very clean procedure...

Tom

killes@www.drop.org’s picture

killes@www.drop.org commented

I don't see why you should need the last step. Be carefull not to replace your config file.

--
Drupal services
My Drupal services

tdebruyn’s picture

tdebruyn commented

The last operation is actually just to show the world that the site is using drupal-4.3.1 ;-)
Note, I haven't actually changed it when upgrading my web site.

I was happy to see that this version would fix forum links (as I have problem with my web site to see the list of all the forums), but unfortunatelly, it didn't help...

http://www.employees.org/~tdebruyn/drupal-4.3.0/?q=forum

is empty and I can't find what's wrong in the taxonomy (as someone suggested me this could be the cause), the "poll" link (sondage) is working fine... weird... it was also working fine with Drupal 4.2.0.

Tom

Anonymous’s picture

(not verified) commented

This is a more simple way (I think). Go to /tmp (or wherever you like) and:

tar xvzf [path to archive]/drupal-4.3.1.tar.gz
chown -R apache-user.apache-user drupal-4.3.1
cd drupal-4.3.1/
rm includes/config.php
cp -Rv --force * [path to your web]/

Cleanup.

killes@www.drop.org’s picture

killes@www.drop.org commented

Replacing all the files should be enough. Do not replace conf.php.

--
Drupal services
My Drupal services

dziemecki’s picture

dziemecki commented

I've actually made a number of code modifications. Is there a list of the files that have changed from 4.3.0 to 4.3.1? I'd like to know what I need to merge before doing a straight file copy.

Thanks,

c0c0c0

Wacky diatribe goes here
killes@www.drop.org’s picture

killes@www.drop.org commented

No there is no such list. Make your own by doing a recursive diff.

--
Drupal services
My Drupal services

dziemecki’s picture

dziemecki commented

This really should be included in any new distro.

Here's what I was able to generate on my own:

index.php
includes\common.inc
includes\thrme.inc
includes\xmlpcs.inc
modules\archive.module
modules\blog.module
modules\book.module
modules\cloud.module
modules\comment.module
modules\forum.module
modules\import.module
modules\locale.module
modules\path.module
modules\ping.module
modules\poll.module
modules\statistics.module
modules\story.module
modules\system.module
modules\user.module
modules\watchdog.module
scripts\code-style.pl
themes\marvin\marvin.theme
themes\xtemplate\xtemplate.theme
themes\xtemplate\xtemplate.xtmpl

There's a couple more that "act" changed in WinDiff, but it looks like it's just white space.

Wacky diatribe goes here
dmjossel’s picture

dmjossel commented

When I first downloaded and installed the final 4.3.0 and began testing it, everything was fine. Last week I downloaded the tarball again, heeding advice that minor fixes were still being rolled in.

All of a sudden, nearly all the 4.3-rated themes weren't working anymore; boxes wouldn't render properly. I finally tracked the change down to a new version of theme.inc, which apparently introduced a new "feature" allowing more flexibility in using CSS in themes. I looked in the forums and the documentation for mention of this change, or how to update the themes to accommodate this change, and came up with nothing.

However, this new "feature" appeared to break just about every theme out there. I put the old theme.inc back (1.149 2003/10/19) and everything was fine again.

So which version of theme.inc is in Drupal 4.3.1?

killes@www.drop.org’s picture

killes@www.drop.org commented

Are you sure you did download the correct version of Drupal? We now have a 4.3-tarball, a 4.3.1-tarball with minor fixes and a cvs-tarball.

--
Drupal services
My Drupal services

Anonymous’s picture

(not verified) commented

I get the strangest error after upgrading...

Note that the value of PHP's configuration option magic_quotes_gpc is incorrect. It should be set to '0' for Drupal to work properly. Either configure your webserver to support .htaccess files so Drupal's .htaccess file can set it to the proper value, or edit your php.ini file directly. This message will automatically dissapear when the problem has been fixed.

Never seen this before. Any idea how to fix this (as I cannot edit my webserver's php.ini) ... I don't see why it wouldn't be reading its own .htaccess, a file which I can see. Why would I suddenly be getting this error, anyway?!

- ray@needmoredesigns.com

Anonymous’s picture

(not verified) commented

My website hosting has magic_quotes_gpc set to 1, so I always got the error message above. Any change to my .htaccess would make my homepage disappear (error 500). On my localhost I can easily set magic_quotes_gpc set=0 in my php.ini. I fixed it all adding the stripslashes in Drupal modules, when needed. For example

if (ini_get("magic_quotes_gpc")) $node->body = stripslashes($node->body);

in the node_save function.

laredo’s picture

laredo commented

Where would I put this?

f (ini_get("magic_quotes_gpc")) $node->body = stripslashes($node->body);

In the actual module?

Thanks

Brian

ax’s picture

ax commented

change these 2 files in 4.3.1 (-: remove; +: add):

index.php:

- check_php_setting("magic_quotes_gpc", 0); 
+ fix_gpc_magic();

includes/commonc.inc:

+ function _fix_gpc_magic(&$item, $key) {
+   if (is_array($item)) {
+     array_walk($item, '_fix_gpc_magic');
+   }
+   else {
+     $item = stripslashes($item);
+   }
+ }
+ 
+ function fix_gpc_magic() {
+   static $fixed = false;
+   if (!$fixed && ini_get("magic_quotes_gpc")) {
+     array_walk($_GET, '_fix_gpc_magic');
+     array_walk($_POST, '_fix_gpc_magic');
+     array_walk($_COOKIE, '_fix_gpc_magic');
+     array_walk($_REQUEST, '_fix_gpc_magic');
+     $fixed = true;
+   }
+ }
+

drupal developers: shouldn't this make into 4.3.x?

laredo’s picture

laredo commented

I have added the above and still get the slashes added, any ideas?

Thanks

Brian

Anonymous’s picture

(not verified) commented

...when drupal.org is browsed with Internet Explorer (mine is version 6.0) the CSS file is loaded at the end, showing the page some seconds as "CSS-less" and then, suddenly, corrected.

This is the trick I use into my website:
just add this line between <head> and </head>

<script type="text/javascript></script>

It works also with a script inside those tags...
I'm sure there will be another method, but I can't find it!
If someone knows it, post it here.

Ciao,
Andrea

zealot’s picture

zealot commented

The flicker of "CSS-less" HTML is connected to the use of the CSS2 @import rule.

Solution 1: don't use CSS2's @import

Solution 2: add a LINK element within the HEAD element
<head>
<link rel="stylesheet" type="text/css" media="print" href="print.css">
<style type="text/css">
@import url(misc/drupal.css);
</style>

Solution 3: As Andrea recommends, add empty SCRIPT tags _before_ all content contained by the BODY element (hence in the HEAD)

kip@tigersfortomorrow.org’s picture

kip@tigersfortomorrow.org commented

Just remember to add the 2nd double-quote after the word javascript.

dziemecki’s picture

dziemecki commented

I just noticed that the node taxonomy is being displayed to the right of the teaser, on this site. Has that been there, all along? If so, where is the setting to enable that? If not, where can I get me some of that?

Wacky diatribe goes here

shane’s picture

shane commented

The taxonomy information next to a teaser is a function of the Theme. I'm not sure which themes support it, but I wrote a custom theme that does the same thing. Simply do:

   if (function_exists("taxonomy_node_get_terms")) 
   {
      if (module_exist("taxonomy")) 
      {
        $terms = taxonomy_link("taxonomy terms", $node);
      }
      $taxo = $this->links($terms);
   }

In your theeme - where ever you would like the taxonomy definition displayed. I have this in my "function node()". I *have not* tested this on 4.3.0 or 4.3.1 - note that core functions often change erratically, so it may not work with anything but 4.2.0. Previous to 4.2.0 - I used:

   if ($terms = taxonomy_node_get_terms($node->nid)) {
      $taxlinks = array();
      foreach ($terms as $term) {
         $taxlinks[] = l($term->name, array("or" => $term->tid), "index");
      }
      $taxo = $this->links($taxlinks);
   }

v/r
Shane

dziemecki’s picture

dziemecki commented

Good info. Thanks!

Wacky diatribe goes here

holz’s picture

holz commented

1. Does Drupal support Flash .SWF files, can I upload a .swf file to Drupal?
2. Will Drupal release out some language packs? I DO need a simp-chinese language.

killes@www.drop.org’s picture

killes@www.drop.org commented

1) Depends. You'd probably need to modify image.module a bit to support swf files. Filestore should handle them just fine.

2) Some Drupal users have supplied translations for a small number of languages. Chinese is not among them. Maybe you can contribute a Chines translation.

--
Drupal services
My Drupal services

arakune’s picture

arakune commented

Hi there,

I have a fresh install of drupal 4.3.1. When I follow the "modules" link under administer->configuration, I receive the following error:

Fatal error: Cannot redeclare import_help() (previously declared in /u2/afs/home/arakune/cp_html/itadakimasu/modules/aggregator.module:5) in /u2/afs/home/arakune/cp_html/itadakimasu/modules/import.module on line 5

Everything else seems to work just fine.

I gather this is a unique problem (I haven't found any similar posts yet), but I wondered if anyone might suggest a fix for a non-coder ;)

TIA!

ax’s picture

ax commented

this is a cvs bug - import.module got renamed to aggregator.module, but import.module not removed from cvs.