bswen
Forum Replies Created
-
Disregard. I found it. *slinks away*
Forum: Plugins
In reply to: [Official Bitly for WordPress] Undefined index errorWith debug mode on I am still seeing an Undefined index notice for every display of a post in a WordPress theme.
Forum: Plugins
In reply to: [Official Bitly for WordPress] Conflict with Yoast SEO pluginIf you look in the bitly.php file around line 90 there begins a series of checks to see if the call for get_permalink originates from certain plugins. You can simply add wordpress-seo to the list to fix the rel=cannonical issue.
At line 118 (after the check for ‘sitemap’ in line 113) I added this code to check to see if the call originates from a directory with the phrase ‘seo’ in it (which would include yoast’s wordpress-seo):
else if (strpos($b['file'],'seo') !== false) // Don't return custom links in yoast seo { $plugin_call = false; break; }This tells the bitly plugin to not override the get_permalink() function for wordpress-seo and makes the rel=canonical tag work properly again.
Forum: Plugins
In reply to: [Custom Post Type Permalinks] Serious conflict with Yoast SEO SitemapI am using version 0.9.3.2 and am not seeing this behavior with the latest version of WP SEO. It is working properly. We’ve got over 12,000 posts.
Maybe give it a try?
http://downloads.wp.xz.cn/plugin/custom-post-type-permalinks.0.9.3.2.zip
Wow, was banging my head on this one. Doing a print_r on the feed object shows them in the XML order, so the reordering by publication date is not even apparent there.
Thanks for posting, and, agreed, the fact that WP orders the feed by publication date should be made explicitly clear on the fecth_feed codex page.
Just to record the command found at stackexchange here:
/* specify the source feed */ $rss = fetch_feed('FEED_URL'); /* disable order by date */ $rss->enable_order_by_date(false);Forum: Plugins
In reply to: [BuddyPress Like] BuddyPress Like UpdateThanks Darren! Am watching this on GitHub.
Big +1 for adding notifications (activity updates for like is nice but can quickly clog the stream on an active site).
Installed an working here – happy to help test and provide feedback – where would you like that to happen?
For anyone else experiencing this, I had to revert to 0.8.7 to get back to my links without the standard post URL base. You’ll find it here: http://downloads.wp.xz.cn/plugin/custom-post-type-permalinks.0.8.7.zip
Hello,
After upgrading to 0.9.2 I am having the same issue as the original poster here and I do have the ‘with_front’ argument already set.
Here are the arguments for my audio content type:
$args = array( 'labels' => $labels, 'public' => true, 'publicly_queryable' => true, 'show_ui' => true, 'show_in_menu' => true, 'query_var' => true, 'rewrite' => array( 'slug' => 'audio', 'with_front' => 'false' ), 'capability_type' => 'post', 'has_archive' => true, 'hierarchical' => false, 'menu_position' => 7, 'taxonomies' => array('primarytopic','category', 'post_tag', 'states'), 'supports' => array( 'title', 'editor', 'author', 'thumbnail', 'excerpt', 'comments' ) );Yet my URLs for the custom content type all have the ‘article’ base on them used for the regular post type.
For instance this URL was:
http://rhrealitycheck.org/audio/2013/05/05/preachers-daughters-family-physicians-and-generation-roe/But after the 0.9.2 update the URL is now:
http://rhrealitycheck.org/article/reality-cast/2013/05/05/preachers-daughters-family-physicians-and-generation-roe/This is causing 404 errors from already existing links coming into my site… any help is much appreciated.
+1 for this functionality, and +1 for the appreciation, thanks Hector
Gotcha, that must be what happened.
No documents to be queued and no errors. I deployed the update to production first (bad practice, I know) and this behavior was happening there, too.
With the addition of the new fields, will all previously processed documents need to be resent to ACS, then? We have about 12,000 documents in the search instance, so perhaps it had not processed them all yet by the time the behavior was noticed and I reverted to 1.3.
The var dump has been added. Thanks for checking it out, let me know what else I can do.
Forum: Plugins
In reply to: [Lift: Search for WordPress] Pagination brokenIf I replace 14100654060 in the query string with 2 or 3, the correct page appears…
Seems that something, not sure what, is going wrong with the get_pagenum_link function to produce that number?
Forum: Plugins
In reply to: [Lift: Search for WordPress] Pagination broken$start is set to 14100654060 on line 55 of /api/cloud-search.php
Forum: Plugins
In reply to: [Lift: Search for WordPress] Pagination brokenHere’s the error produced when attempting to click on or to another page in search results pagination (http://rhrealitycheck.wpengine.com/page/1410065407/?s=rick+perry):
Fatal error: Uncaught exception 'CloudSearchAPIException' with message 'Start must be a positive integer' in /nas/wp/www/cluster-1455/rhrealitycheck/wp-content/plugins/lift-search/api/cloud-search.php:55 Stack trace: #0 /nas/wp/www/cluster-1455/rhrealitycheck/wp-content/plugins/lift-search/api/cloud-search.php(60): Cloud_Search_Query->__validate_start(14100654060) #1 /nas/wp/www/cluster-1455/rhrealitycheck/wp-content/plugins/lift-search/wp/lift-wp-search.php(109): Cloud_Search_Query->set_start(14100654060) #2 /nas/wp/www/cluster-1455/rhrealitycheck/wp-content/plugins/lift-search/wp/lift-wp-search.php(348): Lift_WP_Search::lift_search_query(Object(WP_Query)) #3 [internal function]: Lift_WP_Search::posts_results(NULL, Object(WP_Query)) #4 /nas/wp/www/cluster-1455/rhrealitycheck/wp-includes/plugin.php(230): call_user_func_array(Array, Array) #5 /nas/wp/www/cluster-1455/rhrealitycheck/wp-includes/query.php(2683): apply_filters_ref_array('posts_results', Array) #6 /nas/wp/www/cluster-1455/rhrealitycheck/wp-includes/query.php(2 in /nas/wp/www/cluster-1455/rhrealitycheck/wp-content/plugins/lift-search/api/cloud-search.php on line 55