| User | Post |
|---|
4:37 pm November 15, 2009 | AaronCampbell
| | | | Admin | posts 191 | |
| |
6:52 pm November 15, 2009 | derezzz@gmail.com
| | | | New Member | posts 2 | |
| | So I followed the instructions for installation, but i'm getting an error when I try to activate. It looks like this: Parse error: syntax error, unexpected T_STRING, expecting T_OLD_FUNCTION or T_FUNCTION or T_VAR or '}' in /home4/derezzzc/public_html/immybiggestfan/wp-content/plugins/twitter-widget-pro/wp-twitter-widget.php on line 36 can you help? thanks! |
|
7:08 pm November 15, 2009 | AaronCampbell
| | | | Admin | posts 191 | |
| | The plugin requires PHP 5 and you’re running PHP 4. Most hosts offer PHP5 but you probably have to enable it in your control panel, through .htaccess, or by asking them. Here is a link to some instructions to changing to PHP 5 for certain hosts, but if your host isn't there just open a support ticket and ask for PHP5: http://codex.wordpress.org/Swi…..ng_to_PHP5 | |
|
5:28 am November 18, 2009 | derezzz@gmail.com
| | | | New Member | posts 2 | |
| | Thanks for the assist. I thought that's what it might be and I've managed to upgrade. Now I have a different problem though. The tweets and everything were showing up just fine – now it seems it's not connecting to Twitter. My page only displays the symbol for RSS and the message I entered in case Twitter is down…except Twitter seems to be fine and not my actual tweets. Any advice? |
|
8:53 am November 18, 2009 | AaronCampbell
| | | | Admin | posts 191 | |
| | Unfortunately, there could be a few things that could cause this. - It could be a slow connection from your host to Twitter. The solution for this is to increase the number of seconds to wait for a response from Twitter (default is 2). Unfortunately, if you do this then if it's slow your page will load slowly too.
- You could be bordering on your maximum number of requests per hour with Twitter. If this is the case you'll need to cut back on access to the account through other methods. The widget only uses 12 requests per hour, but if you also use something like tweetdeck, seesmic desktop, mobile twitter apps, etc they all use requests as well.
- Twitter could be having problems. You can't do anything about this, but it sounds like Twitter was working fine.
- There could be a routing problem between your server and Twitter (and not between you and Twitter). Again, you can't do anything about this, but it resolves in time.
If these don't work, please post a link to your site. | |
|