[wp-meta] [Making WordPress.org] #3003: Tagregator - Twitter resets settings randomly

[Making WordPress.org]

#3003: Tagregator - Twitter resets settings randomly
-------------------------------------+------------------
 Reporter:  xkon                     |       Owner:
     Type:  defect                   |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:  needs-patch              |
-------------------------------------+------------------
Description changed by SergeyBiryukov:

Old description:

> Hello,
>
> While I was working on these tickets:
> https://meta.trac.wordpress.org/ticket/2100 and
> https://meta.trac.wordpress.org/ticket/2907
>
> I've noticed that my error log was getting grumpy and I saw this error:
>
> `[22-Jul-2017 11:26:20 UTC] PHP Notice:  Undefined index: consumer_key in
> tggr-source-twitter.php on line 152`
>
> For some reason when you view the results page on the front end the
> twitter module bugs out randomly ( not all times ) and after that php
> error all the settings are getting reset so you are losing all login
> information etc.
>
> I haven't been able to find out why.
>
> @dipeshkakadiya is on it for a solution so we can implement it on gwtd3
> new website as well.
>
> Pointers for devs:
> Grab the /trunk of Tagregator through svn, apply the extra patches to
> have the latest as they have not been implemented yet and then work on
> this ticket.

New description:

 Hello,

 While I was working on these tickets: #2100 and #2907

 I've noticed that my error log was getting grumpy and I saw this error:

 `[22-Jul-2017 11:26:20 UTC] PHP Notice:  Undefined index: consumer_key in
 tggr-source-twitter.php on line 152`

 For some reason when you view the results page on the front end the
 twitter module bugs out randomly ( not all times ) and after that php
 error all the settings are getting reset so you are losing all login
 information etc.

 I haven't been able to find out why.

 @dipeshkakadiya is on it for a solution so we can implement it on gwtd3
 new website as well.

 Pointers for devs:
 Grab the /trunk of Tagregator through svn, apply the extra patches to have
 the latest as they have not been implemented yet and then work on this
 ticket.

--

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/3003#comment:1>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org