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.
Hi @Gnome and welcome to Backdrop
When I create custom layout templates I put them in /layouts/custom/my_layout
Note: you can split modules and layouts between contrib and custom...
Posted19 hours 44 min ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
This post explains how to do this in Drupal 7. In Backdrop, File Entity is already part of core. You will need to download and install module Views Field View.
https://drupal.stackexchange...
Posted2 days 3 hours ago by Alejandro Cremaschi (argiepiano) on:
After alot of trials, i have done the obvious and translated the whole block for different languages with each property condition as follows:
->propertyCondition('langcode', 'en...
Thanks so much! It's working now:
I was able to transfer the docroot files to the containing directory without the need for a second database or any manual configuration export/import/sync...
Ah, I see. Sorry, I hadn't clicked the link and assumed it was the instructions for upgrading from Drupal 7.
If you are simply copying a site from one location on a server to another, the...
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