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.
As I work through things I flush the caches after every change I make.
As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
If you haven't already, flush all the caches.
If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
Posted3 days 3 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
... had a status of '0' that I changed to '1' directly in th edb, in line with other custom modules
Awful idea! That's not how modules get installed! The number in db...
Yes that much I know :)
Thanks for the quick reply...
My info file contains:
name = Fix Zero Search
description = Fixes leading zeros in search.
type = module...
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