Jump to content

FrontendUser: login, logout and register users / members


pwFoo

Recommended Posts

Thanks for the guidance. I don't like captcha's either, but for this site, admins need to approve every registration by hand, so no validation emails can be sent. Akismet or http://stopforumspam.com/ might be alternatives.

The recaptcha module does not require any additional form fields.

So would the hooking thing be something like:

        $form->addHookAfter('processInput', function() {
    
        $recaptcha = wire('modules')->get('Recaptcha')->verifyResponse(wire('input')->post->g-recaptcha-response);
        if(!$recaptcha) {
             $form->fhSubmitBtn->error('reCAPTCHA validation not ok!');
        }
        });

It seems I don't understand where to put it, though. If it is in my register.php, I get a Fatal error: Call to a member function addHookAfter() on null.

Should I put it somewhere in FrontendUser.module (Build registration form function?) or FormHelper.module (Extended PW form api processing function?)?

I'm in no particular hurry to find out, so please focus on your own pressing matters first :)

Link to comment
Share on other sites

No need to change FormHelper or FrontendUser modules.

Have you set $form inside your template like that?

$form = $fu->form;

Try something like that inside your template file (untested code!).

// load module
$fu = $modules->get('FrontendUser');

// prepare / create register form with default fields
$fu->register();

// Add hooks to the form / fields
// Your code here 
$fu->form->addHookAfter('processInput', function() {
        $recaptcha = wire('modules')->get('Recaptcha')->verifyResponse(wire('input')->post->g-recaptcha-response);
        if(!$recaptcha) {
             $form->fhSubmitBtn->error('reCAPTCHA validation not ok!');
        }
});

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

// output register form
echo $fu->render();
Link to comment
Share on other sites

Ok, I was being a bit slow again.. I didn't even render the recaptcha! :-[

So I added to the top

$recaptcha = $modules->get('Recaptcha');

(also $form = $fu->form ;)

and

echo $recaptcha->render();

below the fu render.

Here is the rendering code from the module:

$html = '<script src="'.$this->getJsLink($lang).'" async defer></script>'."\n";
$html .= '<div class="g-recaptcha"'.$this->buildAttributes($attributes).'></div>';

Then this response element is created through JS:

<textarea id="g-recaptcha-response" name="g-recaptcha-response" class="g-recaptcha-response" style="width: 250px; height: 40px; border: 1px solid #c1c1c1; margin: 10px 25px; padding: 0px; resize: none;  display: none; "></textarea>

Yet, the recaptcha answer (=I'm not a robot) seems to somehow not be processed as I get

Fatal error: Call to a member function error() on null

I guess I'll bother the author of the recaptcha module next..

As a new tangent, I'm giving you this proposition to make the module become aware of EmailNewUser.

Edit: well, it is enough to call in my register.php: $modules->get('EmailAdminNewUser');

Link to comment
Share on other sites

The recaptcha module author answered and I noticed I had wrong syntax for the verifyResponse bit (copied from Nico's post).

I also now use wire('') for everything inside the function..

Now there are no other notices than

Fatal error: Call to a member function error() on null

After submitting my registration.

Referring to the fhSubmitBtn->error

Here is my complete register.php:

<?php
if(!$user->isLoggedin()) {
  // load module
  $fu = $modules->get('FrontendUser');
  $recaptcha = $modules->get('Recaptcha');
  // prepare register form
  $fu->register();
 
  $form = $fu->form;

  // process register / form submit
  $redirectDestination = $pages->get(1)->url;
 
        $form->addHookAfter('processInput', function() {

        $recaptchaverify = wire('modules')->get('Recaptcha')->verifyResponse(wire('input')->post('g-recaptcha-response'));
        if(!$recaptchaverify) {
             wire('modules')->get('FrontendUser')->fhSubmitBtn->error('reCAPTCHA validation not ok!');
        }
        });
  $fu->process($redirectDestination);

?>
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
        <title><?php echo $title; ?></title>
        <link rel="stylesheet" type="text/css" href="<?php echo $templatesurl; ?>css/mystyle.css" />
    <link rel="stylesheet" type="text/css" href="<?php echo $templatesurl; ?>css/somestyle.css" />    
    </head>
    <body>
    <div class="container">
    <p>Ylläpito vahvistaa kaikki rekisteröitymiset. Saat sähköpostia, kun olet saanut käyttöoikeudet.</p>
<?php  // output register form
  echo $fu->render();
  echo $recaptcha->render();
?>
    </div>
    </body>
</html>
<?php  die();
}
Link to comment
Share on other sites

You loaded recacptcha module :

$recaptcha = $modules->get('Recaptcha');

No need to reload module :

$recaptchaverify = wire('modules')->get('Recaptcha')->verifyResponse(wire('input')->post('g-recaptcha-response'));

You can use it like : 

$recaptchaverify = $recaptcha->verifyResponse(wire('input')->post('g-recaptcha-response'));

and same for frontenduser module

is there a funtion $fu->fhSubmitBtn->error() ? I didn't use and check module codes or usages be sure there is a function exist... Error mean there is no function exist !

Link to comment
Share on other sites

No, I can't use them like that inside the function.

If I do, I get an error like this on submit:

Notice: Undefined variable: recaptcha in C:\BitNami\wampstack-5.6.2-0\apache2\htdocs\mysite\site\templates\register.php on line 22

Fatal error: Call to a member function verifyResponse() on null in C:\BitNami\wampstack-5.6.2-0\apache2\htdocs\mysite\site\templates\register.php on line 22

Is there something I'm missing?

Link to comment
Share on other sites

Can you try it like :

wire('modules')->get('FrontendUser')->form->fhSubmitBtn->error('reCAPTCHA validation not ok!');

And also you can use loaded modules or variables like this :
 

$form->addHookAfter('processInput', function() use($fu, $recaptcha, $input) {
        $recaptchaverify = $recaptcha->verifyResponse($input->post('g-recaptcha-response'));
        if(!$recaptchaverify) {
             $fu->form->fhSubmitBtn->error('reCAPTCHA validation not ok!');
        }
});
  • Like 1
Link to comment
Share on other sites

Thanks heaps! Now there are no errors.

Now I'm just left wondering, why recaptcha validation is not ok :)

I was testing on localhost and it should work with the API keys, but I'll try in the online website next.

Edit: didn't work in the online website either..

Link to comment
Share on other sites

Thanks heaps! Now there are no errors.

Now I'm just left wondering, why recaptcha validation is not ok :)

I was testing on localhost and it should work with the API keys, but I'll try in the online website next.

Edit: didn't work in the online website either..

You can test recacptcha also on localhost ! But be sure you are using virtual host or when you create a key be sure there is your local domain also added.

Link to comment
Share on other sites

@ukyo: thanks for your tip in PM! Now I could successfully create the user, passing the recaptcha validation!! O0

Adding a post checking condition did the trick:

$form->addHookAfter('processInput', function() use($fu, $recaptcha, $input) {
        if(isset(wire('input')->post) && wire('input')->post('fuRegisterForm') == 'fuRegisterForm') {
          $recaptchaverify = $recaptcha->verifyResponse($input->post('g-recaptcha-response'));
          if(!$recaptchaverify) {
               $fu->form->fhSubmitBtn->error('reCAPTCHA validation not ok!');
          }
        }
        });
Link to comment
Share on other sites

fhSubmitBtn is part of FormHelper and not FrontendUser. That's why you have to use

$fu->form->fhSubmitBtn to get the object and der the Form field error ;)

Inside a hook you can use

$fu = wire('fu');

to work with the FrontendUser object / instance.

Or also the FU Form:

$form = wire('fu')->form

Link to comment
Share on other sites

I'm trying to add an extra field for my registration form: fullname.

Still calling the registration with $fu->register();

I've changed the FrontendUser.module:

// create registration form
        if (empty($fields)) {
            $fields = array('username', 'email', 'password', 'fullname');
        }

and added this:

/**
     * Fullname form field
     * @return InputfieldText Fullname field
     */
    protected function fullnameRegister() {
        $field = $this->modules->get('InputfieldText');
        $field->label = $this->_('Koko nimesi');
        $field->attr('id+name', 'fullname');
        $field->required = 1;
        $field->fhSanitizer = 'text';
        $field->addHookAfter('processInput', function($event) {
            $field = $event->object;
            $fullname = wire('fu')->form->fhValue($field->fullname);
            
            if (empty($fullname))   return;
            else {
              wire('fu')->userObj->fullname = $fullname;
            }
        });
        return $field;

The form field is added fine, but the input is not saved to the user's fullname field. Is there something I'm missing?

Link to comment
Share on other sites

First... do NOT modify the module! Extend it!

Just define the field and add it to the register() optional field array.

Read the wiki documentation (https://bitbucket.org/pwFoo/frontenduser/wiki/Documentation#markdown-header-register). Also take a look at code comments).

Have you added the field "fullname" to the user template? If field is added and value is der ro the userObj it should be saved. See nickname example (https://bitbucket.org/pwFoo/frontenduser/wiki/Register%20extensions%20and%20plugins) and add debugging output to check your value.

Link to comment
Share on other sites

I read the documentation & examples carefully before deciding I have to modify the module. Besides, I wanted to modify the module in any case, because I wanted to translate the labels etc. to Finnish..

I do have the fullname field in the user template, which is the reason I would like the users to be able to populate it already on registering.

This is the best I could do to debug:

I changed the function process:

if ($result === true) {
                var_dump($this->userObj);
                //$this->session->redirect($redirect, false);     // User sucessfully registered
            }

Then I could see that the fullname is empty:

["data"]=> array(10) { ["email"]=> string(16) "dkjdfaa@dfds.com" ["pass"]=> object(Password)#305 (0) { } ["fullname"]=> string(0) "" ["roles"]=> object(PageArray)#306 (6)

The fieldtype for fullname is text, matching what is in fullnameRegister..

How can I debug further to see where it fails to save the input?

Link to comment
Share on other sites

You can translate the field labels or modify the fields (set your own label). Nö need to hack the module ;)

Is $field->fullname the field name string?

$fullname = wire('fu')->form->fhValue($field->fullname);

Should be something like that.

$fullname = wire('fu')->form->fhValue("fullname");

Just add a debugging output inside your hook to verify that.

FormHelper documentation

https://bitbucket.org/pwFoo/formhelper/wiki/Documentation

No PC here to take a closer look. Mobile only for two weeks ;)

Link to comment
Share on other sites

Ah, I had never tried that module translation method.. Languages - Select file does work fine.

$fullname = wire('fu')->form->fhValue("fullname");

YES! That solved it!

But why did it not accept $field->fullname, when it is added to the fields array with

$fields = array('username', 'email', 'password', 'fullname');

I tried both

$fu->register();

and

$fu->register(array('username', 'email', 'password', 'fullname'));

It made no difference.

So how could I do this without hacking the .module file?

I have to somehow add the function fullnameRegister or recreate its functionality and execution.

I have no idea how to do this and it will probably take me 1-2 hours to figure it out (which is why I went with the straight hacking method initially).

Edit: the easiest way would be to simply:

$fu->fullnameRegister = function() {

and add my function there, in my register.php. But the class is not built to accept adding new functions to itself.

Then if I try to add a hook to buildForm, I get "Method FrontendUser::buildForm is not hookable"

Edit2: damn, I managed to spend 1-2 hours today on this, plus maybe 3-4 hours yesterday and only now do I realize pwFoo already supplied the answer in May!

Link to comment
Share on other sites

Hi Beluga,

so all problems solved now? :)

The module is designed to be as flexible as possible. All addons and also changes should be done with params (add or replace fields) and hooks (additional or changes processing). You can translate labels and also change fields from outside if needed...

$usernameField = $fu->form->get("username");

$usernameField->label = "New label";

All is based on PW hooks and PW form api / PW fields.

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

Hi pwFoo, thanks VERY much for this great module :)

Please could you let me know if there is an easy way to prepopulate the username with a value I have in a variable?

I see I can use the code

$fu->register(array('username', 'email', 'password'));

but I can't work out how modify it to not offer the visitor a Username field but for it instead to be prepopulated so at time of submission the username field gets the prepoulated value.

Thanks for any pointers and sorry if this is obvious and I've missed it in my searches. Cheers, -Alan

Link to comment
Share on other sites

Conditional hide / remove fields from form, advanced processing is done in the RegisterEmailValidation plugin.

Password field was removed before the form will be rendered.

https://bitbucket.org/pwFoo/frontenduser/src/71207f581585ac6e089b47790eadbf3bdbedd5a9/FrontendUser/FrontendUserRegisterEmailValidation.module?at=master#FrontendUserRegisterEmailValidation.module-155

But it's a required field, so required have to be changed to false before form process.

https://bitbucket.org/pwFoo/frontenduser/src/71207f581585ac6e089b47790eadbf3bdbedd5a9/FrontendUser/FrontendUserRegisterEmailValidation.module?at=master#FrontendUserRegisterEmailValidation.module-65

It should be also possible to skip the username field.

$fu->register(array('email', 'password'));

It isn't required by the module, but the you have to set the needed attributes before you call ___save($user)

$user is a PW User object.

So a pre-save hook (like used with additional nickname plugin) should work for you.

$fu->addHookBefore('save', function($event) {
    $form = wire('fu')->form;

    if(!count($form->getErrors())) {
        wire('fu')->userObj->nickname = $form->fhValue('username', 'text');
    }
});

Just change it to wire('fu')->userObj->username = ...

  • Like 2
Link to comment
Share on other sites

Sanitize field value is a FormHelper feature ;)

Set sanitizer to field as an additional attribute

$emailField->fhSanitizer = 'email';

Get sanitized value after form processing / submitted

$value = $fu->form->fhValue('emailField')

Change sanitizer if needed...

$value = $fu->form->fhValue('emailField', 'pageName')

Or just do it without FormHelper inside a field processInput hook

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

  // Do ...
}

You can take a look in each FU field (like username field for registration) to see some examples. ;)

Or at the wiki plugin examples (register, login).

Set additional user field "nickname" based on username during registration (plugin).

Just hook before "save", generate the value and set it to the userObj. "userObj" is a temp object of type User. All existing fields will be saved.

$fu->addHookBefore('save', function($event) {
    $form = wire('fu')->form;

    if(!count($form->getErrors())) {
        wire('fu')->userObj->nickname = $form->fhValue('username', 'text');
    }
});

You need an additional field with user input? Add a field with sanitizer and a processing hook... Same as username field ;) So you can use it as starting point

        $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));

If You need more examples or have a plugin idea just post it here.

Hello, 

i have the new fileds, I dont really understand how to write the form values to the user template values ? 

Cound you post an example ? 

Also I need that an email will sent to the admin if an user is registered. User have to be activated and chooses for a group by the admin. 

Thanx for the advice 

Link to comment
Share on other sites

Hello, 

i have the new fileds, I dont really understand how to write the form values to the user template values ? 

Cound you post an example ? 

Also I need that an email will sent to the admin if an user is registered. User have to be activated and chooses for a group by the admin. 

Thanx for the advice 

For email notification and admin activation see this conversation.

Link to comment
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 LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
    • By FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • 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.

      Detailed records
      View mode "Detailed records" 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.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      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 (-).

      New in version 1.1.0
      A new feature comes with version 1.1.0 which offers to record user names of loggedin visitors. Just activate "Record user names" and "Record loggedin user" in the module settings.
      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.
    • By clsource
      Inertia Adapter ProcessWire Module
      Hello! Long time no see.
      I created this module so you can use Inertia.js (https://inertiajs.com/) with ProcessWire.
      Description
      Inertia allows you to create fully client-side rendered, single-page apps, without much of the complexity that comes with modern SPAs. It does this by leveraging existing server-side frameworks.
      Inertia isn’t a framework, nor is it a replacement to your existing server-side or client-side frameworks. Rather, it’s designed to work with them. Think of Inertia as glue that connects the two. Inertia comes with three official client-side adapters (React, Vue, and Svelte).
      This is an adapter for ProcessWire. Inertia replaces PHP views altogether by returning JavaScript components from controller actions. Those components can be built with your frontend framework of choice.
      Links
      - https://github.com/joyofpw/inertia
      - https://github.com/joyofpw/inertia-svelte-mix-pw
      - https://inertiajs.com/
      Screenshots


       
    • By sms77io
      Hi all,
      we made a small module for sending SMS via Sms77.io. It supports sending to one and multiple users.
      You can download it from GitHub and follow the instructions on how to install it - it is quite easy. An API key is required for sending, get yours for free @ Sms77 and receive 0,50 €.
      Hope this helps somebody and we are open for improvement suggestions!
       
      Best regards
      André
×
×
  • Create New...