Forum Activity for @tig

TiG
@tig
10/01/17 05:18:33PM
184 posts

Odd Problems
Jamroom Developers

@brian

So much for that hypothesis.

Do not see the problem in blogs (at least could not recreate). There are no jrDiscussion overrides in the code base so the jrDiscussion is pristine (in code) but there are some template overrides (ancient) for jrDiscussion. Ignoring those.

A listener that sporadically removes items from $_data is of course possible, but for some odd reason it would have decided to start this nasty business last night on its own. The missing data though is not the key concern since it does not affect the database processing - the logic does assemble the comment with or without those items (verified).

The key problem is that we started dropping comments last night after the Beta was created and after an entire day of searching do not have clue one as to why they are processed without error through the code yet do not wind up being committed. We are sporadically (it seems) not committing comments to the database. I wish we had changes to back out but the site has been working fine.

Something is preventing select comments from being committed to the db without triggering any error conditions (at least none I can find).
updated by @tig: 10/01/17 05:20:21PM
TiG
@tig
10/01/17 04:49:01PM
184 posts

Odd Problems
Jamroom Developers

@brian

Note that no changes have been made to Beta; so no hardcoding there by definition. As for production I unfortunately do not know the history, but I doubt anyone would have hard-coded a tie to a site prefixed with 'beta'.

We are users of threaded comments too and have been happily using them for a very long time. I do not think this is related to code - it seems environmental to me (but I do not have the tools to go beyond the sense).

I have checked the listener (which has also been running just fine) and am out of ideas on that. (I wish it were that easy.)

I believe the problem is only on discussions but I can check that. Given these have been working and we have not changed them, I do not expect I will find anything of value. But our key concern is that comments are not being committed to the database 100% of the time. They are being processed (I have traced this through the code) without error, the SQL Insert is executed, the returns all execute as if everything is fine but the comment is not actually stored in the database. It makes me think we are getting hidden time-outs that are not caught. I have no other reasonable speculation for how a seemingly clean posting of a comment can work through the layers of code with no error conditions triggering and all returns occurring yet the comment never actually was committed.
TiG
@tig
10/01/17 04:29:02PM
184 posts

Odd Problems
Jamroom Developers

@brian

Yes. Did the same thing I did to create our alpha site. Used the hosting dashboard to create a new domain named Beta. That is all. No file transfers or anything. I just logged in for the first time and went to the databases. They are the standard, initial databases.

So Beta is simply created. It has had no activity and I never even got to the point of downloading the files locally with PHPStorm. That is, nothing was ever done with Beta.

I would not even bring this up except it is literally the only change we have made to the site in the last few days. And soon after Beta was created strange things started happening in production. I could not begin to explain this.
TiG
@tig
10/01/17 04:16:59PM
184 posts

Odd Problems
Jamroom Developers

@brian

Will check on that, but note that the Beta site is virgin. I simply created the new name and ran the initialization. Never even signed on to it because attention turned to the comments on production. No files uploaded, nothing configured.
TiG
@tig
10/01/17 04:15:19PM
184 posts

Odd Problems
Jamroom Developers

@brian

Just ran another test on the same comment. Note that the info this time came through:

(2017-10-01T19:13:21-04:00.0.23415500 : 0.137)-(mem: 2MB)-(pid: 21816)-(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>This is a reply to comment 2.1</p>
    [comment_thread_id] => 548368
    [comment_parent_id] => 548440
    [comment_thread_level] => 2
    [comment_item_title] => Sophistry
    [_profile_id] => 112
    [_created] => UNIX_TIMESTAMP()
    [_updated] => UNIX_TIMESTAMP()
    [_user_id] => 111
    [comment_hier_id] => 2.1.1
    [comment_hier_count] => 0
)
TiG
@tig
10/01/17 04:10:23PM
184 posts

Odd Problems
Jamroom Developers

@brian

The first item is not the first comment. I typed it in myself in reply to comment '2.1' which in addition to its numbering, is visibly indented on the UI and has referback info to its parent (comment 2). Threading is certainly on because the differences are sporadic, the code being executed depends on threading being on and I verified that threading is on. :)

Strange things are happening (database-centric) today and none of it (yet) makes sense from a code perspective. The only change was the creation of a new domain for Beta testing and soon after things started getting weird on the production site.
TiG
@tig
10/01/17 03:52:35PM
184 posts

Odd Problems
Jamroom Developers

@brian

Understood. The test case is not the first item. It is actually a reply to the second item (i.e. a reply to 2.1).

Note that the data is in the database - it just does not make it to $_data all the time.
TiG
@tig
10/01/17 03:38:10PM
184 posts

Odd Problems
Jamroom Developers

The above post 'Looking for Clues' is really from me.
TiG
@tig
09/20/17 09:20:06AM
184 posts

tinyMCE on Mobile Devices
Jamroom Developers

@michael

Thanks much for providing an unexpected solution.
TiG
@tig
09/19/17 09:56:06PM
184 posts

tinyMCE on Mobile Devices
Jamroom Developers

@michael

Okay so I could bracket the form generation logic only for blogs so that the function(s) thinks it is NOT on a mobile device (when it is). My task then is to find the tightest scope in which to make this happen.

I am not likely to do this, but your response is greatly helpful. Most of the time I ask questions just to avoid hours of research (on my part). That is what is so great about your forum, you guys are on the ball and are willing to share. Much appreciated!
  15