search

bryantAXS / TGL_Twitter

EE Add-on that uses oAuth to display Twitter Feed
11 stars 8 forks source link

PHP error on first load #1

Open objectivehtml opened 12 years ago

objectivehtml commented 12 years ago

When I view a site for the first time on any device it results in a PHP error. Refreshing it fixes the issue. PHP error refers to the access_token index not being defined. Next time the error triggers, I will get the exact error code. I am sure it is an easy fix. I bet if I delete the cache and refresh, it will trigger the error again.

I just wanted to see if you know about this error before I fix it.

bryantAXS commented 12 years ago

Hmm, Off the top of my head I can't think of why that would happen. I haven't looked at that code in a while and it could be from some Instagram API changes that I haven't implemented. I should be able to take a look a little later in the week.

Thanks

Bryant

On Mon, Aug 13, 2012 at 7:47 AM, Justin Kimbrell notifications@github.comwrote:

When I view a site for the first time on any device it results in a PHP error. Refreshing it fixes the issue. PHP error refers to the access_token index not being defined. Next time the error triggers, I will get the exact error code. I am sure it is an easy fix. I bet if I delete the cache and refresh, it will trigger the error again.

I just wanted to see if you know about this error before I fix it.

— Reply to this email directly or view it on GitHubhttps://github.com/bryantAXS/TGL_Twitter/issues/1.

Bryant Hughes bryant@thegoodlab.com www.thegoodlab.com @thegoodlab http://www.twitter.com/thegoodlab

objectivehtml commented 12 years ago

I can confirm it was a result of having the Twitter code on the front end setup correctly, but not having a pin saved in the CP. There were no db records to represent the OAuth tokens. Issue fixed itself once the pin was saved correctly.

bryantAXS commented 12 years ago

ah gotcha, thanks for the update

On Mon, Aug 13, 2012 at 2:02 PM, Justin Kimbrell notifications@github.comwrote:

I can confirm it was a result of having the Twitter code on the front end setup correctly, but not having a pin saved in the CP. There were no db records to represent the OAuth tokens. Issue fixed itself once the pin was saved correctly.

— Reply to this email directly or view it on GitHubhttps://github.com/bryantAXS/TGL_Twitter/issues/1#issuecomment-7704006.

Bryant Hughes bryant@thegoodlab.com www.thegoodlab.com @thegoodlab http://www.twitter.com/thegoodlab