-
AuthorPosts
-
March 24, 2019 at 2:51 pm #1082238
Link to original post: https://www.facebook.com/groups/WordpressEnfold/permalink/1310996315706599/
Having problems with one website. Problem is sometimes hard to replicate, but usually happens on a mobile device, but can sometimes happen on PC also (but not often). Firefox ESPECIALLY has this problem, Chrome SOMETIMES – You never know when it will happen…
Cache = W3TC
Security = WF & server side
Image compression = SmushDebugging Info for Theme support:
Theme: Enfold
Version: 4.5.4
Installed: enfold
AviaFramework Version: 5.0
AviaBuilder Version: 0.9.5
aviaElementManager Version: 1.0.1
ML:512-PU:60-PLA:16
WP:5.1.1
Compress: CSS:all theme files – JS:all theme files
Updates: enabledMarch 24, 2019 at 3:22 pm #1082240that’s odd … i get a lot of “403 forbidden” and “404 not found” statuses for your pages and files like images and CSS … but only when i try to open the site or images with firefox (newest version) …
it doesn’t happen in google chrome.I don’t think this can be related to the Enfold theme. Looks more like a server issue … also i can’t think of a specific reason for this at the moment.
On the other hand when i try to open one of the images directly, i get a brooken 404-page from wordpress. So a WP-Plugin causing this seems more reasonable.Did you try deactivating all your plugins?
Maybe it’s a misconfiguration of W3 Total Cache ?Edit:
Most likely it’s a configuration issue of Word Fence, W3 Total Cache, server side or the interaction of them.
I’d go back to a clean version without any possible related configuration and step by step adding plugins and server modifications.Edit:
These Server HTTP Headers can cause problems, when your settings aren’t matching, like mime type responses from the server:X-XSS-Protection: 1; mode=block
X-Content-Type-Options: nosniff
See for example “Firefox ran into problems supporting nosniff for images”: https://github.com/whatwg/fetch/issues/395
- This reply was modified 5 years, 9 months ago by cg.
March 25, 2019 at 3:50 pm #1082720Hi Mike,
I tried a few times on my iPhone, could not reproduce the issue.
Best regards,
VictoriaMarch 25, 2019 at 5:38 pm #1082771screenshot of network analysis in firefox from my end … 403, 404, 404, 404, 404, etc.pp. …
March 29, 2019 at 8:33 am #1084483Hi,
Please post us your login credentials (in the “private data” field), so we can take a look at your backend.
- Install and activate ” Temporary Login Without Password “.
- Go to ” Users > Temporary Logins ” on the left-side menu.
- Click ” Create New “.
- Add the email address for the account ( you can use (Email address hidden if logged out) ), as well as the ” Role ” making that the highest possible and the expiry about four days
( do be sure that we have enough time to debug ). - Click ” Submit “.
- You’ll now have a temporary account. Please provide us here in the private section the URL, so we can login and help you out.
When your issue is fixed, you can always remove the plugin!
If you prefer to not use the plugin, you can manually create an admin user and post the login credentials in the “private data” field.Best regards,
BasilisApril 3, 2019 at 2:23 am #1086289Here are all the errors in Chrome:
https://www.yourpoolbuilder.com/46
Refused to apply style from ‘<URL>’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/grid.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/plugins/wunderground/assets/css/wunderground.css?ver=2.1.3’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/layout.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/blog/blog.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/base.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-includes/css/dashicons.min.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/postslider/postslider.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons/buttons.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/buttons_fullwidth/buttons_fullwidth.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/comments/comments.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow/slideshow.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/contentslider/contentslider.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/heading/heading.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/google_maps/google_maps.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/gallery_horizontal/gallery_horizontal.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/grid_row/grid_row.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/gallery/gallery.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/hr/hr.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/icon/icon.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/iconbox/iconbox.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/iconlist/iconlist.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/image/image.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/magazine/magazine.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/masonry_entries/masonry_entries.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/promobox/promobox.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/menu/menu.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/progressbar/progressbar.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/avia-snippet-site-preloader.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_fullsize/slideshow_fullsize.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_layerslider/slideshow_layerslider.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/social_share/social_share.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/slideshow_fullscreen/slideshow_fullscreen.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/tab_section/tab_section.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/tabs/tabs.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/toggles/toggles.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/config-templatebuilder/avia-shortcodes/video/video.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-includes/css/dist/block-library/style.min.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/js/aviapopup/magnific-popup.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/plugins/contact-form-7/includes/css/styles.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/shortcodes.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/avia-snippet-lightbox.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-includes/js/mediaelement/mediaelementplayer-legacy.min.css?ver=4.2.6-78496d1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/avia-snippet-widget.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/uploads/dynamic_avia/enfold.css?ver=5c9bd83672b52’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-includes/js/mediaelement/wp-mediaelement.min.css?ver=5.1.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
(index):1 Refused to apply style from ‘https://www.yourpoolbuilder.com/wp-content/themes/enfold/css/custom.css?ver=4.5.4’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.April 3, 2019 at 2:25 am #1086290Loading from Chrome INCOGNITO seems to work (front end only)
Admin login seems stuck infinite redirect…April 3, 2019 at 9:48 am #1086451As i suspected before … remove the Nosniff-Option from your server configuration or serve proper Mime-Types.
April 3, 2019 at 4:45 pm #1086611Hey Cg, I found this related to “nosniff” in htaccess:
#BEGIN NOSNIFF <IfModule mod_headers.c> Header set X-Content-Type-Options nosniff </IfModule> #END NOSNIFF
I have deleted that line in htaccess. Is there anything else related to “nosniff” I need to check?
April 3, 2019 at 4:48 pm #1086612Additional lines in the htaccess:
# BEGIN Protect Against Script Injections Options +FollowSymLinks RewriteEngine On RewriteCond %{QUERY_STRING} (<|%3C).*script.*(>|%3E) [NC,OR] RewriteCond %{QUERY_STRING} GLOBALS(=|[|%[0-9A-Z]{0,2}) [OR] RewriteCond %{QUERY_STRING} _REQUEST(=|[|%[0-9A-Z]{0,2}) RewriteRule ^(.*)$ index.php [F,L] # END Protect Against Script Injections # BEGIN Directory Browsing Block Options -Indexes # END Directory Browsing Block # BEGIN Protect the wp-config.php file <Files wp-config.php> order allow,deny deny from all </Files> # END Protect the wp-config.php file # BEGIN Custom 403 <Files 403.shtml> order allow,deny allow from all </Files> #END Custom 403 # Block the include-only files <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^wp-admin/includes/ - [F,L] RewriteRule !^wp-includes/ - [S=3] RewriteRule ^wp-includes/[^/]+\.php$ - [F,L] RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F,L] RewriteRule ^wp-includes/theme-compat/ - [F,L] </IfModule> # Block the include-only files # BEGIN Disable XML-RPC.PHP <Files xmlrpc.php> Order Deny,Allow Deny from all </Files> # END Disable XML-RPC.PHP # BEGIN PROTECT ACCESS TO HTACCESS <Files ~"^.*\.([Hh][Tt][Aa])"> order allow,deny deny from all satisfy all </Files> # END PROTECT ACCESS TO HTACCESS #BEGIN PROTECT XSS <IfModule mod_headers.c> Header set X-XSS-Protection "1; mode=block" </IfModule> #END PROTECT XSS
These are obviously for security, let me know if any are conflicting or unnecessary…
April 3, 2019 at 4:49 pm #1086614php ini is available to check on this domain, but here are some settings from cpanel found in htaccess:
# BEGIN cPanel-generated php ini directives, do not edit # Manual editing of this file may result in unexpected behavior. # To make changes to this file, use the cPanel MultiPHP INI Editor (Home >> Software >> MultiPHP INI Editor) # For more information, read our documentation (https://go.cpanel.net/EA4ModifyINI) <IfModule php7_module> php_flag display_errors Off php_value max_execution_time 180 php_value max_input_time 180 php_value max_input_vars 2100 php_value memory_limit 512M php_value post_max_size 128M php_value session.gc_maxlifetime 1440 php_value session.save_path "/var/cpanel/php/sessions/ea-php71" php_value upload_max_filesize 32M php_flag zlib.output_compression Off </IfModule> # END cPanel-generated php ini directives, do not edit
April 3, 2019 at 5:06 pm #1086620That worked … the http directive (“nosniff”) is gone … and that should have turned off the “strict Mime Type checking” … but in Firefox i still can’t open your site …
Some of the security options are going too far somewhere … i would go back to a standard setup and work from there … step by step adding plugins and server settings …
Did you try to disable all plugins (especially the security related ones)?
Who added those server configurations?Very difficult to debug this remotely without server access …
April 3, 2019 at 5:18 pm #1086625This reply has been marked as private.April 3, 2019 at 5:19 pm #1086626Ah … that was a local caching error from my site …
=> I can open the page now in Firefox, Firefox Inkognito, Chrome and Chrome Inkognito
Without that Apache nosniff-directive it seems to work now.
Can you confirm that from your end? (after deleting your whole browser-cache)April 3, 2019 at 5:20 pm #1086627W3TC is gone, Wordfence is gone, databases dropped for those in attempt to start over. Something has written to a file somewhere ??
(We have multiple other websites all with Enfold, and on the same server setup, but no problems…only this one website…)April 3, 2019 at 5:32 pm #1086634T-Mobile:
Mobile data on FF (normal browser) = yes
Mobile data on FF (incognito) = yes
Mobile data on Chrome (normal) = NO !!
Mobile data on Chrome (incognito) = yesWIFI
Mobile wifi FF normal = NO
Mobile wifi FF incognito = yes …wtfMobile wifi Chrome normal = yes
Mobile wifi Chrome incognito = yesPC all versions seems ok…for now….
April 3, 2019 at 5:33 pm #1086635The Site works now for me.
There must have been a configuration issue with W3TC, Wordfence or one of the server settings you may have removed.If you want to readd the nosniff-directive, you have to ensure that the server is sending the correct Mime-Types to the browser.
=> https://webplatform.github.io/docs/tutorials/configuring_mimetypes_on_the_server/——
Edit: Try deleting browser caches when you still have errors in some browsers … especially on mobile … a normal “refresh” is not enough on mobile, because it does rely more on caching data … may helpApril 3, 2019 at 7:59 pm #1086656Thanks for all the advice so far, it seems to be working, all b it limping along…
Firefox on Android using wifi still does not like it, styles will not load, or blank screen infinite loading
All others seem to be working as expected…
If this problem persists I will need you to check out cpanel configuration.
Another problem we just ran into is the “color section” with image background applied will hide content blocks within the color section…
April 3, 2019 at 8:08 pm #1086659Side note:
We found a possible error in the -head- section, everytime we update the theme there are stray code in the header / menu” />
<head> <meta charset="<?php bloginfo( 'charset' ); ?>" /> <?php /* * outputs a rel=follow or nofollow tag to circumvent google duplicate content for archives * located in framework/php/function-set-avia-frontend.php */ if (function_exists('avia_set_follow')) { echo avia_set_follow(); } ?> <!-- mobile setting --> <?php if( strpos($responsive, 'responsive') !== false ) echo '<meta name="viewport" content="width=device-width, initial-scale=1, maximum-scale=1">'; ?> <!-- Scripts/CSS and wp_head hook --> <?php /* Always have wp_head() just before the closing </head> * tag of your theme, or you will break many plugins, which * generally use this hook to add elements to <head> such * as styles, scripts, and meta tags. */ wp_head(); ?> </head>
April 4, 2019 at 10:59 am #1086971Just checked your HTML-header output … what are you doing there?
Why do you use a charset for Japanese?
Why don’t you have a title-tag?
What are all those Meta-tags for … you really don’t need them …
Your header-HTML is wrong somewhere: “Error: Stray end tag head.”=> Use the W3C-Validator (https://validator.w3.org/), check your page and solve all those errors.
Sorry … you experiment too much with unnessecary things (e.g. plugins, server settings) … so you have to deal with the results yourself … this is obviously not related to Enfold.
I am out.
April 4, 2019 at 4:37 pm #1087127We add certain meta tags for SEO purposes, and for website ownership validation with Google, Bing & Pinterest.
Your reference to charset makes no sense to me, as that is part of theme head code by default: line 3
<meta http-equiv="Content-Type" content="text/html; charset=euc-jp">
Here is the hook for that line of code from theme source files:
<head> <meta charset="<?php bloginfo( 'charset' ); ?>" />
So if this is something people who purchase this theme need to change, I suggest the developer (or team) make update to the template for US versions, or whatever, but WE did NOT add that line of code, it came with the theme. If it’s not part of the theme we don’t know how it got there…
Title tag: line 21
<!-- Scripts/CSS and wp_head hook --> <title>Your Pool Builder | Swimming Pool Design & Construction Consulting</title>
None of the other meta tags should have any adverse effects on the rendering of the theme, and although you feel are uneeded, our Google results are improved significantly by having these. There is large debate whether to include meta for keywords, author, because most people think that Google ignores them, however, not the case and also Bing does consider these tags.
The stray end tag was mentioned in my previous reply as possible issue in theme source code:
<head> <meta charset="<?php bloginfo( 'charset' ); ?>" />
Where as this “/> is possibly the problem you see, I have removed it, otherwise theme header & top bar will not render correctly.
April 4, 2019 at 4:43 pm #1087130We will be removing the GEO meta tags from header, but the reason for having this was because the company was previously only operating in one state, Texas, but now is a national brand.
April 4, 2019 at 5:00 pm #1087134Ok…. so I manually adjusted the charset on line 3
<head> <meta charset="UTF-8" />
But when looking at the new source code, it still showing this
<head><meta http-equiv="Content-Type" content="text/html; charset=euc-jp">
Which is reference to theme source file here<head> <meta charset="<?php bloginfo( 'charset' ); ?>" />
So I am not sure how to change this correctly…
April 4, 2019 at 5:11 pm #1087137This line of code keeps writing to the header.php each time that I delete it !
<meta http-equiv="Content-Type" content="text/html; charset=euc-jp">
I m trying to put this in place of
<meta charset="UTF-8" />
But every time I do the file updates with the meta tag above. Is the server writing this to the file?
We are on Apache VPS, could there be an update to htaccess we need to make for UTF-8 content-type response ???
- This reply was modified 5 years, 8 months ago by Mike.
April 4, 2019 at 5:23 pm #1087143That Meta-entry is not from the themes header-file. The theme is setting a meta-CHARSET … and that’s a meta-HTTP-EQUIV.
Also you don’t have to overwrite the theme one manually, because the output-variable comes from the WordPress-setting of you page: bloginfo( ‘charset’ )One of your plugins is adding that meta-http-equiv with wrong parameters. Maybe Yoast-SEO has wrong language-settings.
The Google-validation can be made with a DNS-entry … no need to send it with every request in every html-output. Bing and Pinterest probably too have other options.
We are on Apache VPS, could there be an update to htaccess we need to make for UTF-8 content-type response ???
No … it’s in the HTML-output … not in the HTTP-response … obviously it’s not server/apache related.
April 4, 2019 at 6:28 pm #1087164Header.php is now in default version 4.5.5 & all plugins disabled – I am now seeing the correct <meta charset=”UTF-8″ />
I will now try activating plugins one by one.
It seems that when I add my own <head> edits it is causing this to happen? In this case, at what line should we add our custom code to the header.php file?- This reply was modified 5 years, 8 months ago by Mike.
April 4, 2019 at 7:10 pm #1087171I can not figure this out. I put my custom tags just before the </head> and every time I do , the <meta charset=”<?php bloginfo( ‘charset’ ); ?>” /> continues to change to meta-http-equiv
I have no idea, but maybe it is to do with my meta tags & google analytics script.
I have taken all your other advice, expect for the tags that do not offer a directory file for validation (like Pinterest), we will keep the author, keywords meta tags and the analytics tracking script for obvious reasons, but the charset-euc-jp is something we can’t seem to get rid of.
How much of a problem is this?
April 5, 2019 at 11:00 am #1087423It’s not a totally big problem … but indicates that there is something strange happening.
Maybe i am too serious about things like that … :-)As a side note: Those meta-information, like meta-keywords for example, are of no interest for Google. It’s been years now that Google doesn’t use the meta-keywords for ranking. Google is only interested in things the visitor can see.
In my personal opinion SEO-plugins like Yoast aren’t of any use any more. But would go too far to discuss this topic in this already heavy thread … :-)Have a nice weekend.
-
AuthorPosts
- You must be logged in to reply to this topic.