- Mar 13, 2005
-
-
Dries Buytaert authored
-
Dries Buytaert authored
- Patch #18787 by nysus: when trying to delete a forum or container, multiple instances of a Drupal page appear nested inside of each other when the confirmation of deletion page is displayed.
-
- Mar 12, 2005
-
-
Dries Buytaert authored
# The INSTALL.txt no longer contains the SERVER CONFIGURATION block. These settings are now hardcoded into sites/default/settings.php, and are merely scary technical junk here. # The INSTALL.txt has been updated with the latest system requirements. A whole sentence was struck regarding differing versions of PHP for the OSs. # The INSTALL.txt contains URLs to MySQL and PostgreSQL. If we're including the URL for PHP in the same sentence, then there's no reason why we wouldn't include them for the database engines. What are the minimal requirements for the RDBMS? Those should be included here too. # The INSTALL.txt's OPTIONAL COMPONENTS has renamed to OPTIONAL REQUIREMENTS. The only difference between the meaning is the amount of user confusion. # The INSTALL.txt has a new CONTENTS OF THIS FILE, in hopes that people will more immediately notice that there are upgrade instructions at the bottom. # The INSTALL.txt had some potentially confusing lines adjusted, including further clarifications, standarding to "userid" (instead of using both userid and username interchangebly) and so on. # I've moved most of .htaccess php_value's to the ini_set system for /sites/. There are a few reasons for this, chiefly that it is centralizing all the PHP setting modifications to one place. But, this also clears up a few initial configuration issues: first, the user doesn't have to worry about whether they have Apache 1 or 2, and whether they need to change an IfModule line. Also, the running assumption is that these php_value's are /going to work by default anyways/, when the INSTALL.txt suggests otherwise (under OPTIONAL REQUIREMENTS, it talks about "the ability to use local .htaccess files", which suggests that "local .htaccess files" INCLUDING "mod_rewrite" are entirely optional.) Some variables, however, had to remain in .htaccess because they can't be overridden at runtime, but the amount was so small that duplicating them for both Apache 1 and Apache 2 possibilities is no longer a prohibitive concern. # There are two variables in .htaccess that I'm concerned about: track_vars, and allow_call_time_pass_reference. track_vars appears to be no longer necessary (as of 4.0.3, track_vars is always on, and my setting it here had no impact on the results of a phpinfo), and allow_call_time_pass_reference seems, at least here, to ONLY WORK if the .htaccess value is set to "1", and not "On" - meaning that Drupal installations are currently working correctly with its default value (off). According to the PHP docs, this feature is now deprecated. However, since both of these variables require further investigation, track_vars has been moved to settings.php, and allow_call_time_pass_reference has been "fixed" to a 1 (not 'On'). # Along with the changes above for sites/default/settings.php, I've also removed the spacing indent in the documentation, as well as many a few grammatical/punctuation changes here and there. I don't think the leading spacing is "right" according to the style guidelines, but maybe there's a special need for it. Correct me if I'm wrong.
-
Dries Buytaert authored
-
Dries Buytaert authored
- Patch #18692 by Goba: old comments (comments for nodes having no entry in the history table anymore) are counted as new comments, since the timestamp retrieved from the history table is used to check for new comments (which is 0, if an entry was not found). This patch sets the timestamp used to check for new comments to the NODE_NEW_LIMIT value at least (which is when the history table was/should have been pruned).
-
- Mar 10, 2005
-
-
Dries Buytaert authored
- Patch #18676 by frjo: When anonymuos users are allowed to add comments there are a required e-mail field. This field are, as far as i can see, not shown publicly. A user asked me about this and after confirming that it is not shown publicly I added a description that inform the users of this. I have included a patch that add the description "The content of this field is kept private and will not be shown publicly". This is the same description that is used by the profile module.
-
- Mar 09, 2005
-
-
Dries Buytaert authored
-
Dries Buytaert authored
-
Dries Buytaert authored
-
- Mar 08, 2005
-
-
Dries Buytaert authored
-
Dries Buytaert authored
breaks your Drupal. Only themes in './themes/subdir' are picked up now.
-
Steven Wittens authored
- Fix missing format_plural()
-
- Mar 07, 2005
-
-
Steven Wittens authored
-
Dries Buytaert authored
- Patch #18216: fixed nodeapi settings hook.
-
Dries Buytaert authored
-
Dries Buytaert authored
-
- Mar 06, 2005
-
-
Dries Buytaert authored
-
Dries Buytaert authored
-
Dries Buytaert authored
- Patch #18437 by Mathias: Drupal doesn't allow URL aliases that map to Userland Manila posts since they usually contain the '$' and are considered an invalid URL. This patch allows '$' in an URL and thus an alias. It also resolves a disparity between the 'allowable characters' of absolute and relative URLs. As far as I can tell, those parts of the regexp should be the same.
-
- Mar 05, 2005
-
-
Dries Buytaert authored
-
Steven Wittens authored
-
Dries Buytaert authored
-
Steven Wittens authored
-
Dries Buytaert authored
- Patch #18418 by chx: jonbob node_access_view_all patch changed the return value of node_access_where_sql to empty which breaks nicely all queries which are still using this function. This is a good incentive to upgrade to db_rewrite_sql, yes, but I think it causes confusion, 'cos it is not really trivial why the query suddenly not works. Let's make it trivial -- rename it _node_access_where_sql, it is no longer a function to be called from outside. node_access_join_sql similarly.
-
Dries Buytaert authored
-
Dries Buytaert authored
- Patch #18382 by Neil: usability improvement: organized the blocks on the block administration page by region. (I wanted to do that myself!)
-
Dries Buytaert authored
- Patch #18380 by Neil: putting margins on paragraph tags seems like something that Drupal.css shouldn't be doing.
-
- Mar 04, 2005
-
-
Steven Wittens authored
-
Steven Wittens authored
-
- Mar 03, 2005
-
-
Steven Wittens authored
-
Steven Wittens authored
-
Dries Buytaert authored
- Patch #17955 by Neil: there was a subtle difference between form_select() and whatever taxonomy was doing.
-
Dries Buytaert authored
-
Dries Buytaert authored
-
Dries Buytaert authored
- Ignore PHP5's strict warnings for now. The real solution is to rewrite both xmlrpc.inc and xtemplate.inc.
-
Steven Wittens authored
-
Steven Wittens authored
-
Dries Buytaert authored
-
Dries Buytaert authored
- Modified patch #18328 by Neil: currently the two forum topic blocks share a number of topics in block setting. This is a bit confusing since configuring one blockshould not affect another block. Fixed some indentation as well.
-
Dries Buytaert authored
- Patch #17897 by Neil: changed the order of the joins so that a vocabulary which is not associated with any node types doesn't disappear. Also removed a centered column that shouldn't be hard coded and, IMO, looked rather weird.
-