You searched for the word(s): userid:446728

More Search Options

RSS Available

• Re: Database issues slow performance

  The log file of a database is used whenever a transaction to Insert, Update, or Delete a record is made. It is likely that the log has grown to its size through the dnn logger (and other dnn tables) (which logs just about every interaction). When your dnn log reaches the max time period (e.g. 20 days), the log will cleared for records before this period. Thus actual data is cleared, but the entries in the DB Log File still remain. Other DNN Tables that apply this wonderful expansion are: UsersOnline;

  Posted to DotNetNuke (Forum) by walkerstewart on 6/5/2006

• Re: Using EditUrl() on a page

  Hi Tom, You could be having a few issues. 1. Do you have an "Edit" type page with the control key as "Edit" 2. In some cases in ASP.Net the <%# EditURL() %> should be an = (e.g. <%= EditUrl() %> 3. If your edit control is not control key "Edit" you will need to pass the control key that you are using. Hope this Helps,

  Posted to Getting Started (Forum) by walkerstewart on 4/28/2006

• Re: DotNetNuke 3.2 Vers 1.1 Framework Question on Creating users

  The classes you are looking for are the UserController and the UserInfo classes. The location of these files are "admin\Users\" The hash keys are needed by default. However you will likely need to have a webservice to interact with the database correctly, due to the Membership implementation is part of the ASP .Net framework and not the WinForms library. Trust me on this, we had a guy who did something very similar and it caused all sorts of headaches. Hope this Helps,

  Posted to Getting Started (Forum) by walkerstewart on 4/27/2006

• Re: Prevent container from expanding

  If you are using the Standard DNN Installation, this isn't possible (unless you are using a few core modules, e.g. text/HTML you can use a table and force it to be a set width). If you are using custom Skins and containers, you should be easily be able to acheive this by setting the width of the html layout. Hope this Helps,

  Posted to Custom Modules (Forum) by walkerstewart on 4/27/2006

• Re: Paypal integration dotnetnuke module

  What you need is to have a page for the Notify_url to go to. Your code above will be looking for the page in your root dnn install (same as the default.aspx). All the Notify URL does is provides a method for PayPal to hook back into your website. Once this page is called from PP, you will need to so some thing in the code behind to acheive the actions you are after. Hope this Helps,

  Posted to DotNetNuke (Forum) by walkerstewart on 4/27/2006

• Re: Error: Core Localization File Not Found: : ~/App_GlobalResources/GlobalResources.en-US.resx

  Go to your download of the DNN Core; Find the missing file; Copy it to the above location; Problem should be corrected. Hope this Helps,

  Posted to DotNetNuke (Forum) by walkerstewart on 4/27/2006

• Re: NavigateUrl issues

  Yep, the trick to doing this is that you need to pass the Module ID as a parameter. see eg below navigateURL(Me.TabID, "YourControlName", New String() {"mid=" & me.ModuleID, "itemid=" & itemid}) You will need to replace the items below: YourControlName: this is the name you have given to your second "View" control itemid: this should be the item key and value pair you want to display on the second screen. Hope this Helps,

  Posted to Custom Modules (Forum) by walkerstewart on 4/26/2006

• Re: Dynamic Forms

  Check out www.snowcovered.com . There are a number of modules available for purchase which would perform the task that you are looking for. Hope this Helps,

  Posted to Custom Modules (Forum) by walkerstewart on 4/26/2006

• Re: Document Module Errors

  Looks like you may have deleted a file, and the links in the documents module were not updated. You may need to get the module ID and find out by trial and error which file is the problem one and try to fix via the DB. Hope this Helps

  Posted to Core Framework (Forum) by walkerstewart on 4/26/2006

• Re: DNN 4.0.2 cannot edit new modules in portal

  Looks like your've got a collation conflict in your DB. This means that your got a problem when comparing data types (e.g. string -> string, date -> date) This typically occurs when you locally build a site, back it up and restore it on a server with a different collation sequence. Default SQL Install uses: SQL_Latin_..... Non Historic Compat SQL: Latin_.... Little difficult to resolve, but there should be some one out there who can step you through this Hope this Helps,

  Posted to Core Framework (Forum) by walkerstewart on 4/26/2006