October 2006 - support - lists.drupal.org

welcome to your drupal powered
by Mohammed Al-shar' 25 Oct '06

25 Oct '06

hello is there a way not to publish any node at the front page? at www.nattiq.info, I don't want any node to be published, because i let the views module take care of this by generating a block. but if I don't promote any item to the front page I get "welcome to your drupal powered website, ....". is there a way to get red of this? I tried setting the front page to nothing instead of "node" in the setting page, but this generates "page not found" in the front page. the setting currently is that I create an empty node and promote it, but this generates "node/#" which is annoying. Regards, Mohammed al-shar'

3 5

Installed Views Bonus Pack - none of the views show up
by Jody Cleveland 25 Oct '06

25 Oct '06

Hello, I just installed the views bonus pack module: http://drupal.org/project/views_bonus I enabled the module, and went to views. None of the views from that pack show up. Is there something else I need to do? - jody

3 4

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] support Digest, Vol 46, Issue 26
by alex＠bleen.net 25 Oct '06

25 Oct '06

Sent via BlackBerry from T-Mobile -----Original Message----- From: support-request(a)drupal.org Date: Wed, 25 Oct 2006 12:00:02 To:support@drupal.org Subject: support Digest, Vol 46, Issue 26 Send support mailing list submissions to support(a)drupal.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.drupal.org/listinfo/support or, via email, send a message with subject or body 'help' to support-request(a)drupal.org You can reach the person managing the list at support-owner(a)drupal.org When replying, please edit your Subject line so it is more specific than "Re: Contents of support digest..." Today's Topics: 1. Re: local.module and filtering strings (Kobus Myburgh) ---------------------------------------------------------------------- Message: 1 Date: Wed, 25 Oct 2006 08:03:29 +0200 From: "Kobus Myburgh" <ITBJDM(a)puknet.puk.ac.za> Subject: Re: [support] local.module and filtering strings To: <support(a)drupal.org> Message-ID: <s53f1a61.037(a)pcm-nov-gwia-server.puk.ac.za> Content-Type: text/plain; charset=US-ASCII > This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus ------------------------------ -- [ Drupal support list | http://list.drupal.org/ ] End of support Digest, Vol 46, Issue 26 ***************************************

1 0

Re: [support] local.module and filtering strings
by Kobus Myburgh 25 Oct '06

25 Oct '06

> This is rather difficult to do. It might be possibly if you only use > imported strings as the comments that the strings have (see the POT I see your point. > I wonder if the solution we envision for the translations teams might be > a solution for you: We plan to have a Drupal site where you can > translate any Drupal strings inline, i.e. where they occur on the Drupal > page. This will however rely on JavaScript and I don't know how well > screenreaders support this nowadays. I am managing the translations as it is. Sorting the translation strings by module would be nice, but not a necessity for me - it would be like the permissions page - having it sorted differently (or having the header repeat from time to time) would be ideal for me, but not necessary. My point being that PoEdit probably doesn't work well with screen readers, and that is why Mohammed uses the locale.module. This functionality, although not necessary for me, it may be vital to Mohammed. Groete, Kobus

1 0

Re: [support] [development] How to control HTML user input preserving the "style"attributes?
by Michelle Cox 25 Oct '06

25 Oct '06

On 10/23/2006 9:16:20 AM, inkfree press (inkfree(a)gmail.com) wrote: > If it is a search issue, then perhaps the infrastructure folks could take > that under advisement and examine alternate search methods ('see also', > cross-listed, 'related to', etc.) That's a chore, of course, but may well > be worth it to prevent the task clutter which seems to afflict the > contributed modules listings. Some modules do list related modules. Getting it on all modules would take either all maintainers doing it or someone volunteering to go through them all. I had plans on going through quite a few of them in the process of building my current site, but I keep getting distracted. If you'd like to help, you can go through the modules and email me the ones you find that are related or have duplicated functionality and I can add "see alsos" where appropriate, providing that won't piss off the maintainers. Any maintainers want to weigh in on this? Would you object to having a note added to your descriptions to help people decide between modules? Michelle

3 3