Can't see new added custom blocks until refreshing


We are developing new blocks in application/blocks. When we edit a page and add any of these blocks in a new page, it's not possible to see them until refreshing the page with F5. This doesn't happen with concrete5 blocks, but we cannot see any difference in their code.

Any help would be welcome.

Thanks in advance,

Juan Ramón

9-sep-2020 Update:
I forgot to say that our Concrete5 version is 8.3.2.
I allso forgot to mention that the problem also happens when editing one of our custom blocks: changes don't show until refreshing the page.

View Replies:
PineCreativeLabs replied on at Permalink Reply
You may need to check your cache settings. In the dashboard, go to: /system/optimization/cache. If your Block Cache is set to "on", turn it off so you'll be able to immediately see changes during development.

Hope this helps.
jrsanche replied on at Permalink Reply
Thanks for your answer, PineCreativeLabs. My block cache was already off, so it seems that block cache is not the problem.

I keep on asking myself why the problem doesn't happen with the original concrete blocks but only with our custom ones.
JohntheFish replied on at Permalink Reply
Check the browser developer console for errors on saving - before you refresh. If you are overwhelmed with information there, filter the Network tab to look at XHR then at Doc.

The error will likely be in generating a new view() after save() has completed.
jrsanche replied on at Permalink Reply
Thanks for the hint. I've checked the console, and I've seen a 500 error trying to get this URL:

Which seems to be the one responsible for the rendering of the area in which the block was added.

The error message is:

Call to undefined method Concrete\\Controller\\Backend\\Block::getRequestActionParameters()

This getRequestActionParameters() is called in the block's view() method.

This happens when I save the block changes. After that, if I reload the page (still in edit mode) I don't get this 500 error and the block shows in the area. I don't understand why.
Gondwana replied on at Permalink Reply
I may be entirely wrong, but there seems to be a non-ASCII character in that link, which may be escaped in some circumstances.