Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Admin :: File Management - node.get_text is not a functionAdmin :: File Management - node.get_text is not a function
Previous
 
Next
New Post
6/17/2015 8:46 PM
 

A couple of more findings:

(To repeat this is an upgrade from 5.6.2 directly to 7.3.4)

Testing against a 7.1 install, when clicking the upload button under File Manager, the popup activates immediately. On the upgraded 7.3.4 site there is a post back to the page and then the page locks. So is there a setting missing that forces DNN to do the popup instead of the post back? I've checked the Host :: Site Management :: I}Usability Settings :: User Popups is checked.

Additionally, when I try to run the Admin Toolbar :: Tools :: Upload File, it fails. Digging into the code shows that the FileUpload object is not built correctly. Walking the code during page build, shows that the "options" object passed to the dnn.createFileUpload function has all the keys first letter Capitalized, while on the 7.1.x install these keys are start lower case. This causes the instance creation to not complete because it can't find options.clientId (when the actual key is options.ClientId).

upgraded site options object:

  1. optionsObject
    1. ClientId"fileUploader"
    2. ExtensionsArray[0]
    3. FolderPathnull
    4. FolderPickerObject
    5. Height630
    6. MaxFileSize8388608
    7. MaxFiles0
    8. ModuleId""
    9. ParametersObject
    10. ParentClientIdnull
    11. ResourcesObject
    12. ShowOnStartupfalse
    13. Width780
    14. __proto__Object

7.1.x non upgraded site:

  1. optionsObject
    1. clientId"fileUploader"
    2. extensionsArray[0]
    3. folderPathnull
    4. folderPickerObject
    5. height630
    6. maxFileSize29360128
    7. maxFiles0
    8. moduleId""
    9. parametersObject
    10. parentClientIdnull
    11. resourcesObject
    12. showOnStartupfalse
    13. width780
    14. __proto__Object

Any idea where the options Object is created so I can investigate further?

dnn.createFileUpload = function (options) {

    $(document).ready(function () {

        var instance;

        if (options.parentClientId) {

            instance = new dnn.FileUploadPanel(options);

            var $parent = $("#" + options.parentClientId);

            if ($parent.length !== 0) {

                $parent.append(instance.$element);

            }

        }

        else {

            instance = new dnn.FileUploadDialog(options);

        }

        if (options.clientId) {

            dnn[options.clientId] = instance;

        }

    });

 

 
New Post
6/18/2015 12:36 AM
Accepted Answer 

FWIW - After some creative searching of the Community source code we found the source of the problem.

The issue was the "version" of NewtonSoft.Json.DLL installed during the upgrade. We didn't flip the App Pool affiliation to dotNet 4.0 until after the upgrade had completed, so the upgrade process dropped in the dotNet 2.0 version of of the DLL. After we manually updated the DLL to the dotNet 4.0 version the correct case of the options object was built and the File Upload issues were fixed.

Even if there is a global serialization config parameter that forces the Json option keys to start with lowercase for dotNet 2.0 the two versions of the NewtonSoft DLL are not exactly the same out of the box.

 

 
New Post
6/18/2015 4:28 PM
 

Just to be complete: The dotNet 2.0 version of NewtonSoft.Json was installed by a 3rd party module during it's upgrade process (done after the DNN upgrade). The DNN 7.3.4 upgrade package contains only the dotNet 4.0 NewtonSoft.Json DLL.

 
New Post
11/26/2015 7:24 AM
 
I experience the exact same issue after upgrading from 6.2.9. In my case the NewtonSoft.Json is exacly the same but still have this error.

Digging around I found that the getFileUpload() function on dnn.DigitalAssets (line 2450) returns undefined:
2452 fileUpload = dnn[controls.fileUploadId] => returns undefined.

Any suggestions? the DigitalAssets.js files are equal.

 
New Post
11/26/2015 9:35 AM
 
maybe this issue is related: https://dnntracker.atlassian.net/brow...

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Admin :: File Management - node.get_text is not a functionAdmin :: File Management - node.get_text is not a function


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