September 2005 - Development - lists.drupal.org

Re: [drupal-devel] advanced theme in core vs all in core.
by Kobus Myburgh 07 Sep '05

07 Sep '05

As far as the discussion has progressed, I am starting to see more disadvantages to an advanced tab than advantages. Maybe another approach such as: 1. Have the options better organized and documented (as suggested earlier) 2. Have the advanced (complex?) options greyed out with their default settings by default, and simply "unlock" them by one specific advanced setting. might also work. It is always a good usability approach to limit the number of mistakes a user can make. With many advanced settings, a user can easily set the wrong option accidentally with catastrophic results, such as private/public downloads. While on this subject, it might also be possible to havea "reset to defaults" or "reset to previous configuration" for fieldsets with critical options. This would, however, be better discussed on a different thread (feel free to continue this if I am not talking too much nonsense...) Regards, Kobus >>> piotrwww(a)krukowiecki.net 9/7/2005 12:18:24 PM >>> On Tue, Sep 06, 2005 at 10:05:55AM -0400, Khalid B wrote: > > If you ask me, Drupal needs an "advanced" mode, where all these "extra" features > > can be put for users who want then, and hidden for those who don't... > > I came up with this idea some time ago to get over the impasse of > "more options is confusing" vs. "we need an option for X". > > I am + 1 for an advanced settings tab for these less used options. +1 for more settings -- Piotrek irc: #debian.pl Mors Drosophilis melanogastribus!

1 0

[drupal-devel] Re: [drupal:dries] /modules forum.module
by Karoly Negyesi 07 Sep '05

07 Sep '05

> - Usablity improvement: check whether the comment module is enabled. > If not, > show an error message. This solution is inferior to mine http://drupal.org/node/18447 . This enables comment.module automatically. Regards NK

2 1

Re: [drupal-devel] advanced theme in core vs all in core.
by Kobus Myburgh 07 Sep '05

07 Sep '05

> Actually.. having many many many settings configurable via the > interface leads to clutter, which is a usability no-no. This all depends on the presentation of your options. If this is organized properly, this usability no-no can be virtually anulled. Clutter is a usability non-no, sure, but if you organize it properly, even a lot of options can be presented without clutter. If you ask me, Drupal needs an "advanced" mode, where all these "extra" features can be put for users who want then, and hidden for those who don't... Regards, Kobus

7 14

Re: [drupal-devel] I'm back!
by Robert Douglass 07 Sep '05

07 Sep '05

Will somebody block this steven guy? He's always spamming us with viruses ;-) steven(a)acko.net wrote: > <null> > > > ------------------------------------------------------------------------ > > ****************** McAfee VirusScan ************************ > ******* Alert generated at: Wednesday, September 07, 2005 11:14:49 AM ********* > ********************************************************************* > > McAfee VirusScan has detected a potential threat in this e-mail > sent by steven(a)acko.net. > > The following actions were attempted on each suspicious part: > > The attachment "music_ranking.htm.scr" is infected with the W32/Netsky.c@MM virus(es). > This attachment has been deleted to complete the clean process. > > > We strongly recommend that you report this virus-related activity > to steven(a)acko.net. >

1 0

[drupal-devel] I'm back!
by steven＠acko.net 07 Sep '05

07 Sep '05

<null>

1 0

[drupal-devel] advanced theme in core vs all in core.
by Bèr Kessels 07 Sep '05

07 Sep '05

Hi, Recently two issues, namely online/offline icons [1] and several Ajax issues (with konqueror mainly) made me think that we need to give more power to the themes and put less cruft in core. José A Reyero came with that exact same idea [2], which is why I think we should get this idea on the ML. I would like to see one theme in core that does and has it all: AJAX, avatars, icons for user statii, icons in the admin areas, advanced menu styles, and whatever more you can think of. Currently we all "enforce" these things onto all Drupal sites, while in fact we could (and should IMHO) ship a lightweighted drupal. Yet show the power of Drupal in a full featured theme. What do you ppl think? put AJAX in one core theme? Add the online offline icons there? Add more features to a theme? [1] http://drupal.org/node/29281 [2] http://drupal.org/node/30150 Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]

7 12

[drupal-devel] Crucial problem with mysql 4.1.x and collation
by Abalieno 07 Sep '05

07 Sep '05

This is a rather serious problem, from my point of view, that I foresee getting rather widespread if not solved quickly. After a few hours of research and an headache here's what I discovered: - Mysql 4.1.x adds the possibility to set a collation for the database. This seems a new feature that wasn't there before. - By default it seems that every database created or imported is automatically set to "latin1_swedish_ci". The whole database is set with that collation as you install drupal under that version of mysql or import a previous dump. - This is causing a serious corruption in the database while exporting it because accented and other utf-8 characters are just NOT COMPATIBLE with the latin1_swedish_ci set. - This means that if you install drupal on mysql 4.1.x, the very first time you export the database for a backup or whetever else, you'll finish with a corrupted dump because all the accented characters in the nodes, comments and aggregator items will get replaced with GARBAGE. As -> "SaturdayÃƒÂ¢Ã¢â€šÂ¬Ã¢â€žÂ¢s Teen People" in the place of "Saturday ’s Teen People" This is taken from my now broken database and since I noticed this too late I now cannot do anything if not manually change every single entry. How fun. - In the handbook, install.txt and all the other install guides for Drupal THERE IS NO MENTION of the collation. This means that it's written nowhere how to set the collation and so everyone just follows the standard instructions and finishes with a "latin1_swedish_ci" as it happened to me. Including the text in the aggregator items, node and comment bodies. - How the hell the DB must be configured now? Because from what I read here: http://drupal.org/node/15746#comment-36443 It's not even possible to set Drupal to use utf8 because it's still not compliant. So, beside having my database now unrecoverable, how should I set it to have it working properly from now on and be able to back up it without getting unrecoverable garbage text? Then I seriously suggest you to patch the guides and the drupal package to stop this or it would become a rather large problem considering that following step by step the instruction you unavoidably go toward this corruption problem. - HRose / Abalieno

3 3

[drupal-devel] AutoComplete suggestion
by Stefan Nagtegaal 07 Sep '05

07 Sep '05

Just want you guys to see this! We have a nice autocomplete field now, but this is extremely cool! http://script.aculo.us/demos/ajax/autocompleter_customized I love it! Stefan --- Stefan Nagtegaal Drupal Thinker & Themer

2 1

Re: advanced settings (was Re: [drupal-devel] advanced theme in core vs all in core.)
by Kobus Myburgh 07 Sep '05

07 Sep '05

> IMO that page should only be a summary of already defined variables. So, in > contrary to windows registry or (shivver) gnome-conf, this should (IMO) only > list the variables that are settable in other places too. I sort-of disagree with that. Wouldn't that defeat the purpose of what sparked this thread? Having the ability to add extra settings will not be possible if you only keep settings that can be set elsewhere. If you're going for this approach, you're doing useless duplication for the most part. The only people who will use it then are people who know the innards of Drupal very well, i.e. Developers or people who've been involved for a long time in Drupal otherwise. Newbies and less technical users won't... If I understand this whole thread correctly, this started with "adding another option would make the interface cluttered." From there, came the idea that new (less frequently used) options could be added to a separate page. Regards, Kobus

1 0

[drupal-devel] [bug] array-merge() error thrown (issue when rolling back node revisions)
by killes 06 Sep '05

06 Sep '05

Issue status update for http://drupal.org/node/16140 Post a follow up: http://drupal.org/project/comments/add/16140 Project: Drupal Version: cvs -Component: menu system +Component: comment.module Category: bug reports Priority: normal -Assigned to: Anonymous +Assigned to: killes(a)www.drop.org Reported by: lyk0s(a)drupal.org Updated by: killes(a)www.drop.org -Status: patch (code needs review) +Status: patch (ready to be committed) Attachment: http://drupal.org/files/issues/comment_16.patch (828 bytes) this is a bug somewhere else. A menu entry defines callback arguments that are not wrapped in an array. Either a contrib module or comment module. Patch attached. killes(a)www.drop.org Previous comments: ------------------------------------------------------------------------ Tue, 25 Jan 2005 03:25:26 +0000 : lyk0s(a)drupal.org warning: array_merge() [function.array-merge]: Argument #1 is not an array in /Web/cybertrib.com/..../includes/menu.inc on line 349. (I am using PHP 5 :) ------------------------------------------------------------------------ Thu, 30 Jun 2005 13:43:30 +0000 : townxelliot Attachment: http://drupal.org/files/issues/menu.inc_2.patch (596 bytes) As far as I can tell, this bug is still not fixed in the latest (as of today) CVS version. I've attached a patch for it (diff -Nur, as I couldn't work out what the preferred patch format for Drupal is). I found the error occurred when running under PHP 5 and attempting to rollback to a previous revision of a node. ------------------------------------------------------------------------ Sat, 02 Jul 2005 12:27:28 +0000 : Dries I think we can avoid having to do the array_merge() in this case. Would be nice if you could a slightly cleaner solution. It might be possible.

1 0