Have a db_create_item listener that has been working fine for weeks. Tracing a production problem and discovered that the listener is getting different information and it appears to be random. The information that is missing (on occasion) is that used for comment threading: comment_thread_id, comment_parent_id and comment_thread_level. The comment_module is jrDiscussion in all cases (of concern).
Threading is enabled, yet sometimes the information comes in $_data and sometimes not. This is new behavior. Here is an fdebug showing what I am talking about.
(2017-10-01T17:19:58-04:00.0.03866800 : 0.084)-(mem: 4MB)-(pid: 4244)-(ip: 75.132.107.114)-(user: TiG)-(uri: POST /comment/comment_save/__ajax=1)
Array
(
[comment_module] => jrDiscussion
[comment_item_id] => 34677
[comment_profile_id] => 2
[comment_text] => <p>placeholder</p>
[comment_item_title] => Sophistry
[_profile_id] => 112
[_created] => UNIX_TIMESTAMP()
[_updated] => UNIX_TIMESTAMP()
[_user_id] => 111
)
(2017-10-01T17:38:36-04:00.0.70442900 : 0.159)-(mem: 4MB)-(pid: 12868)-(ip: 69.253.152.39)-(user: xxxx)-(uri: POST /comment/comment_save/__ajax=1)
Array
(
[comment_module] => jrDiscussion
[comment_item_id] => 34686
[comment_profile_id] => 2
[comment_text] => <p>...</p>
[comment_thread_id] => 548517
[comment_parent_id] => 548598
[comment_thread_level] => 3
[comment_item_title] => Who is Carmen Yulin Cruz?
[_profile_id] => 11
[_created] => UNIX_TIMESTAMP()
[_updated] => UNIX_TIMESTAMP()
[_user_id] => 10
)
The data provided to the listener in these cases should be identically structured. The database does contain these items (verified).
So does anyone have any ideas on what might cause $_data to be populated differently? To sometimes not include the threading fields stored in the database?
updated by @perrie: 01/02/18 02:49:56PM
