Configuration
You can customise Wishlist’s settings using a PHP configuration file. This is optional: each setting has a default, so you only need to include the values you want to change.
To override a setting, create wishlist.php in your Craft project’s /config directory and return an array of setting names and values. For example, the following will change the name displayed in the control panel:
<?php
return [
'pluginName' => 'Wishlist Tools',
];All other settings keep their defaults. Add any further settings you want to change to the same array. The options below explain the available settings and their defaults. You can also manage many of these settings in the control panel under Wishlist → Settings.
Configuration Options
If you want to change the plugin name in the control panel.
Lists
Whether to allow duplicates in lists.
Whether front-end list, item and add-to-cart actions accept GET requests as well as POST requests, for templates that still use action URLs. Turn it off to require POST requests with CSRF protection, as the upgrade guide explains.
Whether to allow front-end users to manage disabled lists and their items.
Whether to merge a user’s lists with all existing lists for the user, when they log in. This can be useful when lists are modified when logged out, but a user logs in. Any existing lists will be merged.
Whether to purge inactive lists after a certain duration.
If purging inactive lists is enabled, after this duration they will be purged.
If purging inactive lists is enabled, after this duration only guest lists will be purged.
Whether to purge user lists only if they have no items.
Whether to restrict inactive guest-list purging to lists with no items. The default allows inactive guest lists to be purged after purgeInactiveGuestListsDuration, including lists that contain items.
Set how long of an expiry guest users' lists should have, before being forgotten. Provide as 0 to be session-based, or a DateInterval (opens new window) string.
Item Eligibility
These settings control which linked elements can be added from front-end requests. They do not restrict control-panel item management, and existing items can still be removed if their linked element later becomes ineligible. Wishlist continues to support every registered element type permitted by its supported-element-types event.
Whether draft elements can be added to lists from front-end requests. When the list target’s root owner is a draft, enabling this also permits its expected lack of a public URL.
Whether element revisions can be added to lists from front-end requests. When the list target’s root owner is a revision, enabling this also permits its expected lack of a public URL.
Whether disabled, archived, pending, expired, suspended or locked elements can be added to lists from front-end requests. When the list target’s root owner is inactive, enabling this also permits its expected lack of a public URL.
Whether localized elements from a site other than the current site can be added to lists from front-end requests. Other eligibility checks continue to apply.
Whether active elements without a public site URL can be added to lists from front-end requests. Nested elements use their root owner’s public URL.
PDF and plain-template generation is limited to five uncached renders per authenticated user or guest client address and 20 uncached renders per list every 15 minutes. Up to four renders can run concurrently, generated output is cached for five minutes, and rendered template HTML cannot exceed 2 MiB. Multi-node installations must use shared persistent cache and mutex implementations for these limits and cached output to apply across every node.
Set the path to your PDF.
Set the default PDF filename format.
Whether to allow remote images in the PDF.
Sets the paper size for the PDF.
Sets the paper orientation for the PDF.
The template Wishlist will use for HTML emails.
Whether to attach the PDF to the email. See PDF settings for generating the PDF.
Whether the list editing screen displays its information tab.