Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositorySummary of actual problems with RepositorySummary of actual problems with Repository
Previous
 
Next
New Post
9/2/2007 6:44 AM
 

sfabian@gooddogs.com wrote

I am slightly confused, setting the Target to SELF will result in a simple redirect. Not only does it not use javascript in any way, it does not popup a window so popup blockers would have no effect. Setting Target to SELF will use the exact same methoid of displaying the page as every other navigation link in DotNetNuke.

I would suggest that you please double-check your test of using SELF. I cannot imagine any situation, where if the change is properly made, that that would not work

You are right, with SELF, the problem does not appear anymore. But we completely loose the functionnality of opening a new window ! This way, people need to press BACK several times to go back to my website. And with the javascript, you can not use "Open in new tab or new window" --> this is problematic.
To summarise, SELF gives another way of opening links, which does not give satisfaction.
BLANK opens a new window, but in a way which is not convenient for most of software like Norton or default settings of IE....

Greenflash, I have seen that you have exactly the same problem than me with SEARCH and permalink issue (you also have the problem with permalink: after your search and clicking on the result, try to change category by using the drop down box, you will see that nothing is changing. That's why I have removed on my website this drop-down box to 'temporarly" solve the problem).

 

DV

 
New Post
9/2/2007 9:50 AM
 

A new development build of the Repository module, 3.1.14.13179 (dated 9.2.2007), has been posted for download 

Download URL:
http://www.gooddogs.com/dotnetnuke/Downloads/tabid/57/Default.aspx

NOTE: Please read the DISCLAIMER before downloading and installing any Repository development build.

Release Notes:
=======================================================================
03.01.14 Build 13179
Released 09.02.2007
=======================================================================

-- Fixed bug where selecting an item via the PermaLink URL or via a
   Dashboard file entry, the Comment Count would be 0. The fix was a
   change to the grmGetSingleRepository stored procedure. If you are
   already running a previous dev build, then after installing this
   build, you'll have to run the 3.01.14.SqlProvider manually by
   copying the text (do not copy the final GO line ), and pasting it
   into the Host->SQL page, make sure to check the 'execute as script'
   checkbox.

-- Fixed bug where after selecting an item via the PermalLink URL, you
   could not change categories.

-- Fixed bug in Search collection routine. When you searched using the
   core search function and found an item in a Repository module, the
   URL link would not work. It contained grm2id instead of id. NOTE:
   After installing this build and Re-Indexing content using the
   Host->Search Admin page function, I was still getting grmid in the
   results URL. I had to manually deleted the rows from the SearchItems
   table for my Repository moduleid, then Re-Index content in order
   for the new search items to appear. Then on the Search results I
   would see id instead of grm2id.

 
New Post
9/2/2007 10:55 AM
 

Testing in progress.... As usual, I have full confidence in you, and I am installing it on my prod website !

So, people can have an idea of how good the modification are...

DV FX

 
New Post
9/2/2007 11:32 AM
 

Hello,

I have:

0/ Deleted all my search tables
1/ Installed this new dev build
2/ No error during install
3/ Few errors in my log after install - this is NORMAL (because I have many visitors per minute, and since I did not create at once the new procedure - I am upgrading from a previous build - I had some errors related to this procedure not found)
4/ I created the procedures. Steve, can you confirm that I done it correctly ???
There are TWO SQL to run, not just one. I have opened the file and copy-paste the query, without the two GO; two times. Correct ?? I have checked, and the procedure is there.
5/ I have re-indexed my website

Then, I tested everything possible:
A/ Permalink and comment count --> problem solved.
B/ Permalink and change category --> problem solved.
C/ Search --> problem solved.
D/ Download are ok. "Visit" (link template) are OK. I have also checked for "old problem" (to be sure that they do not re-appear !!) --> no problems known.

Congratulations Steve, this works perfectlly. Now, I have sent out an email to my admin and main user, so they can intensively test it. For 30 minutes of use, no error logged. I have updated the thread at the beginning to reflect current status. Thanks Steve. And now, let's focus on this javascript / wind.open problem ?....

 

DV FX

 
New Post
9/2/2007 11:19 PM
 

Kudos on fixing up those things Steve!

I'm also no developer, but I did have a good dig around looking for methods of opening windows to get past popup blockers and the basics are simply that window.open javascripts will get blocked no matter how they are created as that is the method that advertising popups use.

However, given that the user is voluntarily clicking on a link rather than triggering an automated popup, the way to do it will require rendering the link as html, presumably using asp:hyperlink. It really isn't a popup at all, but just a click on a link with target=blank or elsewhere.

I can of course also understand if it's not a simple task to implement that in the Repository code, because for all I know it might require fundamental changes to the way it handles the various types of content. Just letting you know I had a look as best I was able.

Rob

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsRepositoryRepositorySummary of actual problems with RepositorySummary of actual problems with Repository


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out