Having read the notes that came with rt-3.6.0, I realized that there
were no changes to the schema and the acls from 3.4.5 so I decided
I could test out rt-3.6.0
I simply made a clean installation of 3.6.0 on a test box and pointed
it to my existing MySQL database being used by rt-3.4.5. I can login,
but immediately the error below pops up, and I simply cannot proceed:
error: Can’t call method “Content” on an undefined value at /opt/rt3/share/html/Elements/MyRT line 76.
context:
…
72:
73: unless (exists $session{‘my_rt_portlets’}) {
74: my ($d_portlets) = RT::System->new($session{‘CurrentUser’})->Attributes->Named(‘HomepageSettings’);
75: my $user = $session{‘CurrentUser’}->UserObj;
76: $session{‘my_rt_portlets’} = $user->Preferences(‘HomepageSettings’, $d_portlets->Content);
77: }
78:
79: my $portlets = $session{‘my_rt_portlets’};
80:
…
code stack: /opt/rt3/share/html/Elements/MyRT:76
/opt/rt3/share/html/index.html:79
/opt/rt3/share/html/autohandler:279
Is this a result of something stupid I have put in RT_SiteConfig.pm
or what could be the cause?
cheers
- wash
Odhiambo Washington . WANANCHI ONLINE LTD (Nairobi, KE) |
wash () WANANCHI ! com . 1ere Etage, Loita Hse, Loita St., |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
GSM: (+254) 733 744 121 . (+254) 020 313 985 - 9 |
“Oh My God! They killed init! You Bastards!”
–from a /. post
Having read the notes that came with rt-3.6.0, I realized that there
were no changes to the schema and the acls from 3.4.5 so I decided
I could test out rt-3.6.0
There are no changes in DB schema, new content only.
Code you quoted looks for this content. Look at etc/upgrade/3.5.1/content.
File ‘UPGRADING’ does not have information about this.
run
sbin/rt-setup-database --action insert --datadir etc/upgrade/3.5.1
I would like the e-mails with replys to tickets to show the list of Cc:,
right now they hide the Cc. The people who receive the e-mails should see
all the Cc’s. Can this be done somehow?
Is it possible to add the list of Cc to the template for correspondence,
for example by adding to template correspondence something like
$Ticket->ListOfCc’s (Does there exist a field in $Ticket which can give
list of CC’s?)
Tomasz Wlodek | tel 631-344-7448
Brookhaven Laboratory, Building 510M | fax 631-344-7616
Upton NY 11973-5000 |
It’s good to see you around here again. Just ran across some of our
old postings circa 2002 and was thinking kind thoughts in your
direction.
I think I know exactly what the issue you’re facing is. And maybe even
how to solve it.On 6/25/06, Odhiambo Washington wash@wananchi.com wrote:
Having read the notes that came with rt-3.6.0, I realized that there
were no changes to the schema and the acls from 3.4.5 so I decided
I could test out rt-3.6.0
I simply made a clean installation of 3.6.0 on a test box and pointed
it to my existing MySQL database being used by rt-3.4.5. I can login,
but immediately the error below pops up, and I simply cannot proceed:
error: Can’t call method “Content” on an undefined value at /opt/rt3/share/html/Elements/MyRT line 76.
context:
…
72:
73: unless (exists $session{‘my_rt_portlets’}) {
74: my ($d_portlets) = RT::System->new($session{‘CurrentUser’})->Attributes->Named(‘HomepageSettings’);
75: my $user = $session{‘CurrentUser’}->UserObj;
76: $session{‘my_rt_portlets’} = $user->Preferences(‘HomepageSettings’, $d_portlets->Content);
77: }
78:
79: my $portlets = $session{‘my_rt_portlets’};
80:
…
code stack: /opt/rt3/share/html/Elements/MyRT:76
/opt/rt3/share/html/index.html:79
/opt/rt3/share/html/autohandler:279
Is this a result of something stupid I have put in RT_SiteConfig.pm
or what could be the cause?
What’s happening is that RT is looking for the default homepage
settings Attribute in order to display it. You’re using a database
which hasn’t had the extra attributes added, so it barfs.
I think you could fix this by loading the new Attributes, which are
some system-user owned saved searches (aka “portlets”) and the default
home page settings. You’d need to cull those bits from the rest of the
default data loaded with a fresh 3.6.0 install, but I don’t think
they’d get in the way of your 3.4.x install.
I would like the e-mails with replys to tickets to show the list of Cc:,
right now they hide the Cc. The people who receive the e-mails should
see
all the Cc’s. Can this be done somehow?
Is it possible to add the list of Cc to the template for correspondence,
for example by adding to template correspondence something like
$Ticket->ListOfCc’s (Does there exist a field in $Ticket which can give
list of CC’s?)
Tomasz Wlodek | tel 631-344-7448
Brookhaven Laboratory, Building 510M | fax 631-344-7616
Upton NY 11973-5000 |
On 25/06/06 11:27 +0300, Alexandr Ciornii wrote:
| Hello, Odhiambo.
|
| You wrote:
|
| > Having read the notes that came with rt-3.6.0, I realized that there
| > were no changes to the schema and the acls from 3.4.5 so I decided
| > I could test out rt-3.6.0
| There are no changes in DB schema, new content only.
| Code you quoted looks for this content. Look at etc/upgrade/3.5.1/content.
| File ‘UPGRADING’ does not have information about this.
|
| run
| sbin/rt-setup-database --action insert --datadir etc/upgrade/3.5.1
Hello Alexandr,
That did solve my problem. I hope Jesse notices this thread and includes
that important bit in the UPGRADING document, which I read over and over
after I hit this snag. I was initially ashamed of posting to the list,
but well, I am happy it was Jesse’s mistake
cheers
- wash
Odhiambo Washington . WANANCHI ONLINE LTD (Nairobi, KE) |
wash () WANANCHI ! com . 1ere Etage, Loita Hse, Loita St., |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
GSM: (+254) 733 744 121 . (+254) 020 313 985 - 9 |
“Oh My God! They killed init! You Bastards!”
–from a /. post
On 25/06/06 15:08 -0700, Jim Meyer wrote:
| Odhiambo!
|
| It’s good to see you around here again. Just ran across some of our
| old postings circa 2002 and was thinking kind thoughts in your
| direction.
So I do deserve a beer?
| I think I know exactly what the issue you’re facing is. And maybe even
| how to solve it.
It seems you have been actively snooping on the list then. I have been
involved in other things that reduced my ability to pop around as get
appraised on what is going on.| On 6/25/06, Odhiambo Washington wash@wananchi.com wrote:
| >Having read the notes that came with rt-3.6.0, I realized that there
| >were no changes to the schema and the acls from 3.4.5 so I decided
| >I could test out rt-3.6.0
| >
| >I simply made a clean installation of 3.6.0 on a test box and pointed
| >it to my existing MySQL database being used by rt-3.4.5. I can login,
| >but immediately the error below pops up, and I simply cannot proceed:
| >
| >
| >error: Can’t call method “Content” on an undefined value at
| >/opt/rt3/share/html/Elements/MyRT line 76.
| >context:
| >…
| >72:
| >73: unless (exists $session{‘my_rt_portlets’}) {
| >74: my ($d_portlets) =
| >RT::System->new($session{‘CurrentUser’})->Attributes->Named(‘HomepageSettings’);
| >75: my $user = $session{‘CurrentUser’}->UserObj;
| >76: $session{‘my_rt_portlets’} =
| >$user->Preferences(‘HomepageSettings’, $d_portlets->Content);
| >77: }
| >78:
| >79: my $portlets = $session{‘my_rt_portlets’};
| >80:
| >…
| >code stack: /opt/rt3/share/html/Elements/MyRT:76
| >/opt/rt3/share/html/index.html:79
| >/opt/rt3/share/html/autohandler:279
| >
| >
| >Is this a result of something stupid I have put in RT_SiteConfig.pm
| >or what could be the cause?
|
| What’s happening is that RT is looking for the default homepage
| settings Attribute in order to display it. You’re using a database
| which hasn’t had the extra attributes added, so it barfs.
|
| I think you could fix this by loading the new Attributes, which are
| some system-user owned saved searches (aka “portlets”) and the default
| home page settings. You’d need to cull those bits from the rest of the
| default data loaded with a fresh 3.6.0 install, but I don’t think
| they’d get in the way of your 3.4.x install.
I got it working. I believe that if I did “make upgrade”, then perhaps I
couldn’t have had this problem, but I took a different path, as already
explained, and so it happened. I must have misled myself, too, by
believing there was nothing that changed in the database, so those
bits run after “make upgrade” were not necessary.
As Alexandr pointed out, I just needed to run the following:
cd rt-3.6.0/
perl sbin/rt-setup-database --action insert --datadir etc/upgrade/3.5.1
I am not sure if I need to blame the method I used, or the document
named “UPGRADING”
cheers
- wash
Odhiambo Washington . WANANCHI ONLINE LTD (Nairobi, KE) |
wash () WANANCHI ! com . 1ere Etage, Loita Hse, Loita St., |
GSM: (+254) 722 743 223 . # 10286, 00100 NAIROBI |
GSM: (+254) 733 744 121 . (+254) 020 313 985 - 9 |
“Oh My God! They killed init! You Bastards!”
–from a /. post
I got it working. I believe that if I did “make upgrade”, then perhaps I
couldn’t have had this problem, but I took a different path, as already
explained, and so it happened. I must have misled myself, too, by
believing there was nothing that changed in the database, so those
bits run after “make upgrade” were not necessary.
As Alexandr pointed out, I just needed to run the following:
cd rt-3.6.0/
perl sbin/rt-setup-database --action insert --datadir etc/upgrade/3.5.1
I attempted both a clean installation and an upgrade from 3.4.5. Both
left me with the same “content” error as this thread described. I simply
ran the above perl script and things are ok.
You mentioned about doing a “make upgrade” to not have this happen, and
I just wanted to let you know that it’s the same result…at least in my
instance.
I am pretty sure that it tells you to do this in the output of make upgrade.
Yes indeedy. Just checked and at the end of make upgrade I see:
Congratulations. RT has been upgraded. You should now check-over
/usr/local/rt3/etc/RT_Config.pm for any necessary site customization.
Additionally, you should update RT’s system database objects by running
ls etc/upgrade
For each item in that directory whose name is greater than
your previously installed RT version, run:
/usr/local/rt3/sbin/rt-setup-database --dba root
–prompt-for-dba-password --action schema --datadir etc/upgrade/
/usr/local/rt3/sbin/rt-setup-database --dba root
–prompt-for-dba-password --action acl --datadir etc/upgrade/
/usr/local/rt3/sbin/rt-setup-database --dba root
–prompt-for-dba-password --action insert --datadir etc/upgrade/
Max H. wrote:
Odhiambo Washington wrote:
I got it working. I believe that if I did “make upgrade”, then perhaps I
couldn’t have had this problem, but I took a different path, as already
explained, and so it happened. I must have misled myself, too, by
believing there was nothing that changed in the database, so those
bits run after “make upgrade” were not necessary.
As Alexandr pointed out, I just needed to run the following:
cd rt-3.6.0/
perl sbin/rt-setup-database --action insert --datadir etc/upgrade/3.5.1
I attempted both a clean installation and an upgrade from 3.4.5. Both
left me with the same “content” error as this thread described. I
simply ran the above perl script and things are ok.
You mentioned about doing a “make upgrade” to not have this happen,
and I just wanted to let you know that it’s the same result…at least
in my instance.
I am pretty sure that it tells you to do this in the output of make
upgrade.
You are correct. I skipped over this because:
I was a bit confused because I checked in the directory containing the
upgrade items. In rt-3.6.0/etc there is:
3.1.0/ 3.1.15/ 3.1.17/ 3.3.0/ 3.3.11/ 3.5.1/
I didn’t see a 3.4.x, so I assumed I didn’t have to run anything else
after a make upgrade. The reason I say this is because anytime I
upgraded from version 3.4.2 → 3.4.5, I didn’t have to run anything else
after a make upgrade.
Perhaps just assumption on my part and missing small details.
Regardless, it works fine. Thanks!
I am pretty sure that it tells you to do this in the output of
make upgrade.
You are correct. I skipped over this because:
I was a bit confused because I checked in the directory containing
the upgrade items. In rt-3.6.0/etc there is:
3.1.0/ 3.1.15/ 3.1.17/ 3.3.0/ 3.3.11/ 3.5.1/
Which part of “For each item in that directory whose name is greater
than
your previously installed RT version, run:” made you rule out 3.5.1
when you’re upgrading 3.4.5?
I didn’t see a 3.4.x, so I assumed I didn’t have to run anything
else after a make upgrade. The reason I say this is because anytime
I upgraded from version 3.4.2 → 3.4.5, I didn’t have to run
anything else after a make upgrade.
because there’s nothing to upgrade between those versions… as
there’s no 3.4.3 or 3.4.4 or 3.4.5 directory in the upgrade list.
Which part of “For each item in that directory whose name is greater than
your previously installed RT version, run:” made you rule out 3.5.1
when you’re upgrading 3.4.5?
Again…I said it was confusion on my part. Possibly it was confusion on
the initial posters part too.
That’s why I said “Perhaps just assumption on my part and missing small
details. Regardless, it works fine. Thanks!”
I said thanks for helping answer my questions. So thanks to you too.
