Title: Pulling in wrong URL
Last modified: August 20, 2016

---

# Pulling in wrong URL

 *  Resolved [schmidty54](https://wordpress.org/support/users/schmidty54/)
 * (@schmidty54)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/)
 * [http://www.kenshoo.com/testimonials](http://www.kenshoo.com/testimonials) using
   3.5.1
 * I’ve manually inserted the tag twice in my template. At the top of the page WPSocialite
   pulls in the correct URL. In the footer.php WPSocialite pulls in an incorrect
   URL. It’s only happening on this page, and it could have something to do with
   the query I’m running. I’m pulling in a bunch of custom post types and displaying
   them in an
    - . The content from these custom post types are the only content on the page.
      It just happens that WPSocialite in the footer.php is pulling in the URL and
      meta details from the very last custom post type on the page (HomeAway).
 * Any ideas?
 * [http://wordpress.org/extend/plugins/wpsocialite/](http://wordpress.org/extend/plugins/wpsocialite/)

Viewing 5 replies - 1 through 5 (of 5 total)

 *  Plugin Author [Tom Morton](https://wordpress.org/support/users/tm3909/)
 * (@tm3909)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3558958)
 * schmidty54,
 * It looks like you are correct, actually. If this is a custom post loop then my
   suggestion would be to use `wp_reset_query()` (more information [here](http://codex.wordpress.org/Function_Reference/wp_reset_query))
 * If that doesn’t work, use pastebin or gist.github.com and link me to the actual
   code of the page so I can investigate further.
 *  Thread Starter [schmidty54](https://wordpress.org/support/users/schmidty54/)
 * (@schmidty54)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3559056)
 * Thanks Tom.
 * Sorry to do this to you 🙂
    [http://pastebin.com/U0a0Y4gx](http://pastebin.com/U0a0Y4gx)
 *  Plugin Author [Tom Morton](https://wordpress.org/support/users/tm3909/)
 * (@tm3909)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3559057)
 * Don’t be sorry, this actually gave me better insight to what you are doing.
 * Lets try this: If you use the following code in the footer, it will override 
   the global WPSocialite settings, allowing you to define your own URL. If you 
   want wpsocialite to share the page, for example, you can use this:
 *     ```
       <?php
       $args = array(
           'url' => get_bloginfo('url').'/testimonials/'
       );
       wpsocialite_markup( $args );
       ?>
       ```
   
 * I can’t test the above code currently (out of the office) but it should work.
   Give it a try and let me know if it accomplishes what you need.
 *  Thread Starter [schmidty54](https://wordpress.org/support/users/schmidty54/)
 * (@schmidty54)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3559179)
 * Tom, that worked! Thank you so much!
 *  Plugin Author [Tom Morton](https://wordpress.org/support/users/tm3909/)
 * (@tm3909)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3559180)
 * Glad to hear it!

Viewing 5 replies - 1 through 5 (of 5 total)

The topic ‘Pulling in wrong URL’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/wpsocialite_f8f8f8.svg)
 * [WPSocialite](https://wordpress.org/plugins/wpsocialite/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/wpsocialite/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/wpsocialite/)
 * [Active Topics](https://wordpress.org/support/plugin/wpsocialite/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/wpsocialite/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/wpsocialite/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [Tom Morton](https://wordpress.org/support/users/tm3909/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/pulling-in-wrong-url/#post-3559180)
 * Status: resolved