Module Description
The Allow a content type only once module allows the creation of Only One content per language in the selected content types for this configuration.
Uses Configuring content types
To configure the content types to allow for Only One content per language, visit the 'Only One' page (admin/config/content/onlyone), in the Available content types for Only One section check the content types that should have Only One content per language. For this you need the Administer Only One permission.
Configuring module settings
To configure the module settings visit the Settings page (admin/config/content/onlyone/settings), if you want to have the configured content types in a new menu entry named 'Add content (Only One)' you must check the option 'Show configured content types in a new menu entry', the new menu link will be available in the 'Content' page (admin/content) as an action link to the 'Add content (Only One)' page (onlyone/add), then the 'Add content' page (node/add) will show the not configured content types. For this you need the Administer Only One permission.
Creating content
Once you try to Add content (node/add), if the chosen content type is configured to have Only One content and it already has one content created in the actual language, you will be redirected to edit the content, otherwise, you will go to create a new one.
Drush commands
drush onlyone-list Shows a content types list according to the selected status. drush onlyone-enable Enables the 'Only One content' mode on content types. drush onlyone-disable Disables the 'Only One content' mode on content types. drush onlyone-new-menu-entry Configures if the configured content types will be shown in a new menu entry. About 8.x version Aditionals modules
Allow a content type only once (Only One) for Admin Toolbar Very useful if you use the Admin Toolbar module as it handles modifications to the Admin Toolbar Extra Tools module menu entries related to the configured content types. Recommended modules Drush Help Improves the module help page showing information about the module's Drush commands. Similar Projects Node Limit Allows to restrict the number of contents of a specific type that roles or users may create. Differences:
* The user with uid 1 can create unlimited contents even if you define the limit
* If the content limit for a content type is 1 and you create a new one, you can't translate it
* If the content limit for a content type is 1, and you have created a content, if you try to add a new content you are not redirected to the existing content edit form
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Entity Limit Allows to restrict the number of entities of a specific type that an user or role may create. Differences:
* The user with uid 1 can create unlimited contents even if you define the limit
* If the content limit for a content type is 1 and you create a new one, you can't translate it
* If the content limit for a content type is 1, and you have created a new one, if you try to add a new content you are not redirected to the existing content edit form
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Entity Rules Provides a page for selecting and creating Rules components that will be executed when different operations happen to an Entity of a particular bundle. Differences:
* Needs Rules to works
* Requires a lot of configurations, you can take a look inside the Entity Rules Node Limits sandbox
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Issues If you love the Kanban Boards we have one thanks to ContribKanban.
As with all contributed modules, when considering submitting an issue:
* Read the documentation (two or three times is better). Don't forget the home page.
* Review the existing issues list. (Don't forget to select "<- Any ->" for the "Status" field.)
* Gather all the appropriate information. This may include (but is not limited to):
* Drupal version.
* Browser type and version.
* Database type and version.
* Error messages, if any.
* Module settings.
* Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
* If you go to provide a patch use the following naming convention: [onlyone]-[short-description]-[issue-number]-[comment-number]-[drupal-version].patch
And please don't forget to use the Issue Summary Template to report an issue, if you need help to understand how the issue queue works, see the Getting Started in the Issue Queue video.
Development version status The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get from us. Your help on testing this code is greatly appreciated. The translation templates may not always be up-to-date in the dev releases.
Uses Configuring content types
To configure the content types to allow for Only One content per language, visit the 'Only One' page (admin/config/content/onlyone), in the Available content types for Only One section check the content types that should have Only One content per language. For this you need the Administer Only One permission.
Configuring module settings
To configure the module settings visit the Settings page (admin/config/content/onlyone/settings), if you want to have the configured content types in a new menu entry named 'Add content (Only One)' you must check the option 'Show configured content types in a new menu entry', the new menu link will be available in the 'Content' page (admin/content) as an action link to the 'Add content (Only One)' page (onlyone/add), then the 'Add content' page (node/add) will show the not configured content types. For this you need the Administer Only One permission.
Creating content
Once you try to Add content (node/add), if the chosen content type is configured to have Only One content and it already has one content created in the actual language, you will be redirected to edit the content, otherwise, you will go to create a new one.
Drush commands
drush onlyone-list Shows a content types list according to the selected status. drush onlyone-enable Enables the 'Only One content' mode on content types. drush onlyone-disable Disables the 'Only One content' mode on content types. drush onlyone-new-menu-entry Configures if the configured content types will be shown in a new menu entry. About 8.x version Aditionals modules
Allow a content type only once (Only One) for Admin Toolbar Very useful if you use the Admin Toolbar module as it handles modifications to the Admin Toolbar Extra Tools module menu entries related to the configured content types. Recommended modules Drush Help Improves the module help page showing information about the module's Drush commands. Similar Projects Node Limit Allows to restrict the number of contents of a specific type that roles or users may create. Differences:
* The user with uid 1 can create unlimited contents even if you define the limit
* If the content limit for a content type is 1 and you create a new one, you can't translate it
* If the content limit for a content type is 1, and you have created a content, if you try to add a new content you are not redirected to the existing content edit form
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Entity Limit Allows to restrict the number of entities of a specific type that an user or role may create. Differences:
* The user with uid 1 can create unlimited contents even if you define the limit
* If the content limit for a content type is 1 and you create a new one, you can't translate it
* If the content limit for a content type is 1, and you have created a new one, if you try to add a new content you are not redirected to the existing content edit form
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Entity Rules Provides a page for selecting and creating Rules components that will be executed when different operations happen to an Entity of a particular bundle. Differences:
* Needs Rules to works
* Requires a lot of configurations, you can take a look inside the Entity Rules Node Limits sandbox
* There is not drush commands to interact with the module
* You can limit the content creation by users and roles
Issues If you love the Kanban Boards we have one thanks to ContribKanban.
As with all contributed modules, when considering submitting an issue:
* Read the documentation (two or three times is better). Don't forget the home page.
* Review the existing issues list. (Don't forget to select "<- Any ->" for the "Status" field.)
* Gather all the appropriate information. This may include (but is not limited to):
* Drupal version.
* Browser type and version.
* Database type and version.
* Error messages, if any.
* Module settings.
* Submit the issue. If other modules are involved, you may need to submit the issue to those modules as well.
* If you go to provide a patch use the following naming convention: [onlyone]-[short-description]-[issue-number]-[comment-number]-[drupal-version].patch
And please don't forget to use the Issue Summary Template to report an issue, if you need help to understand how the issue queue works, see the Getting Started in the Issue Queue video.
Development version status The development versions (-dev) are where the newest stuff is, including any bug fixes and new features. We try to make sure it is tested before we commit anything, but occasionally a bug will get from us. Your help on testing this code is greatly appreciated. The translation templates may not always be up-to-date in the dev releases.
Module Link
Project Usage
1152
Security Covered
Covered By Security Advisory
Version Available
Production
Module Summary
The Allow a content type only once module aims to solve the issue of allowing only one content per language in selected content types for configuration.
Data Name
onlyone
OPENAI CHATBOT
OPENAI CHATBOT
