Jump to content
pwFoo

FrontendUser: login, logout and register users / members

Recommended Posts

Take a look here how to manipulate forms:

https://bitbucket.org/pwFoo/frontenduser/wiki/Login extensions and plugins

https://bitbucket.org/pwFoo/frontenduser/wiki/Register extensions and plugins

https://bitbucket.org/pwFoo/frontenduser/wiki/Code snippets / Examples

You could try to hook FrontendUser::save

$fu->addHookBefore('save', function($event) {
    $userObj = wire('fu')->userObj;
    $form = wire('fu')->form;
    
    // Do...
});

 

Or username or email field

// hook after field processed (form need to be submitted)
$myField->addHookAfter('processInput', function($event) {
  $form = wire('fu')->form;
  $currentField = $event->object;

  // Do ...
}

 

 

  • Like 1

Share this post


Link to post
Share on other sites

@jmartsch

i've a own registerform created with FormHelper from @pwFoo
but not depending on FrontendUser and i use this code for usernam = email

 

//check for email duplication
if (email_valid($email) == true) {
	//email exists
	$out .= message("email exists...","danger");
} elseif ($password == ''){
	//no password is there
	$out .= message("no password...","danger");
} else {

//email is valid create so we first create a new user
$u = new User();
$u->of(false);
$u->name = $sanitizer->fieldName($email);
$u->email = $sanitizer->email($email);
.....save other fields go on...

you can use $sanatizer->fieldName in a hook on FrontendUser module, too i guess...
regards mr-fan

Share this post


Link to post
Share on other sites

@mr-fan Thank you. Maybe it is the way to go without the FrontendUser Module. I also saw your post 

and thought "That could be the solution I want to use, if there is no simple solution with the FrontendUser module".

Share this post


Link to post
Share on other sites

Set a field to not required is done with FrontendUserRegisterEmailValidation "plugin"

            $form->get('password')->required = false;
            $form->get('EmailPreValidation')->required = false;

You can remove fields with required false 

            // prepare / modify registration form
            $form->remove($form->get('password'));

 

Share this post


Link to post
Share on other sites

I was scratching my head for hours because I couldn't get the add default role plugin to work.
It's probably only me who is so newbie at hooks. But anyway, just wanted to add here for those who have similar problems: 
(@pwFoo, you might want to add this extra line to the documentation ;) )

Hooks must be added before the processing! :-) 

I got my code working this way:

// Add default user role
$fu->addHookBefore('save', function($event) {
    $user = wire('fu')->userObj;
    $user->addRole('dress');
});

// Login after successful registration
$fu->addHookAfter('save', function($event) {
  $user = $event->object->form->fhValue('username','text');
  $pass = $event->object->form->fhValue('password','text');
  $this->session->login($user, $pass);
});

// process register / form submit
$fu->process($redirectDestination);

Thanks for the great module though, it saved me loads of time and it just works.
The email validations is just the icing on the cake. :)

  • Like 1

Share this post


Link to post
Share on other sites

Added the hint to use the hook before "save" to get the changes saved to the user. ;)

  • Like 3

Share this post


Link to post
Share on other sites

I don't understand hooks or/and how the forms API works. I am trying to fix this bit:

Spoiler

$fullname = $modules->get('InputfieldText');
$fullname->label = 'Full name';
$fullname->attr('id+name','fullname');
$fullname->required = 1;
$fullname->fhSanitizer = 'text';

// Call hook after field is processed by PW form api
$fullname->addHookAfter('processInput', function($event) {
	$field = $event->object;
	$mySanitizedCustomInput = wire('fu')->form->fhValue($field->name);
	wire('fu')->userObj->fullname = $mySanitizedCustomInput;
});

$fu->addHookBefore('save', function($event) {
    $user = wire('fu')->userObj;
    $user->addRole('member');
});

 

The fullname apparently does not get saved along with the username when the validation email is sent; the pre-filled form only has the username.

I tried changing $fullname->addHookAfter to addHookBefore, but that made no difference.

I assume the $fullname->addHookAfter function adds the fullname field value to a userObj object, so that it gets saved along with the username and email address in $fu->addHookBefore ... , right?

Or is 'send email validation code' another hookable event than 'save'? Is there a list of available hookable events in the registration process?

Or are custom fields like fullname correctly stored with the userObj by this bit of code, only not automatically added to the pre-filled form by the module?

Should I hook into the validation email event, somehow, and add the fullname field?

 

Or are my assumptions about what goes on in this bit of code all wrong?

 

Share this post


Link to post
Share on other sites

You need to read the FrontendUser documentation examples I think ;)

Take a look here: https://bitbucket.org/pwFoo/frontenduser/wiki/Code snippets / Examples

<?php
$myField = $modules->get('InputfieldText');
$myField->label = $this->_('MyLabel');
$myField->attr('id+name', 'MyField');
//$myField->required = 1;
$myField->fhSanitizer = 'text';

// Call hook after field is processed by PW form api
$myField->addHookAfter('processInput', function($event) {
    $field = $event->object;

    // Value will be sanitized as text with "$sanitizer->text()"
    $mySanitizedCustomInput = wire('fu')->form->fhValue($field->name);

    // Do ...

    // Example: Add value to user during registration
    wire('fu')->userObj->myField = $mySanitizedCustomInput;

    // Need to set an field error?
    // $field->error('Custom field has an error...');
});

// Define the field before you call FU and add it as additional field...
$fu->register(array('username', 'email', 'password', $myField));

 

To extend the FrontendUser module it's needed to know how to use form api and hooks. FrontendUser is just based on PW basic features. 

Share this post


Link to post
Share on other sites

@pwFoo, I have followed the documentation. I don't know how to use forms API, hooks, basic PW features. This is the first PW module I'm working with after spending years on Wordpress.

Share this post


Link to post
Share on other sites

I'm no PHP or PW guru neither but this is how I see it (food for thought):

You created a new input field but didn't make it part of the wire('fu') object – hence pwFoo's comment. So when you get to the 

wire('fu')->process();

your hook will be able to process your input field. This is what happens here:

// Define the field before you call FU and add it as additional field...
$fu->register(array('username', 'email', 'password', $myField));

I'm sure you will get there soon based on the example above.

Share this post


Link to post
Share on other sites

@Jozsef, I have that line in my full code:

Spoiler
<?php
$fu = $modules->get('FrontendUser');
 
$redirectDestination = htmlentities($_SERVER['REQUEST_URI']);
 
$fullname = $modules->get('InputfieldText');
$fullname->label = 'Full name';
$fullname->attr('id+name','fullname');
$fullname->required = 1;
$fullname->fhSanitizer = 'text';
 
// Call hook after field is processed by PW form api
$fullname->addHookAfter('processInput', function($event) {
 $field = $event->object;
 $mySanitizedCustomInput = wire('fu')->form->fhValue($field->name);
 wire('fu')->userObj->fullname = $mySanitizedCustomInput;
});
 
// include fullname in the wire('fu') object?
$fu->register(array($fullname,'username', 'email', 'emailValidation', 'password'));
 
$fu->addHookBefore('save', function($event) {
    $user = wire('fu')->userObj;
    $user->addRole('member');
});
 
$fu->addHookAfter('FrontendUser::save', function($event) use($fu, $input) {
 if($event->return === true) {
  if(!empty($input->post->password) && !count($fu->form->getErrors())) {
   $subject = "Welcome - your new account at mydomain.com";
   $emailContentPlain = "Your connection details:\nUsername: {$fu->userObj->name}\nEmail: {$fu->userObj->email}\nPassword: {$input->post->password}";
   $mail = wireMail();
   $mail->to($fu->userObj->email);
   $mail->subject($subject);
   $mail->body($emailContentPlain);
   $mail->send();
  }
 }
});
 
// Login after successful registration
$fu->addHookAfter('save', function($event) {
  $user = $event->object->form->fhValue('username','text');
  $pass = $event->object->form->fhValue('password','text');
  $this->session->login($user, $pass);
});
 
// Login with the email address instead of the username
$fu->addHookBefore('FrontendUser::auth', function($event) {
        $email = wire('fu')->form->fhValue('username', 'email');
        $loginUser = wire('users')->get("email={$email}");
        if ($loginUser instanceof User && !$loginUser->isGuest()) {
            $userObj = $event->arguments[0];
            $userObj->name = $loginUser->name;
        }
});
 
if ($user->isGuest()) {
$fu->process($redirectDestination);
echo $fu->render();
echo 'or log in here if you already have an account';
echo $fu->login(null, $redirectDestination);
}
 
if($user->isLoggedin()) {
 if (isset($_GET['logout'])) $fu->logout($redirectDestination);
 echo "<a href='?logout'>log out</a>";
 echo '<h3>Hello '. $user->fullname .'</h3>';
}
?>

So I guess it's in the wrong place? I'll try it with a few things turned around and report back...

Edit: Moved the line to current position. Fullname is still blank after the validation email. Will dig into the documentation when I have time and report back...

What does '// Call hook after field is processed by PW form api' do? I thought that bit added fullname to userObj.

Should I replace mySanitizedCustomInput with 'fullname' or 'field' or something else?

Which hookable events are there; processInput, save, ...? Is 'send email validation code' another hookable event?

To be clear, the fullname does get saved fine, but only after manually entering it again after the email validation. Fullname is not saved along with the username before the validation process or is not added to the custom field in the pre-filled form. Or is that the normal process?

 

Share this post


Link to post
Share on other sites

@modifiedcontent, I'm sorry, as I mentioned I'm no expert when it comes to PHP and PW hooks. I hope someone can jump in to help you out. ;)

 

  • Like 1

Share this post


Link to post
Share on other sites

Regarding the email validation, it works great... except when my client tried in on his fully updated iPhone 5, and somehow the session gets lost when he clicks on the link in the activation email he receives: he ends up with the initial default form (username + email), and he's stuck in a loop. I've been trying to reproduce it, but to no avail. He's using Safari, and not in Private Mode (which by the way does break the activation).

Have you any of you guys run into this issue? Or have any clue what could be happening? Thanks in advance.

  • Like 1

Share this post


Link to post
Share on other sites

It's dependent on php session. If you loose the session the registration state is lost too.

Share this post


Link to post
Share on other sites

Thanks pwfoo for your very useful module. I'm still very new and I got an issue about the password validation as the attached image. The text "Not yet validInvalidToo shortToo commonWeakOkGoodExcellent" shown when I get in my Register page. It not work like in the back-end. How to fix it ?

Screenshot - 02092017 - 09:10:47 PM.png

Share this post


Link to post
Share on other sites
1 hour ago, pwFoo said:

The forms are unstyled. Backend styles are needed. 

FormHelper Extra can load the styles, but I think that wasn't added to FrontendUser as feature / option.

https://bitbucket.org/pwFoo/formhelper/wiki/Documentation#markdown-header-formhelperextra

Thank you for you message. I tried to find the information in your link but it's not for a beginner like me, and also in this forum page by page but no one got stuck like me. :'(

Could you please suggest me how to make it works ?

Share this post


Link to post
Share on other sites

FormHelper is loaded here:

protected function buildForm($fields) {
        $this->form = $this->modules->get('FormHelper')->create();

https://bitbucket.org/pwFoo/frontenduser/src/0070dc3106945198ac438bab3ab742b1784080e9/FrontendUser/FrontendUser.module?at=master&fileviewer=file-view-default#FrontendUser.module-176

FormHelper create()

https://bitbucket.org/pwFoo/formhelper/src/d85395b2dd7352a0af7aadeeec5125ba3d9d0bb0/FormHelper/FormHelper.module?at=master&fileviewer=file-view-default#FormHelper.module-61

 

The create() method need additional parameters which need to be passed from template -> FrontendUser -> FormHelper, but it isn't implemented in the FrontendUser module...

 

Or just load / create the needed styles. Here is the function is used by FormHelper

    /**
     * Use admin / custom form styles 
     * @param boolean|string $style true or an css file to load
     */
    protected function pwAdminStyles($style) {
        $this->config->styles->add($this->config->urls->adminTemplates . 'styles/font-awesome/css/font-awesome.min.css');
        
        if ($style === true) {
            $style = $this->config->urls->AdminThemeDefault . 'styles/main-classic.css';
        }
        $this->config->styles->add($style);
    }

https://bitbucket.org/pwFoo/formhelper/src/d85395b2dd7352a0af7aadeeec5125ba3d9d0bb0/FormHelper/FormHelper.module?at=master&fileviewer=file-view-default#FormHelper.module-192

Share this post


Link to post
Share on other sites
On 2/9/2017 at 10:19 AM, Thachakrit said:

Thanks pwfoo for your very useful module. I'm still very new and I got an issue about the password validation as the attached image. The text "Not yet validInvalidToo shortToo commonWeakOkGoodExcellent" shown when I get in my Register page. It not work like in the back-end. How to fix it ?

Screenshot - 02092017 - 09:10:47 PM.png

 


I'm having the same problem. It's unclear from the previous post on how to fix this issue.
Shouldn't this be included in module package?

Share this post


Link to post
Share on other sites

Hi @jasonS,

it looks like the module isn't compatible to the used / latest PW version. I think password inputfield changed?
Can't remember that problem with PW 2.7 and PW Dev 3.x..? 

Anyone tested it with different / older PW versions?

Sorry, I haven't a test / dev environment at the moment and can't spend much time to change / debug it. 

Share this post


Link to post
Share on other sites
On 9.2.2017 at 3:19 PM, Thachakrit said:

Thanks pwfoo for your very useful module. I'm still very new and I got an issue about the password validation as the attached image. The text "Not yet validInvalidToo shortToo commonWeakOkGoodExcellent" shown when I get in my Register page. It not work like in the back-end. How to fix it ?

Screenshot - 02092017 - 09:10:47 PM.png

@Thachakrit @JasonS @pwFoo To get the password validation working you need to add styles and scripts from ProcessWire Admin.

The following is untested with this module but should work if you add it to the page where you do the output of the module:

 <script type="text/javascript" src="/wire/modules/Inputfield/InputfieldPassword/complexify/jquery.complexify.min.js"></script>
    <script type="text/javascript" src="/wire/modules/Inputfield/InputfieldPassword/complexify/jquery.complexify.banlist.js"></script>
    <script type="text/javascript" src="/wire/modules/Jquery/JqueryCore/xregexp.js?v=1466417387"></script>
    <script src="/wire/modules/Inputfield/InputfieldPassword/InputfieldPassword.min.js?v=101-1466417387"></script>

EDIT: Forgot to add the stylesheet. It resides under

/wire/modules/Inputfield/InputfieldPassword/InputfieldPassword.css

 

  • Like 1

Share this post


Link to post
Share on other sites

Interesting module. Maybe a replacement for my module in the (near) future :)

  • Like 1

Share this post


Link to post
Share on other sites

@pwFoo, I haven't tried that module. Not sure if it is maintained. Haven't had time to seriously look into it.

Is the approach similar to yours? Are there usable bits you could steal and integrate into yours? Or contact that developer and join forces?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...