Extended Express Detail Block Reverting to Previous Entry

Permalink
Hi All,

I'm having an issue on my c5 site where one specific block type reverts back to a previous state, after clearing the cache. It is a custom block, based on an extension of the Express Detail block. After clearing the cache, the block reverts back to a previously referenced express entry. The block has been removed and reinstalled, and replaced on 9 separate pages, and the behavior continues.

Any thoughts?

Thanks,
Ezra

View Replies:
MrKDilkington replied on at Permalink Reply
MrKDilkington
Hi newfieldslab,

To better answer your question, you'll need to offer more specific details about your custom block, how you are using it, and the data objects used with it.
newfieldslab replied on at Permalink Reply
Thanks for replying.

The site is using 8.3. It's URL ishttp://discovernewfields.org.

Towards the bottom of the homepage, under the heading "Coming Soon", is the block in question.

The block is pretty straightforward. It started as a cut and paste of the Express Entry Detail, shipped with Concrete5, modified to be a new "Event Card" block in the usual ways. The view.php displays the text content, links, and image reference stored as attributes on an express object. That's pretty much all there is to it.

Why would it be displaying properly for any length of time, until cache is cleared?

Multiple other blocks reference the same express object for their content, and do not show this issue. I might have to dig into that...

Thanks!
-E
MrKDilkington replied on at Permalink Reply
MrKDilkington
@newfieldslab

What are your Express Entry Detail block form settings?
newfieldslab replied on at Permalink Reply 1 Attachment
@MrKDilkington

I have attached the offending, "Event Card" blocks's form.php file.

I believed the form was an extension of original express_entry_detail/form.php, but now I see that such a file does not exist in the generic block.

Thank you for your input!
-Ezra
newfieldslab replied on at Permalink Reply 1 Attachment
@MrKDilkington

Upon further review, I'm not sure I understand what you're referring to. Do you mean the "Advanced Block Settings"? If so please see attached. I've tried various combinations from all off, to all on.

To further the mystery, every time I save the "Advanced Block Settings", whether making a change or not, the block reverts back to displaying a different Express Entry... It's aways the same Entry.

Any suggestions would be helpful.

Thanks!
-E
MrKDilkington replied on at Permalink Reply
MrKDilkington
@newfieldslab

By block form settings, I am referring to the add/edit/form modal dialog for the Express Entry Detail block.

Just to clarify, the custom block is a copy of the core Express Entry Detail block with two extra fields added (a checkbox for displaying ticket prices and a text input for a title)?

What are your concrete5 site cache settings?

Are you using any additional server caching?
newfieldslab replied on at Permalink Reply 1 Attachment
@MrKDilkington
Thanks again.

I've attached an image of the Add/Edit/Form modal.

You are correct, it is a copy of the Core Express object with an addition of two additional fields (text and booloan/checkbox), and a custom view.php.

The site cache settings are:
Block Cache
On - Helps speed up a live site.
Theme CSS Cache
On - Helps speed up a live site.
Compress LESS Output
On - Helps speed up a live site.
CSS and JavaScript Cache
On - Helps speed up a live site.
Overrides Cache
On - Helps speed up a live site.
Full Page Caching
On - In all cases.
Expire Pages from the Cache
Every 5 minutes.

We are also running server-side caching via Google PageSpeed Module.

Hope that helps a bit,
Ezra
newfieldslab replied on at Permalink Reply
@MrKDilkington

Are there any know issues with Google PageSpeed and Concrete5 I should be looking into? In this particular case, clearing the server cache does not fix the block Entry reversion.

Regarding the issue of this one specific block reverting back to display details from a previously selected Entry, I was wondering if it could be an issue in database?

Thanks!
-Ezra
MrKDilkington replied on at Permalink Reply
MrKDilkington
@newfieldslab

I have never used Google PageSpeed with concrete5, so I am not sure if there are potential issues.

I was unable to reproduce this issue using concrete5 full page caching.

You might try asking about this in Slack #general where others might have encountered this.
https://www.concrete5.org/slack...

Do you have the same issue if you use the default core block without the form modifications?
newfieldslab replied on at Permalink Reply
@MrKDilkington

Thanks again for your help. I'll float it out on the slack channel and see if anybody else has any experience with PageSpeed.

Re: same issue with default core block: I cannot recreate the issue on the core block. In fact we have built out multiple blocks from the core block this way, and this one is the only one presenting the issue.... There might be a hint there I can look into.

Thanks!
-Ezra
newfieldslab replied on at Permalink Reply
@MrKDilkington

It was PageSpeed_Mod all along. Once that was disabled, the following steps fixed the issue:
1. Cleared cached
2. Saw block revert to display old entry details
3. Deleted block
4. Added new block instance with new entry
5. Published page
6. Cleared cache
7. Block did not revert.

Thanks again!
-Ezra