Jump to content
pwFoo

FrontendUser: login, logout and register users / members

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 :)

Share this post


Link to post
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();

Share this post


Link to post
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');

Share this post


Link to post
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();
}

Share this post


Link to post
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 !

Share this post


Link to post
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?

Share this post


Link to post
Share on other sites

I see hook function now, its ok but be sure there is wire('modules')->get('FrontendUser')->fhSubmitBtn->error(); function exist.

Share this post


Link to post
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

Share this post


Link to post
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..

Share this post


Link to post
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.

Share this post


Link to post
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!');
          }
        }
        });

Share this post


Link to post
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

Share this post


Link to post
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?

Share this post


Link to post
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.

Share this post


Link to post
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?

Share this post


Link to post
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 ;)

Share this post


Link to post
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!

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites

Yes, all problems solved except depression and embarrassment after failing to notice the existing code snippet.

I think it should be added to the documentation examples as it's such a common use-case.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
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

Share this post


Link to post
Share on other sites

Thanks pwFoo, I'd tried with a pre-save hook but had used the wrong construction, I'll try your version—thanks for the fast reply ^_^

Share this post


Link to post
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 

Share this post


Link to post
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.

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 d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Pip
      Hi everyone!
      I'm trying out the Login/Register module for my site. Noted that the module assigns the newly registered user to login-register role. 
      Once you modify the login-register role's permissions, particularly adding page-edit, the new member role will be set to guest. 
      Thing is I'd like to grant my new users the power to create their own pages. Any advice? 
      Thanks. 
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
×
×
  • Create New...