Skip Navigation

[Resolved] Cannot find login form in Access Controls settings

This support ticket is created 6 years, 4 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

This topic contains 1 reply, has 2 voices.

Last updated by Christian Cox 6 years, 4 months ago.

Assisted by: Christian Cox.

Author
Posts
#1125531

You were right, the bootstrap setting "The theme or another plugin is already loading Bootstrap 3.0" was NOT checked, but rather Toolset uses 3.0. After changing that I no longer get the error. However, after setting it to theme-3.0 then getting out and then going back in it now has a selection SELECTED: "The theme or another plugin is already loading Bootstrap 2.0". Also since experiencing this problem. My log-in form no longer shows up on the front end, but rather a page I've been working on (whether logged in or out), and for some reason Toolset can't find it when in Access Control while setting --Post Groups

#1125535

You said Toolset can't find it when in Access Control. By "it" I assume you mean some post or page where you have placed the Form, correct? If so, is the post or page published? If not, the post will not appear in the results.

If the post is published, we can do some deeper investigation.
- Temporarily deactivate all other plugins except Types and Access, and activate a default theme like Twenty Seventeen. If the problem is resolved, reactivate your theme and other plugins one by one until the problem returns.
- If the problem was not resolved, please open your browser console, refresh the page, and test again. Let me know if any errors appear.