modifiedcontent

I also get a fatal internal server error with FrontendUserRegisterEmailValidation.module in PW 3.0.33: Line 160 in my case, not 110. Line 160 is: Removing that line "fixes" the error, shows the form. Removing everything from the arrow as well. If you try to register, an email gets sent, but it is empty. Changing 'true' to 'false' had no effect. A combination of flydev's solution for line 110 + removing everything from the -> sign, does seem to fix the error. An email does get sent with a validation token. And then the user has to pick a password? And then what? Is there supposed to be a second email, with 'Welcome, now log in here ...'? Or should I structure the form/pages in such a way that picking a password also logs the user in? Is there really no complete working implementation example somewhere? I tried 'check for updates' on the FrontendUserRegisterEmailValidation.module , but get Once you have a working process, how would you style and extend the forms? Beyond using the available classes and ids for CSS. Is there a way to get control over the html? I never use list tags, <li etc., for forms. I'd like to rewrite it to something like this: <div><input placeholder="label text here" ... /></div>

Thanks pwFoo. Is there a complete basic working code example anywhere? This is what I have so far: <?php $fu = $modules->get('FrontendUser'); $redirectDestination = htmlentities($_SERVER['REQUEST_URI']); if ($user->isGuest()) { $fu->register(); $fu->process($redirectDestination); echo $fu->render(); echo 'or log in here if you already have an account'; echo $fu->login(null, $redirectDestination); // with default fields } if($user->isLoggedin()) { if (isset($_GET['logout'])) $fu->logout($redirectDestination); echo "<a href='?logout'>Logout</a>"; } ?> Login/logout works fine. Registration adds a new user, but the user would never know; I need to figure out how to send him/her an email confirmation, with an activation link maybe (?), log them in automatically, ..., what else? I also don't want my registration form to ask for a "username"; only real name - firstname, lastname - and email address and then later maybe addition info. I'll probably end up generating a username from the real name in the background, as I've always done in Wordpress. All these points have probably been discussed somewhere in this long thread, but is there any place where it is all put together into one working example? The documentation gives the basic functions/usage (?) but not how to put it together, leaving out essential points that may be obvious for regular Processwire users, but not if this is the first PW module you try to implement after years in WP world. The code snippets/examples then skip ahead to sanitizing and custom fields. I can't find anywhere how to add an activation link email process. Email activation is mentioned here, but mixed in with a lot of other issues. Where should I start?

Thanks pwFoo. Following the documentation I assumed there was a default $redirectDestination somewhere, like "SELF" - would that be '$_SERVER['PHP_SELF']' or '$_SERVER['REQUEST_URI']' or is there a PW specific way to do that? What does 'return $this' do in your empty($redirect) test?

FrontendUser and FormHelper are the first modules I have installed in Processwire, so I am still very confused about the basics. When I put this in a template file: $fu = $modules->get('FrontendUser'); echo $fu->login(null, $redirectDestination); The output in the site is just the text 'FrontendUser', no login form as I had hoped. What am I missing? Probably something very dumb and obvious.

EsoTalk and Flarum look like old-fashioned bulletin boards to me. I want something much more content focused; member profile pages as content channels and then collect some platform activity on a general homepage. I like the straightforward way PW handles content. If PW can handle users/members in a similar straightforward way, that would be a great starting point. I don't want to use yet another php script that only does one thing.

Thank you for your quick response pwFoo. And Beluga. I have forum websites based on heavily customized Wordpress Multisite now, but it is a structural mess - http://geowebforum.com etc. In Wordpress Multisite each new site is completely independent/disconnected from the others. Buddypress works around that by adding a second users database table. I tried a different approach to minimize the number of plugins and keep everyhing as standard as possible, but Wordpress still makes it hard to manage as one platform. I don't want a classic old skool forum/BB, like this support forum. It should be more like a social network; users have their own profile pages where they can post content in their own channel/newsfeed and then can comment on eachothers content. Whatever the features are going to be, I need a solid, straightforward users/members management system to get started. I'll try your module and will report back here. Thanks again!

I am just getting started on this - building a forum site where users can register an account, have a profile page and then expand from there... Could someone give a summary of this thread. How far along is this module? FrontendUser is listed as alpha/not stable, but does the basic process work? Is it good enough to get started? Is a stable version 1.0 coming any day now or is this an abandoned experiment? Would I be better off trying to develop something very rudimentary from scratch?

I am also getting started with this, a basic social network, where people can sign up, have their own profile page, post stuff, comment on other's posts, etc. How far along are others who have tried this? What are the basic parts I should start with to get a minimal viable version online as soon as possible?

OK, thanks for the responses. I saw that thread with the index.config.php, but wasn't sure if that really answered my question, if there wasn't a simpler way to do it. Still trying to understand how ProcessWire works. I thought you could have different sites on one ProcessWire installation; so one 'wire' folder and then different 'sites'. I have a ProcessWire site at the root of a VPS full of Wordpress sites on sub-domains, all with 'mywebsite' folder names. That is where my confusion came from.

Is it possible to change the name of the default 'site' folder? Like change it to 'mywebsitename'? There is no real technical reason for me to want to do this. I am just afraid that the inconspicuous 'site' will get lost on the server, that I or someone else will end up deleting at some point.