Recently Browsing 0 members
No registered users viewing this page.
I have been using PW for a while; and on every build it seems to perform really well and always have the ability to do what I need. Thanks everyone! I have a site coming up that I want to be involved in but it has some features that I feel PW won't be able to handle...
Here's the list...
Time banking system, interactive map, complex search criteria, calendar/events, login/registration states with payment (subscription?) and profile, front end profile views, internal messaging systems with approval levels and news
Most of these I know I can handle, but the ones I am unsure of are time banking system, login/registration states with payment (subscription) and profile, front end profile views and internal messaging systems with approval levels.
Has anyone ever had any experience with the above? Do you think any of this is possible on PW? I know I am asking a lot of questions but any help would be appreciated. I think most things are self-explanatory but the time-banking system, I'm assuming at this stage, is essentially a bit of a messaging platform where you post requests, record hours and have a statement of those hours. The best example I could find seems to be from the 90s, but to be fair it seems robust (http://hourworld.org/_TimeAndTalents.htm)
Any help or advice would be really appreciated.
I'm working on a project where I've got about 500 members. These members each have their own page with fields that they can edit and others that they can only view, all these member pages are under a parent page (members). Each member's page is bound to the user's profile using a pagefield in the user profile. I would like to have a login form on the sidebar where members log in from the front end and are immediately redirected to their particular page. I plan to use Fredi module to allow them to have front end editing access for their page. I don't want them to access the backend at all.
All suggestions welcome. Thank you
I know this has been discussed before and I've read through a lot of those threads over the past few months, but I'm getting myself all confused and have so many bookmarks my brain is at risk of exploding, so bear with me as I ask for some guidance/clarification.
I have a site with about 500 members that I'm moving to PW. The old database is so convoluted that I'll be importing them manually, which is no big deal as the client is willing to provide plenty of data entry assistance if I need it Each member will have the basic role of "member" with sub-roles "junior", "senior", "elder", etc Each role will be able to view different parts of the member end of the site. This is all easy for me to set up using access by template rules.
Now this is where I'm sweating. I have a feeling it's easy but for some reason I keep confusing myself and probably complicating the whole thing
I would like very much to have each member profile be a page with different fields that I can pull into an aggregated members page for public viewing. That's easy enough to do by me just creating the pages. But how do I then have each member be able to edit certain fields on their profile page and nothing else? I don't want them to be able to edit anything else on the site, just their profile page. And this is what is really confusing me - how do I link the profile page to the members site account? Also, if a new (junior) member joins using a form I will create (via Form Builder), I want a new page to be created for that user but remain unpublished until the client approves them . Again, I know the answers are here somewhere, and I'm sure they're really simple but I'm having major mental block at the moment
Thanks for the help
I just made a website and created the cms using Processwire. It was really great to set up and I can configure it just the way I want it which is perfect. Now this site has 1 main product to sell in 4 colors. My question now is, how do I create a checkout for the visitors with easy payment such as Paypal and iDeal (I live in holland).
I'm not to familiair with PHP to create a whole checkout form which is save enough and with a data system for all the customers myself. So I thought I would only use the shopping cart and catalog function of Prestashop. But how exactly can I set that up?
I was thinking about permalinks. So that customers on my site can select the product and how many they want and after that they get linked right to the checkout page from Prestashop with the exact price and that they only have to fill in their info.
Do you guys have suggestions on this?
I search thru the forum regarding topics of built a membership system.
I knew there are no out-of-box membership to plug into PW to make it happen.
I have to using PW provided api to create all membership dirty work, front-end stuffs like registration, login,logout, user profile, create user content, non front-end stuffs like session handling, user rights
My question is the landing page of these membership functions, registration, login/logout page, user profile page, create content page are to create each of function for a page (associated to a template/template file is necessary) ?