Comments on: DotNetNuke Widgets Guide (Part 2 of 4)

By: Game4453

Game4453 — Sun, 17 Oct 2010 18:11:00 +0000

Hi, I like use Imagevenue but sometimes it fail,
now I have used http://www.isphotobomb.com and is very great.
Keep in touch.

Regards

By: Anonymous

Anonymous — Mon, 27 Sep 2010 12:26:00 +0000

I am trying and failing to get Disqus comments on my dnn site but despite the excellent instructions here…. I am not getting it. Any example code for disqus?

By: BioChemSoc

BioChemSoc — Mon, 26 Apr 2010 13:22:06 +0000

I would greatly appreciate that.

By: techbubble

techbubble — Sat, 24 Apr 2010 02:08:36 +0000

That's a possibility. I only did some cursory testing on IE6 and most likely broke it during some refactoring. I don't have IE6 readily available so I'll need to setup a VM to figure out the cause. I'll see what I an do…

By: BioChemSoc

BioChemSoc — Fri, 23 Apr 2010 17:17:16 +0000

I tried using the StyleSheetWidget, and it seemed to work fine on all the browsers I tried but IE6, where the widget appeared ok, and processed the first event, then wouldn't ever fire an onclick event. Is this a bug with the widget?

By: david

david — Sat, 06 Mar 2010 09:01:30 +0000

Implemented the Rotator Widget and it does the job just fine.
However, How do I wrap text around the images that are rotated?
This is easy with a static image but I have been unable to work it out when using the widget.

By: Paul Fijma

Paul Fijma — Thu, 18 Feb 2010 23:41:00 +0000

i noticed i had made my forum invisible for everybody (not too smart if you want people to look at it

(due to twitterlogin i am now: Paul Fijma aka Arpat )

By: Tim

Tim — Tue, 16 Feb 2010 10:40:55 +0000

I've been playing around with the default widgets and I am having some issues with the VisibilityWidget in dnn 5.2.2. I have a fresh install, and the only third party module im using is the Telerik Rad Controls. All of the other widgets are displaying fine in the the Extropy Beta skin. The only one thats not getting rendered is the VisibilityWidget.

The default in that skin doesnt render at all:

So i tried a couple other variations looking at the parameter names in the VisibilityWidget.js.

With this variation i get atleast an icon with the div element, but again the widget is not being rendered so no functionality is added to the element. I'm not sure where im going wrong. I do wonder if something is bugged in that widget. In the summary section of the this widget it references the StyleSheetWidget...so im wondering if something else is typo'd. Any ideas?

By: uberVU - social comments

uberVU - social comments — Sun, 31 Jan 2010 10:19:09 +0000

Social comments and analytics for this post…

This post was mentioned on Twitter by techbubble: Blogged: DotNetNuke Widgets Guide (Part 2 of 4) http://bit.ly/8nvTs9...

By: The Seven Sins of DotNetNuke Module Developers | TechBubble

The Seven Sins of DotNetNuke Module Developers | TechBubble — Sat, 30 Jan 2010 00:29:25 +0000

[...] cannot be overridden with CSS, users are forced to edit the markup, use Javascript or the StyleScrubber Widget to neutralize the impact of a module’s inline style attribute on other elements of a [...]

By: Arpat

Arpat — Thu, 28 Jan 2010 02:01:59 +0000

this site uses “a” spoiler http://pbphouse.com/forum/index.php?topic=2941….
and here they show a similar jQuery technique
http://www.learningjquery.com/2007/02/more-show…
the syntax i expect to use is for active forums from wwww.activemodules.com (or the regular forum from http://www.dotnetnuke.com
i expect users to use a [spioler={option}] param [/spioler] with a clickable link and hidden text. (spioler is spoiler ofcourse
i am now learning how to add code so i can experiment on my technowebiste http://www.it-pro.nl (forums)

my biggest problem is that every site tels me to add code, but not how and where. what do i need to do step by step to get a spoiler on a text/html module.

i'll find it out, just takes a few hours (or days in current case for me)

By: techbubble

techbubble — Wed, 27 Jan 2010 23:55:14 +0000

Interesting use case, and certainly one that would work. My guess is that the forum module is encoding the widget markup preventing it from being executed. Is there a reference URL where I can see this?

By: techbubble

techbubble — Wed, 27 Jan 2010 23:53:40 +0000

When the widget runs it takes a finite amount of time to execute, the duration of which depends on the number of matching elements. In most cases, this is imperceptible. However, if there is a significant visual impact due to its running, the user will notice elements shifting around. This is expected and in order to overcome it, the code would have to be manipulated server-side as you pointed out.

By: Arpat

Arpat — Wed, 27 Jan 2010 19:33:19 +0000

nice topic.
i am looking to use this VisibilityWidget to create a spoiler to use inside text/html in the forum. Somehow it seems to me that this has to be easy, but so far i was unsuccesful.
the spoiler would be something like:
[spoiler={optional}] {parameter} [/spoiler]

resulting in a "spoiler" = Optional comment, click (or hoover over) to open:
and here is hidden the spoiler tekst.

am i correct it can be done with the visibility widget?
or do i need to use another approach?

By: Andrew

Andrew — Tue, 26 Jan 2010 04:07:57 +0000

You're right–adding things back in is much harder than taking it out. I guess I was thinking more along the lines of there being a DNN 'compatibility mode' that, if switched off, wouldn't emit any of the default styling–more of a server-side version of what this does. Since this widget is client-side, is there any sort of delay while it runs (like the 'dreaded' FOUT problem w.r.t. web fonts)?

By: techbubble

techbubble — Fri, 15 Jan 2010 07:20:04 +0000

I'm trying to picture a usage scenario and am not very clear. The StyleScrubber widget exists to address scenarios where you want to use a certain module, but the markup it emits is not XHTML compliant. What scenario(s) would the compatibility widget be used under? Also, would it just use standard jQuery selectors or some other means to identify which elements would have attributes added? It's pretty trivial to remove attributes, but adding them requires more work and I'm trying to understand a practical usage scenario before I venture to create such a widget.

By: Andrew

Andrew — Thu, 14 Jan 2010 23:18:03 +0000

Maybe instead of the scrubber widget removing unwanted code, someone could create a compatibility widget for people who rely on that unwanted code. They can add it in if they need all of those width, font, color, etc tags added in. I'd rather start with clean code and let people choose to dirty it up rather than patching dirty code…

By: DotNetNuke Widgets Guide (Part 3 of 4) | TechBubble

DotNetNuke Widgets Guide (Part 3 of 4) | TechBubble — Mon, 04 Jan 2010 22:54:18 +0000

[...] DotNetNuke. If you haven’t already done so, read Part 1 (overview of DotNetNuke Widgets) and Part 2 (DotNetNuke Widgets reference) to better understand the concepts explored in this post. Let’s [...]

By: John

John — Fri, 01 Jan 2010 06:39:22 +0000

Superb Nik! Many of us have been curious about this topic. I'd love to see a nice way to remove user's poorly styled entries from HTML blocks (leaving only CSStostyle them) and I suspect the StyleScrubberWidget will work great for this!