- Issue created by @maurizio_akabit
- Assigned to samit.310@gmail.com
- Status changed to Needs work
over 1 year ago 2:15pm 27 June 2023 - Issue was unassigned.
- Status changed to Needs review
over 1 year ago 9:41am 28 June 2023 - 🇮🇳India samit.310@gmail.com
configuration added Please review.
Thanks
Samit K. - 🇮🇹Italy maurizio_akabit
The patch fails using the latest dev version.
In my opinion, looking at the code, we should perform a check to verify the existence of the frontpage view, as it doesn't exist in the minimal Drupal installation. - 🇺🇸United States Greg Boggs Portland Oregon
How about we solve this one by making disable_page_slash_node a dependency? That way we can avoid maintaining the code for that and help a related module get usage when it's code is solid.
- 🇩🇰Denmark ressa Copenhagen
Isn't this method the simplest method to do it via configuration?
- Go to
/admin/structure/views/view/frontpage
- Under "No results behavior" > click "Rearrange"
- Remove these fields and save:
Global: Unfiltered text Global: Unfiltered text
Content: Empty Node Frontpage behavior Content
Global: Title override Global: Title override
From https://www.drupal.org/forum/support/post-installation/2011-02-02/delete... →
I ask because I like to keep the number of modules to a minimum in my projects, and installing two modules for this seems a bit overkill to me ...
- Go to
- 🇺🇸United States Greg Boggs Portland Oregon
In Drupal, there are many different ways to solve problems. Your method loads an entire database view which requires tons of very expensive database queries based on "select * from node" to run. On a site with 20 pages, this is trivial, on a large site with 100,000 pages this is a very expensive way to not print any content on a page.