You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had made an entry in a "Pages" section (with versioning enabled) the homepage by setting it’s URI to __home__. Later on, I decided to create a new Single for the homepage. Craft threw an error saying the site "already had a homepage". Fair enough, so I went and changed the current homepage’s URI to something else (so it was no longer the homepage, verified in the front-end), but Craft continued to complain about the site already having a homepage. I went ahead and deleted the entry altogether and tried again. Still got the error. Only when I ran the garbage collector and removed all traces of the previous homepage entry was I able to create my new Single and mark that to be the homepage.
Steps to reproduce
Create a section with versioning enabled
Create an entry in this section and set it’s URI to __home__
Now change it’s URI to something else
Try to create a new Single and leave the URI field blank
Additional info
Craft version: 3.2.6
PHP version: 7.1.19
The text was updated successfully, but these errors were encountered:
Description
I had made an entry in a "Pages" section (with versioning enabled) the homepage by setting it’s URI to
__home__
. Later on, I decided to create a new Single for the homepage. Craft threw an error saying the site "already had a homepage". Fair enough, so I went and changed the current homepage’s URI to something else (so it was no longer the homepage, verified in the front-end), but Craft continued to complain about the site already having a homepage. I went ahead and deleted the entry altogether and tried again. Still got the error. Only when I ran the garbage collector and removed all traces of the previous homepage entry was I able to create my new Single and mark that to be the homepage.Steps to reproduce
__home__
Additional info
The text was updated successfully, but these errors were encountered: