dotnetnuke

Catalook Credit Card Dropdown Expiry Year

Catalook Credit Card Dropdown Year We experienced a problem with the store checkout only listing a creadit card expiry date up to 2015  Thus the drop down selector in the Credit Card field for expiry date would not allow years fat enough into the future that the customer could select the correct expiry date. The solution we found was this: Navigating to the “Your Cart” module. You can do this by login in as an admin (not host) and buying a product. When it takes you to the cart module…Select Edit Skin from the module menu.Grab the code there, and paste into notepad etc. And look to the code that looks like this.  ListItem Value=”09″ Selected=”True”>2009ListItem… Read More »Catalook Credit Card Dropdown Expiry Year

DotNetNuke can’t upgrade as Host Login does not work

DotNetNuke Upgrade Fails. Cannot login with Host. If you are trying to upgrade your DotNetNuke site and found that you are presented with the Welcome to the DotNetNuke Upgrade Page, but can’t login with your Host (SuperUser) account. DotNetNuke Upgrade – Version 06.02.07 Current Version – 06.02.05 Welcome to the DotNetNuke Upgrade Page. The first step is to choose the language you wish to use for the Upgrade. You are about to upgrade your website to a more recent version of the DotNetNuke application. Applying upgrades on a consistent basis is the best way to ensure that you are protecting the integrity of your investment and the security of your users and assets. Before proceeding… Read More »DotNetNuke can’t upgrade as Host Login does not work

DotNetNuke HTML Editor Background Black

When you get a black background in the HTML Editor. The solution is easy. Look for the file found here: \Providers\HtmlEditorProviders\Telerik\Config\ConfigDefault.xml Edit it to add this line: <property name="CssFiles">~/Providers/HtmlEditorProviders/Telerik/Config/EditorCustom.css</property> Looking like this: Then edit this file: \Providers\HtmlEditorProviders\Telerik\Config\EditorCustom.css To look like this: body {   background-color: white;   background-image: url(image_path);   color: black; }   That’s about it.

DotNetNuke Forum Module 05.00.02 The missing link!

DotNetNuke 05.06.03 Pain If you look at the project downloads for dotnetnuke, you will notice that the forums module has the latest version as: 05.00.01 And if you click the link from within this page: http://www.dotnetnuke.com/Resources/Downloads/Projects-Downloads.aspx 05.00.01 is exactly what you get. All sounds neat and tidy… right? Not really, because if you install the latest version of DotNetNuke 05.06.03 (an important security release) you will kill your forums. Dead as dead. And if you check around for an update of the forum module, you will not find one either in your Module Definitions, or in the DotNetNuke website. But keep looking to codeplex and you find this: 05.00.02 and what is strange, it is… Read More »DotNetNuke Forum Module 05.00.02 The missing link!

Problem With DNN Blog Module 04.01.00 – 01

We found an issue with what is the current release version of DotNetNuke Blog module 04.01.00 or 04.01.01. First up, we don’t know what the version number should actually be, as the compiled version on the download is 04.01.00 but the source code is referenced as 04.01.01. We presume there is some difference, but who knows what it is. Anyway The Problem The problem is that any forms on a page that run the blog module, will not allow form data to be validated. By validated, we are talking about ensuring a number is entered in a number field and text in a name filed etc. The cause is the blog module is using an… Read More »Problem With DNN Blog Module 04.01.00 – 01

DotNetNuke Automated Backlink Module

  Today we released an update to the Automatic Backlink Module for DotNetNuke. Details of the update are available here: http://www.interactivewebs.com/automaticlinkbuilder/Support/VersionHistory.aspx But include improvements on the way site monitoring is handled and the way the module works with the known GZIP issues. An example of the module can be seen here: http://www.interactivewebs.com/Admin/DotNetNukeWebsites.aspx?&action=add where you can add your site for back linking.

Codeplex InteractiveWebs Profile Updated

Today we updated out profile at Codeplex http://www.codeplex.com/site/users/view/InteractiveWebs mostly so that we could slam a review up for the latest dotnetnuke 5.6.2 release. The review points out that the release is not one of the worst releases of dotnetnuke, but it is buggy and caused us some problems. We are quite disappointed that this is the last 5x release, and hold little hope about the initial releases of DotNetNuke 6x. Shame for all the hype and spin that dnn corporation have been putting on themselves that they are so happy to release such junk.

Adding the Module –Mushroom Image

Getting your site ready for Mushroom Image Once you have installed the Mushroom Image module, you will need to ensure your site is ready to host jQuery. DotNetNuke makes this easy, but there is one small change we recommend first. 1. Login as Host 2. Go to HOST SETTINGS and locate the jQuery settings: 3. Tick the option for “Use Hosted jQuery Version” 4. In the Hosted jQuery URL, type: http://ajax.googleapis.com/ajax/libs/jquery/1/jquery.min.js Background DotNetNuke currently runs with jQuery version installed. That is to say that DNN have included some jQuery files that will sit on your web server and ensure that jQuery works on your site. The only problem is that at the time of writing… Read More »Adding the Module –Mushroom Image

DotNetNuke User Experience Team Cracks Me Up

Today it was drawn to my attention that the DotNetNuke Corporation has a User Experience Team. Good on DNN Corp for caring about UI, and so they should. What cracks me up about it is this. Go to the webpage and seek more information on the UI team members. First from the list is Joe Brinkman. (Not picking on you Joe, but your smile is first on the list).   Notice the *******, Ohio ********* (Funny hay) Where is my User Experience I would like to know? How can a UI team allow the details page of their team profile pictures look like that… I’m still laughing about it as I write it now. Are… Read More »DotNetNuke User Experience Team Cracks Me Up

DotNetNuke AjaxControlToolkit, Version=3.0.30930.28736 Error

Could not load file or assembly ‘AjaxControlToolkit, Version=3.0.30930.28736, Culture=neutral, PublicKeyToken=28f01b0e84b6d53e’ or one of its dependencies. The located assembly’s manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) We were playing today with a trial module from another developer. Received the above error. After much mucking around, we found that the very specific version of the AjaxControlToolkit.dll file that came with the module, was not installed during the normal module setup. We extracted the file into the \bin\ directory on the site, and joy to the world. Strange that a specific version is required and that the 3.5 or 4.0 version does not work. This is how they referenced a specific version. Not… Read More »DotNetNuke AjaxControlToolkit, Version=3.0.30930.28736 Error

How do I know DotNetNuke Corp is off the rails?

There are load of features and functions about DotNetNuke that tick us off. Some big, some small and some that are baseless. It never ceases to astound me why they do some features and functions so poorly. Today I had to write about a pet hate… Why when we go to the module definition page, do we see a list of “Upgrades?” with the painfully ugly Microsoft style highlighted version number. Really. Whoever built that system.. was that look the best you could come up with. It is painful enough that the stupid system does not allow third party developers to reference an RSS feed for their own updates. (Would have thought that was a… Read More »How do I know DotNetNuke Corp is off the rails?

DNN Modules – Advanced Login updated

We have updated our popular advanced login module for DNN. The updates can be viewed from the DotNetNuke Advanced Login Module Website here.   With the Advanced Login Module, users of your website can login with an email address or otherProfile information instead of having to remember a user name. Additionally you can allow verification of identity with profile data other than a password. First Name for example. Restrict and allow access based in IP address, and then redirect based to a DotNetNuke page based on IP address of the user.