I assume that you aren't using a Virtual Directory for your Umbraco install. You can disable the ResolveUrls lookup in the umbracoSettings.config, just set it to False.
In answer to your question... e.g. What the heck is it doing?
Just taken a look at the core source and ResolveUrlsFromTextString is called from most places where a Property value will be outputted; e.g. XSLT's output, <umbraco:Item>, INode's Value property (in Razor).
The method itself performs a RegEx, looking for any attributes containing a file/path ... it then tries to resolve/correct the application paths, e.g. "~/media/whatever" would resolve to the appropriate path - this is useful when using a virtual directory.
If you have a lot of links/images inside a macro (regardless if it's XSLT or Razor), then the RegEx is going to be applied against it ... causing a big performance hit!
So if you're not using virtual directories, then it's recommended to disable that feature.
Thanks for your quick reply. I will keep this setting in mind from now on. However it does
Turns out that the issue was caused by a connectionstring defined in the <conncectionStrings> section, which for some reason had same credentials as the one defined in UmbracoDbDsn?
I'm a bit confused right now, but now it's working. Will try to investigate further and share my findings.
How to read the umbraco trace log?
Hi guys
I'm currently trying to figure out how I should read the trace log in more detail.
I have deployed a site from staging to the live environment and now the site is slow.
I tried adding ?umbdebugshowtrace=1 and I can see the "Resolve Urls" for some reason seems to be very slow, which can be seen in the image below.
Can anyone explain to me what this means?
The site is running smoothly on our staging environment.
I'm running Umbraco 4.7.1.1
Stage environment is Windows 2008 Server, MSSQL Server 2008 R2, IIS7.5
Live environement is Windows 2008 Server, MSSQL Server 2008, IIS 7.5
(Yes I managed to script the database and deploy from MSSQL Server 2008 R2 to MSSQL Server 2008 - It nearly killed me :)).
Could it be some configuration on the server that we have missed?
Looking forward to receive any feedback.
Cheers,
Jan
I Should also mention that on the live site we're currently running on the IP adress and no hostname is assigned yet.
Also there is some Url Rewriting done, but I'm confident that if it was the issue then it would have showed on staging.
/Jan
Hi Jan,
I assume that you aren't using a Virtual Directory for your Umbraco install. You can disable the ResolveUrls lookup in the umbracoSettings.config, just set it to False.
Cheers, Lee.
In answer to your question... e.g. What the heck is it doing?
Just taken a look at the core source and ResolveUrlsFromTextString is called from most places where a Property value will be outputted; e.g. XSLT's output, <umbraco:Item>, INode's Value property (in Razor).
The method itself performs a RegEx, looking for any attributes containing a file/path ... it then tries to resolve/correct the application paths, e.g. "~/media/whatever" would resolve to the appropriate path - this is useful when using a virtual directory.
If you have a lot of links/images inside a macro (regardless if it's XSLT or Razor), then the RegEx is going to be applied against it ... causing a big performance hit!
So if you're not using virtual directories, then it's recommended to disable that feature.
Cheers, Lee.
Hi Lee
Thanks for your quick reply. I will keep this setting in mind from now on. However it does
Turns out that the issue was caused by a connectionstring defined in the <conncectionStrings> section, which for some reason had same credentials as the one defined in UmbracoDbDsn?
I'm a bit confused right now, but now it's working. Will try to investigate further and share my findings.
Cheers,
Jan
Turns out that we missed change some credentials in the <connectionStrings> section, which was the cause of the trouble. #h5is :)
/Jan
is working on a reply...