I have website based on Umbraco 5. I have installed contact form plugin (http://cultivjupitercontact.codeplex.com/).
And on the web page at the end of this contact form there are always characters "". It looks like that:
...
<input type="submit" value="Send" />
</fieldset>
<input name='uformpostroutevals' type='hidden' value='somevalue' /></form>
I suspect there is something wrong with encoding. I have tried to change it(to ANSI or UTF-8 without BOM but it didn't helped. Perhaps I have changed it in wrong file, cause I don't really know where exactly this ''is coming from. All I know it came with this plugin.
On different server those extra characters are "".
How can I get rid of those extra characters?
Any help much appreciated!
You need to upgrade to the 5.0.1 patch release or later.
This is due to a bug that includes the BOM (Byte order mark) for UTF-8 files as detailed in the bug report "Text encoding in file when saving the template".
I can verify that upgrading to 5.0.1 fixed the issue.
Related
I've updated a website from TYPO3 7.6 to 9.5.
Now it seems that the frontend output of CKEditor removes whitespaces between two HTML tags:
<strong>sometext:</strong>more text
In the editor, there is a whitespace between the closing </strong> and the opening <a> tag.
Is there any way to configure this?
I think that the problem here is that on version 9.5 the Fluid Content Elements are using the viewhelper <f:spaceless> that removes the white spaces - see
/typo3/sysext/fluid_styled_content/Resources/Private/Layouts/Default.html
If this is wrong for you you can override the default layout file removing it.
I've tried this for myself and the RTE deosn't remove the whitespace between </span> <a href.....
I Have experienced issues with the CKEditor after uprgading from 7.6 to 9.5 too.
In my case I had to cleanup my TypoScript.
If you have any old configuration in your TypoScript (RTE.whatever), remove that and try again.
Maybe you can remove all of your custom TS and check the RTE behavior to make sure the error came from there.
I'm making a web application using ASP.NET Core 2.2 and trying out Razor Pages more or less for the first time. When using "asp-for" attributes in order to bind an HTML input to a PageModel property, everything works just fine, but then when editing any attribute in any HTML element in the script that also has an "asp-for" attribute defined, all "asp-for" values for every other element but the one I'm editing are scrambled/wiped out.
I'm using the latest version of Visual Studio 2019 Community Edition and all extensions are up to date. ASP.NET Core 2.2 and all included packages are their respective latest stable versions.
I've tried disabling all extensions one by one, restarting the application each time to see if one of them is causing any strange behaviour- I'm not using many to begin with though, mostly just GitHub integration and "Format on Save" at the moment.
I've also tried going through the preferences and unchecking many of the validation options for HTML and C#, and things like automatic quotations for new attributes and closing bracket insertions... basically, anything that I thought could potentially have an impact. Nothing has worked.
An example would be something like:
<div>
<table>
<tr>
<td>Entry ID:</td>
<td><input type="text" asp-for="EntryID" /></td>
</tr>
<tr>
<td>Entry Name:</td>
<td><input type="text" asp-for="EntryName" /></td>
</tr>
</table>
</div>
When editing any of the attributes for any element with an asp-for attached, the asp-for value for the other tags will be scrambled. This happens both when I use the backspace key or the delete key, so it doesn't appear to be keyboard-shortcut related.
Here's a gif of the issue (not enough reputation to post images apparently- apologies).
https://drive.google.com/file/d/1f1gZSvGrQ8ehpTNwKOA2YbCkfLhx_o-M
If anyone has any ideas, I'd be quite grateful. This is really killing productivity and I haven't really come up with any ways to consistently get around the issue- usually when deleting the entire attribute all at once (which still scrambles other values), I can hit Undo once and it'll undo the scrambling but not the deletion itself. That's not 100% though, so it's just a big headache all around.
UPDATE 7/31: I've gone ahead and reported this to Microsoft as per Peter B's suggestion. A link to the report can be had here if anyone comes along with the same issue and are wondering at the progress there.
Your gif shows it happening for the id attribute, but you shouldn't try to specify the id because the Input Tag Helper already does it for you:
The Input Tag Helper:
* Generates the id and name HTML attributes for the expression name specified in the asp-for attribute. [...]
Source:
https://learn.microsoft.com/en-us/aspnet/core/mvc/views/working-with-forms?view=aspnetcore-2.2
I agree that it seems to be acting a bit weird. If it persists, you can try reporting the weird behaviour, as described here: https://learn.microsoft.com/en-us/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2019
When I tried to validate a recent project, I got multiple errors which say "Malformed byte sequence: 92." What does this mean? It's got something to do with the charset UTF-8, but I can't find ANY information online about what this problem is or how to fix it. If anyone out there could give me a hand, that would be great!!! I only know HTML, CSS and a little JavaScript.
Okay, I figured it out. I was saving my projects as ANSI. There was a setting under the "File" tab in my code editor (Programmer's Notepad) entitled "Encoding". I changed that to UTF-8 and it cleared up the validation problems.
I hope someone can help me with this issue.
For a few months (since last August) there has been an ongoing issue on my site with strange characters appearing all over the place - especially in user generated content.
I have searched and searched for answers but nothing ever seems to work, although the most pressing (in the blog component) has been resolved by setting JCE to validate HTML - which is does fine in the Blogging component (EasyBlog) but doesn't anywhere else (where it is less critical but still an issue).
Here is what I have done so far:
Checked the site from multiple machines, multiple browsers - no difference.
Checked the MySQL database and table collation - which are utf8_general_ci
Added AddDefaultCharset UTF-8 and AddCharset UTF-8 .php to the .htaccess files. I played about with these for ages and these two seemed to be the only combination which didn't crash the site.
Have checked the HTML headers and they definitely have the correct content encoding types (set to UTF-8)
I have tried different WSIWIG editors to no avail. Besides it is often in the code output where the characters appear - typically a A next to a »
I have tried a hack to force the connection script to UTF-8 but this causes the site to crash.
If anyone has any ideas at all as to what I can do still ... I'm all ears (please)
Many thanks in advance
If your server is running PHP 5.4+ I would suggest that you try the following solution described in the JCE forums:
In the Editor Global Configuration, set "Entity Encoding" to "UTF-8"
In the "Custom Configuration Variables" field, add:
keep_nbsp:0
The keep an eye out for the JCE 2.3.2 release which will address this issue.
Things to note:
anywhere the spurious â or  is occurring will have to be edited to remove the characters (once the changes above have been applied to JCE).
the problem is Joomla! 2.5.x's use of get_html_translation_table() which relies on default values and PHP 5.4 changed the default encoding parameter to UTF-8. Previously it defaulted to ISO-8859-1
For the core you could try and modify _decode() in /libraries/joomla/filter/input.php, look for the line (around 644):
$trans_tbl = get_html_translation_table(HTML_ENTITIES);
and change it to:
$trans_tbl = get_html_translation_table(HTML_ENTITIES, ENT_COMPAT, 'ISO-8859-1');
Did anybody successfully manage to correctly export a vcard from a Website containing Microformats (hcard) with this Firefox Plugin?
When doing so, I end up with weird characters instead of (german/spanish) Umlauts. While it's really easy to provide vcards as well, I would like to know if someone managed to correct the charset/character problems I am experiencing.
Does your document + hcard validates?