Character encoding issue - ¤ ¤ Currency sign (typography)
Hi All,
We've built a document type comprised of umbraco drop down lists with a couple of prevalues. The document type is comprised of a a few umbraco drop downs with different prevalues. In short, we're allowing users to select a horizontal alignment, vertical alignment and banner type. In the razor template we then join all three together to find the path for the partial. e.g. top-middle-short.cshtml
the code for this is:
VerticalAlignmentType + "-" + HorizontalAlignmentType + "-" + BannerType;
The error we're getting is:
The partial view '/Banners/¤middle-¤left-short' was not found or no view engine supports the searched locations.
As you can see, the first two drop down types (vertical and horizontal) have the currency sign (https://en.wikipedia.org/wiki/Currencysign(typography) ¤) being injected but the last dropdown list value. I've looked into the database and it's actually stored in there so I suspect it's something to do with the prevalues of the umbraco drop down list. Has anyone else ever experienced this? If so what did you do to solve it? At the moment we're just doing a string replace as a quick hack but i'd like to find out why this is being caused.
Further info: We're using umbraco as a service and programming on both Windows and Macs (we're seeing the encoding issue on both but only locally not in our azure environments).
Had this same issue first time we used UaaS migrating an existing site; appears to be an issue with Courier/Umbraco Deploy though don't have exact cause & therefore fix.
Migrated project was a mutli-site install with domains (and therefore culture) set on child nodes.
Issue was only present in Drop Down List pre-values.
We've resolved this but are unsure what the exact fix was as we had a few days of whack-a-mole trying different things to fix various issues.
Things to try that possibly made a difference (for us anyhow):
1) In the back office, under Settings -> Languages check that these are correct. In our case the site being migrated was English (United Kingdom) rather than the default English (United States).
Umbraco will add a default English (United States) on all new projects/installs; could possibly cause an issue - we noticed that all domains got transferred but as en-us rather than en-uk.
We deleted the unwanted English (United States) language.
2) Do you have a <globalisation> element in your web.config; we also removed this.
After this, wiping environment and ensuring en-us language was no longer present in local or remote environment we successfully pushed all content without seeing the issue again (took a couple of attempts, schema synchronisation caused language to be downloaded locally, then uploaded remotely again after deletion).
The only other thing we did was downgrade target framework from 4.5.2 to 4.5 - don't think it was necessary but did it anyway in effort to get site working as close to using "Umbraco defaults"...
Not amazing but it works for now. I can strip it out of the database manually but it keeps coming back so I'll try the suggested fixes above and get back to you.
Character encoding issue - ¤ ¤ Currency sign (typography)
Hi All,
We've built a document type comprised of umbraco drop down lists with a couple of prevalues. The document type is comprised of a a few umbraco drop downs with different prevalues. In short, we're allowing users to select a horizontal alignment, vertical alignment and banner type. In the razor template we then join all three together to find the path for the partial. e.g. top-middle-short.cshtml the code for this is: VerticalAlignmentType + "-" + HorizontalAlignmentType + "-" + BannerType;
The error we're getting is: The partial view '/Banners/¤middle-¤left-short' was not found or no view engine supports the searched locations.
As you can see, the first two drop down types (vertical and horizontal) have the currency sign (https://en.wikipedia.org/wiki/Currencysign(typography) ¤) being injected but the last dropdown list value. I've looked into the database and it's actually stored in there so I suspect it's something to do with the prevalues of the umbraco drop down list. Has anyone else ever experienced this? If so what did you do to solve it? At the moment we're just doing a string replace as a quick hack but i'd like to find out why this is being caused.
Further info: We're using umbraco as a service and programming on both Windows and Macs (we're seeing the encoding issue on both but only locally not in our azure environments).
Thanks!
Dave
Had this same issue first time we used UaaS migrating an existing site; appears to be an issue with Courier/Umbraco Deploy though don't have exact cause & therefore fix.
Migrated project was a mutli-site install with domains (and therefore culture) set on child nodes.
Issue was only present in Drop Down List pre-values.
We've resolved this but are unsure what the exact fix was as we had a few days of whack-a-mole trying different things to fix various issues.
Things to try that possibly made a difference (for us anyhow):
1) In the back office, under Settings -> Languages check that these are correct. In our case the site being migrated was English (United Kingdom) rather than the default English (United States).
Umbraco will add a default English (United States) on all new projects/installs; could possibly cause an issue - we noticed that all domains got transferred but as en-us rather than en-uk.
We deleted the unwanted English (United States) language.
2) Do you have a <globalisation> element in your web.config; we also removed this.
After this, wiping environment and ensuring en-us language was no longer present in local or remote environment we successfully pushed all content without seeing the issue again (took a couple of attempts, schema synchronisation caused language to be downloaded locally, then uploaded remotely again after deletion).
The only other thing we did was downgrade target framework from 4.5.2 to 4.5 - don't think it was necessary but did it anyway in effort to get site working as close to using "Umbraco defaults"...
Hope you find solution!
Exact config setting we removed was:
Thanks for your reply Gavin! Our current fix is:
Not amazing but it works for now. I can strip it out of the database manually but it keeps coming back so I'll try the suggested fixes above and get back to you.
Just tried this and we don't have this in our web config so at least we can eliminate this as a possible cause.
We are also using the latest available Umbraco Deploy package:
UaaS.Courier.UIversion 3.0.2Available from http://nightly.umbraco.org/?container=umbraco-deploy-release or MyGet feed - https://www.myget.org/F/uaas/api/v3/index.json
This is likely what fixed it in our case.
is working on a reply...