- Development - lists.drupal.org

[drupal-devel] [task] improve theme system
by walkah 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: walkah Status: patch looks good to me. +1 walkah Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 11:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent.. ------------------------------------------------------------------------ April 28, 2005 - 11:40 : stefan nagtegaal Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file. ------------------------------------------------------------------------ April 28, 2005 - 11:44 : dikini +1 from me it makes help text themeable it uses semantic markup, which is good practice, or as some say the Right Way ------------------------------------------------------------------------ April 28, 2005 - 12:00 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/cleaner_themable_help_0.patch (1.99 KB) The patch had DOS line endings and wouldn't apply. I fully support this patch. +1 ------------------------------------------------------------------------ April 28, 2005 - 13:38 : adrian I completely +1 this. ------------------------------------------------------------------------ April 28, 2005 - 16:07 : stefan nagtegaal Attachment: http://drupal.org/files/issues/phptemplate_drupal_get_help.patch (816 bytes) Because Adrian +1's this, his reward is a proper patch against PHPTemplate, sorry I forgot this one... here it is, a really simple one liner which does the job... <?php Index: phptemplate.engine =================================================================== RCS file: /cvs/drupal/contributions/theme-engines/phptemplate/phptemplate.engine,v retrieving revision 1.24.2.1 diff -u -F^f -r1.24.2.1 phptemplate.engine --- phptemplate.engine 23 Apr 2005 01:04:53 -0000 1.24.2.1 +++ phptemplate.engine 28 Apr 2005 21:03:59 -0000 @@ -219,7 +219,7 @@ function phptemplate_page($content) { 'tabs' => theme('menu_local_tasks'), 'messages' => theme_status_messages(), 'layout' => $layout, - 'help' => menu_get_active_help(), + 'help' => theme('help', drupal_get_help()), 'styles' => theme_get_styles(), 'mission' => $mission, 'is_front' => $frontpage, ?>

1 0

[drupal-devel] [task] improve theme system
by stefan nagtegaal 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: stefan nagtegaal Status: patch Attachment: http://drupal.org/files/issues/phptemplate_drupal_get_help.patch (816 bytes) Because Adrian +1's this, his reward is a proper patch against PHPTemplate, sorry I forgot this one... here it is, a really simple one liner which does the job... <?php Index: phptemplate.engine =================================================================== RCS file: /cvs/drupal/contributions/theme-engines/phptemplate/phptemplate.engine,v retrieving revision 1.24.2.1 diff -u -F^f -r1.24.2.1 phptemplate.engine --- phptemplate.engine 23 Apr 2005 01:04:53 -0000 1.24.2.1 +++ phptemplate.engine 28 Apr 2005 21:03:59 -0000 @@ -219,7 +219,7 @@ function phptemplate_page($content) { 'tabs' => theme('menu_local_tasks'), 'messages' => theme_status_messages(), 'layout' => $layout, - 'help' => menu_get_active_help(), + 'help' => theme('help', drupal_get_help()), 'styles' => theme_get_styles(), 'mission' => $mission, 'is_front' => $frontpage, ?> stefan nagtegaal Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 18:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent.. ------------------------------------------------------------------------ April 28, 2005 - 18:40 : stefan nagtegaal Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file. ------------------------------------------------------------------------ April 28, 2005 - 18:44 : dikini +1 from me it makes help text themeable it uses semantic markup, which is good practice, or as some say the Right Way ------------------------------------------------------------------------ April 28, 2005 - 19:00 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/cleaner_themable_help_0.patch (1.99 KB) The patch had DOS line endings and wouldn't apply. I fully support this patch. +1 ------------------------------------------------------------------------ April 28, 2005 - 20:38 : adrian I completely +1 this.

1 0

[drupal-devel] [task] improve theme system
by adrian 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: adrian Status: patch I completely +1 this. adrian Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 18:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent.. ------------------------------------------------------------------------ April 28, 2005 - 18:40 : stefan nagtegaal Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file. ------------------------------------------------------------------------ April 28, 2005 - 18:44 : dikini +1 from me it makes help text themeable it uses semantic markup, which is good practice, or as some say the Right Way ------------------------------------------------------------------------ April 28, 2005 - 19:00 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/cleaner_themable_help_0.patch (1.99 KB) The patch had DOS line endings and wouldn't apply. I fully support this patch. +1

1 0

[drupal-devel] [task] Make posting permission more granular.
by Gerhard Killesreiter 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/10426 Project: Drupal Version: cvs Component: comment.module Category: tasks Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: Gerhard Killesreiter Status: patch menesis, thanks for looking at the patch! Currently, we have two ways to determine permissions for a node. One is the general node_access function and one is the node specific function (eg book_access). I have implemented the comment permission check through the latter. This has two reasons: It does not change the current behaviour for those modules and it does not require database queries. I am open for discussion on it. Gerhard Killesreiter Previous comments: ------------------------------------------------------------------------ August 29, 2004 - 06:55 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment.patch (5 KB) There have been requests to private forums. I think the most straightforward way to allow them is by extending the node_access hook. The attached patch tries this. It assumes that my node object caching patch got committed. Afterwards loading a node twice won't be a performance issue anymore. The patch is untested, I'd like to get feedback on the implementation. ------------------------------------------------------------------------ August 31, 2004 - 16:53 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment_0.patch (5.02 KB) The patch is now tested. I think this needs a better explanations: The patch isn't only for forums (which still need some kind of taxonomy permissions) but applies to all nodes. You can set individual nodes to be commentable through the _access hook. This would be helpfull for a forum where only a selected role should be allowed to post, but others should read the announcements. ------------------------------------------------------------------------ September 4, 2004 - 08:57 : killes(a)www.drop.org The patch has a small problem: We need either to move this check <?php if ($op == 'comment' && $node->comment == 2 && user_access('post comments')) { return TRUE; } ?> before the db query (and thus taking away a bit of the power from that patch) or add a grant_comment column to the node_access table: alter table node_access add grant_comment tinyint(1) unsigned NOT NULL default '0'; ------------------------------------------------------------------------ September 5, 2004 - 10:42 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment_0_0.patch (4.78 KB) Keeping up with CVS. I'd like to receive some feedback on the resolution of the problme mentioned above. ------------------------------------------------------------------------ September 13, 2004 - 02:25 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/module_0.patch (7.1 KB) Keeping up with cvs. Node modules should implement _access('comment'). ------------------------------------------------------------------------ September 14, 2004 - 06:38 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/commentable.patch (7.89 KB) Had forgotten blog.module ------------------------------------------------------------------------ February 5, 2005 - 00:19 : Steven Is this patch still needed? Doesn't it tie comment.module unnecessarily into node.module? ------------------------------------------------------------------------ February 8, 2005 - 00:01 : killes(a)www.drop.org Yes, the patch is still needed. The patch actually removes more code from node.module than it adds. Both modules are essential to Drupal and some degree of interaction is tolerable, I think. You can still disable comment.module withou any ill effects. ------------------------------------------------------------------------ April 26, 2005 - 21:07 : Cvbge Hello I need to be able to a) post/reply etc on forums as anonymous user b) do not anon users to edit it's own (probably made by other anon users) forum posts c) do not allow anyone to post comments to any other node types AFAIK currently it's not possibile, but it'd be possibile with this patch, so I'd be glad it it was accepted. ------------------------------------------------------------------------ April 27, 2005 - 15:35 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/commentable_0.patch (8.85 KB) Updated patch. Note that the db upgrade path is missing. I'll add that after my revisions patch got committed. ------------------------------------------------------------------------ April 28, 2005 - 17:26 : menesis The patch looks strange to me, because of such changes in each module: <?php if ($op == 'comment') { if (user_access('post comments') && $node->comment == 2) { return TRUE; } } ?> They are not needed. I think they even negate the other parts of the patch, by always allowing to comment those node types. Usually hook_access deals only with permissions defined by that module, and not mess with other permissions, node module handles those anyway. So node-access-comment_0.patch [1] looks better than later patches, except the above last hunk in node.module. I might be wrong, and I haven't tested it... A big change and access modules need to be modified too... [1] http://drupal.org/files/issues/node-access-comment_0.patch

1 0

[drupal-devel] [task] Make posting permission more granular.
by menesis 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/10426 Project: Drupal Version: cvs Component: comment.module Category: tasks Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: menesis Status: patch The patch looks strange to me, because of such changes in each module: <?php if ($op == 'comment') { if (user_access('post comments') && $node->comment == 2) { return TRUE; } } ?> They are not needed. I think they even negate the other parts of the patch, by always allowing to comment those node types. Usually hook_access deals only with permissions defined by that module, and not mess with other permissions, node module handles those anyway. So node-access-comment_0.patch [1] looks better than later patches, except the above last hunk in node.module. I might be wrong, and I haven't tested it... A big change and access modules need to be modified too... [1] http://drupal.org/files/issues/node-access-comment_0.patch menesis Previous comments: ------------------------------------------------------------------------ August 29, 2004 - 09:55 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment.patch (5 KB) There have been requests to private forums. I think the most straightforward way to allow them is by extending the node_access hook. The attached patch tries this. It assumes that my node object caching patch got committed. Afterwards loading a node twice won't be a performance issue anymore. The patch is untested, I'd like to get feedback on the implementation. ------------------------------------------------------------------------ August 31, 2004 - 19:53 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment_0.patch (5.02 KB) The patch is now tested. I think this needs a better explanations: The patch isn't only for forums (which still need some kind of taxonomy permissions) but applies to all nodes. You can set individual nodes to be commentable through the _access hook. This would be helpfull for a forum where only a selected role should be allowed to post, but others should read the announcements. ------------------------------------------------------------------------ September 4, 2004 - 11:57 : killes(a)www.drop.org The patch has a small problem: We need either to move this check <?php if ($op == 'comment' && $node->comment == 2 && user_access('post comments')) { return TRUE; } ?> before the db query (and thus taking away a bit of the power from that patch) or add a grant_comment column to the node_access table: alter table node_access add grant_comment tinyint(1) unsigned NOT NULL default '0'; ------------------------------------------------------------------------ September 5, 2004 - 13:42 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/node-access-comment_0_0.patch (4.78 KB) Keeping up with CVS. I'd like to receive some feedback on the resolution of the problme mentioned above. ------------------------------------------------------------------------ September 13, 2004 - 05:25 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/module_0.patch (7.1 KB) Keeping up with cvs. Node modules should implement _access('comment'). ------------------------------------------------------------------------ September 14, 2004 - 09:38 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/commentable.patch (7.89 KB) Had forgotten blog.module ------------------------------------------------------------------------ February 5, 2005 - 03:19 : Steven Is this patch still needed? Doesn't it tie comment.module unnecessarily into node.module? ------------------------------------------------------------------------ February 8, 2005 - 03:01 : killes(a)www.drop.org Yes, the patch is still needed. The patch actually removes more code from node.module than it adds. Both modules are essential to Drupal and some degree of interaction is tolerable, I think. You can still disable comment.module withou any ill effects. ------------------------------------------------------------------------ April 27, 2005 - 00:07 : Cvbge Hello I need to be able to a) post/reply etc on forums as anonymous user b) do not anon users to edit it's own (probably made by other anon users) forum posts c) do not allow anyone to post comments to any other node types AFAIK currently it's not possibile, but it'd be possibile with this patch, so I'd be glad it it was accepted. ------------------------------------------------------------------------ April 27, 2005 - 18:35 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/commentable_0.patch (8.85 KB) Updated patch. Note that the db upgrade path is missing. I'll add that after my revisions patch got committed.

1 0

[drupal-devel] [task] improve theme system
by killes 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: killes(a)www.drop.org Status: patch Attachment: http://drupal.org/files/issues/cleaner_themable_help_0.patch (1.99 KB) The patch had DOS line endings and wouldn't apply. I fully support this patch. +1 killes(a)www.drop.org Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 17:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent.. ------------------------------------------------------------------------ April 28, 2005 - 17:40 : stefan nagtegaal Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file. ------------------------------------------------------------------------ April 28, 2005 - 17:44 : dikini +1 from me it makes help text themeable it uses semantic markup, which is good practice, or as some say the Right Way

1 0

[drupal-devel] Requesting code review on HTTP auth module
by Tim Altman 28 Apr '05

28 Apr '05

Greetings, I've been working on a module to replace Drupal's login form with HTTP auth. Since this has to do with authentication, I'd appreciate some code (and logic) review. The module is in http://cvs.drupal.org/viewcvs/drupal/contributions/sandbox/junyor/http_auth/. Thanks! -- Tim Altman

3 5

[drupal-devel] [task] improve theme system
by dikini 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: dikini Status: patch +1 from me it makes help text themeable it uses semantic markup, which is good practice, or as some say the Right Way dikini Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 16:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent.. ------------------------------------------------------------------------ April 28, 2005 - 16:40 : stefan nagtegaal Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file.

1 0

[drupal-devel] [task] improve theme system
by stefan nagtegaal 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/21517 Project: Drupal Version: cvs Component: theme system Category: tasks Priority: normal Assigned to: stefan nagtegaal Reported by: stefan nagtegaal Updated by: stefan nagtegaal -Status: active +Status: patch Attachment: http://drupal.org/files/issues/cleaner_themable_help.patch (1.99 KB) The attached patch does: - remove unused function theme_help() and theme_error(); - added a wrapper function drupal_get_help() inside common.inc (for consistency with drupal_get_title(), drupal_get_breadcrumb(), etc); - reimplemented theme_help(), only this time for a more consistent way for themers; This patch makes it easier to theme the page specific helptexts for drupal. To change your PHP-based themes, you can do: <?php - if ($help = menu_get_active_help()) { - $output .= '<small>'. $help .'</small><hr />'; - } + $output .= theme('help', drupal_get_help()); ?> To change your PHP-Template based theme: <?php if ($help): ?> <?php print $help; ?> <?php endif; ?> becomes a simple: <?php print $help; ?> If this patch is accepted i'll try to make the functions for returning the local tasks and the status messages behave the same.. Overriding the <div class="help">...</div> could be done through deifinig your own theme_help() function in your theme or template.php file. stefan nagtegaal Previous comments: ------------------------------------------------------------------------ April 28, 2005 - 18:21 : stefan nagtegaal The theme system is very inconsistent and not clean. In a steady stream of patches i'll try to make the theme system clean and let most of the theme functions behave the same.. One of the main goals is, that when writing themes in PHPTemplate for example, the way how things are being returned is different from theme function to theme function.. Let's try to unify this, so theming will be more efficient, simpler and more consistent..

1 0

[drupal-devel] [task] Introduce Daylight Saving Time for Drupal
by Sage 28 Apr '05

28 Apr '05

Issue status update for http://drupal.org/node/11077 Project: Drupal Version: cvs Component: base system Category: tasks Priority: normal Assigned to: killes(a)www.drop.org Reported by: killes(a)www.drop.org Updated by: Sage Status: patch This is an incredibly useful feature and I would like to see it incorporated into the next release (current release is 4.6.0). Sage Previous comments: ------------------------------------------------------------------------ September 25, 2004 - 22:01 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/dst.patch (6.04 KB) Many people have wanted to have a Daylight Saving Time setting in the past. If we use the "server time" modell (all times are displayed the same around the world) this isn't all that hard to do. I found a lot of usefull information here: http://webexhibits.org/daylightsaving/g.html The patch introduces a new DST setting and uses it if the "Configurable time zones" setting is switched off. ------------------------------------------------------------------------ September 25, 2004 - 23:40 : gordon This is a lovely patch, but you do realise that you have opened a can of worms. Daylight saving is a messy business, I had to write the Contestable Electricity billing for a company here in Australia which had multiple installations in multpile timezones, all with different daylight savings rules, which impacted upon the bill. The way that dst is legistated is very messy and here is Australia it is very messy. Daylight savings don't follow state lines, as some towns that are very close to the border may choose to follow the only the daylight saving period of the next state, and when we had the olympics NSW went into daylight savings months before anyone else. There are other examples of weird things like even the 1 hour forward is not also true. I know that in the 1999 change to daylight savings there was a small set of islands north of New Zealand that went ahead by 2 hours as they wanted to be the first into 2000. >From what I can see of your patch it only allows for a single daylight savings period for the entire system. Their can be situations where there can be users from multiple countries and in different timezones/dst. I think that entire timezone system needs to looked at again, and maybe re-implement it so that it will allow for dst. Maybe make it a bit more user friendly so instead of setting up the timezone by name much like how operating systems do it, and then this will automatically work out the timezone. +1 for this is something that would be good, but it still needs work. ------------------------------------------------------------------------ September 26, 2004 - 09:13 : Anonymous The patch works as it is now. I had good reason to limit its capability to the setting where users cannot chose their own timezone. ;) I also assume that a server administrator knows if he has dst or not. I also didn't (yet) cater for all countries where dst is in use mainly because some insist on not giving a sensible rule for the change dates. ------------------------------------------------------------------------ September 26, 2004 - 17:54 : killes(a)www.drop.org Attachment: http://drupal.org/files/issues/dst_0.patch (6.04 KB) The last comment was mine. After a code review by Kjartan I provide a slightly improved patch. I want to stress that solving the DST issue in a "suits everybody" manner isn't the intention of this patch. It solves the problem for people who have chosen to let all times on their site be displayed in the server's time setting. By covering a large portion of the earth's landmass I hope to be able to help most site admins. It would be possible to extend the patch to allow users to chose their DST setting, too. In my experience, however, users tend to not care about time settings at all. This may be EUrocentric though, as we have only one time zone. Feedback is welcome. ------------------------------------------------------------------------ September 27, 2004 - 16:12 : drumm +1 >From a code review I think this is an excellent solution. Could use a little more comments in the section that sets $node->date to explain the (probably good) reasoning behind that chunk of code. I don't have anything resembling a good set of tests so I did not apply the patch and try it. ------------------------------------------------------------------------ January 25, 2005 - 15:38 : killes(a)www.drop.org I just want to point out that this patch still applies and would make for a fine feature for Drupal 4.6... ------------------------------------------------------------------------ January 26, 2005 - 11:46 : alliax wouldn't hurt to have this feature in upcoming drupal. I would use it for sure, my users are from the same place, with dst

1 0