Create a Blueprint with a Slug Field

Oct 13, 2025 by orovajewels.com 74 views

Introduction

As a Statamic user, I've encountered a peculiar issue where new entries in a collection still generate slugs even when the slug field is conditionally hidden based on a "has profile" boolean. This behavior is unexpected and may lead to inconsistencies in the slug generation process. In this article, we'll delve into the bug description, reproduce the issue, and explore possible solutions.

Bug Description

The issue arises when creating a blueprint with a slug field that is set to auto-generate based on the title, but is conditionally visible based on a "has profile" boolean. When the slug field is hidden, I expect it to be empty and remain empty. However, new entries created with "has profile" set to false still have a slug generated.

How to Reproduce

To reproduce this issue, follow these steps:

Create a Blueprint with a Slug Field: Create a new blueprint with a slug field that is set to auto-generate based on the title. Make sure the slug field is conditionally visible based on a "has profile" boolean.
Create a Collection with Slugs Not Required: Create a new collection with slugs set to not required.
Create a New Entry with "Has Profile" Set to False: Create a new entry in the collection with "has profile" set to false.
Observe the Slug Generation: Observe that the new entry still has a slug generated, despite the slug field being hidden.

Logs

No logs are provided in this case, as the issue is more related to the behavior of Statamic's slug generation process rather than an error in the logs.

Environment

Here's a summary of the environment used to reproduce this issue:

Environment
Application Name: <redacted>
Laravel Version: 10.48.27
PHP Version: 8.3.17
Composer Version: 2.8.6
Environment: local
Debug Mode: ENABLED
URL: <redacted>
Maintenance Mode: OFF

Cache
Config: NOT CACHED
Events: NOT CACHED
Routes: NOT CACHED
Views: CACHED

Drivers
Broadcasting: log
Cache: file
Database: mysql
Logs: stack / single
Mail: smtp
Queue: sync
Session: file

Statamic
Addons: 4
Sites: 1
Stache Watcher: Disabled
Static Caching: Disabled
Version: 5.46.0 PRO

Statamic Addons
alt-design/alt-redirect: 1.3.3
aryehraber/statamic-logbook: 3.3.0
jacksleight/statamic-bard-texstyle: 3.4.1
stillat/relationships: 2.2.1

Installation

This issue was reproduced on a fresh Statamic site installed via the CLI.

Additional Details

No additional details are provided in this case, as the issue is relatively straightforward and easy to reproduce.

Possible Solutions

To resolve this issue, you can try the following solutions:

Disable Slug Generation: Disable slug generation for the collection by setting the slug_required field to false.
Use a Custom Slug Field: Use a custom slug field that is not auto-generated based on the title.
Update Statamic Version: Update Statamic to the latest version, as this issue may be resolved in a newer version.

Conclusion

Introduction

In our previous article, we explored the issue of slug generation on entries with no slug in Statamic. We delved into the bug description, reproduced the issue, and explored possible solutions. In this article, we'll provide a Q&A section to help you better understand the issue and its resolution.

Q&A

Q: What is the issue with slug generation in Statamic?

A: The issue arises when creating a blueprint with a slug field that is set to auto-generate based on the title, but is conditionally visible based on a "has profile" boolean. When the slug field is hidden, new entries created with "has profile" set to false still have a slug generated.

Q: How do I reproduce this issue?

A: To reproduce this issue, follow these steps:

Create a blueprint with a slug field that is set to auto-generate based on the title.
Create a collection with slugs set to not required.
Create a new entry in the collection with "has profile" set to false.
Observe that the new entry still has a slug generated, despite the slug field being hidden.

Q: What are the possible solutions to this issue?

A: To resolve this issue, you can try the following solutions:

Disable slug generation for the collection by setting the slug_required field to false.
Use a custom slug field that is not auto-generated based on the title.
Update Statamic to the latest version, as this issue may be resolved in a newer version.

Q: Why is this issue occurring in the first place?

A: This issue is likely occurring due to a bug in Statamic's slug generation process. When the slug field is hidden, Statamic may not be properly checking for the presence of a slug before generating a new one.

Q: How can I prevent this issue from occurring in the future?

A: To prevent this issue from occurring in the future, make sure to:

Disable slug generation for collections where it is not required.
Use custom slug fields that are not auto-generated based on the title.
Regularly update Statamic to the latest version to ensure you have the latest bug fixes and features.

Q: Can I customize the slug generation process in Statamic?

A: Yes, you can customize the slug generation process in Statamic by using a custom slug field or by creating a custom plugin to handle slug generation.

Q: Where can I find more information about this issue?

A: For more information about this issue, you can refer to the Statamic documentation, the Statamic community forums, or the Statamic GitHub repository.

Conclusion

In conclusion, the issue of slug generation on entries with no slug is a common problem that can be resolved by disabling slug generation, using a custom slug field, or updating Statamic to the latest version. By following the steps outlined in this article and the Q&A section, you should be able to better understand the issue and its resolution. If you have any further questions or concerns, feel free to ask in the comments below.