We are pleased to announce that the Drupal 4.6.0 release candidate is available. A list of the major changes can be found in the CHANGELOG file. We fixed most pressing issues during the code freeze, so we'd like you to help polish this release and to help iron out the remaining 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/files/projects/drupal-cvs.tar.gz



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. 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.6.0 release. When Drupal 4.6.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.

Important upgrade notes:

  • For the most trouble free transition, it is recommended that you first upgrade existing installations to Drupal 4.5.
  • Several files moved (or got removed) so it is recommended not to copy the new sources over your existing installation. Any left-overs might cause breakage so make a backup and start fresh.
  • For the same reason, it is recommended to disable contributed themes and modules before starting the upgrade process. Upgrade them afterwards. Also note that not all contributed themes and modules have been updated to work with Drupal 4.6.
  • As a result of the improved multi-site support, the configuration file includes/conf.php moved to sites/default/settings.php. If you had a custom configuration file like includes/my-domain.com.php, you'll need to move and rename that to sites/my-domain.com/settings.php. Note that the new configuration file has a number of new configuration options compared to the old includes/conf.php. Consult INSTALL.txt and the default sites/default/settings.php for details.

Support and bug reports

For support and bug reports, please consult the Drupal project page. Please use the bug tracker to file and track bug reports. All Drupal contributors are encouraged to focus on the pending bugs as well as on documentation.

Developer information

Developers should be aware that custom themes and modules for Drupal 4.5 need to be updated to work with Drupal 4.6.0. If you maintain a theme or module in Drupal's contributions repository, or if you want to contribute to Drupal development, this is the time to update themes and modules. A list of changes since Drupal 4.5 can be found in the Module developer's guide and Theme developer's guide. Also note that the DRUPAL-4-6 CVS branch has been created in the contributions repository.

Translator information

The interface translation templates in the contribution CVS repository are now updated to reflect the strings used in the Drupal 4.6.0 RC. Please update your translations accordingly. Note that there might be string changes later on in the release process.

Comments

freyquency’s picture

another day made awesome by a RC release!

this post brought to you by:
`':,..,:'``':,..,:'``':,..,:'``':,..,:'`
erik mallinson

sgtaw’s picture

This release is great!

Keep up the awesome work
~*
Juice Plus

neofactor’s picture

- Love the new block managment and the Forums are so easy to config now.
- Search index % is nice.

Questions:
- Under settings the Image handling is displaying a "1", What is this?
- I saw something about a new image api? What and where is that?
- Theme tag additions... Where are they listed?

Surpised there is not an install script via php yet... For those looking for a quick install script... here is mine, just setup your database 1st:

#!/bin/sh
cd www
wget http://www.drupal.org/files/projects/drupal-cvs.tar.gz
tar -zxvf drupal-cvs.tar.gz
rm drupal-cvs.tar.gz 
mv drupal-cvs/* drupal-cvs/.htaccess .
rmdir drupal-cvs
mkdir files files/pictures
chmod 777 files

mysql -u db_username -p db_drupalcvs  < database/database.mysql

exit
Steven Mansour’s picture

*Big* thumbs up on the new block admin layout, much faster to work with when you have a lot of blocks.

richardb’s picture

Nice little script, great timesaver.

neofactor’s picture

Is anyone working on an offical installer? Perhaps a web base install/updater? Similar to postnuke and others. I was thinking of developing one if no one else has started... or contribute to the project if there is one out there.

Let me know.

David McIntosh
neofactor.com

kbahey’s picture

There are two developments on that front.

Civic Space has an installer and Adrian is writing one. They may be combined at some points.

Read lists.drupal.org for drupal-devel. There is a discussion on that at the moment.

--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

B.X’s picture

Different terms for forums is a bad idea... I now use (and I shall use) 4.5.2 is really best release of the Drupal.

sepeck’s picture

I like them. More bad news for you then. The new image module uses a seperate taxonomy/category as well.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

B.X’s picture

The Drupal was beautiful idea (taxonomy and node), but now became "as everywhere"... There is no beautiful idea, there is no logicality, farewell the Drupal... One more PHP-Nuke - it is uninteresting...

Steven’s picture

Ffs stop being so dramatic about it. The taxonomy system is still used under the hood. Taxonomy forum feeds still work for example. If you really want the ability to have one global taxonomy, work on it instead of doing nothing but complaining.

Make a patch, suggest how the two methods can be harmonized. Make mockups. Do something constructive. But the truth is that setting up a forum was a usability nightmare for most users in 4.5, and we tried to fix it. This has made a lot of people happy.

--
If you have a problem, please search before posting a question.

B.X’s picture

The patch is not the decision of problems, the good idea is destroyed (uniform taxonomy), development has gone in other direction, one more module uses other sections (image), and then? For all to do patches?

Yes, it "was too good" (uniform taxonomy), that could proceed "too long"...

ccourtne’s picture

Ok, the current solution does not suite your needs, and because of your attitude not many will be willing to help you solve it. I know I won't be trying to fix your issues based on your over the top I know better than anyone attitude. I believe everyone working on Drupal does so in their spare time for fun and the benefit of others. You can disagree with anything anyone does but you should take more time and effort to be constructive about expressing it. I created the original patch and with the correct phrasing of how this might not work for some part of the user base I would have jumped at fixing it.

The common taxonomy for everything does not work for all sites any more than the private module taxonomies works for your needs. mikeryan has posted a thoughtful bug report indicating this change negatively impacted his site. It is a completely valid point brought up that some people may still desire non-hidden module taxonomies. Which could potentially be easily fixed via a setting, the back end implementation uses taxonomies completely just puts a more intuitive interface on them for many situations.

mikeryan’s picture

I've submitted an issue on the problems forum-specific taxonomy cause.

No one questions that improving forum usability was a noble goal. The "solution", though, was implemented with total disregard for the perfectly reasonable design decision to use a common vocabulary for different node types. It seems the implementor(s) simply took it for granted that everyone would use a special taxonomony just for their forums, and that's not the case. It's not helpful to tell people whose sites are broken by this "well, I like it" - someone should have made some effort to make the change upward-compatible.

Mike
Fenway Views

tvst’s picture

my website is a multi-language site and i have taxonomies such as "english", "portuguese", "spanish", etc, to denote the language each node is in — and this applies to all node types. here is what i mean.

i haven't installed 4.6rc yet, but if it does indeed use different taxonomies for forums i will be forced to stay with 4.5. it would be really nice to allow the administrator to choose the taxonomy style (type-based, or universal).

ejahn’s picture

This is the nicest drupal site I've seen yet! I wouldn't do anything that would render it inoperable either. What theme and modifications did you make to get this look?

bmc-1’s picture

So, guys - is there any disscussion about how taxonomy could be extended? I don`t see no reason why we can`t do something like "multiple taxonomies" or something like that. Or taxonomy could be controled (if it should be enabled/disabled on some type of content).

PS: The way it changed in 4.6 branch i dislike eather.

jeremy@civicspacelabs.org’s picture

I see that you can still select taxonomy terms when you go to create a forum topic, but there is no way to display the taxonomy at ?q=forum. Couldn't you just used the forum containers (which I like a lot) and populate them with the taxonomy terms?

Emiliano’s picture

Hi!

I just installed Drupal 4.6 RC and everything worked fine! I liked the improvements a lot! ----> Congratulations all developers! :-)

About the image module, I don't know if I did the right thing, but I installed CVS version of it. The problem is that Drupal complained the duplicate image.inc in 2 diferent places (includes and modules/image). I tried to fix it, but then other erros came up.

Did I miss something? Shouldn't I have installed image.module CVS?

Thanks e congrats again!
Emiliano.

Malthus’s picture

Whose new image module? (And where can I get it?)

sepeck’s picture

walkah is working on it.
http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/walkah/image

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

syscrusher’s picture

Along those lines, I have also built a new module called image_import which brings a feature similar to the "directory upload -- fast" feature in the old image.module, to walkah's new image.module. This module expects the image files (and, optionally, text files containing captions) to be manually uploaded into a directory on the server; the module then imports these images [and captions] to create image nodes compatible with walkah's module.

My code is at an ALPHA test level with regard to stability, though it does function in a test environment. I would welcome any test reports and suggestions for improvements to code or documentation.

Download from:

http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/syscrusher/im...

A Drupal project exists at:

http://drupal.org/node/19860

Please submit bug reports and suggestions as an issue to that project, from here:
http://drupal.org/node/add/project_issue/19860

Scott ("syscrusher")

killes@www.drop.org’s picture

Could this be extended to import other file types as well? I am thinking about PDFs, Movies, whatever.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

syscrusher’s picture

... I didn't have time to generalize it at this point.

I'm not against doing this, but there are some very image-specific things in my module. The "right" way to do this kind of generalized import would be to make it an extensible import API, in the way that Flexinode can be extended with new field types, and then my module would become one of several extended "toolkits" for the generalized import.

If there's a demand for this functionality, I'm willing to take on the project after I get some other work off my plate.

Scott

kzeng’s picture

When I attempted to do a search in the RC, I got the following error message:

warning: Compilation failed: characters with values > 255 are not yet supported in classes at offset 52
 in /usr/local/psa/home/vhosts/kzeng.info/httpdocs/drupal-test/modules/search.module on line 257.
warning: Compilation failed: characters with values > 255 are not yet supported in classes at offset 143
 in /usr/local/psa/home/vhosts/kzeng.info/httpdocs/drupal-test/modules/search.module on line 265.

Is it caused by some bugs in search.module? Thanks!

--------------------------
http://www.kzeng.info

silverwing’s picture

I'm getting an error in search also:
user error: Unknown column 'i.sid' in 'field list'
query: SELECT COUNT(DISTINCT i.sid, i.type) FROM search_index i INNER JOIN node n ON n.nid = i.sid INNER JOIN users u ON n.uid = u.uid WHERE n.status = 1 AND (i.word = 'cat') in /home/blah/includes/database.mysql.inc on line 66.

silverwing

www.misguidedthoughts.com

Dries’s picture

Looks like your database is not properly installed/upgraded. Did you upgrade or did you install a fresh copy of Drupal? Did you get any errors? We can't help you unless you provide us more background information and details about your setup.

silverwing’s picture

I upgraded from 4.5.2, and I didn't get any errors.

I'm having another issue with the blocks, so I'll drop my db, upload my backup, and try again tomorrow.

Question, though. This is my first time upgrading a drupal installation. Which upgrade script should I choose? (This wasn't clear to me.)

silverwing

www.misguidedthoughts.com

Kief’s picture

I'm also interested in the answer to this. I've tried different options from the dropdown on the update.php script by trial and error, but I'm not confident I have it right since I'm still working out issues with modules. Can anybody clarify which option should be chosen to upgrade from Drupal 4.5.2 to the 4.6/cvs version?

Thanks,
Kief

Gábor Hojtsy’s picture

Drupal knows the last update performed, so it will automatically select the next update, from which all updates are run. That makes your database up to date. The update preselected by Drupal should be fine.

tsal’s picture

It simply selected the first option on the list, which gave me nothing but errors. So, I had it run everything since 4.5.0, and that only worked for some of the errors.

In other words, this fix did not work, any other suggestions?

phatPhrog’s picture

I, too am getting an error using search, but different than the ones listed.

This is a fresh install of 4.6 RC using the pushbutton theme.

warning: Missing argument 2 for do_search() in /home/httpd/vhosts/gnuker.com/httpdocs/modules/search.module on line 472.

warning: Cannot modify header information - headers already sent by (output started at /home/httpd/vhosts/gnuker.com/httpdocs/includes/common.inc:385) in /home/httpd/vhosts/gnuker.com/httpdocs/includes/common.inc on line 193.
bkark’s picture

I get the following search errors on a fresh 4.6 RC install:

warning: Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support at offset 0 in /modules/search.module on line 258.

warning: Compilation failed: this version of PCRE is not compiled with PCRE_UTF8 support at offset 0 in /modules/search.module on line 266.

I don't get these errors with other Drupal's on another server. I'm able to search with no problems on a 4.5.2 installation though. The server in question is running PHP 4.3.8.

Any thoughts?

Steven’s picture

The 4.6 search is significantly different and requires UTF-8 support in PCRE. This has been confirmed to work properly as of PHP 4.3.3 and should be available with default compilation settings.

--
If you have a problem, please search before posting a question.

insomoz’s picture

drupal cvs version

Compilation failed: characters with values > 255 are not yet supported in classes at offset 52 in /path/to line 258.

I'm getting the same problem, Is there a fix
I'm running rhe - apache 2 - php ver 4.3.10

Steven’s picture

Check which version of PCRE (perl-compatible regular expressions) is compiled into PHP (use phpinfo() or something similar). The search improvements really required UTF-8 support in regexps. Though it was originally though compatibility would not be an issue (due to misleading docs about PCRE UTF-8 support in the PHP manual), it was decided that this is an acceptable compromise for the improved functionality.

A standard, out of the box PHP 4.3.3 or higher works fine for me. If you compiled your PHP yourself, you need to check PCRE.

The Drupal 4.5 search was really not up to snuff, so it is also not worth it to make a 4.6 compatible version of that. Really, if it turns out you can't use 4.6 search.module, you're better off with a Google search box for your site.

--
If you have a problem, please search before posting a question.

insomoz’s picture

Ive installed and configured for pcre
Is their a list of configured extenstions modules that drupal needs to be installed with such as
./ --enable-mbstring --enable-mcrypt
etc etc

insomoz’s picture

Yep thats what It was I updated pcre
ver 4.3.11 and apache 2 and the search sort of works now, I dont think its indexed everything properly yet

Steven’s picture

..will give you a report of how much has be indexed.

--
If you have a problem, please search before posting a question.

Dries’s picture

What PHP version are you using? (Note that you're better off using the issue tracker to report bugs.)

silverwing’s picture

Use the issue tracker! Just got caught up on this thread!

Anyways, I've got:
PHP version 4.3.10
MySQL version 4.0.22-standard

silverwing

www.misguidedthoughts.com

Mad Maks’s picture

i have the same problem with the search and reported it before my php version is according my host 4.3.10 but a version script say 4.3.2.

my host say that it has something to do with a RH version renaming (?) maybe is that the problem.

MM

enthusaroo’s picture

Unfortunately, I'm having a problem with the upgrade.

Here are the steps that I took:

A) Made a backup of all files.
B) Deleted all files in my Drupal installation.
C) Uploaded all files from Drupal-CVS.
D) I don't see a conf.php file in Drupal-CVS (is there suppose to be one?), so I uploaded the old one to the includes/ directory.

Here is what I get when I attempt to run update.php or access any of the pages:

Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)

:(

What did I do wrong? I'm upgrading from Drupal 4.5.2.

nathanwastaken’s picture

Hi,

In Drupal 4.6, there is no conf.php, instead, as the code base now supports multiple sites, you have to go to 'sites/default/settings.php'.

This is effectively the new conf.php in 4.6.

So, just delete the conf.php file in the drupal directory, configuire the settings.php file, and you should be right.

Dries’s picture

That is correct. I just updated the announcement and added a note about it.

enthusaroo’s picture

Great! Sorry, I must have missed that part of the announcement. I'm going to go test it out now!

Steven’s picture

The search requires PHP 4.3.3.

--
If you have a problem, please search before posting a question.

Dries’s picture

In that case, we have to update INSTALL.txt as well as the system requirements page in the handbook.

killes@www.drop.org’s picture

This is quite a let down. I am not amused. :(

[Update: This was apparently non-intentional, PHPs docs made Steven believe unicode support for regexes was available for PHP 4.1.]
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.5 does not work with PHP 5.

rkendall’s picture

Steven, would you be able to do an (optional) patch that would get search working for older versions?? I had a look at the regex, but it just confused me :-/

Would be much appreciated. (I'd be happy to compromise on some functionality to at least having it working).

I just started with a small web compay, who has an older server (with about 100 sites on it), which uses an incompatible version of PHP - since the server uses Ensim to manage all the accounts, it's not really possible to upgrade without the risk of taking a heap of sites down (unfortunate yes).

I was hoping to get the other developers (at this company) on to using Drupal, but I can't use Drupal 4.6 with search for any new sites (or upgrades) on this server. We will get a new (second) server soon, but it's still a pain.

killes@www.drop.org’s picture

I've discussed this with Steven in great detail as I have a similar problem. However, the chances are very slim or rather non-existent. Your best bet woul dprobably be to port the old search to Drupal 4.6. Be aware that a google search bar might give you better results, though.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

p_____n’s picture

Immediately, I was going to update the Japanese translation file.

--
Drupal Japan

Artti’s picture

Hi,

Does 4.6 support multiple sites with shared content (different domains but same search results)?

nathanwastaken’s picture

Drupal 4.6 does support multiple sites of the one codebase, so I can't see it being a problem.

If you set it up, so that you point the codebase to different base URL's, but connect to the same database it should work. You will need to configuire the 'sites/default/settings.php' file, and then create a new directory in the 'sites' folder for each additional site (just copy the default and rename it, then change the base URL). I am not sure, so maybe some core developers could offer a hand as well.

If you get it working, let me know. (probably in a different thread).

harald.walker’s picture

With 4.5.x you were already able do this. One drupal installation and one central database if you like. Originally I wanted to do it like this, but then I decided to use separate databases per domain, because it caused too many problems within the site navigation and became too user (visitor) unfriendly this way. When all is ready I will be using one central Drupal installation for 4 different sites.

Steven’s picture

You can share content through tablesharing, but it might be tricky to set up. The search depends on the node table being unique, so you'd need to share the node table as well. This means that your sites would have the same content, except maybe displayed differently or using different taxonomies.

--
If you have a problem, please search before posting a question.

Artti’s picture

I'll have to start testing :)

One more question came to my mind just now: Is it possible to make search results link to correct sites? So that content that has been created and mapped for one site could be always shown in that particular site?

I'm really starting to get interested in Drupal development. Only wish I had more spare time.

inteja’s picture

I just set this up with 3 sites on the one hosting account with no problems. Initially I just set it up with the one database but that shares content (and config settings if not overridden) between the sites, so I duplicated and prefixed the database tables then simply added the prefix to sites/settings.php and they now each work independently (but share same codebase).

See default themed, "under construction" sites here:

www.construct3d.com
www.nosmalldreams.net
www.neocosm.net

Brian.

--
Brian.

mike3k’s picture

I've done an ugly theme hack in 2.5.x to present different appearances (as well as changing the name) based on the URL, while presenting the same content. See http://www.worldbeatplanet.com/ and http://www.shareyourmusic.com/

Also, if you want to maintain the illusion of different sites when the user clicks a link, set the base url something like: $base_url = "http://".$_SERVER['HTTP_HOST'];

I plan to clean it up when I upgrade to 2.6.

--
Mike Cohen, http://www.mcdevzone.com/

kiev1.org’s picture

NOT WORK image.module!!!!
and htmlarea image preview from image.module not work
I too have not found realization of the idea http://drupal.org/node/15854 : (Display of blocks by zones instead of left-right) :( So in fact and the code becomes simpler! And to designers it is more convenient

And in general DRUPAL among CMS - the first - and because of simplicity. Do not complicate a code

I love drupal!

Steven’s picture

Please report bugs and feature requests through the issue tracker. Putting strange symbols and using uppercase (shouting) only annoys others.

--
If you have a problem, please search before posting a question.

mariagwyn’s picture

I too ran into the image module problem. I assume that it will take some time to fix as it is an addition, but it is sure a useful one. Here is the scenario:

On BOTH an upgrade from 4.5.2 to 4.6, and a clean install of 4.6, when I go to the admin/modules, I get the following error:

Fatal error: Call to undefined function: module_get_path() in /home/mgwynm/public_html/drupal/modules/image/image.module on line 4

(gotta love 'fatal error' - seems so threatening). The only resolution is to remove the image module. Note also that this happens whether I have additional modules (non-core) installed, or not. It also happens whether or not I have the image module activated.

Hope that helps.

Maria

respinos’s picture

I believe inactive modules have to be loaded in order to gather their information for the module admin list, which is problematic modules (even if disabled) affect this function.

griffinn’s picture

According to the Module Developer's Guide, module_get_path() is no longer supported in Drupal 4.6.

If you would like to change the code yourself, open image.module with a text editor and find all instances of module_get_path('something_here'), and replace that with drupal_get_path('module', 'something_here')

Or submit a bug in the Image module's issue tracker (but I bet somebody else has already done the same), and download a new cvs when the issue is fixed.

nautis’s picture

Just wanted to report that the upgrade went smooth. Took about 5 minutes and everything looks good after some initial testing. Anticipate many non-core modules to break under the new version. I lost images, textsize, weblinks, and a few others.

My favorite change is the new search interface - nice and simple. Simple is good. I also dig the "blog it" button available on the front-end rss feeds block. I'd like to see this included in the aggregator module. This is something I really like about CivicSpace's aggregator. I'll add this as a feature request. Thanks for all your hard work. The install and upgrade is well documented. I know it's a thankless task, but is very helpful to newbies like me. Thanks.

- matthew | nautis.com

theque’s picture

I can't see primary links.... where are they?

neofactor’s picture

What do you mean? They are right there were we left them... /admin/themes/settings

I added "test | test" for ya to see here: http://drupalcvs.neofactor.com/

theque’s picture

What about auto primary links... like in 4.5.2, when enabling modules like forum, poll etc. primary links appears automatically....
Or it's just my morbid imagination? :)

killes@www.drop.org’s picture

This was a Drupal 4.4 feature. It was removed as it did not scale well. Modules do now put links in the main navigation block.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

mariagwyn’s picture

I installed the 4.6 as an upgrade from 4.5.2. While I had a few errors with modules I forgot to turn off, the following one I am not sure what to do with (this happens anytime I do a search):

warning: Missing argument 2 for do_search() in /home/mgwynm/public_html/drupal/modules/search.module on line 467.

warning: Cannot modify header information - headers already sent by (output started at /home/mgwynm/public_html/drupal/includes

I tried to submit this via a bug tracker, but I was very confused by the project pages (I am a bit of a newbie). If you need to see the upgraded site, go to:
mariagwyn.com/drupal.

This is certianly not burning for me, as I still have my previous version up and running elsewhere.

Thanks,
Maria

Steven’s picture

It sounds like you have an old contributed module lying around. There is only one place in 4.6.0 core where do_search() is used, and it correctly used there.

--
If you have a problem, please search before posting a question.

mariagwyn’s picture

--Update--
I found the problem. I modified the book_review module to create my own module, and the search function (from the book_review module) looks like this:
$find = do_search(array("keys" => $keys, "type" => "node", "select" => "SELECT s.lno AS lno, n.title AS title, n.created AS created, u.uid AS uid, u.name AS name, s.count AS count FROM search_index s, node n LEFT JOIN users u ON n.uid = u.uid WHERE s.lno = n.nid AND s.type = 'jarticle' AND n.status = 1 AND s.word like '%'"));

Is there a way to implement this correctly? In your response, please note that I know very little to no php. I literally hacked away at the book review module to make the changes I wanted, all trial and error. I am open to learning more (drupal teaches me every day), but I am a designer, not a coder.

Thanks,
Maria

I very likely do have an old module laying around, actuall, a number as I am curious to see what still works. Any idea which old module might be causing this problem?

Also, am I to understand that at this point, any module other than those in the actual drupal core are not necessarily going to work? Not a problem, just want to know when I should really try to upgrade, and how long I should wait.

Thanks,
Maria

chx’s picture

weblink is also having this problem.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

sepeck’s picture

Isn't weblink being redesigned for this update into 2-3 related module bundles?

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

syscrusher’s picture

We are working on this, but it is a large effort and will not be done by the time 4.6 is released. I'm expecting to see this happen as a contrib module for 4.6 after its release. There will be an upgrade script from the existing weblink module, so go ahead and use that for now. :-)

Scott

a.k.karthikeyan’s picture

well i tried a little hack and its working.. I too have old modules of which the searches where giving the same errors as u got ... .jst try this

In search.module
previous :
line 486 : function do_search($keywords, $type, $join = '', $where = '1', $variation = true)

after the change :
line 486 : function do_search($keywords, $type='node', $join = '', $where = '1', $variation = true)

make similiar changes to all the old modules as shown in the example below :
bookreview.module :

function bookreview_search($keys) {
// TODO: Implement search by name, subject, title, review, isbn, etc...
$find = do_search(array("keys" => $keys, "type" => "node", "select" => "SELECT s.lno AS lno, n.title AS title, n.created AS created, u.uid AS uid, u.name AS name, s.count AS count FROM search_index s, node n LEFT JOIN users u ON n.uid = u.uid WHERE s.lno = n.nid AND s.type = 'bookreview' AND n.status = 1 AND s.word like '%'"));

return $find;
}

After the change :

function bookreview_search($op = 'search', $keys = null) {
switch ($op) {
case 'name':
return t('bookreview');
case 'search':

// TODO: Implement search by name, subject, title, review, isbn, etc...
$find = do_search(array("keys" => $keys, "type" => "node", "select" => "SELECT s.lno AS lno, n.title AS title, n.created AS created, u.uid AS uid, u.name AS name, s.count AS count FROM search_index s, node n LEFT JOIN users u ON n.uid = u.uid WHERE s.lno = n.nid AND s.type = 'bookreview' AND n.status = 1 AND s.word like '%'"));
}
return $find;
}

Regards,
Karthikeyan

Steven’s picture

Bookreview needs to be re-evaluated to see if the search is needed. The search changes between 4.5 and 4.6 are significant and affect the way search should be used, both in code as well as UI.

Simply porting over the old search won't do much good.

--
If you have a problem, please search before posting a question.

a.k.karthikeyan’s picture

ya you are right. But its jst to get things moving. Well waiting for the actual release.

Regards,
Karthikeyan

mariagwyn’s picture

Karthikeyan,

Thanks for your search update. I actually gave up on 4.6 b/c I was having too many problems, but just reinstalled (the image module helped). I ran in to the same problem, but your fix works perfectly. Thank you very much, and sorry for the delay. I appreciate you taking the time to 'get things moving.'

Maria

mariagwyn’s picture

I am running into the following error with a php engine:

Missing argument 1 for phptemplate_templates() in /home/mgwynm/public_html/drupal/themes/engines/phptemplate/phptemplate.engine on line 44.

I know you mentioned that not all themes/engines are updated for 4.6. Is this true of the phpengine itself, or is my theme wrong (I actually only have freindselectric currently uploaded)?

Also, I know that you (Dries) have requested that problems be put into the tracker, so if this is more appropriate there, please let me know how to do that as I am finding the tracker a bit confusing. Is there a place for 4.6 problems specifically? I am only seeing 4.5.

Thanks again, and it looks nice so far...I am sure the bugs will be worked out.

Maria

jairo.serrano’s picture

Go to the CVS downloads ang get this.

Jairo Serrano
Ingeniero de Sistemas
Drupal Spanish

mariagwyn’s picture

I must have downloaded the wrong one. It took 3 tries, but eventually the one under phptemplate simply labeled cvs (not cvs.tar) worked.

Muchas gracias,
Maria

Steven’s picture

We've had some trouble with the CVS packaging since today... sorry for the inconvenience.

--
If you have a problem, please search before posting a question.

jtite’s picture

Hello,

I would like to know if in the new multiple site configuration system the user sessions can be shared across the Drupal-powered sites, for example if a server host two drupal sites one under www.domain.com and another under sub.domain.com sharing the same database, can drupal detect a user already loged in www.domain.com in the sub.domain.com subdomain so he/she doesn't have to enter his/her user/pass aigain and share user's information accross multiple sites (single sign-on) ??

killes@www.drop.org’s picture

That should work (at least I am going to try a similar setup).

You will need to share at least the sessions and users table. You'll also need to make sue that your cookie gets set for the whole domain.
See here: http://drupal.org/node/1486
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

szimszon’s picture

then I have the following error:

warning: pg_query(): Query failed: ERROR: invalid input syntax for integer: "" in /var/www/linux.oregpreshaz.hu/docs/includes/database.pgsql.inc on line 45.

user error:
query: INSERT INTO node (title, body, format, uid, type, teaser, status, moderate, promote, sticky, comment, created, changed, nid) VALUES('egy', 'ketto', '1', '2', 'story', 'ketto', '1', '', '1', '', '2', '1110284925', '1110284925', '11') in /var/www/linux.oregpreshaz.hu/docs/includes/database.pgsql.inc on line 62.

warning: Cannot modify header information - headers already sent by (output started at /var/www/linux.oregpreshaz.hu/docs/includes/common.inc:385) in /var/www/linux.oregpreshaz.hu/docs/includes/common.inc on line 193.

How can I fix the problem?

Tnx.

griffinn’s picture

Not only that. Multiple built-in and third-party modules are not working correctly with PostgreSQL.

Generally speaking, every time an INSERT query is run that tries to put NULL into an integer field, the abstraction layer renders the NULL into a null string (''), and PostgreSQL doesn't like that.

adrian’s picture

I have tested the postgres port to the best of my ability and time available, but it seems like I might have missed something.

If you report them, mark them as critical .. they obviously need to be fixed.
--
The future is so Bryght, I have to wear shades.

szimszon’s picture

I have sent one issue, with priority critical 2 days ago. I have no answer received. (The patch in post is wrong, it is for my previous post in another issue)

I have found one another bug report 1 days ago.

PageTurners@page-turners.net’s picture

Another day, another version of Drupal :-)

Site is running at page-turners.net

thesaint_02’s picture

Does dropping PEAR DB mean that PostgreSQL is no longer supported?

What are the plans for the database support? A self-made database abstraction? Or Mysql-only?

chx’s picture

PostgreSQL is natively supported. Other DBs? Writing a database.*.inc is a piece of cake, maintance of DDL parts (default database and updates) is another issue. Volunteers are welcome.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

eka’s picture

PHP5 support comes with this release?

:)

Eka

exeye’s picture

I guess not yet :|

REQUIREMENTS
------------

Drupal requires a web server, PHP4 (http://www.php.net/) and either
MySQL or PostgreSQL. Drupal requires PHP 4.1.0 or greater on Linux
and PHP 4.2.3 or greater on Windows. PHP5 is not yet supported.
chx’s picture

There was talk about this, and I think there will be PHP5 support, yes. Not E_STRICT, that would require an insane amout of work, otherwise it will run. I also think, the code is at place already, only that text needs to be changed.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

Dries’s picture

Drupal 4.6 should work with PHP5. I just updated INSTALL.txt accordingly. Thanks for pointing this out exeye.

irwin’s picture

I upgraded from a prerelease version and lost the Categories block (then did a few other things and royally screwed up my web site). I'm wondering if anyone here knows what happened to that block (it wasn't actually part of a module, was it)?

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

killes@www.drop.org’s picture

It got removed as it was considered rather useless. If you wantit back you can create a php block.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

irwin’s picture

Well, I was using. it. :\ In any case I got it back by digging the PHP code up from the old version of the module.

If you are going to remove things like blocks or other features, you might want to consider deprecating them first as opposed to simply deleting them. I find it scary to update Drupal at times for the reason that something I'm used to, or built my site around might disappear during the upgrade. I understand that this is only an RC release so things aren't expected to work right out of the box, but a phase-out period might help reduce potential problems and user complaints.

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

kbahey’s picture

Hey Irwin.

Nice theme on Suikoden. Simple and clean.

You may want to have a favicon to go with it.

Congrats.
--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

dreed47’s picture

Hi Irwin,

I really like your theme as well. Is it publically available anywhere?

Gábor Hojtsy’s picture

Drupal is very quickly moving forward, and is not about to keep stuff, which is not desired. If you are not keen on this pace, you are not required to upgrade (especially not on a live site). You can use a DB dump and a test site to check out changes. In fact you should.

sepeck’s picture

I respectifully suggest in the future that you upgrade on a test site first. That way you don't risk blowing up your production site. See the link in my signature.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Jaza’s picture

Where I am posting this comment now, there was (last time I checked - about 24 hours ago) a large tree of interesting comments that has now disappeared. I am assuming that this is the reason for the disappearance:

Update by Dries: as the comments in the discussion are growing unwieldy, I'm deleting comments that are off-topic.

Well, Dries, the comments that were here were getting off-topic, and there were starting to become too many of them, but I think deleting them was a very bad idea. The comment that caused the mass of responses was one from killes, the exact words of which I no longer have (since they've been deleted), but with went something to the effect of:

Since when do developers care about users?

This was said in relation to the removal of the taxonomy block, and the idea that maybe it would have been better to deprecate it first before removing it.

A lot of people posted opinionated comments, saying what they thought about killes's statement, and about having that kind of attitude in OSS (and all software) development. There was a lot of important, insightful, and constructive discussion going on here. I think that the Drupal community really could have learnt some things if these comments were left here. I also think that those people had a right to have their comments left where they posted them, and not to have them deleted.

Have those comments been permanently deleted, or have they simply been unpublished? If there is any way to retrieve them now, then I would strongly urge the Drupal.org admins to re-publish them either here, or as a separate forum topic. I think that it goes against the spirit of Open Source to silence peoples' voices (even if it is for practical rather than for personal reasons). Please do the right thing, and bring these comment back!

Jeremy Epstein - GreenAsh

Jeremy Epstein - GreenAsh

Dries’s picture

Those comments have been deleted permanetly. You are welcome to start a new forum topic to discuss any of the above issues. Thanks.

cel4145’s picture

hmmm...i happen to know that this is commonly used by bloggers. seems silly to deprecate something like this unless it was requiring too much maintenance to suppor t the upgrade.

killes@www.drop.org’s picture

Sorry Charlie, I guess there weren't many bloggers at DrupalCon:
http://drupal.org/cvs?commit=13931
Maybe you can convince Dries to put it back in.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

cel4145’s picture

It doesn' t affect me directly because I'll switch back to taxonomy_html (see my previous comment). I actually kind of liked the taxonomy_html implementation a little bit better, but had used the categories block just because it was in Drupal core and thus a block enable switch to check to use.

sepeck’s picture

Rather then a built in function, couldn't this be one of the Block configuration ideas. I rather like that. Perhaps a how to add a php block to obtain this result. THis would have the side effect of introducing the custom blocks.

http://drupal.org/node/17170

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

cel4145’s picture

to make sure that taxonomy_html is updated and working properly with Drupal 4.6rc.

irwin’s picture

My site's not a blogging site and I'm not worried about its removal myself since I repaired it, but feature-removal might be something to be more careful about in the future. At the least, make CVS log messages very detailed (more along the lines of "Removed Categories Block. Use taxonomy_html module instead") so users can search.

Is there a central changelog that developers can update/check things off of for each Drupal revision? I know that a roadmap is posted up every release but perhaps a mechanism to record feature changes in a central location can help reduce problems like this. I suggested above using CVS message "nodes" as one option but I'm not sure if that's a great idea.

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

killes@www.drop.org’s picture

The CVS logs are currently the only way to trace feature addition/removal. In addition, Dries occassionally writes some "Drupal quickies" which mention the larger changes.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

irwin’s picture

There is something else:

http://drupal.org/project

There's no reason we can't use the Project module to our advantage for a situation like this. Take a look at this thread and read the suggestion. I'm not sure what you might think of it but perhaps it's worth considering the benefits and drawbacks of such a system.

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

Matt Simpson’s picture

I'm starting to use Drupal because I want a blog engine, and I like the other capabilities too. Are you talking about the ability to arrange blogs entries into categories? That's not going to be supported in 4.6?

rkendall’s picture

The categories (or taxonomy as it is called) is integral to Drupal - it is very flexible and can be used in many ways. This is not going away!

It was just a side-block that enabled displaying a list of categories in one particular way that has been removed. It wasn't very good, and there are many other ways to display a list of categories.

tulula’s picture

My Vocabulary and terms were wiped out with the upgrade to my test site AND have tried all day to try to add them back in the Categories-Add Vocabulary, and it hangs until I get to a "server not found" type error. ANYWAY, when I check out the logs, it thinks that it's "anonymous" trying to add the vocabulary with a nice "access denied".

I noticed that my database is holding the vocabulary/term info there... ?!?! besides that and block disappearances (which I fixed easily)... hasn't been the easiest upgrade

Matt Simpson’s picture

What is at least one other way to display a list of the categories within a block?

It's good to hear that the categorization mechanism (the module) is not going away. Otherwise, how would one assign category terms when creating a posting. But without the categories block, how is one supposed to enable:

1) a filtered view of a category
2) navigation between categories
3) assignment of a submission to a category?

chx’s picture

... ask Boris Mann! He we explain you in nice, colorful terms as he did to us on a bus in Brussels why he just "loved" the categories block...

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

adrian’s picture

The proliferation of taxonomy_* modules is a sign that the categories block wasn't very good at what it was supposed to do.

--
The future is so Bryght, I have to wear shades.

irwin’s picture

I don't remember the Categories block being in Drupal 4.4 or earlier, so I believe that the proliferation of taxonomy modules might have been a sign that there was nothing else available at the time.

I may be wrong of course, but my previous Drupal site desperately needed some kind of categorical menu and I don't remember seeing Categories available.

That said, Categories could probably use improvement, but if people find it useful, it might be better to perhaps merge one of the more useful taxonomy_* modules into core instead of deleting the function. I suppose we'll find the truth out after 4.6 is released to see if anyone asks for the Categories block back.

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

Boris Mann’s picture

Here's what was wrong with the old one from my point of view:
* not styleable
* all terms from all vocabularies listed AND all mixed together
* no options to control anything -- e.g. not show date, not show post counts
* sorted by last post to a category

It did everything that people might want (dates, post counts, term lists)...except it did them all badly.

It being in core meant it was difficult to make changes. One of the taxonomy_* modules (as Charlie points out) should ideally do this. Except they all kind of suck.

It would be great if someone could post a code snippet for a custom block that pulls out the list of terms for a particular vocabulary.

Hope that's colourful enough for everyone :P

irwin’s picture

The old categories block sorted by last post to a category. :)

A new good module would be the best way; you can't quite get the level of control you need with just a PHP code block if you want to make it easily adoptable. Good set of requirements, though, I will keep them in mind when I will invariably need to write my own Categories block. ;)

-- Irwin
* Drupal at work -> http://suikoden.mine.nu (Suikoden-themed Role-playing Game.)
* My other Drupal site -> http://scrapped.mine.nu (Video-game & Anime-themed Blog)

bmaleszyk’s picture

Much to my chagrin, I am using the Categories block on my "blog-centric" site, but I really don't mind that the this blog is removed in 4.6. I agree with the users posting here that it was not useful in most cases.

All sites, Drupal-powered or not, use a taxonomy (or set of taxonomies) to organize their information, but the information design and taxonomy usage for each site can differ greatly. When it may be useful for one site to present a list of categories sorted by most recent post, another site may have posts which use multiple vocabulary terms, use different taxonomies for different modules (photo galleries, for instance), and other purposes.

Also, the taxonomy block never took into consideration that a taxonomy is, by its definition, a hierarchy (or a multiple-hierarchy, with related terms).

Therefore, it's removal from the Drupal codebase will force site organizers to think more about how they use Drupals vocabularies for the betterment of the site's overall experience, not just another neglected navigation tool.

--
The wisdom's in the trees not the glass windows
You can't stop wishing if you don't let go
Of the things that you find and you lose and you know
- Jack Johnson

www.maleszyk.com

iraszl’s picture

This is very exciting! I've just downloaded and installed it locally on my Mac. Everything went smooth except one thing. On the administer/settings page it gives me the following error message:

Unable to load the GD toolkit

I don't know if this a bug or is it my settings that are wrong. I have ImageMagick, but not GD...
---
http://creativebits.org

sepeck’s picture

There is a bug report for this already
http://drupal.org/node/17645

GD is part of php. Do a search for how to do phpinfo.php to see what the php settings for your server are. You may want to consider adding GD2 to your install, or not.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

iraszl’s picture

GD was not a requirement for the core installation in 4.5. What does it do now in 4.6? What kind of operations require GD2? I can't see anything that would resemble the image module features. Please explain!
Thank you!
---
http://creativebits.org

Gábor Hojtsy’s picture

The new image module (from walkah's sandbox) uses the base functionality provided by Drupal 4.6.x+ core to handle images. Currently (in 4.6RC) the user picture (previously called avatar) handling is performed by the image subsystem.

iraszl’s picture

I see. thank you!
---
http://creativebits.org

irwin’s picture

For Debian users (might apply to Mac Fink users as well), try grabbing the php4-gd module and update your php4.

apt-get install php4 php4-gd

Restart Apache. Fixed my GD problems. :)

-- Irwin
Drupal at work -> http://suikoden.mine.nu
Suikoden-themed Role-playing Game.

kecinzer’s picture

I trying this version and I must claim, that I found many bugs using modules.
I have to fix many bugs in weblink module, now I trying event module, but I can't fix error in this module.
I'm so sad about this, because another function looks great.

sepeck’s picture

More errors with the user contributed modules?

Has the module been updated to work with 4.6rc? If the contributed module has not been updated to work with 4.6rc this is not a problem with 4.6rc, it is a problem with the contributed module. Check the module cvs commits and file bug reports or patches against the project. See if the contributed module author has any intention of updating it.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

rkendall’s picture

The release candidate of 'Drupal' (core) is not the same as a release candidate for the modules.

Some of the module maintainers wait until a release candidate before they even start upgrading modules to work with a new release (if they make updates before core development has settled, they may be wasting their time).

When the official 4.6 release is made, only modules that work with it will be listed under the 4.6 downloads. This may start as a smaller list, but will grow as module maintainers get around to making the needed changes for 4.6.

If you want to test any modules, you can use the CVS ones, but there are no guarantees.

Hope that helps.

kecinzer’s picture

Yes, I understud it.
But, I don't understend, why developers of Drupal doing changes those will cause module incompatibility.
It is possible to do this changes, but when goes out every new version of Drupal all modules going off and need patching?
Sorry, I'm new and I discovered Drupal, when actual version was 4.5.2, so I don't know if this changes (whose need to patch modules) comings out in older releases.

Oh, sorry for my english :).

killes@www.drop.org’s picture

I am not sure I understand your question, but if your questions was why we do not keep backwards compatibility in mind, the answer is: If we would, Drupal would become a unusable, bloated programm. We don't want that.
--
If you have troubles with a particular contrib project, please consider filing a support request. Thanks. And, by the way, Drupal 4.6 will support PHP 5.

malfunct’s picture

I think at some point the core interface (not implementation that can change whenever it wants to) needs to be locked down and changed only when there is extreme need (for instance the php 5 compatibility effort).

Gábor Hojtsy’s picture

If you are keen on Drupal, you are going to like it changing for the better all the time... If you need some stall project, choose another CMS. We are moving, improving progressively.

irwin’s picture

But this shouldn't mean that the Interface has to change with each minor revision, so while it might not happen, I hope to be able to write a module or build a Drupal web site that I am not afraid to upgrade one day because a module maintainer can't keep up with new revision changes.

Progression is good, but taking time to design interfaces that don't need changing is good too. I'm hoping that changes like the new node API (compared to the one in 4.0.0) and the new theme API are going to be stable for at least a couple of years.

That said, many the modules from the 4.5.2 distribution work fine in Drupal 4.6.

-- Irwin
* Drupal at work -> http://suikoden.mine.nu (Suikoden-themed Role-playing Game.)
* My other Drupal site -> http://scrapped.mine.nu (Video-game & Anime-themed Blog)

sepeck’s picture

Drupal version change from 4.4 to 4.5 to 4.6 is not a minor revision. If people think that the admin area needs to be changed/improved, then they need to make grapical mockups with how the proposed workflow will work/improve things. The admin changes from 4.4 and 4.5 were the result of extensive discussions here on Drupal by usability folks and developers. It was facinating to watch and learn from.

Some intial ideas were easy and it turned out that small things made it a lot better. Others turned out to make simple things harder, so were not done.

There is discussion on what the interface goal should be, task base, workflow based...... what!? I think that the workflow in 4.5 is better than 4.4. So far, 4.6 works better for me than 4.5. I have seen one or two mockups/proposals for better ones and made my opinion known of those. I think it could be better, but I don't really know how to make it better myself. Some of the Civicspace folks are doing usability studies on stuff and hopefully they will have some proposals in the future.

In any case, if you have some idea's, make the mockup and start a new topic in the forums. Developers can't develop without a plan/goal and it may turn out that any given proposal has serious reason's why it wouldn't work well. (e.g. It would do well for a forums site, but would make it harder for a corporate cms site). It also may turn out to be the spark that takes off.

One of the dev's indicated that they make custom task based menu's for his customers... I have to admit that I am looking at doing that myself as the 'content' admins don't need all the stuff I see as the site admin, and it makes it more convient for them if it's all there in one menu.

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

Steven’s picture

We do design good interfaces, but the simple fact is that we're not afraid to rip out a piece of code and replace it with something different, if it's better.

If we make UI changes, modules should follow suit, or the usability will go down. If we implement new functionality, people will expect that functionality to work with any module.

If you look at the module upgrading guide, you'll see that many of them require active changes from the module's side, simply because the functionality changed.

--
If you have a problem, please search before posting a question.

Gábor Hojtsy’s picture

Unlike the others, I understand you are talking about API and not UI interfaces. Although I think you will not be able to use a contrib module in two years, not only because it is not going to work, but because you will have different needs, and the modules will offer different functionality by then. Two years is a very long time on the net...

By the way, our comments are going offtopic, so they are good subject for deletion :) Not because developers do not care, but because we are offtopic.

Steven’s picture

I was taking about API, but the simple fact is that often UI and API go hand in hand. It does not make sense to address new functionality the same way as old functionality. But yeah, this is heading off-topic...

--
If you have a problem, please search before posting a question.

Steven’s picture

This is why we have a detailed module upgrading guide. The link has been peppered all over this thread already.

--
If you have a problem, please search before posting a question.

bomarmonk’s picture

I had trouble with the upgrade from 4.5.2 to 4.6 using the upgrade.php script. Since there are others who had similar problems, I'll reveal how I finally succeeded.

First, I backed-up my entire mySQL database using phpMyAdmin and the export command.

Then I created a new subdirectory for the new Drupal CVS (I'm already running Drupal in a subdirectory, so I only needed to remember to update the location of this directory in the CVS file: sites>default>settings.php)

I also needed to change the settings for $access_check from $access_check = TRUE; to $access_check = FALSE. (new directory--- a user hasn't been created yet).

Next, I loaded the backup of my drupal 4.5.2 database (using phpMyAdmin) into a new mySQL database (I'm keeping the old one in place for now, while I tinker around with CVS). The name of this database needed to be changed in Drupal CVS at: sites>default>settings.php.

Now I used phpMyAdmin to disable all the contributor's modules, by "browsing" the system table in the drupal database. I manually "edited" the row of data for any added modules by changing the "status" from a "1" to a "0."

Here's the tricky part: although I am quite ignorant of how this update works, I believe some core modules should remain enabled! At first, I disabled all the modules thinking this was the safest bet for the update. However, this seemed to cause problems in updating the database... I'm not sure if this is true, but someone with more knowledge can clarify if this is the case and which core modules should remain enabled for the update.

Now, I'm ready to run the update script by visting "www.mysite.com/drupal/update.php." Oddly enough, I would have thought I should have chosen the update labeled with 3/03/2005. But this performed absolutely no update on my database (no messages communicating what it did) and when I visited my site, it gave me the following error:

user error: Unknown column 'severity' in 'field list'
query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, 'access denied', 'admin denied access.', 1, 'view', '/drupal/index.php?q=admin', '24.205.103.66', 1110388514) in /home/gov/alpinecounty/WWW/drupal/includes/database.mysql.inc on line 66.

Fatal error: Unknown column 'severity' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, 'php', 'Unknown column \'severity\' in \'field list\' query: INSERT INTO watchdog (uid, type, message, severity, link, location, hostname, timestamp) VALUES (0, \'access denied\', \'<em>admin</em> denied access.\', 1, \'<a href=\\"admin\\" class=\\"active\\">view</a>\', \'/drupal/index.php?q=admin\', \'24.205.103.66\', 1110388514) in /home/gov/alpinecounty/WWW/drupal/includes/database.mysql.inc on line 66.', 2, '', '/drupal/index.php?q=admin', '24.205.103.66', 1110388514) in /home/gov/alpinecounty/WWW/drupal/includes/database.mysql.inc on line 66

Choosing the "first update since Drupal 4.5.0 release" worked. No errors and the script actually performs updates to my database. This "first update since..." confused me at first since I am upgrading from drupal 4.5.2.. It does the trick apparently.

Now, I went back to my update.php and changed the $access_check from $access_check = FALSE; back to $access_check = TRUE.

When I enter my new CVS drupal directory I can login with my old user name and password and begin exploring CVS. I hope that this explanation helps anyone else who may have some of the same problems. I also hope that if I've misrepresented these steps in any way, that someone with more knowledge will lend some clarification or corrections.

rkendall’s picture

You make it sound quite complicated, but of course, there is more than one way to skin a cat (or do a Drupal upgrade).

About the modules; I can't really comment on potential upgrade problems by disabling all Drupal core modules, but I guess leaving core modules enabled shouldn't cause problems. The important thing to remember is to disable _all_ non-core modules.

Here would be my method to get a test site working in another sub directory (test upgrade).
1. copy all drupal files from existing website into your test directory.
2. copy complete drupal database into a test database.
3. update the test copy settings for the new location and database (conf.php).
4. log in to the test site as admin, and disable all non-core modules.
-- now we are ready to test an upgrade --
5. delete all the files in the test directory, and replace it with the CVS files (do not add any modules)
6. Edit settings file for test database and location.
7. Run the update script (you will already be logged in as admin, and it should automatically select the right set of updates).

That's it, no error messages, no database hacking.

Then you would test contrib modules one by one, etc....

rkendall’s picture

Presuming a non-core theme is being used, you will need to copy that across into the themes directory as well, but as with modules, it is probably better to disable non-core themes to start with (just change theme to bluemarine before upgrading).

tonyce@drupal.org’s picture

Thank for the tips. A few questions.

What is the best way to copy the drupal database?

With regards to modules (what do you mean by "do not add any modules"?). When I delete all the drupal files in my test directory, do i leave the modules directory and then just completely replace any core modules in the modules directory, or do I delete everything)? If the latter what process would i use to get my contrib modules back into the module directory and start integrating them back into my drupal install and not lose any possible module related data?

The modules are the tricky part to me since you do not want to lose any database information for modules that installed their own tables in the previous drupal database during the update process.

rkendall’s picture

Even if you don't have the contrib module activated or the files in the 'modules' directory, all your data will be safe in the database.

When the module is upgraded to work with 4.6, you can download the new version and put it the 'modules' directory (following any module specific upgrade instructions). When you activate it again, you should find all your data appear again.

Of course, there is a chance that something might go wrong - but that's why your doing a test upgrade. :)

fwnetwork’s picture

I still get the same error.

rkendall’s picture

Oh, forgot to answer about copying databases.

I use phpMyAdmin to manage my MySQL databases. It has various export options, and various upload options.

Otherwise you can use the command-line mysqldump program.

bomarmonk’s picture

Note my comments below relate to phpMyAdmin 2.6.0-pl3:

Just be careful that when you backup your database, you've selected all the tables and data. I used export "database" (there's an export tab at the top of the right-frame's options when you open the database). I accepted the default settings for export, clicked on "select all" under the tables list, checked "save as file," renamed the file to my liking, and under compression selected "none" (I have a high speed connection, so compression might be better with a slower connection--dial-up). When you hit "go" at the bottom of the export page, the database will be saved in a location that you choose in the file browser window.

Now I have a second empty mySQL database I wanted to fill for testing:
To get the database up, first I make sure I am looking at the proper database that needs to be filled with the exported data (you can use your database window in the left-pane to browse the databases-- I had to change my config file in phpMyAdmin to access the new database, but I think there is a way to access both). Then I selected "SQL" in the options in the top right-pane, where it says "...location of text file" in the SQL page, I select "browse." Then I can browse my directories until I find the file I exported. When I select this file and then press go, my tables, data, and entire database will be uploaded to the test database. That should do it.

smartango’s picture

I am playing with drupal from a week now. I am interested in i18n module: it happen this:

CREATE TABLE `i18n_node` (
`trid` int(10) unsigned NOT NULL default '0',
`nid` int(11) NOT NULL default '0',
`status` smallint(6) NOT NULL default '0',
PRIMARY KEY (`trid`,`nid`)
) TYPE=MyISAM;

# Add language field to node table

ALTER TABLE `node`
ADD `language` char(2) NOT NULL default '';

# Add language and trid fields to term_data
ALTER TABLE `term_data`
ADD `language` char(2) NOT NULL default '',
ADD `trid` int(11) NOT NULL default '0';

is the db(mysql) change, (ok i18n_node table) what does it do update.php?

what about problem with other patch/modules?

chx’s picture

Until 4.6 is not released neither Jose nor I will NOT reroll patches. If someone has a lot of free time, to reroll patches sometimes two times a day, come, join us!

Of the DB changes, update with update.php to 4.6, and change after it. On the other hand, update.php does not care about the original state... at least I think so.

--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.

mariagwyn’s picture

I just rewrote over the 4.6 install I had (following the advice to download a fresh copy). I haven't really done anything on the original working install. But, I have the following error:

Parse error: parse error, unexpected T_CONSTANT_ENCAPSED_STRING in /home/mgwynm/public_html/drupal/includes/common.inc on line 1086

Line 1086 of common.inc in my installation is:

  $element = '<input type="radio" class="'. _form_get_class('form-radio', $required, _form_get_error($name)) .'" name="edit['. $name .']" value="'. $value .'"'. ($checked ? ' checked="checked"' : '') . drupal_attributes($attributes)' />';

No new modules have been added.

Any ideas? I don't know what it means. All files were updated.
Thanks,
Maria

Prometheus6’s picture

It needs a concatenation operator.

drupal_attributes($attributes)' />';
should be
drupal_attributes($attributes) . ' />';

mariagwyn’s picture

Thanks. I replaced it, uploaded, and had the same error on a different line. I ended up having so many erros (5 of the same, then a new one) that I simply redownloaded the newest common.inc, wrote over mine, uploaded, and we appear to be good to go. Thanks for the help. I am not sure how the file got corrupted, but it works now.

Maria

Bèr Kessels’s picture

The manuals clearly state that you shoud *not overwrite*. But use a clean set of files.
---
NOTE: this announcement is *not* a support thread. all support will be deleted

[Bèr Kessels | Drupal services www.webschuur.com]

mariagwyn’s picture

My understanding of this comment in the manuals was that we should not overwirte 4.5 by 4.6, not that we can't replace 4.6 with 4.6. Is that an incorrect read?

Bèr Kessels’s picture

Explanation by case:
Drupal 4.5 lives in:
/drupal

You first move that to
/drupal-4-5

Then you makea new directory
/drupal

There you can dump your new installation

Now you copy (one at the time time) your custommade themes into /drupal/themes and modules into /drupal/modules
debug and upgrade them when you do so. Lastly you can look on drupal.org for modules that you needed in the old site, so that you can install these on the new site too.

The reason behind all this is that Drupal is not backwards compatible. If you simply drop your new 4.6 over an old 4.5 some files will remain and corrupt your system.

off course you can replace 4.6RC with 4.6 when it is released.

---
If this solved you problem, please report back. This will help others whom are looking for the same solution.
Next time, please consider to file a support request.

[Bèr Kessels | Drupal services www.webschuur.com]

mariagwyn’s picture

That is helpful. However, I realized that I mis-typed. My problem occured when I overwrote 4.6RC with a 'fresh' download of 4.6RC. Somehow the file became corrupted, though no other files had the same problem.

Steven’s picture

If you upload your files through FTP, then some FTP clients will append to the file by default if the existing file is smaller than the new file ("resume upload"). This is of course bad if the two files are not the same. Perhaps this is what happened.

--
If you have a problem, please search before posting a question.

slowrock’s picture

I got this message when tried to click "parent" link after wrote a first comment for first story.

warning: Missing argument 1 for comment_reply() in /var/www/slowrock/html/index/modules/comment.module on line 364.

edg’s picture

I just installed Drupal and got this same error message.

warning: Missing argument 1 for comment_reply() in /home/

moebis’s picture

Dries,

I did a search for a Slovak translation and it appears the project was dropped. I would like to offer to work on it, my wife has agreed to start the translations over the next few weeks. I'll look into how to setup the interface translation templates.

This post serves several purposes. 1) To let anyone who may be searching for a Slovak translation know it will be started. 2) To officially start the CVS project for this.

I'm very new to this, so any suggestions on where to start would prove very helpful. Pitfalls, steps, etc. Thanks.

www.moebis.com

Steven’s picture

The best place to start in the contribute link at the top of this site.

--
If you have a problem, please search before posting a question.

moebis’s picture

I already applied for CVS access and have Tortoise CVS on my win box. What I want to do is have my wife translate the site on the fly (as she finds a term, adds the Slovak translation for it) and then I can export the .PO and .POT files. The only problem I'm having now, is the instructions are a little bit unclear as to how to "import" or "use" the template in the CVS translation directory. If I follow what it's saying, I have to manually text edit each .PO file and edit the headers, then compile as a entire .POT and upload ALL to CVS? Clearer instructions will go a long way to getting more people to either 1) Finish translations or 2) Start translations on ones that don't exist. I'll volunteer to writeup a quick FAQ or Getting Started guide, once I'm comfortable with the process.

www.moebis.com

muzza’s picture

Hi All,

I need some information to get multiple sites working in 4.6.0. If my default Drupal site is at www.example.net and I want another site at www.example.net/subsite then according to the documentation I have to make a directory in sites called www,example.net.subsite and in the settings.php file in that directory point to the subsite mysql database and make the base URL www.example.net/subsite. If my document root for www.example.net is /www/srv/htdocs then does my content for this subsite go in /www/srv/htdocs/subsite or does the content go under my sites directory? In this case does anything need to be changed in apache to handle this or in the case of other sites with completely different domain names?

Thanks

Murray

muzza’s picture

Hi All,

I have tried increasing the all the upload limits for users in Administer / Settings / Uploads but I still can't upload any file > 1MB. Could someone please indicate where this setting is stored (table name or config file) so I can work around the problem.

Thanks

Murray

sepeck’s picture

turn on upload module.
admin / settings / uploads.

Please start a new thread for support questions. :)

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

muzza’s picture

Hi Sepeck

The upload module is on. The size of the files is the problem. I can upload files < 1MB to a total of 1MB which is pretty useless for me at the moment. Whatever I set the individual and total file size limits appears to have no effect.

Regarding threads - I hope this is the correct place to post this question. I was not sure if I should post questions about the release candidate in the support forums.

Murray

Netlynx’s picture

I'm not using the new release yet but you might find it is to do with the php settings on your server.

These are the settings I tweaked to get it working on 5.2

php.ini settings required to allow large file uploads (note mine is a private site for clients so the limits are lifted to 50mb; adjust to what you need):

max_execution_time = 60; --note: if this is not high enough (in seconds) your upload just times out.
max_input_time = 60;
memory_limit = 50M;
upload_max_filesize = 50M;
post_max_size = 50M;

You will find these in your php.ini file.
Good hunting.

muzza’s picture

It was the limits in php.ini. I will note that one down for future reference.

Thanks for your help.

Murray

sepeck’s picture

Threads on RC in the support forums are fine :)

If it's not there, then it's probably in your php.ini as the other reposnse suggests. If you drop a phpinfo script (see php.net) on your web server you can see your servers settings. Mine has upload_max_filesize = 16M

-sp
---------
Test site...always start with a test site.
Drupal Best Practices Guide

-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide

muzza’s picture

The ldap_addressbook module works fine for me on 4.6.0 with no changes from 4.5.2 although I had to make some of the suggested fixes on to make it work on 4.5.2 originally. In other words if you got it working on 4.5.2 it should work fine on 4.6.0.

Unfortunately the same can't be said for the project module which is probably a lot more complicated. I installed it and got the error below when I enabled it:

warning: Missing argument 1 for project_node_types() in /srv/www/htdocs/modules/project/project.module on line 50.

When I tried click on the project link I got the error below:

Fatal error: Call to undefined function: node_access_join_sql() in /srv/www/htdocs/modules/project/project.module on line 282

Does anyone know of the status of porting the module to 4.6.0?

Thanks

Murray

igorschlum’s picture

Hello Murray,

Following the Fosdem Event, we installed Drupal 4.6 and this Friday the Project Module. The 4.5.2 version was not working, but the CVS version is find.

Igor

muzza’s picture

Hi Igor,

Thanks for the reply. I tried the CVS version and it installed OK but it appears still to have problems. I created a project but it didn't appear in the list of projects so I can't add issues to it. I also get the errors below when I view My Projects,

warning: Invalid argument supplied for foreach() in /srv/www/htdocs/includes/tablesort.inc on line 160.

warning: Invalid argument supplied for foreach() in /srv/www/htdocs/includes/tablesort.inc on line 198

Looks like things are getting closer but there is still a bit of work to do yet which is probably why it is still in CVS and not a 4.6.0 release yet. It is not a big show stopper for me to use the module. I imagine the bugs will be ironed out soon.

Regards

Murray

bkark’s picture

After choosing to delete a user, instead of confirming the deletion, it just brings me back to the users page with no errors and the user is still there. If I try to delete a user who hasn't been blocked yet, instead of being told I can't delete them, it also just brings me back to the user list. Has anyone else successfully deleted a user with 4.6 RC?

Donovan’s picture

I received the following error when deleting a forum:

user error: Table 'db98198454.forum' doesn't exist
query: SELECT f.nid FROM forum f WHERE f.tid = 15 in /homepages/.../includes/database.mysql.inc on line 66.
warning: Cannot modify header information - headers already sent by (output started at /homepages/.../includes/common.inc:385) in /homepages/.../includes/common.inc on line 193.

However, I receive a successful "forum deleted" message after clicking "back" and refreshing the page. My installation uses a database prefix -- is it possible that the prefix is being ignored in an isolated block of code?

Donovan.

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

David Poblador i Garcia’s picture

Post title is written both on the title and body field when using Blogger API. info + patch

malfunct’s picture

I've been upgrading my main database since like 4.1.x or something like that, so it could have some old stuff lying around in it but this is the first time an upgrade gave me errors.

Basically one of the last things the upgrade does is put a primary key constraint on the term_node table. My term_node table has lots of non-unique rows and so altering the table to add the constraint fails. I am at a loss as to what a query to remove all but one of the non-unique rows would look like so I can't make any suggestions but fixing the upgrade issue should probably be done before releasing as my logs are filling up with errors due to non-unique results being returned in term_node queries.

malfunct’s picture

There is one log line for each update attempt. I didn't realize the update script was integrated with the rest of drupal. Its actually pretty nifty that it is.

I manually removed all the duplicates and added the primary key constraint and now there are no issues that I can see.

jweiss’s picture

Just wondering how long this rc is finalized?

kbahey’s picture

Real Soon Now. Sometime in April most probably.
--
Consulting: 2bits.com
Personal: Baheyeldin.com

--
Drupal performance tuning and optimization, hosting, development, and consulting: 2bits.com, Inc. and Twitter at: @2bits
Personal blog: Ba

AliaK’s picture

I might have missed something really obvious, but I've just upgraded the db from 4.5.2 to 4.6RC and now the aggregator feeds aren't displaying the urls as links, just escaping & displaying the html
eg http://www.indienews.org/ - 4.5.2 used to display the url as a link (whereas an older 4.something, maybe 1? version did both - http://www.aliak.com/module.php?mod=import&op=feed&id=17, but that's another issue), but not display images, but 4.6 doesn't seem to do either. I've checked content filters. is there somewhere else I should check? I don't remember having to set anything up for this to work on other sites but perhaps I had extra modules installed which did it. atm I only have base 4.6rc, no contributed modules installed. will continue tomorrow night.
should I raise a bug for this or have I just missed a config somewhere.

thanks for the new enclosures tag in the syndicate though!! this is working well from my initial tests!

update: sat 02/04:
I installed url filter and tried all ordering combinations, but still no luck. I've rolled back to the 452 aggregator.module and it's ok. still doesn't display images, but at least the urls are being converted to links.

is anyone else having this issue or just me

thanks

jvincher’s picture

is this the same issue as I am mentioning here?

URL's don't convert and the feed body displays HTML tags.

http://drupal.org/node/19874

jdlilly’s picture

Thanks for making mutiple sites easier in 4.6, it is much appreciated.
Having installed/configged 4.6 w/out a problem, I'm now trying to set up mutiple sites on my local development instance (Windows box).

Per the instructions, I set up a second database (drupal_foo), a new sites folder (localhost.foo), and I modified the new settings.php with the right parameters...

$db_url = 'mysql://myuserhere:mypasswordhere@localhost/drupal_foo';
$base_url = 'http://localhost/foo';

When I browse to http://localhost/, I get my original site.
When I browse to http://localhost/foo I get a "requested URL not found error." Am I setting it up wrong or does this method not work when you are using localhost (working locally)?

I searched the forums and comments, could not find an answer to this.
Thanks.

marqpdx’s picture

hi bro,
might work to try setting up the second as foo.localhost instead, and then refer to it as http://foo.localhost

you might have to setup a virtual host in http.conf...

ml

Prometheus6’s picture

The way it works on *nix is to set your domains up to point to the same actual location, via symbolic link or by having DNS point the domains to the same directory. You don't actually want a physical directory for your subsequent sites.

In Windows using IIS, setting up virtual directories should work. You can set up http://localhost/foo pointing to your Drupal install directory. With Apache, you'll have to set up the Windows equivalent of a symbolic link. There are several utilities that will help; here's a Google search to start you out.

SeanK’s picture

Congratulations on currently having less than 10 outstanding critical bugs remaining in the cvs version.

I've only started testing the CMS recently, and find it to be the most robust tool I've seen to date. Bravo on a wonderful product.

I still see that there are quite a few outstanding normal bugs, however several are nearly six months old at this point; some are older than that.

At what point is your threshold set for the RC to consider the release stable and go gold?

Lou Quillio’s picture

Currently linked `drupal-4.6.0-rc.tar.gz` (and CVS) appears to contain a truncated `database.mysql`.

Lou Quillio’s picture

Never mind. My mistake.

calumet’s picture

In the 4.6RC version, for login users this piece of code is used:
< f o r m action="?q=user/login&destination=node" method="post">

In 4.5.2, was used:
< f o r m action="?q=user/login" method="post">

(without the spaces in " f o r m")

The new code in 4.6RC broken XHTML validation. "&" should be sustituted with "&amp;" for correct XTHML.

Is this a bug or a missed something?

Steven’s picture

I fixed this bug. Next time please follow instructions and report bugs through the issue tracker!

You can use the <code> tag for posting HTML like that.

--
If you have a problem, please search before posting a question.

alexis’s picture

Hi, just to report I've just installed 4.6RC from CVS, everything went fine and I like what I see.

Forums are so much easy to setup.
It's nice having access control right where it is and not having to go to users.

I've got all the modules I use from CVS too and so far I only find problems with bookreview (it seems it's still using 4.5 features). I will review it in detail tomorrow.

I will rework my php template tomorrow too.

One question, do I still need using sections.module to have a different template applied to my admin pages?

Thanks for your great work!

Alexis Bellido - Ventanazul web solutions

dr05’s picture

The new Theme 4.6.0 use a standard theme with NO TABLES for the desig?
(Ok tables for the calendar are evt. ok.)
- W3C AAA compatible?

Steven’s picture

There are several contributed CSS-based themes for Drupal. For core, tabled is still the most versatile solution unfortunately. Drupal is not a blog: we need to accomodate more than just text + comments.

--
If you have a problem, please search before posting a question.

leblank@cyberocity.com’s picture

Grats on the new release! I'm sure a lot of people put a lot of work into it! I will be upgrading soon as the dust settles a little bit.

I couldn't help noticing a couple of spirited conversations about taxonomy. I thought about them for about an hour and it seems there are valid points to either side. So, IMHO, and with a fervent hope I won't get trampled by the elephants as they peer squinty-eyed at shadows and wheel about pugnaciously on this narrow little jungle trail ... I would ask if it is possible to just put in a switch to select between the new taxonomy and the old taxonomy.

Perhaps the new taxonomy could be a default "auto" setting for use by new-b's and those who prefer it, and then a simple checkbox in admin allowing change to the old taxonomy form.

This may be a way to have the functionality of both, which are both valid, and this would be an overall plus no matter which side you're on, I hope.

Lot more work though I imagine, but perhaps it might be a possibility.

Humbly dodging the mighty elephants, kings of the jungle, who shake the earth as they pass, in all their majesty, whose pooh pooh is perfume to our noses, blah blah blah ...

LeBlank

iraszl’s picture

"X new ..." links always takes you to the latest unread posts which is great. Except when there are many pages. In that case it just takes you the first page of the thread instead of the latest post. The users on my site find this very annoying, if this is intentional, pls think it over one more time. Thank you so much!
---
http://creativebits.org

robertb9527’s picture

I am lovin it!

---
http://www.b9527.net

phireak’s picture

Any one can resolve? error below
--------------------------------------------------------
{head} {styles}
{_BLOCK_.header.logo} {_BLOCK_.header.site_name}
{secondary_links}
{primary_links}

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.

The first thing you will need to do is create the first account. This account will have full administration rights and will allow you to configure your website. Once logged in, you can visit the administration section and set up your site's configuration.

Drupal comes with various modules, each of which contains a specific piece of functionality. You should visit the module list and enable those modules which suit your website's needs.

Themes handle the presentation of your website. You can use one of the existing themes, modify them or create your own from scratch.

We suggest you look around the administration section and explore the various options Drupal offers you. For more information, you can refer to the Drupal handbook online.
--------------------------------------

nathandigriz’s picture

http://www.hiveminds.co.uk/node/883

You can fix this yourself or use the file provided and upgrade to from 4.6.6 to 4.6.8.