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.

Catalook Credit Card Dropdown
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”>2009
ListItem Value=”15″>2015
ListItem Value=”16″>2016
ListItem Value=”17″>2017
ListItem Value=”18″>2018
ListItem Value=“19″>2019
ListItem Value=“20″>2020
Make it look like this exactly for the update at this time.

This will give you a larger future expiry date.

Adding .OFT Fonts to IIS Mime for DNN DotNetNuke

Making .OTF Font work in DotNetNuke DNN Skin

To get a DotNetNuke DNN site to correctly display .OTF fonts, it is necessary to add a MIME type to IIS.

Making this change is easy.

  • In IIS, click on the Server Name.Double Click on MIME Types

IIS 7 MIME

  • Add a New MIME Type – .otf – Font/otf

OTF MIME Type in DNN

That’s it.

For good measure you could restart IIS from a command prompt with “IISRESET”

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.

image

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 with the automated upgrade process please ensure that:

  • you have made plans to first attempt this process in a staging environment
  • you have documented your current installation characteristics including doing research on the compatibility of any third party modules which you may be using
  • you have created the necessary backups of your environment so that you will be able to restore your website in the event of an unexpected upgrade failure.

Solution

Just simply close your browsers, or better yet, grab a browser that you have not accessed for some time. Then try hitting your URL and loggin in with the new browser session. While I did not bother to work out what the cache issue was, I did find it was cache related to an open browser session that was trying to authenticate to a previous session.

Easy when you know how~!

DotNetNuke HTML Editor Background Black

When you get a black background in the HTML Editor.

image

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:

image

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;
}

image

 

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

image

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:

image

05.00.02 and what is strange, it is released before the DNN 05.06.03 update, like significantly before it… like 1 month.

This Forum Update is NEEDED if you want the forum module to work on DNN 05.06.03

http://dnnforum.codeplex.com/releases/view/67840

Release Notes

The same module as 5.0.1, except compiled against DotNetNuke 5.6.3 (and therefore is a minimum requirement) and the same version of Telerik (2011 SP2) included with it.
NOTE: This was compiled against, and for, 5.6.3 and is included with that release (Not released yet, as of June 12th (try 5 July).

All so confusing!

It waisted a lot of our time trying to work out what is going on. All we know is that DNN 05.06.03 broke a bunch of stuff, including the Forum Module. There is a fix but it is hidden on codeplex and is incorrectly referenced.

Very Unprofessional DNN Corp!

What you need to know

If you update to DNN 05.06.03 – your forums will die.

To fix it, download the hidden forum update 05.00.02 here: http://dnnforum.codeplex.com/releases/view/67840

Problem With DNN Blog Module 04.01.00 – 01

imageWe 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 old ASP.Net 1.0 validation function. While it should be using ASP.NET 2.0 with the updated validation behaviours as found here:

http://msdn.microsoft.com/en-us/library/0ke7bxeh.aspx

With this mistake, if you use Page.Validate on ASP.NET 2.0, page validation groups are ignored and the controls are validated.

Why the BLOG module is even coded this way is quite questionable in any case. However without DNN being a true open source system, we have no ability to fix this were needed in the source.

Our solution

We fixed the problem and recompiled a version that people can download an use for free.

Blog_04.01.01_Install A

You can install this on top of any DNN blog module 04.01.00 and we would expect that future releases of the blog module will not be affected by this version we compiled. However they may well revert back to their junk code in the future releases.

DotNetNuke Automated Backlink Module

image

 

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.

image

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

Avatar

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.