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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN error messages abuseDNN error messages abuse
Previous
 
Next
New Post
2/11/2012 7:55 AM
 

Hello all,
I have noticed that on some of our websites users started to abuse the error displaying feature...
You can simply copy the URL and instead of the real error message, you can write your own...

Just like this:
original error
original error

custom text
with custom text in URL
This is just annoying! More damage can be done when the messages are like this (and read below):
bad error
you got the idea right? :)

The biggest issue here for us right now is that those links got shared on Facebook/Twitter and other users started to flame the company websites and us as the devs of the website...

Is there any fix that we can apply to hide those errors, or maybe make them visible only to admin or something else?

Cheers for the answer!

Regards,
W.

 
New Post
2/11/2012 10:33 AM
 

no, there is no way to suppress the injected messages (the code does encode the content so html/javascript cannot be injected i.e. cross-site scripting)

The problem with suppressing the messages is that if a non-admin has an issue then they dont have the detail to report, relying on admins to check their event viewer. If you feel this is something you need add an enhancement request to support.dotnetnuke.com requesting a setting to disable querystring error message text.


Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US
 
New Post
2/11/2012 11:47 AM
 
Hey Cathal, thank you for your fast reply.
I thought so, but I wasn't 100% sure, if there is any other way around...

I made a quick and dirty workaround of this problem using simple jQuery script which hides the error message, so for developers it's still there but not visible for normal users.

<script type="text/javascript">
$(function () {
   var tmp = $(".NormalRed").text();
   if (tmp == "A critical error has occurred.") {
      $(".NormalRed").parent().hide();
      $(".NormalRed").parent().prev().hide();
  }
});
</script>

I added this JS code to Default.aspx file, you can also put it in the skin probably.
I could use .remove() insted of .hide() but then you won't see if there are any real errors besides in the even viewer.

What do you think? Any other ways around this?

Regards, W.
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...DNN error messages abuseDNN error messages abuse


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