Tom Goering
Forum Replies Created
-
Forum: Plugins
In reply to: [Jetpack - WP Security, Backup, Speed, & Growth] Remove the CSSNever mind. I reverted back to version 3.1.1 and all is good again.
Here is a good tool from Google to check how much things can slow down your pages for both mobile and full screen.
Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Okay, I have been trying to figure this out for myself. Here is the code I have made so far that places a rel=next and prev in the head. I place the following into the head and everything works except I can’t figure out how to declare what the last comment page is so that only a rel=”prev” link shows on that page. I have extracted the portion of the code that I can’t seem to get working… Any ideas?
<?php if ($cpage <1){ echo ('<link rel="next" href="'); echo esc_url(get_comments_pagenum_link()); echo('">');} elseif ($max_page && $cpage) {echo ('<link rel="prev" href="'); echo esc_url( get_comments_pagenum_link($cpage -1) ) ; echo('">');} elseif ($cpage) {echo ('<link rel="next" href="'); echo esc_url( get_comments_pagenum_link($cpage +1) ) ; echo('">'); echo ('<link rel="prev" href="'); echo esc_url( get_comments_pagenum_link($cpage -1) ) ; echo('">');}?>The problem code extracted from above:
elseif ($max_page && $cpage) {echo ('<link rel="prev" href="'); echo esc_url( get_comments_pagenum_link($cpage -1) ) ; echo('">');}Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Right, but I don’t have another option; I have to use comment pagination — I have some pages with well over 1000 comments; and the amount grows daily. The comments are the content, so in effect, each new comment page created is a new page of searchable/valuable content. What the rel=prev and rel=next tags in the <head> do is help the search engines realize that the attached pages are related and not duplicates.
from the link I provided for Google concerning the implementation, “[It is a] Hint to Google [about] the relationship between the component URLs of your series with rel=”next” and rel=”prev”. This helps us more accurately index your content and serve to users the most relevant page (commonly the first page). Implementation details below.”
For comment pagination, I think it is even more important to send the “hint” because those pages have a real shot at being considered duplicate. (I posted this question in the Google Webmaster Forum, and the rel=next and prev option is what was advised).
As the page says, they will always strive to try and figure out the relationships on their own, and ultimately, that may be my only option — I still love your plug-in because it has allowed my content to become more conversational which in turn has made it a valued resource to those seeking enlistment. Thanks!
Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Is something in the works? This is a major issue; I need to do something about the amount of duplicate content that Google’s Webmaster Tools is telling me I have.
Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Just checkin on progress, how is it coming? Is it possible?
Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Here is one of the many pages on my site that has a ton of comments — right now it’s at 56 pages of them. So, right now, Google thinks I have 56 duplicate titles, etc..
https://www.navycs.com/blogs/2009/09/17/navy-recruiting-medical-waiver-processForum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Right, and I took that down because it isn’t doing what it should be doing (according to the Google article I posted). What it should be doing is connecting the pages that are related — meaning, the first page would have a rel=”next” to the second page, and the second page would have a rel=”next” to the third and a re=”prev” to the previous (in this example, back to the first page), and so on — the last page (the last comment page in this example) would have just the rel=”prev” link back to the next to last page.
WordPress currently skips over the comment pages altogether.
Forum: Plugins
In reply to: [WP-Paginate] Love the Plugin, But…Actually, I was looking at the comments because that is what I use specifically, but I guess it should be an option for both.
Thanks!
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] Same Link 4 TimesThanks! It appears 4.2.2 works as advertised. ??
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] Same Link 4 TimesVersion with the issue was 4.2.1, and not version 4.1.2 (I reverted back to 4.1.2 and it works as before)
Forum: Plugins
In reply to: [YARPP - Yet Another Related Posts Plugin] Not workingSame here — same post link 4 times. Not good.
Forum: Plugins
In reply to: [SEO Title Tag] SEO Title Tag 3.4.1 not working properlyI reverted to Version 2.3.3, and it works perfectly.
Forum: Plugins
In reply to: [WP Super Cache] WP-Super-Cache: Served supercache file from PHPDoes anyone have mod_rewrite option of this plug-in working??
Forum: Plugins
In reply to: [WP Super Cache] WP-Super-Cache: Served supercache file from PHPI apologize for posting again, but while looking at both sites, https://inphotos.org/ and https://ocaoimh.ie — the sites Donncha contributes to according to the links in the admin portion of the plug-in — both return “WP-Super-Cache: Served supercache file from PHP” in the server header. I assume mod_rewrite is used as recommended on both of those blogs, but they both appear not to be serving pages as designed (according to the header). Are those sites returning the errors listed above as my site does? Am I missing something? Is there a bug, or am I the only one experiencing this issue? I would love to figure out how to get the mod_rewrite to work — Hostgator is at a loss, too.
Forum: Plugins
In reply to: [WP Super Cache] WP-Super-Cache: Served supercache file from PHPMy result of the Cache Tester:
Couldn’t resolve host ‘www.navycs.com’
Cache Tester
Test your cached website by clicking the test button below.
Fetching https://www.navycs.com/blogs/ to prime cache: OK
Fetching first copy of https://www.navycs.com/blogs/: FAILED
Fetching second copy of https://www.navycs.com/blogs/: FAILEDOne or more page requests failed:
The pages do not match! Timestamps differ or were not found!
My server header for a page in my blog:
HTTP/1.1 200 OK
Date: Tue, 06 Aug 2013 20:24:29 GMT
Server: Apache
X-Powered-By: PHP/5.3.27
Vary: Accept-Encoding,Cookie,User-Agent
Cache-Control: max-age=3, must-revalidate
WP-Super-Cache: Served supercache file from PHP
Content-Encoding: gzip
Content-Length: 5740
Keep-Alive: timeout=5, max=75
Connection: Keep-Alive
Content-Type: text/html; charset=UTF-8