Total spitball, but are you saying that custom blocks got disabled? That sounds like it could be related to the new ability to disable blocks rather than removing them.
That's strange. Would you mind providing more details about how the home page was set up? If this is a bug with 1.22.0 it'd be great to try to fix it, but it'd be crucial to be able to reproduce the problem.
The blocks in the layout/template were de-activated. They are not 'custom' but I use 'layout-node' module for the front page. All other pages are fine.
I don't think the update intended to disable those. It's probably a bug or a regression. Would you be willing to open an issue in the Backdrop queue with detailed information on how to reproduce?
Using core I was not able to recreate the issue. There may be some bug with Layout Node module.
I installed a fresh 1.21.4 site, added a custom block to the home layout. Then upgraded to 1.22.0. My custom block was still visible. So seems to work fine with core. I suggest adding an issue to the Layout Node module project.
Thank you, Martin and Olaf! I had a feeling that there might be something out there already :)
I will check all three options (I will look at porting modules) and report back which one...
The Views Watchdog module for Backdrop "extends the Views module and allows to create custom lists of log entries". On Github, there is also a Wiki page with information about available fields,...
Posted4 days 19 hours ago by Olaf Grabienski (Olafski) on:
Hi Irina
I have often wondered this. I have had Log Filter on my list of possible migrations for a while; this uses a JS library to do the filtering. I notice on the project page of this...
Posted4 days 19 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Comments
Any errors in the log? Have you tried clearing caches?
Try downgrading. In the meantime, what are you using for your home page? A view? the Home layout? A node?
Thank you for the quick response
The problem was, that upgrade disabled the content of the blocks on the front page. Now enabled and all is fine.
But why???????
I use layout-node for overriding some backdrop problems. Wanted a custom front page.
Total spitball, but are you saying that custom blocks got disabled? That sounds like it could be related to the new ability to disable blocks rather than removing them.
Or are you saying nodes were unpublished?
That's strange. Would you mind providing more details about how the home page was set up? If this is a bug with 1.22.0 it'd be great to try to fix it, but it'd be crucial to be able to reproduce the problem.
The blocks in the layout/template were de-activated. They are not 'custom' but I use 'layout-node' module for the front page. All other pages are fine.
The site is: https://havredalzendo.dk/
No error.log
There should be at least a warning about this in the update instructions/notes.
I don't think the update intended to disable those. It's probably a bug or a regression. Would you be willing to open an issue in the Backdrop queue with detailed information on how to reproduce?
Issue created.
Using core I was not able to recreate the issue. There may be some bug with Layout Node module.
I installed a fresh 1.21.4 site, added a custom block to the home layout. Then upgraded to 1.22.0. My custom block was still visible. So seems to work fine with core. I suggest adding an issue to the Layout Node module project.
Herb, I was able to reproduce the problem and also found the causes for it. Updates on the queues:
https://github.com/backdrop/backdrop-issues/issues/5629
https://github.com/backdrop-contrib/layout_nodes/issues/13