[ielbury]

Changing the cache duration to 1 makes this problem reproduceable.

Added a print_r($tweet); before the if($tweet[‘text’]) and this is the result:

stdClass Object ( [created_at] => Wed Feb 12 02:01:22 +0000 2014 [id] => 433420533779402752 [id_str] => 433420533779402752 [text] => Twitter is Quietly Testing A New Version - Looks A Lot Like Facebook http://t.co/pmWTk6jKrU via @mashable [source] => Buffer [truncated] => [in_reply_to_status_id] => [in_reply_to_status_id_str] => [in_reply_to_user_id] => [in_reply_to_user_id_str] => [in_reply_to_screen_name] => [user] => stdClass Object ( [id] => 102263196 [id_str] => 102263196 ) [geo] => [coordinates] => [place] => [contributors] => [retweet_count] => 0 [favorite_count] => 0 [entities] => stdClass Object ( [hashtags] => Array ( ) [symbols] => Array ( ) [urls] => Array ( [0] => stdClass Object ( [url] => http://t.co/pmWTk6jKrU [expanded_url] => http://on.mash.to/1bnjwj7 [display_url] => on.mash.to/1bnjwj7 [indices] => Array ( [0] => 69 [1] => 91 ) ) ) [user_mentions] => Array ( [0] => stdClass Object ( [screen_name] => mashable [name] => Mashable [id] => 972651 [id_str] => 972651 [indices] => Array ( [0] => 96 [1] => 105 ) ) ) ) [favorited] => [retweeted] => [possibly_sensitive] => [lang] => en ) 
Fatal error: Cannot use object of type stdClass as array in /var/www/wp-content/themes/dante/swift-framework/sf-functions.php on line 200

If I change the cache duration back to the default, the tweet is returned as an array as such it works.

Hope this helps!

[ielbury]

FYI, I just remembered that the oAuth Twitter Feed plugin was updated to version 2.2 around the same time as the Dante 2.0 release.

I checked the support for the oAuth Twitter Feed plugin and there does not appear to be any support issues related to this issue in the 2.2 time frame but I could be wrong.

[ielbury]

I get this error as well except at line 198.

[Tue Feb 11 20:01:07.743069 2014] [:error] [pid 1614] [client 192.168.0.54:58161] PHP Fatal error: Cannot use object of type stdClass as array in /var/www/wp-content/themes/dante/swift-framework/sf-functions.php on line 198

In my case it looks like it happens after calling getTweets() and the cache containing the tweets has expired. It happens once then everything is Ok until the cache expires again.

This problem started after the 2.0 update. I am currently on 2.1.

Thanks, Ian

[ielbury]

Same problem for me. Portfolio pages all now full width.

[ielbury]

Hey Ed,

I do not think animated icon box makes sense on touch devices because people don’t go around touching things to find out if there are hidden gems under elements. This is a mouse metaphor IMO the hover event allows people to find the hidden gems.

If I were you, I would not spend time on this as it doesn’t make sense … hence my stuuupid comment 🙂

Cheers,
Ian

[ielbury]

@mworley, That was NOT intended to be a d!ck response. I apologize if it came across that way and it offended anyone! My brevity sometimes gets me in trouble.

I have been working with a non-technical person right now and I am trying to show her how to find this kind of stuff out for herself. My experience is that if people know of these little tricks and are self sufficient, they get a lot more satisfaction and are more productive. Most non-technical people would not even attempt to try this and they should IMHO. Using the inspector is useful far beyond just finding image sizes, it’s good for finding the sizes of text, parallaxes any element for that matter.

Anyways Happy Holidays to you @mworley!

[ielbury]

Forget this question … it is stuuuupid … another rat hole.

It does take too much trial and error to find these things out and then the regression to fix the places where you have used the metaphor. It would be nice if there were hints in the docs … maybe a wiki so the users could share their experiences?

The bottom line is the animated style does not work on IE or mobile devices! Pick one of the other styles as they work better on all devices/browsers.

[ielbury]

Hi Ed,

This is not your problem. Sorry for that!

After looking at the last post I realized that there needed to be a redirect as there was other content that was being referenced using http:. A quick Google and sure enough, I have to add a few more lines to my .htaccess.

I got the correct .htaccess entries from this post http://codex.buddypress.org/getting-started/htaccess-redirects-for-force_ssl_admin/

Thanks for the support!

[ielbury]

I think this problem is caused by some code somewhere being hardcoded with http scheme instead of looking at the current session’s scheme. i.e. http and https are being used when only https should be used.

If you try use the editor on IE, you get the message “Only secure content is displayed”. If you press “Show all content”, the page refreshes and the editor is now useable. When you use Chrome, there is no error and the editor is not functional.

I have attached a screen shot of the IE error message and how the editor looks when it fails and a shot of the Chrome console.

I have seen this problem on several sites where IE works but Chrome doesn’t. It’s unusual that IE works and Chrome doesn’t 🙂

I hope this helps you Ed?

Cheers,
Ian

[ielbury]

Problem solved in 1.2. No code changes required.

Thanks for the support.

[ielbury]

Thanks for the info @cvac01,

The toolkit was setup with the API key before but I started to have performance issues so deleted the plugin (Not sure why and did not try to diagnose).

My problem is I don’t have the toolkit installed and the new code does not deal with this gracefully as it is assuming that everyone will install the plugin. I am sure there are others that do not want to install the toolkit for a variety of reasons.

I prefer to only install plugins I need in order to reduce my security vulnerability surface area.

Cheers

[ielbury]

Hi Ed,

Unfortunately the site is behind a firewall right now. When I get some time, I will try and get you setup to diagnose this.

Thanks,
Ian

[ielbury]

I just looked at the original post and noticed the I wrote the wrong function and it should be sf_latest_tweet and not sf_get_tweets. My bad!

I still stand by my hypothesis that the arguments are backwards.

[ielbury]

I changed the code in widget-twitter.php by reversing the arguments to make it work.

With your standard code, if I enter a count of 5, I get the tweets for @5.

I know that someone else in this forum has this same issue and it was related to a lower level api function signature change. When they changed the signature, they made it backwards compatible by checking for an int or string for the count. In this case, the check is broken when the count is passed in 1 versus ‘1’.

I suspect that depending on where the count comes from and if it’s converted to a proper int, it’s broken but in other places it’s not. Gotta love dynamic languages 🙂

[ielbury]

@cvac01, I am not sure if this is your problem, but the Twitter oAuth plugin requires the PHP cURL module installed and activated.

It looks like you are on a Linux box, for Ubuntu:

sudo apt-get install php5-curl
sudo service apache2 restart

Ed, I know that it was in the docs by way of a referenced article. It might make things easier for newbies like me If this requirement was highlighted as a point.

Cheers,
Ian