Great Ideas. Always Flowing.

We are not happy until you are happy. Client satisfaction guaranteed. Whatever your needs and requirements, we have the skills and resources for the job!

Quick login...


Or... now make it easy with Facebook Integration
Connect via Facebook



Top Sellers

Frustrated over the lack of customization for your user's registration fields? Dynamically setup your DNN Portal with custom registration fields, layout, questions, and other core integration options......

Ultra Video Gallery is a brother product of Ultra Media Gallery, UVG allows you to upload videos in various format and automatically encode them to flv or H264 format, you also can add videos from internet or record live videos from your webcam.

Build high performance, completely customizable data-entry forms and views driven by your DNN and external databases. New built-in tools make it a snap to quickly create data entry forms, data views, and even database tables. Plus, add your own HTML, CSS, Javascript, SQL commands, stored procedures,

The most advanced DotNetNuke shopping cart on the planet. Easy to use e-Commerce, Secure Shopping Cart Software and SEO friendly. B2C / B2B Ecommerce Sites.

One stop solution for events calendar and events registration! FREE DOWNLOAD is available now!

bug - changing from custom to standard dnn style sheet
Last Post 08-02-2010 07:40 AM by Curtis Eidson. 2 Replies.
AddThis - Bookmarking and Sharing Button Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Author Messages
Curtis EidsonUser is Offline
river guide
river guide
Posts:98
Avatar

--
07-30-2010 10:23 AM
    I've noticed that changing the setting from "use custom dynamic forms style sheet" to "use standard dotnetnuke style sheet" doesn't really work.  It looks like the html always points to the style sheet (even if you have a fresh module that was never changed to use a custom stylesheet, the html still points to a css file in your portal root, that doesn't exist).  The only way to truly switch back to a "standard DNN style sheet" is to delete the css file.  It's ok if the stylesheet is not deleted when this option is changed, but then the html/css code should be removed or commented out of the page (on render).

    Also, it would be great if the stylesheets & js files were created in a sub directory and not the portal root.  Even better might be to create a core "dynamic forms" directory with sub-directories that would include js, css, file exports, pdf's, etc.



    Dynamic Forms allows you to use both the standard DotNetNuke styles for your form or a custom Dynamic forms style sheet if you choose to. By selecting a custom style sheet you will be able to work from a default style sheet template and modify style classes within the forms module.
    Chad NashUser is Offline
    Posts:5260
    Avatar

    --
    08-01-2010 03:52 PM
    Hi Curtis - Well actually regardless of if you use the custom stylesheet the module should be creating one initially. This is because some parts of the module (outside of the fields) use stylesheet options and classes. This might include things for the ratings control to actually work or other things such as for the feature to 'pop up example text next to field' to work. So regardless, the module should be doing this... The difference between your selection is actually what class the fields call so 'NormalTextbox' VS 'DynamicForms_Textbox' etc..

    Thanks for your comments on where they are saved. I agree that it would be more beneficial to save the files in an alternate folder, unfortunately this would be a major issue for users upgrading that we would have to review. Somehow during the upgrade process also move their existing CSS/JS files for each and every module instance or the upgrade would cause problems for them. Something for us to review though down the road.

    Thanks!

    -Chad
    Curtis EidsonUser is Offline
    river guide
    river guide
    Posts:98
    Avatar

    --
    08-02-2010 07:40 AM
    Hi Chad-

    interesting...I've tested this on a few different installs/servers/dnn versions and I don't see that a css file is created until i switch that option to use DF CSS. 

    Ver:3.30.61.0 / 5.4.4

    steps to reproduce:

    1. create new page
    2. drop df module on a page
    3. run wizard and select a few standard questions / exit /save (tried it without wizard too)
    4. look at the module id at the top of DF (1193) / search the source for "dynamicforms_module_1193.css" (it does exist)
    5. look in file manager for /portals/0/Dynamic-Forms_Module_1193.css and the file does not exist (also ran a file sync and looked at the directory via windows c:\ directoy)
    6. switch DF/CSS option
    7. check file manager and file now exists

     

    I understand why it should be there and it still seems like something may not be working correctly?

    Curtis

    You are not authorized to post a reply.


     
     

    Join our mailing list...

    Get current news and events the easy way
     
     
       
    Subscribe Me

    Recent Blogs...

     
    Copyright 2005 - 2011 by Data Springs, Inc.
     
  • film izle
  • 720 izle
  • film
  • sinema izle
  • film makinesi
  • T�rk�e dublaj film
  • film izle
  • film izle
  • baglan film izle
  • sinema izle
  • 1080 film izle
  • film mercegi