Recently Browsing 0 members
No registered users viewing this page.
I have this "editor" role, that has the "user-admin-all" permission.
I tried several times, doing different things sets of permissions, but I can't make a user with this role being able to make another user an "editor" too. PW disables the "editor" checkbox. I read the documentation 3 times that my eyes cannot see what I'm missing anymore.
Reference: PW 3.0.62 and uikit3 based site using the Regular-Master profile.
The issue is that blog posts for the particular site in question are automatically formatted as /blog/<blog-post-title>. It is evident the path format should have been configured as /blog/<year>/<month>/<blog-post-title>.
Please could someone advise whether or not it is possible to change the path format for the blog posts of an existing active site that uses the regular profile?
Any assitance would be greatly appreciated.
I'm using the LoginRegister module and I'm getting an internal server error when I try to login with a wrong password more than one time.
I've found that the error comes from the SessionLoginThrottle.module, because, for security reasons, is better to prevent too many failed logins.
Ok, good. But, am I wrong if I think it's too bad to show an Internal server error to the user instead of a simple error in template saying the user to wait X seconds to retry to login?
Is there a way to do that? It would be great if I could get the error string and style it in the page the way I like.
And in the SessionLoginThrottle admin configuration, I think that could be a good idea to be able to change the maximum number of login attempts before the error is shown.
I'm trying to understand how I could have users log in as "members", provide them with a customized experience, but still serve them cached pages?
For example let's say I have 3 roles
Guest Member SuperUser And let's say I have a NavBar type component that has a menu. Plus it has "log in!" if guest, or "logged in as Mike Smith"
I would want guests to see a cached site with guest-only page access. Members should also see cached pages, but their menu may have access to members-only pages or fields or information. Furthermore they might have a "logged in as Mike Smith" element. SuperUsers can stay uncached. How does one go about creating that cache so that visitors aren't constantly re-creating the menu? Or that when "Sally Baker" logs in, she doesn't see a homepage that is cached for "Mike Smith" with all his elements?
Thank you in advance for any replies.