Sign in Register
Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • David Zweben 231 posts 688 karma points
    Sep 13, 2013 @ 03:43
    David Zweben
    0

    Server error: Value cannot be null. Parameter name: name

    I just tried installing Search and Destroy on an otherwise empty Umbraco 6.1.5 installation. I made a very simple 'Location Page' document type with the following properties, all textstrings: Address Line 1, Address Line 2, City, State, Postal Code, Country, Phone Number. I then made 3 nodes with this document type and filled in all of the fields except phone number and address line two. Next, I went over to the dashboard control, installed the Google Maps data type, selected my "Location Page" document type, and added the Google Maps property to it. Then I selected my Location Page document type again in the geo code section, selected all of my properties except 'phone number', and selected the Google Maps field to store the coordinates in (not sure if that was the correct thing to do). Finally, I clicked the GeoCode button and was presented with a 'success' message.

    I then went to my Location Page documents in the Content section, and got the error shown below. I'm not sure what value/parameter it's talking about. The only thing I can think of that I left blank were the Address Line 2 fields on my location pages, but I would hope that wouldn't be enough to break everything. Any ideas what might be causing this?

    Server Error in '/' Application.

    Value cannot be null.
    Parameter name: name

    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.ArgumentNullException: Value cannot be null.
    Parameter name: name

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


    Stack Trace: 

    [ArgumentNullException: Value cannot be null.
Parameter name: name]
   System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams) +14043133
   umbraco.cms.businesslogic.datatype.BaseDataType.LoadSettings(List`1 settings) +328
   umbraco.cms.businesslogic.datatype.AbstractDataEditorControl.OnInit(EventArgs e) +208
   System.Web.UI.Control.InitRecursive(Control namingContainer) +186
   System.Web.UI.Control.InitRecursive(Control namingContainer) +421
   System.Web.UI.Control.InitRecursive(Control namingContainer) +421
   System.Web.UI.Control.InitRecursive(Control namingContainer) +421
   System.Web.UI.Control.InitRecursive(Control namingContainer) +421
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +189
   umbraco.controls.ContentControl.AddControlNew(Property p, TabPage tp, String cap) +3853
   umbraco.controls.ContentControl.CreateChildControls() +1259
   System.Web.UI.Control.EnsureChildControls() +189
   umbraco.controls.ContentControl.OnInit(EventArgs e) +51
   System.Web.UI.Control.InitRecursive(Control namingContainer) +186
   System.Web.UI.Control.AddedControl(Control control, Int32 index) +189
   umbraco.cms.presentation.editContent.OnInit(EventArgs e) +1231
   System.Web.UI.Control.InitRecursive(Control namingContainer) +186
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +2098


    Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.17929

    Copy Link
  • David Zweben 231 posts 688 karma points
    Sep 14, 2013 @ 00:10
    David Zweben
    0

    I'm eager to try out this package, so I tried again on a brand-new Umbraco 6.1.5 installation, and documented my steps right from the beginning in the hopes it would help track down the bug I'm encountering. At the end of this attempt, I got the same exact error as shown above, so this appears to be easily reproducable. Here's exactly what I did:

    • Set up a new local IIS site in IIS Manager on Windows 7 (IIS 7.5.7600)
    • Set the site to a .NET Framework V4.0 application pool
    • Extracted the Umbraco 6.1.5 ZIP to the site's root
    • Navigated to the site's localhost URL and began installation
    • Chose SQL CE 4 as the database option
    • Created an admin user
    • Skipped installing a starter kit
    • Went to settings and made a new document type, homepage, with no properties and an empty template.
    • Made a new document type and template 'Location Page'
    • Added the following properties, all as Textstrings: address, city, state, postalCode, country
    • Allowed Location Pages as child nodes of the Homepage document type
    • Created a 'homepage' node
    • Created 3 Location Page nodes under that, with all fields filled with unique sample data
    • Went to the developer section, install local package, and selected and installed Seek and Destroy 1.0
    • Went straight to the Seek and Destroy dashboard control
    • Installed the Google Maps data type from the dashboard control, got a success message
    • Chose 'Location Page' under 'Add google maps property to a doctype', entered 'googleMaps' under property alias and clicked 'Add property', got a success message
    • Chose 'Location Page' under 'Type of documents to geocode'
    • Chose my 5 Textstring properties in the dropdown menus below
    • Chose the new 'googleMaps' field as the 'Field to store coordinates'
    • Clicked GeoCode, got a success message
    • Navigated to the first of my Location Page nodes in Umbraco, got the same server error as shown above. All 3 'Location Page' nodes, as well as any new ones I create, are broken. My 'homepage' node works fine.
    • Went to the document type settings for 'Location Page', added a new Textstring property, 'Coordinates'
    • Went back to the Seek and Destroy dashboard control, repeated my steps from before with the 'Geo code documents' section, but this time selected my 'coordinates' textstring property instead of the Google Maps property
    • Checked the Location Page nodes again, still broken
    • Removed the Google Maps datatype that I created through the dashboard control from the Location Page document type
    • Checked the Location Page nodes again, they worked and the Coordinates fields were filled in with the correct coordinates
    My current thought is that choosing the Google Maps property as the field to store coordinates is incorrect, and is causing this issue. I am going to try again, but this time I'll set up a 'coordinates' text string property from the start, and select that the first time. Fingers crossed.

     

    Edit: Looks like my guess was wrong. I reverted to a backup from before I tried installing the package, and installed again, this time selecting a separate 'coordinates' property as the field to store coordinates, and I got the exact same error as on my earlier attempts.
    Copy Link
  • David Zweben 231 posts 688 karma points
    Oct 03, 2013 @ 18:55
    David Zweben
    0

    Have you been able to look into this at all? I was really hoping to use this package, but right now I can't get anywhere with it. Please let me know if there's anything else I can do to help figure out what's going wrong.

    Thanks, David

    Copy Link
  • Wesley Herpoelaert 52 posts 123 karma points
    Nov 14, 2013 @ 14:16
    Wesley Herpoelaert
    0

    Hello David,

    Just use the updated version of Google Maps datatype (2.1 instead 2.0.6).
    This will fix the error.

    Copy Link

  • This forum is in read-only mode while we transition to the new forum.

    You can continue this topic on the new forum by tapping the "Continue discussion" link below.

Please Sign in or register to post replies