Copied to clipboard

Flag this post as spam?

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


  • noam.prime 2 posts 51 karma points
    Mar 10, 2014 @ 10:37
    noam.prime
    0

    getting Error: Argument 'uTagsy.PropertyEditors.TagsController' is not a function, got undefined

    Hi, I'm getting an error in the admin when I try to edit or add new post. here's a snapshot of the error from the chrome's developer tools:

    this Error occurs only on servers (both QA and Production, both has IIS7 running) not in localhost and it causes a bug which prevents the ability to insert tags in posts.

    Does anyone has an idea why is it happenning and how I can fix this?

    I hope I wrote this in the right forum.

    Thanks,

    Noam

  • noam.prime 2 posts 51 karma points
    Mar 11, 2014 @ 16:38
    noam.prime
    0

    Anyone, Please...

  • Kleber Hucalo 26 posts 165 karma points
    Jun 26, 2014 @ 04:58
    Kleber Hucalo
    0

    I am getting same error, did you fix it?

  • Kleber Hucalo 26 posts 165 karma points
    Jul 02, 2014 @ 03:15
    Kleber Hucalo
    0

    Ok

    I found the solution for this issue, if anyone out there is looking for the same thing.

    When I was running the website in http it worked fine, when switch to https is was causing the problem.

    On local all worked fine both http and https.

    My problem was with the SSL certificate in the server being expired.

    Then the solution was to generate new SSL certificate, upload to server and bind it to website (https) in the IIS.

    Refresh the browser cache by clicking ctrl+f5 and should work again.

    Great stuff 

  • wayferer 9 posts 50 karma points
    Aug 14, 2014 @ 19:01
    wayferer
    0

    I'm also getting this error but I'm not running HTTPS. Any other suggestions?

    Edit:

    Seems like if I change the package.manifest from:

    {
        propertyEditors: [
                {
                        alias: "uTagsy",
                        name: "uTagsy Tag Editor",
                        hideLabel: false,
                        valueType: "INT",
                        editor: {
                                view: "~/App_Plugins/uTagsy/propertyEditors/uTagsyEditor.html?v=25"
                        }
                }
        ],
    
        javascript: [
            '~/App_Plugins/uTagsy/propertyEditors/uTagsyEditor.controller.js?v=60'
        ]
    }
    

    to:

    {
        propertyEditors: [
                {
                        alias: "uTagsy",
                        name: "uTagsy Tag Editor",
                        hideLabel: false,
                        valueType: "INT",
                        editor: {
                                view: "~/App_Plugins/uTagsy/propertyEditors/uTagsyEditor.html"
                        }
                }
        ],
    
        javascript: [
            '~/App_Plugins/uTagsy/propertyEditors/uTagsyEditor.controller.js'
        ]
    }
    

    It will load fine. Now I have the following error:

    Error: Duplicates in a repeater are not allowed. Repeater: tag in currentTags key: string:l
    at Error (native)
    at http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:161:273
    at Object.fn (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:90:12)
    at Object.e.$digest (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:90:356)
    at Object.e.$apply (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:92:431)
    at j (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:101:80)
    at r (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:104:449)
    at XMLHttpRequest.v.onreadystatechange (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:106:90) angular.min.js:63
    
    Error: Duplicates in a repeater are not allowed. Repeater: tag in allTags key: string:l
    at Error (native)
    at http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:161:273
    at Object.fn (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:90:12)
    at Object.e.$digest (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:90:356)
    at Object.e.$apply (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:92:431)
    at j (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:101:80)
    at r (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:104:449)
    at XMLHttpRequest.v.onreadystatechange (http://{sampleurl}/umbraco/lib/angular/1.1.5/angular.min.js:106:90) angular.min.js:63
    

    Not sure if I'm on the right track or not?

  • Timothy Lee Russell 20 posts 43 karma points c-trib
    Sep 22, 2015 @ 23:47
    Timothy Lee Russell
    0

    Having the versioning number on the javascript paths (which we were doing because of caching problems) does seem to cause problems somewhere in the pipeline.

  • Luca Annuiti 16 posts 76 karma points
    Feb 05, 2015 @ 14:30
    Luca Annuiti
    0

    I've getting the same error on v.7.2.1 , but previously it was working.

    I think the problem appered after the upgrade from 7.2 to 7.2.1

    Any suggestion ??

Please Sign in or register to post replies

Write your reply to:

Draft