I want to restrict access to the entire site except the login page, but Toolset Access only allows controlling specific parts of the site, not full-site access.
Solution:
Use a third-party plugin like Restricted Site Access (https://wordpress.org/plugins/restricted-site-access/) to block the entire site except the login page; then use Toolset Access alongside it to control internal access by user role. Compatibility between the two should be tested on your specific setup.
I noticed that the “Display Name” field is not showing in the WordPress admin user profile, and I suspect Toolset may be hiding it.
Solution:
Create a site backup, then go to WordPress Dashboard > Plugins and temporarily deactivate all Toolset plugins. Check if the “Display Name” field reappears in Users > Profile. If it does, Toolset is affecting the display. If not, the issue lies elsewhere.
I want to add a front-end delete button for a post that has multiple relationships, and I need to understand the difference between “Trash the post” and “Delete the post,” as well as whether related relationships are also removed.
Solution:
“Trash the post” moves it to the WordPress Trash and allows recovery; “Delete the post” permanently removes it. In both cases, Toolset removes the relationships linked to the deleted post, but the related posts themselves are not deleted unless custom code using before_delete_post and toolset_get_related_posts() is implemented.
I am using Toolset and WPML to build a bilingual “People” directory, but the French archive page doesn’t appear in the language switcher and shows untranslated content, despite using WPML’s Advanced Translation Editor.
Solution:
Go to WPML > Support > ATE Error Log and check for plugin conflicts; in this case, deactivating The Events Calendar plugin resolved the translation sync issue and allowed the French archive and form elements to display correctly.
I am using WP All Import Pro with Toolset to import/export posts with nested taxonomy terms, but the import assigns full hierarchies incorrectly—checking parent terms even when only child or subchild terms were selected originally.
Solution:
Since WP All Import handles the import/export logic, including taxonomy hierarchies, contact their official support for guidance on configuring term import mappings properly.
