CRITICAL: Version 0.9.2.5 Breaks Source Code & Headers On WordPress

  • After upgrading I noticed that there are problems with the source cod. This is critical as search engines should see the entire source. When 0.9.2.5 is activated this happens. It does not happen with 0.9.2.4. I was able to discover this by using the facebook linter as facebook shares began to populate with weird characters during sharing. I confirmed the issue in Google webmaster tools by viewing a page as the Googlebot. I’ve deactivated the plugin until a fix can be found. I would downgrade but that causes problems with inconsistent versions between phpbb and WordPress. Hope this information helps.

    THIS IS CRITICAL AS SEARCH ENGINES WILL NOT INDEX OR WILL DROP PAGES THAT DON’T DISPLAY SOURCE CODE & TEXT THEY CAN PARSE.

    0.9.2.5 Looks like this:

    [That’s way too much code to paste here – please use the pastebin – https://pastebin.com/ ; not using code buttons also means your code gets corrupted by the forum’s parser ]

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author jhong

    (@jhong)

    Hi,

    Can you give me an indication of what is broken in your page source?

    I don’t need to see the source of the whole page — just the part that you think has changed since the previous version.

    You may well find that you have introduced the bug yourself when updating phpBB — perhaps by saving the phpBB files incorrectly (they should be saved as UTF-8 without a byte-order marker.

    Also, please let me know which page(s) this happens on — I’m not sure if you are referring to the forum or the blog portion of your site.

    Thread Starter mykkal

    (@mykkal)

    Hi there, everything is UTF-8. I uploaded the files as is. The problem presented itself after an automatic update using wordpress.

    I then recopied the files manually. I posted the full code on your forum after wordpress would not accept the code here. Here is the link: https://www.wp-united.com/viewtopic.php?f=15&t=3756

    This is what the HTML source code looked like after the upgrade: 

    <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "https://www.w3.org/TR/REC-html40/loose.dtd">
<html>
<head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head>
<body><p>?</p></body>
</html>

    And of course now its normal. This is what it looks like before the upgrade and after I deactivated the plugin.

    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="https://www.w3.org/1999/xhtml" lang="en-US">
<head profile="https://gmpg.org/xfn/11">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta http-equiv="X-UA-Compatible" content="IE=Edge">
<title>Why Jay-Z Is Willing To Divest Ownership Share of Nets & Become NBA Agent ? Rasha Entertainment | Rasha Entertainment</title>
<link rel="pingback" href="https://rashaentertainment.com/xmlrpc.php">
<link rel="alternate" type="application/rss+xml" title="Rasha Entertainment ? Feed" href="https://rashaentertainment.com/feed/">
<link rel="alternate" type="application/rss+xml" title="Rasha Entertainment ? Comments Feed" href="https://rashaentertainment.com/comments/feed/">

    I really like the plugin… its very much a help to the community. As soon as this bug is fixed I want to reactive as I have to create accounts manually for wordpress contributors now.

    The blog is https://rashaentertainment.com and the forum is https://forum.rashaentertainment.com

    Thread Starter mykkal

    (@mykkal)

    Did that help?

    Thread Starter mykkal

    (@mykkal)

    I tried downloading and uploading the plugin again. Still had the same issue. Older version works fine though.

    Would it be possible that you make this a priority? If you need to test again our blog that would be fine.

    Thread Starter mykkal

    (@mykkal)

    [Please stop posting in uppercase & shouting at us. Post de-capped.]

    Can I get an update or resolution please? I just reported a bug to you that affects all wordpress 3.5.1 users. I reproduced it myself.

    We cannot use the forum right now. This is killing my stats on the web. Is anything being done?

    Thread Starter mykkal

    (@mykkal)

    DO YOU PLAN TO CONTACT US ABOUT THIS?

    Thread Starter mykkal

    (@mykkal)

    Still broken, does the plugin author think he could reply?

    Hi Mykkal,
    I see you are in a hurry and not getting replies.
    I would like to recommend you to post your issue on wp-united.com
    It is a official support forum for WP-United and there are a lot of guys discussing issues and customizations.
    Maybe you can try there to get solution faster…
    Regards
    Uros

    Thread Starter mykkal

    (@mykkal)

    I posted there before here. The plugin author asked one question and disappeared.

    I’ve noticed that in a lot of the support threads. Doesn’t seem like he normally comes up with the solutions… Just the community.

    Plus this is a critical bug affecting anyone using W3tc filesystem caching. Some bug is inserting weird characters into the HTML the search engines see causing them to drop sites from the search results.

    You can only see this in the facebook linter or Google Webmaster. Viewing the source in a web browser looks normal. So…basically most people don’t know anything is amiss until search engine traffic slows down

    Plugin Author jhong

    (@jhong)

    Hi,

    Sorry for the delay. On the contrary I’m usually quick to respond to support requests, but this is a difficult, busy time.

    It looks to me like you have gzip turned on in phpBB but WordPress or your server is further gzipping content, leaving the forum content to be double-gzipped.

    Try disabling gzip in phpBB, see if it helps.

    Thread Starter mykkal

    (@mykkal)

    Hi Jhong, that doesn’t work. The code that the SEO engines pull from the site is still foul. See below.

    HTTP/1.1 200 OK
Cache-Control: max-age=599809, public
Connection: Keep-Alive
Date: Sat, 27 Apr 2013 18:49:27 GMT
Keep-Alive: timeout=1, max=100
Pragma: public
Content-Length: 15310
Content-Type: text/html; charset=UTF-8
Content-Encoding: gzip
Expires: Sat, 04 May 2013 17:26:17 GMT
Last-Modified: Sat, 27 Apr 2013 17:26:17 GMT
Accept-Ranges: bytes
ETag: "3bce-4db5af2fc4040"
Server: Apache
Vary: Accept-Encoding,Cookie
X-Pingback: https://rashaentertainment.com/xmlrpc.php
X-Powered-By: W3 Total Cache/0.9.2.9

??}?r9??1?????4?x?]???V?o+??s??PY YR???P%??8??a_?D????
?6?'?%????DJ?=??gZ$Q@"3?Hd&??'???N????G???y???+???^?????????sV3??$
?NT??,?B????Je8??釽??q?
????jjc?]????M??j?zbk
????lX
????
?3~>)??~/i??s?+?????g?n[v?-???u\???
?uz??*?Vd?os?#?a??;?[?=?????XG??*D?*? ???B????O?????W??c?V??,??????3?#'r???%?;?Zad9?*??p:??c

    It looks like I can’t use W3tc with regular page. And its hard to mix caching plugins. With opcode caching everyhing is fine. With page cache disabled everything is fine. As soon as I turn page caching on things break.

    Please gix this. The issue seems to be it is not generating this information if a UTF-8 char set. If I disable WP-United every part of W3TC cache works.

    Also noticed people cannot use BBCode on the forum anymore. This is crippling.

    Thread Starter mykkal

    (@mykkal)

    You are right tho… the compression was the problem. If I turn off http compression in w3tc everything seems to work. But thats a big drop in pagespeed.

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘CRITICAL: Version 0.9.2.5 Breaks Source Code & Headers On WordPress’ is closed to new replies.