Drupal

Drupal 6.5 and 5.11 released

By BXTra |
Drupal 6.5 and 5.11 released, fixing security issues More information can be found -> HERE Drupal 6.5 and Drupal 5.11, maintenance releases fixing problems reported using the bug tracking system, as well as critical security vulnerabilities, are now available for download. Upgrading your existing Drupal 5 and 6 sites is strongly recommended. There are no new features in these releases.

Drupal 5.9 released

By BXTra |
Drupal 5.9 released, fixing security issues Drupal 5.9 has been released to correct a vulnerability that was inadvertantly left in Drupal 5.8 Drupal 5.9 Release Note The ninth maintenance and security release of the Drupal 5 series. Only fixes for security vulnerabilities and other bugs have been committed. New features are only being added to the forthcoming Drupal 7.0 release. This release fixes a security vulnerability. Sites are urged to upgrade immediately after reading the security announcement: * SA-2008-046 - Drupal core - Session fixation In addition to this security vulnerability, the following bugs have been fixed in the 5.9 release: * #281042 by schuyler1d. Render blocks before CSS and JS header generation. * #232433 by Damien Tournoud. Use non-localized date for RSS. * #281494 by beeradb. Code style. * #252580 by Robert Douglass, Gerhard Killesreiter, flobruit: avoid division by zero, when all search weights are set to 0. * #252921 by David_Rothstein and agentrickard: remove unused join, which caused column type compatibility problems with postgresql; improves postgresql compatibility. * #128846 by takashi, chx, bdragon, wedge, salvis, Shiny: rewritten queries on PostreSQL need to have matching DISTINCT ON and ORDER BY expressions * #280934. Make sure session is always regenerated.

Drupal 6.3 and 5.8 released

By BXTra |
Drupal 6.3 and 5.8 released, fixing security issues More information can be found -> HERE Drupal 6.3 and Drupal 5.8, maintenance releases fixing problems reported using the bug tracking system, as well as security vulnerabilities, are now available for download. Drupal 6.3 also includes some changes to the installer to prevent file ownership issues on shared hosts; upgrades jQuery to version 1.2.6; improves PostreSQL compatibility; fixes performance issues in search, menu and form API and contains a variety of other small improvements. It should also be noted that the Views for Drupal 6 release candidate requires Drupal 6.3 to run properly.

Drupal 6.2 fixing security issues Released

By BXTra |
Drupal 6.2 is now available HERE Drupal 6.2 Release Note This release fixes security vulnerabilities and also changes APIs. Sites are urged to upgrade immediately after reading the security announcement: * SA-2008-026 - Drupal core - Drupal core - Access bypass In addition to this security vulnerability, the following bugs have been fixed since the 6.0 release: * #228120 by jvandyk: typo in documentation in comment.tpl.php * #226480 by gpk: fix wording on when node access rebuild button is displayed in node_configure() * #229817 by mcarrera: l() attributes were not properly specified in theme.inc's theme_username() * #234403 by alienbrain: PHP.net documents we should use CRLF in mail headers, so do that * #226555 by jvandyk, Rok Zlender: fix notice level error in xmlrpc.inc * #204415 by chx: actually use 'administer content types' permission for node type editing instead of 'administer nodes' * #234699 by hass: theme_link() did not mark frontpage links active properly * #237717 by hass: missing t() in system_clear_cache_submit() * #232037 by pwolanin: (performance) block regions should only be populated when called for, not in all cases (fixes performance expectation on 403/404 pages) * #226728 by chx: (performance) temporary cache table entries were not flushed, causing cache_menu and cache_form to grow big * #231587 by pwolanin, killes: (performance) use two level cache in menus, instead of storing very large amounts of data multiple times * #239196 by jvandyk and myself: missing status check on nodes in search indexing counter * rolling back #234403 by Bevan and damz: we should keep using LF in mail headers, without CR, CRLF causes problems * #238564 by scor: two missing t() calls in update.module * #241629 by solotandem: dblog module left one more row in, when cleaning up in cron * #244597 by kbahey: remove cruft from user_login(), that added extra message to the form was never used or displayed

Drupal 6.1 fixing security issues Released

By BXTra |
Drupal 6.1 is now available HERE Drupal 6.1 Release Note This release fixes security vulnerabilities. Sites are urged to upgrade immediately. For more details, please see the security announcement: * SA-2008-018 - Drupal core - Cross site scripting In addition to this security vulnerability, the following bugs have been fixed since the 6.0 release: * #189568 by dvessel: module .css files were not overriden from theme .info files * #212608 by stefgosselin, webchick, slightly modified: get rid of notice when sorting blocks (minor) * #218513 by moshe weitzman, Pancho: code documentation formatting fixes for menu.inc (minor) * #220827 by Arancaytar, ax: fix code comments in _menu_navigation_links_rebuild() (minor) * #227548 by Heine, AjK: misuse of db_escape_string(), when db_escape_table() should have been used

Script to Migrate PHPNuke to Drupal - UTF8 to UTF8

By BXTra |

Update (Feb 25, 08): New Version 0.04w that included 2 lines of code below can be downloaded -> HERE .

I need to port a website in PHPNuke 7.8 to Drupal 5.7. I've searched all over and found a script to do that from this website. The latest version on that website is 0.02w. The script works great but with a problem, the language that is not English didn't import correctly. All those non-english characters show as "?" So, that imported data can't be used.

Then, I continue looking for more information and found a newer version which is 0.03w from this website. This newer version gave me the same problem.

I, then, looked into the script, checked my database. I found that the data on my temporary PHPNuke database is UTF8. (It has been converted when I imported into MySQL.) So, what I need to do is to import data from UTF8 to UTF8. The migration script didn't write to do that. So, I put these two lines into the script line 280 (in Migration Script version 0.03w) :

$result = mysql_query("SET NAMES utf8", $link);
$result = mysql_query("SET CHARACTER SET utf8", $link);

The script near line 280 (With 2 more lines of code) will look like below :

	//Connect to MySQL
	$connected = true;
	$link = @mysql_connect($host, $username, $password);
	if (!$link)
	{
		failure("Connection to MySQL could not be made. Edit this file and make sure that the database settings are correct.");
		echo " Error returned by MySQL (if any): (" . mysql_errno() . ") " . mysql_error() . " \n";
		$connected = false;
		if (isset($_GET["section"]))
		{
			exit();
		}
	}
	$result = mysql_query("SET NAMES utf8", $link);
	$result = mysql_query("SET CHARACTER SET utf8", $link);
	
	// if you have php5 and the "tidy" module, this will clean up user text for you.
	function tidyhtml($str)
	{

Test the migration script and it works perfectly now.

Note 1: You can convert MySQL data in PHPNuke to UTF8 using import feature under phpMyAdmin. (When import, select "Character set of the file" to what it original is.) After imported, those data will be UTF8. Then, use script with 2 more lines above to convert data to Drupal.

Note 2: My tested computer runs on Windows XP with the following software installed
     - phpMyAdmin 2.11.0
     - MySQL 5.0.45
     - Apache 2.2
     - PHP 5.2.4

Note 3: What I did is to import users and stories, not forum or anything else. That means I didn't test the script if it works with those functions or not.

Drupal 6.0 released

By BXTra |

Drupal 6.0 Download

After one year of development we are ready to release Drupal 6.0 to the world. Thanks to the tireless work of the Drupal community, over 1,600 issues have been resolved during the Drupal 6.0 release cycle. These changes are evident in Drupal 6's major usability improvements, security and maintainability advancements, friendlier installer, and expanded development framework. Further, from bug fix to feature request, these issues follow-through on the Drupal project's continued commitment to deliver flexibility and power to themers and developers.

What's new

The Drupal 6.0 release contains many improvements, some visible from the first click, and others hidden beneath the hood. While the complete list of changes is too lengthy to list here, we have included just a few of the reasons we're so excited about Drupal 6.

Drupal 6 RC4 is now available

By BXTra |

Drupal 6 RC4 is now available HERE

Drupal 6 RC4 Release Note

We are proud to present the fourth release candidate of Drupal 6.0. Building on the extensive testing of the third release candidate, we have discovered and fixed a number of critical issues, including errors during search indexing in languages with accented characters, the display of unpublished content in menus and book outlines, and localized menu data being saved into the database. Thanks to the cooperation between the jQuery and Drupal communities, we have also updated the version of jQuery to be included with Drupal 6 to the latest 1.2.3 release. I want to publicly thank jQuery's John Resig and his team for providing a new jQuery release in time for Drupal 6!

Although I had hoped that the third release candidate would be our last before Drupal 6's official release, our priority is to ensure that Drupal 6 is the fastest, most stable, and feature-filled version of Drupal yet. We've translated your experiences with the previous release candidates (including my own upgrade of drupal.hu) into a number of bug fixes, and will be watching closely for any other last-minute issues. I'm again hopeful that this will be the final release candidate before the official release of Drupal 6.0.

Drupal 6 RC3 is now available

By BXTra |
Drupal 6 RC3 is now available HERE Drupal 6 RC3 Release Note We are proud to present the third release candidate of Drupal 6.0. We hope that this will be the final release candidate before we can make an official release of Drupal 6.0. Since the second release candidate, we have fixed various issues including JavaScript performance problems, cleaned up menu updates, added several improvements to the update.module, and added a memory requirements check to update.php. We have even added some small usability improvements since RC2. Status of some of the most well known modules: CCK has a Drupal 6 compatible development version available for testing purposes, and a beta release is expected to be available soon, while a final, stable release will likely be delayed until a 6.x release of Views is ready for testing (more status information). Views is undergoing major changes, and will likely not be ready before the middle of February at the earliest.