RT::Attribute::Name workaround patch

Jim, Roy, Joby, Carole and other who have problems with
"RT::Attribute::Name Unimplemented", please, try attached patch, I
think it should help.

Apply it to lib/RT.pm instead of lib/RT.pm.in if you’re going to
apply it on installed RT code.
Patch is simple and you can even apply it with patch command.

Don’t forget to stop and start server.

Please, report back about results.

Best regards, Ruslan.

attribute_name.patch (1.2 KB)

Hi Ruslan;
I am afraid the patch does not fix the problem, I applied the patch to
lib/RT.pm , cleared cache stoped then started apache , query builder
loaded a search , then tried to remove one of the show columns and bang
the error stack appeared …
again the system or reference is RT-3.4.4 apache 2, mod_perl 2, dbix
1.33 , mysql 4.1.14
please note that this error does not show up with dbix 1.27 , so I’ll
ask again … ist a good idea to roll dbix back to 1.27 … I do not want
to fix a problem and create another.

Roy

Ruslan Zakirov wrote:

Hi Ruslan;
I am afraid the patch does not fix the problem, I applied the patch to
lib/RT.pm , cleared cache stoped then started apache , query builder
loaded a search , then tried to remove one of the show columns and bang
the error stack appeared …
that’s bad.

again the system or reference is RT-3.4.4 apache 2, mod_perl 2, dbix
1.33 , mysql 4.1.14
What version of the perl do you use?

please note that this error does not show up with dbix 1.27 , so I’ll
Too many changes between 1.27 and 1.33[1] to say something useful.
[1] Search the CPAN - metacpan.org

ask again … ist a good idea to roll dbix back to 1.27 … I do not want
to fix a problem and create another.
Could you try version by version update from 1.27 to 1.33 to
understand where exactly we have problem?

Roy

Ruslan Zakirov wrote:

Jim, Roy, Joby, Carole and other who have problems with
“RT::Attribute::Name Unimplemented”, please, try attached patch, I
think it should help.

Apply it to lib/RT.pm instead of lib/RT.pm.in if you’re going to
apply it on installed RT code.
Patch is simple and you can even apply it with patch command.

Don’t forget to stop and start server.

Please, report back about results.


Best regards, Ruslan.


=== lib/RT.pm.in

— lib/RT.pm.in (revision 1155)
+++ lib/RT.pm.in (local)
@@ -312,21 +334,30 @@
=cut

sub InitClasses {

  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
  • require RT::ACL;
  • require RT::Attachments;
  • require RT::Attributes;
  • require RT::CachedGroupMembers;
    require RT::CurrentUser;
  • require RT::Templates;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::Date;
  • require RT::EmailParser;
  • require RT::GroupMembers;
  • require RT::Groups;
  • require RT::Handle;
  • require RT::Links;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Principals;
    require RT::Queues;
    require RT::ScripActions;
    require RT::ScripConditions;
    require RT::Scrips;
  • require RT::Groups;
  • require RT::GroupMembers;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Templates;
  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
    }

}}}

Best regards, Ruslan.

Ruslan Zakirov wrote:

again the system or reference is RT-3.4.4 apache 2, mod_perl 2, dbix
1.33 , mysql 4.1.14

What version of the perl do you use?

v5.8.7 built for i686-linux

please note that this error does not show up with dbix 1.27 , so I’ll

Too many changes between 1.27 and 1.33[1] to say something useful.
[1] Search the CPAN - metacpan.org

Yep , gone through them and nothing to indicate or hint that may cause a
problem …

ask again … ist a good idea to roll dbix back to 1.27 … I do not want
to fix a problem and create another.

Could you try version by version update from 1.27 to 1.33 to
understand where exactly we have problem?

I had that in mind to do, I was hoping to avoid it …

Roy

I think we cracked it, this error only appear with version2 >= 1.32
of DBix (have not tried 1.35), the offending line is :
$field = $self->_Accessible($field, “column”) while
$self->_Accessible($field, “column”);
within sub __Value , comment the line out and everything works …
Ruslan and Co, are we on the right track or will removing this line
break other things
Roy

Ruslan Zakirov wrote:>On 11/3/05, Roy El-Hames rfh@pipex.net wrote:

Hi Ruslan;
I am afraid the patch does not fix the problem, I applied the patch to
lib/RT.pm , cleared cache stoped then started apache , query builder
loaded a search , then tried to remove one of the show columns and bang
the error stack appeared …

that’s bad.

again the system or reference is RT-3.4.4 apache 2, mod_perl 2, dbix
1.33 , mysql 4.1.14

What version of the perl do you use?

please note that this error does not show up with dbix 1.27 , so I’ll

Too many changes between 1.27 and 1.33[1] to say something useful.
[1] Search the CPAN - metacpan.org

ask again … ist a good idea to roll dbix back to 1.27 … I do not want
to fix a problem and create another.

Could you try version by version update from 1.27 to 1.33 to
understand where exactly we have problem?

Roy

Ruslan Zakirov wrote:

Jim, Roy, Joby, Carole and other who have problems with
“RT::Attribute::Name Unimplemented”, please, try attached patch, I
think it should help.

Apply it to lib/RT.pm instead of lib/RT.pm.in if you’re going to
apply it on installed RT code.
Patch is simple and you can even apply it with patch command.

Don’t forget to stop and start server.

Please, report back about results.


Best regards, Ruslan.


=== lib/RT.pm.in

— lib/RT.pm.in (revision 1155)
+++ lib/RT.pm.in (local)
@@ -312,21 +334,30 @@
=cut

sub InitClasses {

  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
  • require RT::ACL;
  • require RT::Attachments;
  • require RT::Attributes;
  • require RT::CachedGroupMembers;
    require RT::CurrentUser;
  • require RT::Templates;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::Date;
  • require RT::EmailParser;
  • require RT::GroupMembers;
  • require RT::Groups;
  • require RT::Handle;
  • require RT::Links;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Principals;
    require RT::Queues;
    require RT::ScripActions;
    require RT::ScripConditions;
    require RT::Scrips;
  • require RT::Groups;
  • require RT::GroupMembers;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Templates;
  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
    }

}}}


Best regards, Ruslan.

interesting. That code is there to allow column aliasing. What are the states that $field goes through in that loop?

We’re definitely getting somewhere. Nice debugging
Best,
JesseFrom: Roy El-Hames rfh@pipex.net
Date: Friday, Nov 4, 2005 12:34 pm
Subject: Re: [PATCH] RT::Attribute::Name workaround patch

I think we cracked it, this error only appear with version2 >= 1.32 of DBix (have not tried 1.35), the offending line is :
$field = $self->_Accessible($field, “column”) while $self->_Accessible($field, “column”);
within sub __Value , comment the line out and everything works …
Ruslan and Co, are we on the right track or will removing this line break other things
Roy
Ruslan Zakirov wrote:

Hi Ruslan;
I am afraid the patch does not fix the problem, I applied the patch to
lib/RT.pm , cleared cache stoped then started apache , query builder
loaded a search , then tried to remove one of the show columns and bang
the error stack appeared …

that’s bad.

again the system or reference is RT-3.4.4 apache 2, mod_perl 2, dbix
1.33 , mysql 4.1.14

What version of the perl do you use?

please note that this error does not show up with dbix 1.27 , so I’ll

Too many changes between 1.27 and 1.33[1] to say something useful.
[1] Search the CPAN - metacpan.org

ask again … ist a good idea to roll dbix back to 1.27 … I do not want
to fix a problem and create another.

Could you try version by version update from 1.27 to 1.33 to
understand where exactly we have problem?

Roy

Ruslan Zakirov wrote:

Jim, Roy, Joby, Carole and other who have problems with
“RT::Attribute::Name Unimplemented”, please, try attached patch, I
think it should help.

Apply it to lib/RT.pm instead of lib/RT.pm.in if you’re going to
apply it on installed RT code.
Patch is simple and you can even apply it with patch command.

Don’t forget to stop and start server.

Please, report back about results.


Best regards, Ruslan.


=== lib/RT.pm.in

— lib/RT.pm.in (revision 1155)
+++ lib/RT.pm.in (local)
@@ -312,21 +334,30 @@
=cut

sub InitClasses {

  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
  • require RT::ACL;
  • require RT::Attachments;
  • require RT::Attributes;
  • require RT::CachedGroupMembers;
    require RT::CurrentUser;
  • require RT::Templates;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::Date;
  • require RT::EmailParser;
  • require RT::GroupMembers;
  • require RT::Groups;
  • require RT::Handle;
  • require RT::Links;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Principals;
    require RT::Queues;
    require RT::ScripActions;
    require RT::ScripConditions;
    require RT::Scrips;
  • require RT::Groups;
  • require RT::GroupMembers;
  • require RT::CustomFields;
  • require RT::CustomFieldValues;
  • require RT::ObjectCustomFields;
  • require RT::ObjectCustomFieldValues;
  • require RT::Templates;
  • require RT::Tickets;
  • require RT::Transactions;
  • require RT::Users;
    }

}}}

 >>

Best regards, Ruslan.