Products

Solutions

Resources

Partners

Community

About

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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStore1.00.01 - Shipping fee format bug1.00.01 - Shipping fee format bug
Previous
 
Next
New Post
5/17/2006 9:13 AM
 

Hello !

What i have do :

- tried to change taxes rates with the value 19.60 > get an error "format must be #.##"

- Tried to modify shipping fee > no problem first time, but when refresh, value is set to "0".

- Modifyed the value on DB, set ShippingFee to "30,0000". When i refresh, i have "30", and not "30.00".

Now it's impossible to change the shipping fee, even if i set the DB value to "0" and setup it using the admin module.

I get this error :

---------------

Server Error in '/' Application.

Input string was not in a correct format.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.FormatException: Input string was not in a correct format.

Source Error:

The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.

Stack Trace:

[FormatException: Input string was not in a correct format.]
   System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal) +2753027
   System.Number.ParseDecimal(String value, NumberStyles options, NumberFormatInfo numfmt) +119
   System.Decimal.Parse(String s) +22
   DotNetNuke.Modules.Store.Providers.Shipping.DefaultShippingProvider.DefaultShippingAdmin.btnSaveShippingFee_Click(Object sender, EventArgs e) +97
   System.Web.UI.WebControls.LinkButton.OnClick(EventArgs e) +105
   System.Web.UI.WebControls.LinkButton.RaisePostBackEvent(String eventArgument) +107
   System.Web.UI.WebControls.LinkButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7
   System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11
   System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +174
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

[PageLoadException: Input string was not in a correct format.]
   DotNetNuke.Services.Exceptions.Exceptions.ProcessPageLoadException(Exception exc, String URL) +354
   DotNetNuke.Framework.PageBase.Page_Error(Object Source, EventArgs e) +375
   System.Web.UI.TemplateControl.OnError(EventArgs e) +105
   System.Web.UI.Page.HandleError(Exception e) +73
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +6944
   System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +154
   System.Web.UI.Page.ProcessRequest() +86
   System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) +18
   System.Web.UI.Page.ProcessRequest(HttpContext context) +49
   ASP.default_aspx.ProcessRequest(HttpContext context) +29
   System.Web.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +154
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

---------------------

 

 

Thank you for reading !

 

 
New Post
5/17/2006 10:33 AM
 

That seemed to be a Localization problem.

 

In fact i'm french, and the "," is used in money sized values instead of ".".

That's why we haven't problem using 01.00.01 with an English user.

You could add something like .Replace(",",".") .

 

 

Seb

 
New Post
5/18/2006 12:16 PM
 

This localization bug is not only in shipping fees, but also in the string that is passed to Paypal.

In this case the decimal "," in the currency field should be changed to a "."

The decimal "," (in "##,##") comes from the user's preference, and may be required by currencies validation scripts !

This is a showstopper because either you cannot input a value as ##.##, or you cannot validate a payment with ##,##

 

 


Benoît Sarton
www.bsi.fr
www.dotnetnuke.fr
 
New Post
5/19/2006 12:12 AM
 
Thanks for reporting this issue.  I will look into it ASAP.

Best Regards,

Robert J Collins | Co-Founder & President

Netlogic Corporation

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsStoreStore1.00.01 - Shipping fee format bug1.00.01 - Shipping fee format bug


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