Search the Community

Showing results for tags 'users'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Welcome to ProcessWire
    • News & Announcements
    • Showcase
    • Wishlist & Roadmap
  • Community Support
    • Getting Started
    • Tutorials
    • FAQs
    • General Support
    • API & Templates
    • Modules/Plugins
    • Themes and Profiles
    • Multi-Language Support
    • Security
    • Jobs
  • Off Topic
    • Pub
    • Dev Talk

Found 56 results

  1. Hi, How can I display, on every page of my site, what roles can view that pages template, based on what is checked in settings>templates>template-name>ACCESS TAB? I've only gotten as far as displaying the name of the current template: echo $page->template->get('name'); But I'm stuck here. Tried things like $page->template->get('permissions'); but I guess it's a bit more complicated than that. Hope someone van point me in the right direction. Cheers.
  2. In my world, Super Users / Editors should only be able to work with Pages and administer users. Everything else is the domain of the web master. The purpose is to prevent technically inexperienced editors from destroying core elements of a site, such as fields and templates. That leaves me with the question, how to deny Super Users access to Setup, Modules and Roles / Permissions? PS: May I also suggest that it shall be possible to set Permission for each of the main menu items - including their sub-menu items.
  3. I have 100+ spam/Russian user accounts on a semi-test site. Is deleting them one by one the only option? Is there no way to select a whole page of spam user accounts and batch delete them?
  4. Is there a way to restrict logins for users so that one user can't be loggedin in two places at the same time? e.g. auto logout user after inactivity (of say 15 minutes..?), or logout action and disallow login if user still "logged in" somewhere?
  5. hey there, i'm using processwire for the first time, so maybe it's a dumb question. but i'm trying to have an options field which values are the users of the processwire. i don't need the values to be displayed, it's just for the administration of the page. but each time a new user is created / a user is deleted the options field should be updated automatically. is something like that possible?
  6. I am trying to rewrite Soma's suggestion here to export fields from the users database to a cvs file, with variations like this: $array = $users->explode(function($item){ ...etc. And $array = $users->find('start=0')->explode(function($item){ ... But keep getting 'Call to a member function ... on a non-object' errors. I guess $users is the non-object? I am trying to use this within a function, that is called with a button click. Is $users not available within a function? I see there are new export/import features coming up - great! - but it is all about $pages. Should $users work the exact same way? This works as demo starting point. Now I just have to replace the $list with something from $users:
  7. Thought I'd show some work in progress modules. Subscribers https://github.com/benbyford/Subscribers has functions for logging in new users, added with new subscriber role bulk export the subscriber users to comma delineated SubscriberList (submodule) module adds an admin page to view your subscribers and page through them, or export WireMailChimp https://github.com/benbyford/WireMailChimp (though I need to change the name on github) Implements https://github.com/drewm/mailchimp-api adds any user save to a mailchimp list settings for API and List id only adds users that have a checked email_subscribe field to true
  8. I'd really like Processwire to have a robust page based permissions system rather than just template based out of the box. If the page tree is compared to a file system, it would be nice to be able to set owner (user), group (role) and public permissions on a page and have this propagate to sub-pages unless explicitly over-ridden. With a large site, it's quite possible to have multiple sections that use the same templates, but where editing needs to be assigned to different people, for different parts of a site. I've seen some proofs of concept that have never been updated or maintained, so I'm sure it can be done, but this is a bit of a show-stopper for me with an otherwise excellent CMS. I might be able to have a go at something myself, but since this is security related, and I haven't had a go at module development before, it would be really handy to have something robust that just works.
  9. Hi, I'm sure this is maybe in the works already, given that findMany() is a recent addition to the API, but having this (and the other new find options) available to $users would be a great addition. Cheers, Chris NB Communication
  10. Hi all, I discovered Processwire a little over a week ago and have been playing around with it ever since. Going through the tutorials, creating templates, pages, etc. and see what a nice system it is. However, I'm led to believe that's it's not meant for user-centric sites, and by that I mean a site where you expect to have hundreds/thousands of users and expect them to log in, update their profiles, submit content, create galleries, message each other, chat in the Forum, get email notifications, etc. etc., you get the idea. I was trying to update the Profile page last night by adding fields for First Name, Last Name, Profile Pic, and a bunch of others and realized that it's not that easy to do. There's not even a template.php file for the Profile page. Am I just not seeing it because I'm so inexperienced with the CMS? Or, is Processwire really geared more towards sites where not much user interaction is expected? thanks, Ray
  11. Hi, I posted a question on Stack and as yet not got an anwser that is something novel. I'm interested to know if this worries anyone else and whether we can do something about it. So here goes: If a user logins to your online sevice, let's say a job posting site, they give you an email and password to access your service later... Lets say a malicous person with access to the server could write into the template to store the passwords as plain text somewhere. Given that people generally don't use a new password for each website, now that malicious person has the potential to access other online services using these details (where there isn't any secondly security like 2-factor). Is there anything we can do to battle this? In an ideal world, maybe setting up a zero-knowledge algorithm to log people in and out... https://security.stackexchange.com/questions/155806/what-to-do-about-compremised-passwords-through-malicious-sites-or-site-hacks/155823#155823 food for thought
  12. Hi there Can I ask what would be the best way to approach a situation where you require front-end users to log in before before being shown certain content and being able to download files. The users would be set up by the site manager (not superuser), but I want to keep it simple for these admins, without mixing guests up with all the site admins, and for them not to have choices over user roles etc. Would the best option be to use the built in users functionality? In which case, is there a way to keep this section of users separate from the main users list. In an ideal world, you'd create a new user as a new page under a separate parent and separate from the rest of the sites admin users. I've been searching on the forums and am getting a little confused. Many thanks if anyone could share their opinion. Kind regards Nik
  13. Would it be possible to configure a different path to the templates for different users/roles? E.g. for the user admin the templates reside in the folder /site/dev-templates/ and for all others users the templates lie in the folder /site/templates/? With this, you could have a production-version of your templates and when logging in as a special user you can work on your development-version simultaneously. Maybe there could be a function to check-in ready templates to the production-version.
  14. within my module not sure how to delete the current user and redirect without incurring this error: Fatal error: Exception: You do not have permission to execute this module - ProcessPageView (in /srv/users/serverpilot/apps/betaville-dev/public/wire/core/Modules.php line 1022) #0 /srv/users/serverpilot/apps/betaville-dev/public/wire/core/Modules.php(940): Modules->getModule('ProcessPageView') #1 /srv/users/serverpilot/apps/betaville-dev/public/wire/core/Session.php(609): Modules->get('ProcessPageView') #2 /srv/users/serverpilot/apps/betaville-dev/public/wire/core/Wire.php(398): Session->___redirect('/') #3 /srv/users/serverpilot/apps/betaville-dev/public/wire/core/Wire.php(333): Wire->runHooks('redirect', Array) #4 /srv/users/serverpilot/apps/betaville-dev/public/site/modules/Subscribers/Subscribers.module(345): Wire->__call('redirect', Array) #5 /srv/users/serverpilot/apps/betaville-dev/public/site/templates/login.php(27): Subscribers->deleteUser('benjaminbyford5...') #6 /srv/users/serverpilot/apps/betaville-dev/public/wire/core/TemplateFile.php(182): require('/srv/users/serv...') #7 /srv/users/serverpilot/apps/betavi in /srv/users/serverpilot/apps/betaville-dev/public/index.php on line 248 $u = $this->user; // user found and deleted $this->users->delete($u); // send to homepage $homepage = $this->pages->get('/'); $this->session->redirect($homepage->url);
  15. Hi all, I am currently building a custom membership functionality for a client. Here are the procedure: User fills in a membership registration form. Based on the form data, it is supposed to do the following create user, add roles (guest, subscriber OR free-trial) if free-trial, remove/disable user after X number of days if free-trial, add user to mailchimp list in the free-trial segment if subscriber, add user to mailchimp list in the subscriber segment if subscriber, create a new invoice via Freshbooks API and get Freshbooks to charge to user's credit card via Stripe My questions: What is the best approach on this? all in one module? or separate tasks into its own module? Are there any existing module(s) that already do these things? Thanks Rudy
  16. Hi guys, I have this structure: - page group A (template group) --- events group A (template group_events_list) ------ event 1 (template group_event) ------ event 2 (template group_event) ... --- news group A (template group_news_list) ------ news 1 (template group_news) ------ news 2 (template group_news) ... - page group B (template group) --- events group B (template group_events_list) ------ event 1 (template group_event) ------ event 2 (template group_event) ... --- news group B (template group_news_list) ------ news 1 (template group_news) ------ news 2 (template group_news) ... - page group C (template group) --- events group C (template group_events_list) ------ event 1 (template group_event) ------ event 2 (template group_event) ... --- news group C (template group_news_list) ------ news 1 (template group_news) ------ news 2 (template group_news) ... So every group has the same structure with events and news but they share the same template. Now, i would like to limit access for group admin to a specific group branch so that the group A admin, can access, edit, and create/delete new pages for group A, but i can not edit other group. The same for group B admin, and so on. I understand that the best idea would be to use a template - role access, but i don't want to create a different template for every group, since every group page has the same fields, structure etc. I've tried this module http://modules.processwire.com/modules/page-edit-per-user/ (even if it says just to pw 2.4 and i'm using pw 2.7.2) and i can limit access to just one group per user, but just for editing pages, not for creating new ones. And if i give page creation permission to a template, let's say group_events_list, for a specific role, than that role can create pages for every group events. How can i limit editing and creating permission just for a single group (and its children pages) per user. Is it possible? Thanks a lot!
  17. I've been using PW for about 2 or 3 years but have never really done anything with users (until now) apart from setting up users and roles for the background. I now have a project that requires following and am looking for some high level advice and an audit of my thinking. Client needs to set up users in the Admin and associate a private page with each user. Each user will have a different private page which we'll create. Users need to login via a form and be automatically directed to a private page Each user will only access a single private page BUT a private page may be associated with serveral users Requirements (for Client) A: Client needs to setup a user(s) in the admin. - No problems there and I'll just use the Access pages etc and create usergroups, roles and users. B: Client needs to associate a private page with a user - I'm thinking a user is just a page so I can add a field to a user admin template and let Client select the private page Requirements (for front end user) C: User needs to login via a web form - I'm pretty sure I can do this via the API and some sample code around the forums D: User should them be automatically redirected to a private page client setup in step A. Note: Each user has a different (and only 1) private page - I'm thinking that my login code has a reference to a variable ($privateURL) and once they're logged in, they get directed to that My biggest unknown is what might be best.... Should I create a PageSelect field within each private page which allows client to cherry pick which users can access this page OR Should I add a field called PrivateURL to the user templates and associate pages to users that way? Thanks for any advice.
  18. Hi guys I have a tiny PW site with a blog and want to give my client admin access create and edit her own posts, moderate comments etc. I've already set her up as a User, assigned her a role of "blog-author" with permissions of: View pages Edit pages View Blog page User can update profile/password However, when I log in as her I am wondering how I could achieve following within the admin IE Not hard-coding or PHP-ing? 1. Retain the "Add New" button on the top right of my Admin screen with just "Add new blog post" appearing. 2. Restrict her view of the site tree to just the Blog and child pages 3. All her to edit any pages under the blog parent Particularly confused as to why no. 3 is not working as her role of "blog-author" has "edit-pages" ticked.
  19. Hi guys Having problems publishing a new role. I can create it, tick the permission checkboxes and hit publish. Once I return to the Roles overview page, the role remains unpublished. I'm preforming this action as a super-user with full permissions so I should be able to achieve this. As all things PW-related are pages, I tried too to drill down through the page tree and directly manipulate the page under Tree > Admin > Access > Roles No joy there either. This is on 2.7.3 dev. Nothing in the error logs and I have a few sites based on this site in exact same environment with no role problems. Any tips?
  20. Hello, I have setup multiple templates for users on a 2.6.17 install. My user template is "therapeut". I added a new role "admin" with following permissions set Now when I login with user role "admin", I cannot edit the userpage "harald-roeder" with template "therapeut" through the page tree. But I can edit the same userpage through Access->Users->harald-roeder. Is this a bug?
  21. Hello everyone! My first post here. I found Processwire a while ago and have recently been getting to know the system. So far i like it a lot. Right now i'm trying to make a "page"-field where an admin can select and attach users with a specific role. I can get a list of all users, and filter by different fields, but i don't know how to access the roles. As i understand it, selectors can not be used to find user roles, so i wonder if anyone has another approach. I could add a new field to each user with the role names, but that seems a bit awkward. Thanks in advance!
  22. How can i build multi-user-system for the frontend? I have an approach like: Pagetree: Login -Admin(Admin-Overview) -- Veranstaltungen -- Agenda/Daten -- Multimedia -- Veranstalter -- Import/Export -- Einstellungen -user-1(Overview) -- Veranstaltungen -- Agenda/Daten -- Multimedia -- Profil -- Benutzer -user-2(Overview) '' '' ... users: user-1, user-2 the users have the role: client When the successfull login happens: if($user->isLoggedin()){ if($user->isSuperuser()){ $session->redirect("./admin-overview/"); } else if($user->hasRole("client")){ $session->redirect("./$user->name/"); } } On the beggining of the _main.php where all the content will be loaded: To avoid access to the content from another user from the url. if($user->isLoggedin()){ if($page->name != $page404->name){ if($user->name != $page->rootParent->name){ $session->redirect("$page404->url"); } } } Am I on the right way or is this the completely false? Can you give me a better approach, a better, safer way to achieve a multi-user-system/management for the frontend?? I must migrate an existing Web-Application that was build with yii to Processwire.
  23. In addition to a site administrator I need two special types of users, teachers and students. I was simply adding their profile fields to the default user template, but could not seem to set visibility by role for certain fields that were only applicable for the teacher template. I tried role=teacher, page.role=teacher, etc... The test field wouldn't show, so I instead went ahead and set the userTemplateIDs and usersPageIDs in config.php to $config->userTemplateIDs = array(3, 50, 51); // default, student, teacher $config->usersPageIDs = array(29, 1023, 1024); // default, student, teacher -- the above IDs belonging to existing templates and parent pages, of course. But now when I go to the Users page at /processwire/access/users/ I get this: That line is if(!$roles->has("id=$guestID")) $page->get('roles')->add($this->wire('roles')->getGuestRole()); and I don't see the problem there. When I comment it out, I can access the page, and see that my test teacher user indeed has no role, maybe that's throwing the error (although I'm not logged in as him). How do I set the respective roles for these new user templates? What else do I need to do to have these properly set up? I assumed the username would be the page name by default so it's got that and the necessary title, email, password, plus some extra fields. Any tips? I'm using v2.6.15 dev. Thanks.
  24. I'm trying to hide some of the pages on my website from users that are not logged in. I'm trying to achieve this by changing the settings of the page's template like so: This hides the page from my navigation which is good, but it doesn't block the user from surfing to the page directly which I think should be happening if I interpret the settings correctly? When I first encountered this issue I was running PW 2.6 but I've since updated to 2.6.8 alas to no avail. I hope someone will be able to help me out and I will be happy to provide more information about this issue if need be. I'm currently working around this issue by adding a $user->isLoggedin() include to my pages but this isn't as clean as setting the permissions directly from the CMS imo.
  25. Hi all! My first post here, and I'm pretty new to the PW thing, even if I'm falling in love with it . Currently, I'm making a portal with PW and trying to add a few custom fields to the users' profile (image, socials, etc.). The issue here is that I'm able to add custom fields to the user profile, but PW doesn't save the values into these fields. It does let me insert the text or upload the image, but doesn't stores them into the database. And no error is printed out. By looking into the network traffic I did find that in some case it returns a JSON response: {"error":false,"message":"AJAX Page not saved (no changes)"} I've searched/googled about this particular issue but didn't find anything about it. I also have tried the solution described in this other topic (https://processwire.com/talk/topic/1002-cant-upload-imagefiles-problem/) to try in solving the image issue at least, without any good result. I thought the problem was maybe connected to the file permissions on the local installation, but the same situation has verified on remote test installation. I'm using latest stable PW version on WAMP: Apache v2.4.9 PHP v5.5.12 MySQL v5.6.17 Any idea, friends? Thanks.