I'm using Umbraco 7.1.4 on IIS 7, and it seems that I've run into a small problem. The error below appears whenever I try to load a document in the backend that contains a RTE (NLS or otherwise), from a global IP.
Since the error is referencing NLS, I figured I'd ask for help here.
This line is where it breaks:
var nsLocalization = injector.get("nsLocalizationService");
Any idea what's going on?
Error: Circular dependency:
at Error (native)
at Object.c [as get] (http://xxx.xxx.xxx.xxx/umbraco/lib/angular/1.1.5/angular.min.js:27:72)
at tinymce.create.init (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/plugins/newsletterstudio/plugin.min.js:25:43)
at Array.e (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:8:20024)
at i (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:3:2958)
at Object.N.init (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:8:20481)
at n.<anonymous> (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:8:18602)
at Array.<anonymous> (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:3:31755)
at i (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:3:2958)
at h (http://xxx.xxx.xxx.xxx/umbraco/lib/tinymce/tinymce.min.js?umb__rnd=7.1.4.742119501:3:31732) angular.min.js:63
(anonymous function) angular.min.js:63
(anonymous function) angular.min.js:54
(anonymous function) angular.min.js:108
e angular.min.js:31
(anonymous function) angular.min.js:34
Yes, the page loads - partially. Meaning; all the umbraco stuff loads, but all other custom plugins stop working when it hits the error (probably because they use angular too).
As for a screenshot, yes - I could upload one, but it would not give you any more information than what I posted =/
The really strange thing is, that when I load the page through the global IP from the machine running IIS, there is no issue.
The machine is running IIS 7 on Win7 Ultimate (en/us) with 'Invariant Language (Invariant Country)' in the globalization settings where all encoding is utf-8 (in case that makes any difference).
Thank you for taking the time to look in to this :)
By "all the umbraco stuff loads, but all other custom plugins stop working ...." I mean that the umbraco UI loads, and I can navigate - but all the "custom plugin properties" on the affected node stop loading as soon I hit the error (just common js/angular error shenanigans).
'Global IP' might not be the correct term - but by that, I mean; I'm connecting to the site through my publicly available IP (ie. 87.xx.xx.157) - and yes, if the 'clear cache' button wasn't virtual, I'm pretty sure I would have broken it by now ;)
Unfortunately I'm not at the office today - so I can't do a 'screenr' of it - sorry (since the error only occurs when I access the IP from outside my local network).
On the bright side - the error does not occur when I access the site through the host provider - so there is that.
I imagine it might be some configuration error in IIS that messes up the localization somehow - a one in a million case maybe? :)
Thanks again (and sorry if this turns out to be a waste of time :P)
As far as I can know these package should work togheter with Newsletter Studio.
So you're saying that it works from the public IP but not from the development enviroment? It's really hard to tell the problem... are you running the site in debug mode or "release"? (I mean the <compilation debug="".. /> settings? Just thinking that the breakpoint you hit might be wrong? Or are you loading some of the scripts two times?
I've been running the package on both english and swedish servers with different settings so I can't really see that this should be the issue either...
What if you try a clean install of Umbraco with the Newsletter Studio? Are you haveing the same problem in that enviroment?
I set up Umbraco on a local IIS server at my home (I use this as a test environment for things that do not work well on localhost [twitter/linkedin/facebook oAuth]), because the place where I work has a very restricted network.
The site is accessible through the public IP that my ISP provided me with.
When I access the site through the public IP from my home network, the error does not appear.
When I access the site through the public IP from any other network, I get the error.
When I access the site through localhost, I do not get the error.
Yes, debug is set to true, no scripts are being loaded twice - and the error-output is grabbed from Chrome's console.
The setup is:
Webserver: IIS 7 running on a private machine with access through a public IP on port 80
Database: MSSQL 2012 hosted at UnoEuro (Language: English (United States) - Collation: Danish_Norwegian_CI_AS)
Afraid I can't provide any more details until I get back to the office tomorrow. Will do a test on a clean install when I get there, since I can't replicate the error from home =/
I'll post my findings as soon as I have something.
So, I did a little testing, but the outcome is still the same..
However - a fresh install of umbraco with nothing but newsletter studio seems to work fine (as expected). But I ran into some authentication issues with umbraco when accessing the fresh install's backend from the office, so I couldn't test what I wanted to test - namely, changing from a NS RTE into a regular umbraco RTE (as I remember doing that at some point on the site where the error pops up).
Sorry to keep you waiting - but I will not be able to test again until I get back tomorrow =/
As a sidenote; I asked a few friends to test the site where the error pops up, yesterday, and they did not encounter the error! But I still encountered it when I tried at the office today. So I suspect it might be related to either the machine at the office, or their network.
On the fresh installation I made yesterday I managed to replicate the error by turning the NS RTE into a regular umbraco RTE.
Create a new document type with a Newsletter Studio RTE property
Add a node with the document type
Change the document type's RTE property from NS RTE to umbraco RTE
Revisit the node (the editor should no longer load and the Circular Dependency error pops up)
I had some more people test the site yesterday - but nobody encountered the error. So, there is a slight chance it might just be related to the machine/network I use at the office (will try and hijack some of my co-workers machines and test there too).
Okey - so to clearyfi some things. The RTE in Newsletter Studio is a regular TinyMCE-data type - the only difference between the standard RTE and the one used in Newsletter Studio is that we have added 3 buttons for Newsletter Studio-specific features.
So what you are saying is that when you include the Newsletter Studio RTE on a document type you get the Circular Depencency errors? In that case I need to check this since if you are sending the newsletter from the content-section chances are that you might would like to include the Newsletter Studio-specific features in the RTE.
I'm gonna try to replicate the error but I'm really busy for the upcomming umbOktoberfest in Frankfurt this weekend - so I'll probably digg into this during next week.
1. Add new doc type and put the "Newsletter Studio Send out" property on that doc type, and also the "Newsletter Studio RTE" 2. Load the edit-view in the content-section - no errors 3. Go back to Settings and change the RTE to the standard Umbraco RTE - still no errors...
Afraid I can't give you more info than what I have already =/
But, by 'the other way around', I did not mean 'switch back and forth' - what I meant was; create the initial property as an Umbraco RTE, then, switch to NS RTE. (sry, that's what you did - messed up the order.. NS -> Umb)
That's how I triggered the error here.
(I'm honestly beginning to suspect that it is the machine at the office being a little wonky, as I have problems replicating the error from any other machine - so, again - sorry if this turns out to be a waste of time).
I'm now getting the circular dependency error after uninstalling the Newsletter Studio package. It has completely crippled my localhost instance of Umbraco as I'm no longer able to load any RTEs on the content pages.
Thank you for sharing your solution. So the circular dependency error was due to the buttons in the tinyMceConfig-file? They should be removed during the uninstall-process - did you have the chance to see any errors in the logs?
Circular Dependency
Hi,
Thanks for an excellent package :)
I'm using Umbraco 7.1.4 on IIS 7, and it seems that I've run into a small problem. The error below appears whenever I try to load a document in the backend that contains a RTE (NLS or otherwise), from a global IP.
Since the error is referencing NLS, I figured I'd ask for help here.
This line is where it breaks:
Any idea what's going on?
Hi!
This is strage - does the page load at all? Could you share a screenshot as well? I'll try to reproduce this!
Yes, the page loads - partially. Meaning; all the umbraco stuff loads, but all other custom plugins stop working when it hits the error (probably because they use angular too).
As for a screenshot, yes - I could upload one, but it would not give you any more information than what I posted =/
The really strange thing is, that when I load the page through the global IP from the machine running IIS, there is no issue.
The machine is running IIS 7 on Win7 Ultimate (en/us) with 'Invariant Language (Invariant Country)' in the globalization settings where all encoding is utf-8 (in case that makes any difference).
Thank you for taking the time to look in to this :)
Hi!
Okey!
I have tried to reproduce the bug but I can't do it.... could you record a screenr? (https://www.screenr.com/)
Is there any other packages installed? Have you installed the newsletter package multiple times?
Could you explain more about "all the umbraco stuff loads, but all other custom plugins stop working ...."?
How do you mean that you're using the "global" IP? Could this be cache related? Have you tried to empty the web broseser cache?
( Sorry for just shooting out ideas here =D )
Hello again,
Sorry for the late reply - long night :)
I have a few packages installed:
NS has only been installed once.
By "all the umbraco stuff loads, but all other custom plugins stop working ...." I mean that the umbraco UI loads, and I can navigate - but all the "custom plugin properties" on the affected node stop loading as soon I hit the error (just common js/angular error shenanigans).
'Global IP' might not be the correct term - but by that, I mean; I'm connecting to the site through my publicly available IP (ie. 87.xx.xx.157) - and yes, if the 'clear cache' button wasn't virtual, I'm pretty sure I would have broken it by now ;)
Unfortunately I'm not at the office today - so I can't do a 'screenr' of it - sorry (since the error only occurs when I access the IP from outside my local network).
On the bright side - the error does not occur when I access the site through the host provider - so there is that.
I imagine it might be some configuration error in IIS that messes up the localization somehow - a one in a million case maybe? :)
Thanks again (and sorry if this turns out to be a waste of time :P)
Hi!
As far as I can know these package should work togheter with Newsletter Studio.
So you're saying that it works from the public IP but not from the development enviroment? It's really hard to tell the problem... are you running the site in debug mode or "release"? (I mean the <compilation debug="".. /> settings? Just thinking that the breakpoint you hit might be wrong? Or are you loading some of the scripts two times?
I've been running the package on both english and swedish servers with different settings so I can't really see that this should be the issue either...
What if you try a clean install of Umbraco with the Newsletter Studio? Are you haveing the same problem in that enviroment?
// m
Hey :)
What I mean is:
Yes, debug is set to true, no scripts are being loaded twice - and the error-output is grabbed from Chrome's console.
The setup is:
Afraid I can't provide any more details until I get back to the office tomorrow. Will do a test on a clean install when I get there, since I can't replicate the error from home =/
I'll post my findings as soon as I have something.
Great! I'll try digg around as much as I can but let's look closer tomorrow!
Hi again,
So, I did a little testing, but the outcome is still the same..
However - a fresh install of umbraco with nothing but newsletter studio seems to work fine (as expected). But I ran into some authentication issues with umbraco when accessing the fresh install's backend from the office, so I couldn't test what I wanted to test - namely, changing from a NS RTE into a regular umbraco RTE (as I remember doing that at some point on the site where the error pops up).
Sorry to keep you waiting - but I will not be able to test again until I get back tomorrow =/
As a sidenote; I asked a few friends to test the site where the error pops up, yesterday, and they did not encounter the error! But I still encountered it when I tried at the office today. So I suspect it might be related to either the machine at the office, or their network.
I'll keep you posted :)
There we go :)
On the fresh installation I made yesterday I managed to replicate the error by turning the NS RTE into a regular umbraco RTE.
I had some more people test the site yesterday - but nobody encountered the error. So, there is a slight chance it might just be related to the machine/network I use at the office (will try and hijack some of my co-workers machines and test there too).
Hi!
Okey - so to clearyfi some things. The RTE in Newsletter Studio is a regular TinyMCE-data type - the only difference between the standard RTE and the one used in Newsletter Studio is that we have added 3 buttons for Newsletter Studio-specific features.
So what you are saying is that when you include the Newsletter Studio RTE on a document type you get the Circular Depencency errors? In that case I need to check this since if you are sending the newsletter from the content-section chances are that you might would like to include the Newsletter Studio-specific features in the RTE.
I'm gonna try to replicate the error but I'm really busy for the upcomming umbOktoberfest in Frankfurt this weekend - so I'll probably digg into this during next week.
Cheers
Correct - the error only occurs after changing the property from NS RTE to umbraco RTE. It works fine if I just add the NS RTE and leave it like that.
I'll let you know if I discover something new.
Have a nice trip to Frankfurt :)
Bump :)
Any luck reproducing this?
Hi!
I have not had any time to work on this yet due to other releases. Is this a show-stopper for you atm?
Hi,
Not a total showstopper - but would definitely like to see a fix/workaround before we go live.
I've actually encountered it on localhost too now =/ - usually pops up after clearing the cache (with the 'Clear Cache' extension for chrome).
Hi again!
I've tried to
1. Add new doc type and put the "Newsletter Studio Send out" property on that doc type, and also the "Newsletter Studio RTE"
2. Load the edit-view in the content-section - no errors
3. Go back to Settings and change the RTE to the standard Umbraco RTE - still no errors...
So... i can'r reporduce it.. :/
Hi :)
Did you try the other way around?
Umbraco RTE -> Newsletter Studio RTE
That's how I reproduced the error.
Hi!
Yes i switched back and forth... could you give me some exact steps on how to reproduce this on a clean document type?
Hi,
Afraid I can't give you more info than what I have already =/
But, by 'the other way around', I did not mean 'switch back and forth' - what I meant was; create the initial property as an Umbraco RTE, then, switch to NS RTE. (sry, that's what you did - messed up the order.. NS -> Umb)
That's how I triggered the error here.
(I'm honestly beginning to suspect that it is the machine at the office being a little wonky, as I have problems replicating the error from any other machine - so, again - sorry if this turns out to be a waste of time).
I'm now getting the circular dependency error after uninstalling the Newsletter Studio package. It has completely crippled my localhost instance of Umbraco as I'm no longer able to load any RTEs on the content pages.
Okay, I was able to solve this issue by deleting the extra buttons and plugin in the /Config/tinyMceConfig.config file.
Unfortunately, I'm now getting a new error that was never there before and seems to have nothing to do with this package:
Hi!
Thank you for sharing your solution. So the circular dependency error was due to the buttons in the tinyMceConfig-file? They should be removed during the uninstall-process - did you have the chance to see any errors in the logs?
Thanks for letting me know about your issues.
// m
is working on a reply...