I have created a simple UDT with only 2 columns:

1) BSCName
2) BSCURL

Now, I have 3000+ names and URL's that I needed to upload into this UDT. So I created a sql script to insert this data straight into the tables: UserDefinedRows and UserDefinedData. (ofcourse after proper checking with the field id's etc...)

I needed the BSCURL to be opened in new window and hence I appended the string "|options=W" to all the URL's before uploading them to [userdefineddata].[fieldvalue].

Everything went well and I can see all the data in UDT on dnn page. The only issue is when I click the url it opens in new browser but does not execute the link it just stays as dead page and this is what I see in the newly opened dead page address bar:

http://localhost/udttest/LinkClick.aspx?link=http%3a%2f%2fwww.myurl.com%2fsubfldr%2findex.shtml&tabid=73&mid=413

What I have observed is on dnn page when I open any data row in edit mode, the checkbox for "Open in New Window" is not checked by default. It should be because I added the string "|options=W" when I uploaded the URL's. so now I manually check it, and save the record and bingo the link now gets executed in the new window instead of staying dead.

Another behaviour is that when I open the data row in edit mode and dont do anything and just hit the "save" link/button, bingo the URL again starts getting executed instead of staying dead in the window.

So guru's help me understand what magic have I missed that the URL is not getting executed unless I explicitly open the data row in edit mode and hit "save"? What exactly is the "save" button/link doing to the URL field? - is it setting some kind of hidden flag somewhere in some table that the url is valid and can now be executed?

Please guide me somewhere, I read the manual but still no hint out there. How do I make all the url's work by default after I uploaded it. All the data has came exactly as I wanted including the URL, except that the "LinkClick.aspx" does not execute any link, unless I manually open the row and just hit save without even doing anything.

I need a solution that i can fix all the 3000+ rows at a time, I will go mad if I have to sit and open every single one of the data row in edit mode and click save link/button. I just can't imagine 7000+ clicks, that kind of faint's me.

Every help is very highly appreciated.

I thnk you much in advance.

---

www.dotnetnuke.umaisa.com dnnsupport@dotnetnuke.umaisa.com - free DNN support - www.dotnetnuke.umaisa.com/dnnsupport

Hey Sid,

Please share with the rest of the class, your findings and how you fixed your dead LinkClick.aspx url issue.

Thanks

---

Jason Graves www.steadyrain.com www.dotnetnuked.com

Hello, it's me again. UDT uses the core URL control to represent and handle URLs. If a link is entered to any URL control that is used in the portal and it's being saved, than the control registers the entered URL in a table called #your_prefix#_Urls. So if a link in DotNetNuke is executed via the LinkClick.aspx (http handler) it needs to be existent in the table #your_prefix#_Urls otherwise it results in a blank page error. I managed to transfer the missing URLs via a SQL statement like this: INSERT INTO dbo.#your_prefix#_Urls SELECT DISTINCT 0, --PortalID CAST(UDD.FieldValue AS nvarchar) as UDT FROM dbo.#your_prefix#_UserDefinedData UDD WHERE 1=1 AND UDD.UserDefinedFieldId = 12 -- my individual URL field AND CAST(UDD.FieldValue AS nvarchar) <> '' --sort out defected URLS AND CAST(UDD.FieldValue AS nvarchar) <> 'http://' --sort out defected URLS AND SUBSTRING(CAST(UDD.FieldValue AS nvarchar),0,8) = 'http://' --sort out URLS not starting with 'http://' After that all the links finally worked :-) But apparently I wanted to much. All links now should open in a new window and thus I added the string "|option=W" to the existing URL FieldValue using this statement: UPDATE dbo.#your_prefix#_UserDefinedData SET FieldValue = CAST(FieldValue AS nvarchar) + N'|options=W' WHERE 1=1 AND UserDefinedFieldId = 12 -- my individual URL field AND CAST(FieldValue AS nvarchar) <> '' AND CAST(FieldValue AS nvarchar) <> 'http://' AND SUBSTRING(CAST(FieldValue AS nvarchar),0,8) = 'http://' Unfortunately this all messed up again. My URL FieldValue was shredderd e.g. like this: http://examp|option=W Do you guys have an idea if what went wrong ? Is the problem due to the ntext data type ? But nevertheless, at least the initial link problem should be solved now ! regards DeBilly