Documents Tab on Person Profile Showing Error Page Context Entity Has Not Been Configured

[ChristineBema]

Description

The core Documents block is occasionally showing this error on version 15.2. You can cause it by going in and changing the Document Types in the block settings.

Actual Behavior

Sometimes when going to the Documents tab on a person's profile, this message appears: The page context entity has not been configured for this block. Go to Page Properties and click Advanced and enter a valid parameter name under 'Context Parameters', even though the Context Parameter on the page properties is PersonId. This should not throw an error. Sometimes the documents show, like when you clear out all the Document Types allowed in the block and fill them back in, but then the error comes back.

Expected Behavior

All the documents should show because the Context Parameter on the page, PersonId, is correct.

Steps to Reproduce

1. Go to a 15.2 system. Cannot reproduce on demo site.
2. Do to the documents tab on someone's profile.
3. If the error isn't already there, change the document types allowed.
4. Refresh the page. The error should be there now.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug or enhancement is already reported.
• Try to reproduce the problem on a fresh install or on the demo site.

Rock Version

15.2

Client Culture Setting

en-US

[leahjennings]

I'm so glad you submitted this! We are running v16.0 and have this happen intermittently. It's happened a total of 3x since upgrading. To "fix" it, I will change the document types allowed. The error disappears for a bit, and then someone will report that it's back. Haven't been able to dig into what is triggering it to occur on v16.

[Koriganp]

I can also confirm this is occurring on our instance, also 15.2. The Documents tab on the Person Profile pages is saying that I am missing a Context Parameter (which I am not) and as soon as I populate the Document Types with one or many, or remove one or many, it resolves itself, but the issue reemerges in five minutes or so.

[chead4]

Thank you all for commenting on the issue. Although I haven't been able to recreate on v15.2 or v16.0 we will continue to investigate. If the issue occurs again, please include a screenshot that includes the url.

[ChristineBema]

The URL looks like this: https://rock.pinelake.org/person/132503/persondocs. Make sure to refresh the page a few times after changing the document type parameters. I'm seeing it with three different churches on 15.2.

[leahjennings]

We are running Fluid on v16.0.

I just checked, and it "slipped" back to doing it again. Here's a screenshot of the page with the URL I last "fixed" this around 3PM ET today.

Page Properties > Basic Settings:

Page Properties > Display Settings:

Page Properties > Advanced Settings:

Here's a GIF that shows how I "fix" it. I have not yet figured out how to recreate it, I only know when one of our ministers lets me know.

[mijobryco]

I've experienced the same behavior as above. I removed the Entity Type and Re-added. I am not able to consistently recreate the issue. When adding/removing the Document Types, it appeared to fix the issue but then randomly return. It hasn't however returned since removing and re-adding the Entity Type, at least for me so far.

[ChristineBema]

Thanks for that idea! I'll try it and see if it works.

[mijobryco]

Just reoccured for me so I guess it isn't the fix, sorry ChristineBema

[Koriganp]

I found that doing any change to the block and saving it causes it to work again. (i.e. changing the "Show Security Button" form yes to no, adding or removing one or all Document Types, renaming it). Not sure if that helps.

[chead4]

I was able to recreate it today. Thank you all for the feedback.

[nairdo]

TL;DR
We believe we've fixed this bug, but please let us know if you see it happen again after updating to v16.1.

Longer Story
We were able to capture some data while it was happening on the PreAlpha site and then applied a code change (live, on-the-fly) in order to fix what appeared to be the bug. (There was a clear condition†† that could cause this particular bug.) The simplified code change did fix it, and during the live testing we removed the fix and the problem re-appeared. That's good. We did that multiple times to verify this.

However, during testing... after adding a document, deleting a document and then putting the code back into the original state, we were unable to re-create the problem (as so many others above have also seen). Therefore that gives us a small amount of pause, since the state of the things [the "contexts"] seemed to look the same as when the bug was occurring. Nevertheless, the simplified code should make the condition†† not occur.

[JRichmond27]

@nairdo are you able to share what the clear condition is that causes this bug? Is it something that's avoidable?

We're still on 15.3, and this issue is happening very consistently for us. The only fix I've found is to edit the block settings, but then the problem comes back anywhere from a few minutes to a couple hours later.

[nairdo]

@JRichmond27 Sorry, I can only give you a technical answer... The condition that would cause this bug is if there are no items in the page's "context entity types" collection or if the 'required' context entity types are not in the page's context entity types collection.

The v15.4 alpha testing is almost over, but since the fix above is small enough, I'm going to see if we can get that into v15.4 too. If we can, we'll also label this issue with "Fixed in v15.4" too.

[JRichmond27]

@nairdo that's awesome, thank you!!!