WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Twitter Widget Pro problem (8 posts)

  1. LilAbhi
    Member
    Posted 2 years ago #

    I just set up Twitter Pro for my wordpress website using the weaver theme. I am getting the following msg in the primary widget area.

    Warning: preg_replace_callback() [function.preg-replace-callback]: Requires argument 2, 'wpTwitterWidget::_hashtagLink', to be a valid callback in C:\xampp\htdocs\wordpress\wp-content\plugins\twitter-widget-pro\wp-twitter-widget.php on line 342
    RSSFollow us on Twitter
    Inovex Inc
    
        good luck Inovex FC! 04:18:38 PM September 29, 2009 from web
    that is exactly what it is displaying.

    It shows the last tweet but also shows all of that error No idea why but it does. I have barely any luck getting answers on any forum because i can not show my website. Someone please help me i only have the rest of the week to finish this site.

  2. digitalsingularity
    Member
    Posted 2 years ago #

    I'm getting a similar problem. I'm on wordpress 3.2.1 and now running version 2.2.1 of the plugin. This wasn't a problem before this morning's upgrade of the plugin. :(

    I'm seeing:
    Warning: preg_replace_callback() [function.preg-replace-callback]: Requires argument 2, 'wpTwitterWidget::_hashtagLink', to be a valid callback in D:\Hosting\2103316\html\blog\wp-content\plugins\twitter-widget-pro\wp-twitter-widget.php on line 342

  3. LilAbhi
    Member
    Posted 2 years ago #

    I have not found a single thing to fix the problem. Did you find anything

  4. digitalsingularity
    Member
    Posted 2 years ago #

    Nope, haven't tried or found anything. I'm not a web developer, so I'm a little afraid to go mucking around in php code.

  5. LilAbhi
    Member
    Posted 2 years ago #

    Exact same problem with me. I am just a 16 year old co op student at a placement until the end of this month

  6. digitalsingularity
    Member
    Posted 2 years ago #

    Oh, looks like 2.2.2 just came out. That fixed the problem. Update your plugin, if you haven't already.

  7. LilAbhi
    Member
    Posted 2 years ago #

    wait which plugin are you using?

  8. LilAbhi
    Member
    Posted 2 years ago #

    wait nevermind just had to refresh the page its good

Topic Closed

This topic has been closed to new replies.

About this Topic