- Development - lists.drupal.org

profile module maintainer?
by Karoly Negyesi 10 Jan '06

10 Jan '06

Hi! Someone would care for profile enough to don the profile maintainer mantle? This http://drupal.org/node/43989 issue tells me that currently profile module is quite a bit neglected. Regards NK

2 1

Re: [development] profile module maintainer?
by Kobus Myburgh 10 Jan '06

10 Jan '06

Hi, I can't use CVS, nor am I all that good at programming, but I am very fond of profile module and starting to learn PHP and Drupal (4.7) more on a daily basis due to my ongoing study of automember.module of which I will be maintainer soon. I am therefore willing to take up this task, but it might go slow in the beginning, because I am still learning, and someone will have to do the uploads for me. If this is okay with everyone, I'll take up this task. Regards, Kobus >>> karoly(a)negyesi.net 1/10/2006 7:42 AM >>> Hi! Someone would care for profile enough to don the profile maintainer mantle? This http://drupal.org/node/43989 issue tells me that currently profile module is quite a bit neglected. Regards NK

4 4

Re: [drupal:dries] /modules user.module
by karoly＠negyesi.net 10 Jan '06

10 Jan '06

8 15

Re: [development] profile module maintainer?
by Kobus Myburgh 10 Jan '06

10 Jan '06

I will be waiting to hear from Dries then. Until then, I can point out another type *grin*. My name is Kobus, not Korbus. *chuckle*. Kieran, don't worry about it though - most English-speaking people make that exact same typo. I am not sure why. Maybe it is because they can't pronounce it. Let me make an attempt to write it out as it is pronounced: - Ko (as in the qui in quit, but not as short as that - the vowel sound is longer) - bus (as the bis sound in business) I hope that clarify some things for you :-) Regards, Kobus >>> karoly(a)negyesi.net 1/10/2006 9:37:38 AM >>> On Tue, 10 Jan 2006 08:15:27 +0100, Kieran Lal <kieran(a)civicspacelabs.org> wrote: > > On Jan 9, 2006, at 10:53 PM, Kieran Lal wrote: > Typo: > >> I think it's worth taking a step back an(d) applauding Korbus. Yes. Sorry for nitpicking but this typo confused me greatly. I am astonished. Within an hour I put out the call, someone with a long, long Drupal history has stepped forward. Thanks. Your PHP knowledge is surely an understatement -- and even if you are not on Rasmus level, well, none of us is :) That's all I can say, it's Dries call from this point :) Regards NK

2 1

RE: [development] Re: the admin theme, profiles
by Steven Peck 10 Jan '06

10 Jan '06

While learning to theme Drupal, having to theme the admin area is a serious pain. It really is. However, I would not trade that built in integrated look for any other CMS or option. You log in, you see more options. Not logged in? You don't know those options are there for the most part. Yes, I had to spend some extra time on my site, but it looks consistent all the way through. None of that jarring color change/shift. At the current rate of debate, I might be able to contirbute actual solutions towards the admin area in 4.8. -sp ________________________________ From: development-bounces(a)drupal.org on behalf of Bèr Kessels Sent: Tue 1/10/2006 12:50 AM To: development(a)drupal.org Subject: Re: [development] Re: the admin theme, profiles Op dinsdag 10 januari 2006 05:12, schreef Theodore Serbinski: > On 1/9/06, Bèr Kessels <ber(a)webschuur.com> wrote: > > Not silly. just look at wordpress! There are hundreds of potential sites > > where editing, adding, moderating content is considered *administration*. > > And believe it or not, the node forms are often even harder to theme > > right, then the admin/ pages, esp on fancy layouts. > > Actually, this is one of Drupal's biggest strengths. I have a client > that had Wordpress but to manage content you had to go into admin, > find the article, then edit it. But it is *far* easier to traverse > your site logged in, goto the page you want and edit it. 10 to 1, it > is far easier for your client to find the page they want to edit on > the website visually then it is to search for it. > > Now, however, should it be themed differently? Entirely different, but > I do agree, admin/ is really the admin area. When you edit a node, I > think it can be more visually appealing and have some sort of 'admin > border' or whatever you may have it, to make things stand out a bit > more. As to what, well as we all say, code is gold, so I'll have > something soon. Well, even if you are completely right, and I am utterly wrong. The point I tried to stress is that we should *give people the power to choose for themselves*. If drupal ships with a hardcoded admin theme and area, the first thing we will here a dozn times is "how can I make page foo/bar look like the onse in admin?"

1 0

Re: [development] websiteoptimization.com css size
by Edgard Durand 10 Jan '06

10 Jan '06

Hello all, This is my first post here. I have been following this thread with interest. Here's my opinion about drupal.css 1. drupal.css shouldn't be split in multiple files. Reason: Performance, more requests to the web server, adding overhead. Even if the files are cached browsers can be configured to check for changes every time the page is visited. Logs become bigger too. 2. If possible add a checkbox to admin->themes to disable drupal.css. Reason: For advanced users (themers), they will find easier to add complete stylesheets to their themes instead of overriding drupal.css, I have found very difficult to override certain default styles, besides overriding only increases the size (duplicating code) instead of only one stylesheet there are two. Best regards. Edgard Durand http://capmex.biz 2006-01-06

10 18

RE: [development] E-Commerce - Call for Developers, testers etc
by Walt Daniels 10 Jan '06

10 Jan '06

On Heydon's test site I was having trouble changing my password (core bug I suspect). I just tried again and got a different message: warning: array_filter() [function.array-filter]: The first argument should be an array in /home/.emerson/ecommerce/ecommerce.heydon.com.au/modules/user.module on line 1247. But it claims to have succeeded and in fact did set my password. So far I don't see anything to test having to do with ecommerce on the site. There is an empty product list and I am not an admin so I can't do much. It is good to see so many people having signed up to do work.

2 1

proposal for issues: post 4.7 marker
by Bèr Kessels 10 Jan '06

10 Jan '06

Hi, This is an infrastructure mail, but since it mostly affects developers I chose to mail it here. I tried to make an estimation on how many bugs and features with and without patches are still there, holding up the 4.7 release. It seems rather impossible, so I decided to conclude with "a lot". A solution, could be to add a version "post 4.7". So that we can mark issues that are interesting, but not for now, as post 4.7. I know we have "postponed" but that is hardly used. And more: postponed does not indicate untill when it is postponed. It also cannot co-exist with "patch (code needs work)" and so statuses. Is it possible and usefull to add a tag "post 4.7" where we can reassign issues to? Bèr

5 5

Minor changes on form api docs
by Robert Garrigós Castro 09 Jan '06

09 Jan '06

I have made some minor changes on the http://drupaldocs.org/api/head/file/contributions/docs/developer/topics/for… page because of missing property #submit (former #execute) and a deprecated note on #extra property (now #attributes). I discussed this with chx and applied the changes. That was 4 hours ago. I don't know whether some one has to have it a look in order to these changes be available to the web or not. If that's the case, this is a reminder. Sorry if it's just a matter of time. Robert Garrigos

2 1

announcment: microcontent, an attempt to make drupal basics simpler.
by Bèr Kessels 09 Jan '06

09 Jan '06

Various times, I heard Dries talking about tasks he wants to see done easier. Things he considers "basic stuff to do in Drupal". I stolea list from a mail to the documentation list, but some points, IMO should be made *simple* in Drupal. We can document how one does it, but the better way is to make code to do this. * 2. Setting up an about page.* * 3. Setting up a contact page.* * 6. Setting a mission statement and slogan.* * 9. Figuring out the difference between 'story' and 'page' (and grokking the node system).* My shot at this, for sympal/drupalCOM is a module called microcontent. I want to take this opportunity to get some input from the community on the workings of this module. * Every microcontent entry is a node. * Every microcontent entry is available as a block (so this is also a blocks-as-nodes module) * You can choose "special" microcontent types. For now: * site summary (site title, site body) * mission (mission title, short mission, long mission) * site details (footer) So the basic site setup is done trough our *content* areas. Blocks are made/moderared trough our famous *content* user interfaces. We could choose (we did so for sympal/drupalCOM) to prefill the database with dummy missions (edit mission <= link) and other dummy microcontent (about page etc), but that would mean that the contrib module ships with an install script. No longer deeply hidden admin pages to change the mission, but living withing the other content. About pages, and a contact page will be part of my microcontent v2. in that v2 I want to integrate 3rd party modules, such as that contact.module, or other modules that affect small pieces of user-end content on the site. Please give some feedback, or ideas, because i want to release this module before 4.7 ;) http://drupal.org/node/43839 --------- This, btw is Driess complete "what should be documented for noobs" list 1. Installing the Drupal database scheme and creating the first user account. 2. Setting up an about page. 3. Setting up a contact page. 4. Creating a navigation menu/structure. 5. Adding one or more roles and configuring their permissions (eg. allowing some users to create content, allowing some users to access content). 6. Setting a mission statement and slogan. 7. Installing a new or different theme. 8. Setting a block in the side bar. 9. Figuring out the difference between 'story' and 'page' (and grokking the node system). 10. Configuring cron.

5 7