Jump to content
adrian

Phone Number Fieldtype

Recommended Posts

@Juergen - so sorry about the label translations - totally my fault - I was so used to pushing to the dev branch lately that I didn't think about breaking changes. I don't think it's worth reverting the change that broke those labels given how new this version is, but I'll be sure not to break that again.The undefined offset on line 322 is a different thing - that happens if you don't define the example numbers in a format - note the:  | 61,07,45673456,123 at the end of the line.

australiaNoCountryAreaCodeLeadingZero | {([phoneAreaCode,0,2])} {[phoneNumber,0,4]} {[phoneNumber,4,4]} {x[phoneExtension]} | 61,07,45673456,123

What I will do though is add default example numbers so you don't get that PHP Notice.

 

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, Juergen said:

PHP Notice: Undefined offset: 3 in .../site/modules/FieldtypePhone/FieldtypePhone.module:322

New version fixes this notice.

Sorry once again for the label issues :)

  • Like 1

Share this post


Link to post
Share on other sites

Hello Adrian,

just to clearify: the empty labels problem happens after upgrading to the version with the option of hiding the labels (I think version 2.0.10) not from version 1 to version 2 (major upgrade).

Thanks for the fast fix!!

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, Juergen said:

just to clearify: the empty labels problem happens after upgrading to the version with the option of hiding the labels

Yeah, understood - I changed the names of the settings fields to be more semantically correct. I shouldn't have changed them once I pushed v2.x to master, but what's done is done now I think and it's still early days for this new version so I don't think it will affect too many people.

  • Thanks 1

Share this post


Link to post
Share on other sites

@adrian I've just installed the module (2.0.12), I have an issue.

PHP Notice: Undefined offset: 1 in .../site/modules/FieldtypePhone/FieldtypePhone.module:320 when saving the module settings with this:

/*Hungary*/
hungaryAreaCodeOnly {([phoneAreaCode])}-{[phoneNumber,0,3]}-{[phoneNumber,3,4]}

If I add " | 1-21-123-4567" to the end, the notice is gone. You noted this new "part" in a post here and provide an example on the module's config page but it did not seem to be mandatory.

 

Share this post


Link to post
Share on other sites
4 minutes ago, szabesz said:

hungaryAreaCodeOnly {([phoneAreaCode])}-{[phoneNumber,0,3]}-{[phoneNumber,3,4]}

I think I figured it out, I am missing the first pipe character and that is why I got the warning.

  • Like 1

Share this post


Link to post
Share on other sites
4 minutes ago, szabesz said:

@adrian I've just installed the module (2.0.12), I have an issue.

PHP Notice: Undefined offset: 1 in .../site/modules/FieldtypePhone/FieldtypePhone.module:320 when saving the module settings with this:


/*Hungary*/
hungaryAreaCodeOnly {([phoneAreaCode])}-{[phoneNumber,0,3]}-{[phoneNumber,3,4]}

If I add " | 1-21-123-4567" to the end, the notice is gone. You noted this new "part" in a post here and provide an example on the module's config page but it did not seem to be mandatory.

 

The issue you are seeing is actually the missing pipe (|) between the name and the format. Try this:

/*Hungary*/
hungaryAreaCodeOnly | {([phoneAreaCode])}-{[phoneNumber,0,3]}-{[phoneNumber,3,4]}

 

  • Like 1

Share this post


Link to post
Share on other sites
3 minutes ago, adrian said:

The issue you are seeing is actually the missing pipe (|) between the name and the format.

Thanks! These sort of cryptic patterns ARE very useful but only after I have implemented them properly :)

  • Like 1

Share this post


Link to post
Share on other sites

New version:

1) Adds a new option to "Allow Letters in Input" which is to support companies who like to publicize their phone number using letters, like: 1800-CALLNOW - the default is for this to be off so validation still checks that all are digits, but with this on, you can also enter letters.

2) Has some tweaks to prevent a component suffix from displaying if there is no value for the next component. 

 

  • Like 2

Share this post


Link to post
Share on other sites

I just added new options for putting component labels in field placeholder and adding a custom class to each component input (eg. uk-input).

image.png.fc89b054023a72b6f95847809697fea9.png

  • Like 2

Share this post


Link to post
Share on other sites

Hi all - I have started a new 3.0 branch which has some more breaking changes.

This new version moves the country code into it's own "data_country" database field and stores a raw version of the number in the default "data" field. The reason for this is to make it possible to do a:

$pages->find("phone=13727654876")

Before you could only find by component parts, like:

$pages->find("phone.country=1, phone.are_code=372, phone.number=7654876")

My need for this was to find a user by their full raw/unformatted phone number as returned by the Twilio sms service's POST response.

I'll keep the changes in this branch for a while, but I would encourage new installs to try this version.

Let me know how it goes.

  • Like 2

Share this post


Link to post
Share on other sites

Hi Adrian,

I have not yet installed the 3.0 branch because I though before I spend time on it I ask you about an issue we have.

So we still have version 2.0.15 and the field is added to users (dunno if it matter as at all...) When the inputbox of the "core" number (not country, area nor extension)  is empty then Chrome automatically fills it in with the username used for logging into ProcessWire on the standard login screen and letting Chrome save the credentials. In other words, if we have Chrome save the login info, the current user's name gets injected into the inputbox when editing a user with an empty number, and this is an annoying issue because the inputbox must be manually cleared if we want to save the user.

Have you any idea how to stop this behavior?

  • Like 1

Share this post


Link to post
Share on other sites

Hi @szabesz - it can probably be solved quite easily with some autocomplete attributes.

Can you please try adding: 

autocomplete="pw-phone-country"
autocomplete="pw-phone-area-code"
autocomplete="pw-phone-number"
autocomplete="pw-phone-extension"

to the respective subfields. Here is the chunk of code that these need inserting into: https://github.com/adrianbj/FieldtypePhone/blob/ab02ad1a6aafc1b1abce60317cd97ce5a2c35374/InputfieldPhone.module#L98-L116

Let me know if that works as expected and feel free to submit a PR.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the quick reply, based on it found this article: https://www.20spokes.com/blog/what-to-do-when-chrome-ignores-autocomplete-off-on-your-form This is also what you suggest, right?

The thing is that it is not my Mac which has this issue but a Windows machine I do not have access to right now. Hopefully I can test it on that machine on Tuesday. I want to make sure I test it with that setup too.

Share this post


Link to post
Share on other sites
19 minutes ago, szabesz said:

This is also what you suggest, right?

Yeah, I think so. Honestly I am not too up on the current state of this autocomplete stuff, but I think my suggestions will work.

Let me know how it goes when you test on Tuesday.

  • Like 1

Share this post


Link to post
Share on other sites

Hello @adrian

is it possible to disable the input field length fe

style="width:60px;"

by entering something into the settings field?

If not, it would be great if you add the possibility to enter fe a "-" to disable the rendering of the style attribute. This could be useful if you are using the UIKit template because there are various input length classes ('uk-form-width-medium'....)  and you dont need the input field length.

Best regards Jürgen

  • Like 1

Share this post


Link to post
Share on other sites

Hi @Juergen - I just added the option to both the master and 3.x branches. Let me know if you have any problems.

@szabesz  did you ever end up testing the autocomplete stuff?

Also, I'd like to move 3.x to master pretty soon because it's definitely much easier to work with raw numbers that way. Does anyone have any ideas for any other improvements that might also be breaking changes so we can get these in for this new version?

  • Like 1

Share this post


Link to post
Share on other sites
19 hours ago, adrian said:

@szabesz  did you ever end up testing the autocomplete stuff?

Yes I did, I just did not have the time to report and later on forgot to. I did not do any extensive testing, I just checked if the issue was gone on that particular machine or not. Since the issue had never showed up again, I guess the changes applied were the cause of it.

Share this post


Link to post
Share on other sites

FYI - I just merged the 3.0 branch to master - be warned that this is a breaking change because of the new data_country db field so please don't update existing installs unless you're prepared to do some DB manipulation - if you want to and can't figure out the required SQL commands, let me know and I can post something here.

  • Like 2

Share this post


Link to post
Share on other sites

Hello,

I have created a standard field type as userphone , then I added this field to the User template. I created a phone field type using Phone Field module. I added this field to the User template also.

image.thumb.png.f40f3d23d3f8849fdf15e13a06ef63b6.png

Now I used the below to create a test user

 $u = new User();
$u->of(false);
$u->name = "saarun";
$u->email = "saarunthomas@example.com";
$u->pass = "123456";
$u->Phone = 9446196667;
$u->userphone = 9446196667;
$u->headline = "hello there";
$u->paid=1;
$u->addRole("registered");
$u->save();
$u->of(true);

and I tried to out put as below

     $item = $users->get("saarun");
echo $item->email;
echo $item->Phone;
echo $item->paid;
echo $item->headline;
echo $item->userphone;

and I got the output a below.  Neither the userphone value nor the Phone value are output ... what am I doing here wrong  ? pls help

and I want to use this field in the Login/Register module. I want know whether this field support in the Login/Register registration form ??

image.png.eee59c5c952dd521d71cb1dd8d23cd22.png

Share this post


Link to post
Share on other sites
11 minutes ago, JeevanisM said:

Hello,

I have created a standard field type as userphone

It's a good idea to limit your support request to only one category. Posting in multiple places makes it very difficult to track the progress.

  • Like 1

Share this post


Link to post
Share on other sites
3 minutes ago, rick said:

It's a good idea to limit your support request to only one category. Posting in multiple places makes it very difficult to track the progress.

I found this thread at last only, will delete all other posts.

Share this post


Link to post
Share on other sites

@JeevanisM - I don't know why the integer phone number isn't working, but for the phone number field you have to set the subfields separately, eg:

$u->Phone->country = 944;
$u->Phone->number = 6196667;

or if you have the field set up to keep the area code in a separate subfield:

$u->Phone->country = 944;
$u->Phone->area_code = 619; 
$u->Phone->number = 6667;

and don't forget to use the field's formatting options to style the output how you want.

Share this post


Link to post
Share on other sites

Just making a note here that Form Builder doesn't seem to see this field anymore as of the v3 - not sure if the last fix you mentioned above for v2 would work. I will give it a try.

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 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');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...