Custom field textarea too small

Folks:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more accessible?

Thanks,

Matt
Matt Adams
Development & Network Services, Cypress Interactive
http://cypressinteractive.com, http://edsuite.com

-----Original Message-----
From: rt-users-bounces@lists.bestpractical.com [mailto:rt-users-
bounces@lists.bestpractical.com] On Behalf Of Matt Adams
Sent: Tuesday, 12 January 2010 16:44
To: rt-users@lists.bestpractical.com
Subject: [rt-users] Custom field textarea too small

Folks:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more
accessible?

Use Chrome, it can resize text areas…

Sadly, I’ve never been successful in ‘easily’ changing the textarea sizes.

I tend to use an external text editor then paste the results into the tiny-box.

Stuart

Folks:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more accessible?

You can modify share/html/Elements/EditCustomField (copy it in
local/html/Elements/ before) and change Cols (5) and Rows (15), but that
will be for all customfield of type textarea.

Stuart Browne wrote:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more
accessible?

Use Chrome, it can resize text areas..

On a related note, FireFox has a similar extension that does allow you
to change the textarea on the fly:
http://netticat.ath.cx/extensions.html

That doesn’t probably help you much if you’re stuck with IE

Regards,

Joop

Folks:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more accessible?

You can modify share/html/Elements/EditCustomField (copy it in
local/html/Elements/ before) and change Cols (5) and Rows (15), but that
will be for all customfield of type textarea.

There is also a callback in EditCustomField called EditComponentName
which you could use to say “actually, use EditCustomFieldBiggerTextbox
if the CF’s name is Foo” and then you just need a callback and a
custom component

-kevin, who occasionally uses the Safari feature to resize textboxes

Matt,

I’m not sure if the same line numbers apply for 3.8.x, but this is what
we dod for 3.6.4:

To modify the way certain Custom Fields are set up for entering data,

the following code should be added after line #76 and before the

last “return”

command in the directory /apps/rt/rt-[x.x.x]/local/html/Elements:

* *"EditCustomField"* -- Additional code after line #76*:*

# Beginning of Override Code ===============
if ($Type eq “Text”) {
$Rows = 8;
$Cols = 50;
} elsif ($Type eq “Wikitext”) {
$Rows = 8;
$Cols = 50;
} elsif ($Type eq “Select” and $MaxValues == 1) {
$Rows = 1;
$Cols = 30;
}

# End of Override Code

This code allows the entry “box” to be much larger and easier to use.
I’m not sure if this is what you were referring to, but I hope it helps.

Kenn
LBNLOn 1/11/2010 11:25 PM, Emmanuel Lacour wrote:

On Mon, Jan 11, 2010 at 10:44:15PM -0700, Matt Adams wrote:

Folks:

I’ve created a custom field for a static description we’ll use on some
of our project-related tickets. Unfortunately the textarea is so small
as to be almost useless.

Is there anything that can be easily done make this field more accessible?

You can modify share/html/Elements/EditCustomField (copy it in
local/html/Elements/ before) and change Cols (5) and Rows (15), but that
will be for all customfield of type textarea.


http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: sales@bestpractical.com

Discover RT’s hidden secrets with RT Essentials from O’Reilly Media.
Buy a copy at http://rtbook.bestpractical.com

Thanks to all who’ve replied thus far … I ended up editing the
templates and changing the cols and rols.

Matt Adams
Development & Network Services, Cypress Interactive
http://cypressinteractive.com, http://edsuite.com

Thanks to all who’ve replied thus far … I ended up editing the
templates and changing the cols and rols.

But Kevin is right, you should use the callback as this will make
upgrade easiers thant modifying original files.

On a related note.

Is there a way to make the correspondence editor have more rows? I dug at
this once and it looked like the rows configuration option only affects the
non-javascript version.

Thanks,
BrianOn Jan 12, 2010 4:49 PM, “Emmanuel Lacour” elacour@easter-eggs.com wrote:

On Tue, Jan 12, 2010 at 11:43:31AM -0700, Matt Adams wrote: > Thanks to all
who’ve replied thus far …
But Kevin is right, you should use the callback as this will make
upgrade easiers thant modifying original files.

http://lists.bestpractical.com/cgi-bin/mailman/list

On a related note.

Is there a way to make the correspondence editor have more rows? I dug at this once and it
looked like the rows configuration option only affects the non-javascript version.

Take a look through RT_Config.pm
The config option for rows on the non-JS version references the JS config
option

-kevin