[rt-users] Broken link in tickets I own table from RT at a glance page.

[Jesse Vincent]

Alex Krohn at Gossamer Threads fixed it up locally with the following  
snippet. I'm on-site with a client today, but if somebody could clean  
it up a little bit (I suspect it needs to load the RT::System saved  
searches attribute by something other than id and it needs a wrapper  
so that it can run as a standalone script.

-j

	From: 	  alex at gossamer-threads.com
	Subject: 	fixing webpath in database
	To: 	  jesse at bestpractical.com

Hi Jesse,

Quick question for you if you have a moment. I ran into the problem with
__WebPath__ not getting stored in the database for "Highest priority
tickets I own" search on a few new 3.6.1 installs. After reading:

http://www.gossamer-threads.com/lists/rt/devel/58955#58955

I put something together to fix up the value in Content in the
Attributes table on this installation:

	my $attr = RT::Attribute->new($RT::SystemUser);
	$attr->Load(18);
	my $hash = $attr->Content;
	$hash->{Format} =~ s,<a href="/,<a href="__WebPath__/,;
	$attr->SetContent($hash);

and it worked fine. However, for one user account, I still get links to
'/Ticket/Display', rather then '/rt3/Ticket/Display'. i.e.  
__WebPath__ is
missing. All other users on this install show up fine.

Is there somewhere else I would need to update for this?

Thanks!

Alex

--
Alex Krohn <alex at gossamer-threads.com>
Gossamer Threads Inc. http://www.gossamer-threads.com/
Tel: (604) 687-5804 Fax: (604) 687-5806



On Nov 17, 2006, at 2:18 AM, James Mitchell wrote:

> I have searched quite a bit, not found a fix but I did find a  
> workaround.
>
> http://lists.bestpractical.com/pipermail/rt-users/2006-October/ 
> 042231.html
>
> On Tue, 2006-10-03 at 18:21 +0200, Wolfgang.Fuertbauer at ebewe.com  
> wrote:
> > Great! it works!
> > one has to remove and add the Subject column in "Customize ..."
>
>
> So, as you see, if you edit the table, remove the subject column  
> and re-add it
> with the link, it should work (and did on mine but that doesn't  
> solve the
> problem for any other users...)
>
> If anybody finds a genuine fix, please re-post it here for the  
> benefit of anybody
> finding this thread via a search.
>
> Thanks,
>
> James
>
> +++++
>
> Unless expressly stated otherwise, the contents of and attachments  
> to this email represents only the views of the sender as expressed  
> to the intended recipient. It does not necessarily represent the  
> view of the company and is not intended to place any legal  
> obligation upon the company, nor does it commit the company to any  
> course of action or contractual undertaking. If you are not the  
> intended recipient of this message/information, please inform the  
> sender by return of mail and destroy the message and any  
> attachments. Use or disclosure of any of the contents of the  
> message by unauthorised persons may result in legal action being  
> taken.
>
> +++++
>
> _______________________________________________
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
>
> Community help: http://wiki.bestpractical.com
> Commercial support: sales at bestpractical.com
>
>
> Discover RT's hidden secrets with RT Essentials from O'Reilly Media.
> Buy a copy at http://rtbook.bestpractical.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20061117/556a524a/attachment.htm>