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
Can have multiple pages the same name. Although this isn't a problem, it could still cause problems.
Each page will have it's path and route dynamically created before save in Mongo. Although it would be bad to have the same name at the same level for example :
The solution for now would be to add unique : true to the page model in Node and also to save wasting a request, check if the page title is unique in the pages collection.
The text was updated successfully, but these errors were encountered:
Currently uses a bit of code duplication in controllers\pages.js line 11 to build the path string for the check - coped from the PagesSchema declaration. Ideally this would use a function that the schema would also use, but not sure of the scope of this. Have todo'd it.
Can have multiple pages the same name. Although this isn't a problem, it could still cause problems.
Each page will have it's path and route dynamically created before save in Mongo. Although it would be bad to have the same name at the same level for example :
www.siteify.io/about
www.siteify.io/about
It's not a problem to have :
www.siteify.io/customer
www.siteify.io/people/customer
As the routes would be different. . . .
The solution for now would be to add unique : true to the page model in Node and also to save wasting a request, check if the page title is unique in the pages collection.
The text was updated successfully, but these errors were encountered: