<head> <meta charset="<?php bloginfo( 'charset' ); ?>" />
<head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"> " />
<header<?php print $attributes; ?>>
<header<?php print $attributes; ?><meta http-equiv="Content-Type" content="text/html; charset=utf-8">>
I am not so sure if you are trying to be funny or rude, but anyways, hahaha. Sorry if I hurt your feelings in some way Please let me know. Also, @cPanelLauren, delete my previous post.I wish I could go back 13 years and plant potatoes in my farm instead of getting into hosting business.
You see, the problem is that there are hundreds of files we did not even open it in the first place. They automatically got the meta tag. Our main website has +800 files. Plus our customers have the same problem on the shared servers. This is certainly not a workaround, this would work for a website with a few pages. On top of that w3 shows tons of error in many pages, google webmaster is shooting tons of error for that.The only temporary workaround I have at the moment is to download the file, edit locally, and reupload to overwrite, rather than editing directly via cPanel.
Quite an obvious solution to most I'm sure, but currently having to use this method on a few templates and should do the trick for anyone who has templated with persisting greater than symbols appearing at the top of their page.
Some insight into that, while, yes on the surface this would appear to be something that would be fixed quickly, it's not always that simple. There are things that have to be weighed when determining to make a change in a feature - longevity/direction (is this feature going to be present in future versions), If 3rd party is it modifiable?, Impact (what impact does this have on the product), Unintended consequences (will changes made here affect other items), Backlog (does the team have time for this in this sprint or are other features/changes taking precedence), etc.. I'm not saying specifically which if any of these are the case in this issue but really, it's not just issue reported -> Issue Fixed/Won't Fix.This is issue is a quick pool from technical point of view and it shouldn't take this long to get fixed. 12 of october 2019 this was reported by @rajeevacj today is almost february 2020.
Yay, glad that this is going to be fixed soon.Now, I do have an update on this, as of today the issue is in progress which indicates that it's being actively worked. From the case notes there is a fix for this which was committed today. I'll update you as to the status as it becomes available. Right now it looks like the fix will be available in v86.
|Thread starter||Similar threads||Forum||Replies||Date|
|New Thread How to get the default cPanel Zip file?||File Management||0|
|W||Cpanel user data rollback?||File Management||4|
|W||SOLVED Cpanel reading file size incorrectly||File Management||4|
|E||Fail or abborted cpanel account transfert||File Management||1|
|V||Cpanel Directory to a second Drive||File Management||5|