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.
You can edit images and load them back to the same folder with the same name and extension, this will not create a problem. Replace directly in the file system, without the use of CMS, for CMS...
I was under the impression you could not do that - don't know where I got that idea from... thought it had to do with the way Backdrop manages image files.
I think given the warning on the source site:
At this time, if your new project can afford to require PHP 5.5+, which it should, please use PHP's native password_hash() /...
Posted2 days 21 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
I did a very quick test and if the Display format of the webform submission value is HTML then it appears but if plain text then it doesn't, so something is included regardless of if empty when...
Posted2 days 23 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
Just to clarify it appears that the item: Fix Search for "On the Web" module, is about the search on backdropcms.org at https://backdropcms.org/modules
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