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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...am I stupid or are they unhelpful? am I stupid or are they unhelpful?
Previous
 
Next
New Post
6/11/2009 10:58 AM
 

Well I dont know the demo but if I saw a demo that i would expect everything on there to be in my skin also, expect from modulecontent than but a homepage slider if not mentioned it wasnt part of the skin I would say yes. so If had bought ths skin I would say unhelpfull and bad rating on snow but thats another thing

As for the js that will not work you cannot paste the entire js file in the header. that wont work,

just link to the file direcvtoly on the google code store

<script src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" type="text/javascript"></script>

also what they suggest is bad practice you need to call scripts in the header of your page not somewhere on your page

this is just the jquery script. The jquery script alone wont make a slideshow you need extra code which I dont see anwhere mentioned in the mail


 

 

 

 

 
New Post
6/11/2009 2:44 PM
 

I agree with armand that a script of that size is best included via its own external file -- I hadn't realized how large (from what I can see in the screenshots) of a script block you were dealing with.  Also, since it appears that you may have an entire script library rather than just a function dedicated to one unique task, page header inclusion is more in order as, in the future, you may decide to add more modules that make use of the same library.
  
  
Regarding script placement in the page header (and anything else being "bad practice"):
This is were I respectfully disagree with armand's comments.  Certainly concern over script management is valid:  would you rather have all script referneces in one place (the page header) to see what's being included and in what order?  Or would you prefer to have module-instance-specific scripts housed with the target modules (in the HEADER / FOOTER) so that those tightly-coupled scripts "travel" with the modules if modules are moved from page-to-page (but you won't know that such scripts are there without peeking at every module's HEADER and FOOTER setting)?
  
The reality is that individual modules often have their own internal script references anyway -- such references never show up in the source of a skin or in a DNN page's header setting.  The "better script management" argument is further reduced thanks to the proliferation of free browser-based web page inspection tools (covering HTML / CSS / JavaScript and sometimes XML / XSLT).  With such tools -- Google Chrome has a very decent one built-in -- one can easily see a report of all script references in one place.
  
Of greater concern, then, is the order of invocation of scripts as well as any script references to specific page elements.  Page header placement is often critical for "shared" script libraries (like jQuery in this example) that will be accessed by multiple modules.  On this count, however, it should be noted that some scripts' preferred-placement is at the end of a page rather than in the header.  One common example: Google Analytics' instructions say to place the script at the end of a page for more accurate metrics (I know, I know -- when GA first launched it was actually the other way around...)

  
In other cases, end-of-page placement is not just suggested but is required to avoid potential errors.  To use another Google example, consider the Google AJAX search script library.  That solution provides the ability to attach itself to a user-specified input textbox and a user-specified target results container.  This quite nicely provides "in-page" search results instead of browsing to or opening a new "search results" page.  Depending on the placement of such target elements in your DNN skin and the speed your pages load, the external Google AJAX library linked in a page's header area may complete its loading and attempt to "attach" too soon -- before the input box and results container have been rendered in the page, resulting in an error and a non-functional search box.  To correct this, one must instead invoke the AJAX search library at the end of a page rather than in the header of a page.
  
End-of-code script placement can apply at the module level as well.  One example where script placement in a module's FOOTER makes sense:
  
   Where do I put my script?  Javascript and the DotNetNuke FOOTER field
   http://www.eguanasolutions.com/DNN_Blog/EntryID/25.aspx 
 
 
All of this is to say that there are valid cases for choosing to place scripts in a module's HEADER and/or FOOTER rather than the page header.  It is not sufficient to make a blanket statement that one must "call scripts in the header of your page" and that anything else is "bad practice" -- clearly there are cases where header placement "wont work".
 
-mamlin


esmamlin atxgeek.me
 
New Post
6/12/2009 8:24 PM
 

Even though I haven't found the answer yet, I am very impressed with this forum. It is very helpful and alive.

I've been told I'm on DNN 4.5 (i think) and I need to run the script  script src="http://NAMEOFSITE/resources/shared/scripts/jquery/jquery.min.js" type="text/javascript"></script> in the PAGE header settings and not the module header settings. Then I place the following code in the module header settings: 

<script type="text/javascript">

//<![CDATA[

  jQuery.noConflict();

  var slideCurPos = 0;

  var slideItemCount;

  var slideItemWidth = 760;

  var slideInterval;

  var jQueryslideLinks;

  var jQueryslideItems;

  jQuery(document).ready(function(){

   /*************************************************/

   /*** [SLIDE FUNCTIONS] ***************************/

 jQueryslideLinks = jQuery("#slideNav a");

 jQueryslideItems = jQuery("#slideItems div");

 jQueryslideLinks.attr({'href': ' void(0)'});

 slideItemCount = jQueryslideItems.size();

 slideTo();

 slideInterval = setInterval(slideToNext, 10000);

 jQuery("#slide-previous-link").click(function () { slideToPrevious(); });

 jQuery("#slide-next-link").click(function () { slideToNext(); });

    jQueryslideLinks.click(function () {

      clearInterval ( slideInterval );

      slideCurPos = jQueryslideLinks.index(this);

   slideTo();

   slideInterval = setInterval(slideToNext, 10000);

    });

 function slideToPrevious() {

   clearInterval ( slideInterval );

   slideCurPos--;

   if(slideCurPos < 0) { slideCurPos = slideItemCount-1; }

   slideTo();

   slideInterval = setInterval(slideToNext, 10000);

 }

 function slideToNext() {

   clearInterval ( slideInterval );

   slideCurPos++;

   if(slideCurPos >= slideItemCount) { slideCurPos = 0; }

   slideTo();

   slideInterval = setInterval(slideToNext, 10000);

 }

 function slideTo() {

   jQueryslideLinks.removeClass('slideNavSelected');

   jQueryslideLinks.eq(slideCurPos).addClass('slideNavSelected');

   var slideTo = (slideCurPos * slideItemWidth);

   jQuery("#slideItems").animate({ marginLeft: "-"+slideTo+"px" }, 1500 );

 }

 

   /*** [/SLIDE FUNCTIONS] **************************/

   /*************************************************/

  

  });

//]]>

  </script>

 

 

This didn't do anything initially but then I placed the HTML code in the HTML field within the module.

 

<div id="BL"><a id="slide-previous-link" href=" void(0);"><!----></a></div>
<div id="BR"><a id="slide-next-link" href=" void(0);"><!----></a></div>
<div id="slideContainer">
<div id="slideItems">
<div class="cbox"><img height="320" width="740" alt=" " src="/portals/145/s1.png" /></div>
<div class="cbox">
<ul style="margin: 0px; padding: 0px; float: left; width: 48%; text-align: left;">
    <li><strong>1 Great Color</strong><br />
    Current skin pack contains one great color</li>
    <li><strong>3 Width Options</strong><br />
    Small Wdith \ Medium Width \ Full Width</li>
    <li><strong>4 Background Options</strong><br />
    Black \ Color \ Gray \ White</li>
    <li><strong>W3C standard XHTML compliant skin</strong><br />
    Fully accessible designs and layouts.</li>
    <li><strong>Flexible pane layouts</strong><br />
    Total 15 panes to meet complex layout.</li>
</ul>
<ul style="margin: 0px; padding: 0px; float: right; width: 48%; text-align: left;">
    <li><strong>3 skin objects:theme \ layout \ cssmenu</strong><br />
    Free skinobject, which can be validated with w3c</li>
    <li><strong>10 Banner Container Options</strong><br />
    Self-adapting width,self-adapting height</li>
    <li><strong>8 Containers</strong><br />
    All the containers can be validated with the W3C</li>
    <li><strong>3 text sizes Supported</strong><br />
    10px \ 12px \ 14px,Default 12px, changing on the client</li>
    <li><strong>SiteMap Skin included</strong><br />
    Simple sitemap code and multi lanugage supported</li>
</ul>
</div>
<div class="cbox"><img height="250" width="620" alt=" " src="/portals/145/s3.png" /></div>
<div class="cbox"><img height="300" width="670" alt=" " src="/portals/145/s4.png" /></div>
<div class="cbox"><img height="320" width="740" alt=" " src="/portals/145/s1.png" /></div>
</div>
</div>

This has got me farther. Now I see text slide back and forth but no images. I don't even know where the images are pulling from in the code...

This is what I'm ultimately trying to achieve. http://www.dnnskin.net/apple-grey  the rotating image banner is all I want.

getting closer!

 

M

 

 
New Post
6/13/2009 5:52 PM
 

well i cant help you with that exact slider, there are plenty of these scripts around just google for jquery image slider or carousell

Ihave a very simple other slider based on the new slider on the dnn homepage you can find instructions here

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/-1/threadid/313038/scope/posts/Default.aspx

 

 

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...am I stupid or are they unhelpful? am I stupid or are they unhelpful?


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