Jump to content
adrian

Page Field Select Creator

Recommended Posts

Hey Joss,

I am personally not a big fan of the Add New button at all - I know it seems like a nice shortcut, but for some reason it just seems more confusing to me than anything. I am sure others love it though :)

Anyway, my point is that even though I don't like it, it is the PW default to have templates appear in here if all the conditions are met, so wouldn't most people expect this behavior and would prefer it wasn't overridden by default?

Maybe it should be another configurable option when setting up a new Page field? I'd add it at the end, below "Allow new pages to be created from field?"

What do you think - does that seem like the best option?

Share this post


Link to post
Share on other sites

I went ahead and made it an option. By default it is added to the shortcut button, but you have the option to prevent this.

Also made a couple of other minor fixes / tweaks.

Joss - let me know if that works ok for you.

  • Like 1

Share this post


Link to post
Share on other sites

I think that helps - if nothing else it remins me that this happens, and that is good. Thanks!

Share this post


Link to post
Share on other sites

I noticed that after creating fields with this module, I have a new button on the Page Tree for adding new items.

post-825-0-52612100-1415708030_thumb.jpg

I would like to know how its done.

Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

This is done when you have a template with family setting to have allowed children template. On the children template select the parent template to allow, there will appear a setting to turn off or on if it should add it to the "Add New" button.

  • Like 1

Share this post


Link to post
Share on other sites

This is done when you have a template with family setting to have allowed children template. On the children template select the parent template to allow, there will appear a setting to turn off or on if it should add it to the "Add New" button.

Thanks a lot!  :-)

Share this post


Link to post
Share on other sites

Hi,

   can i add chain of child pages using Page Field Select Creator module...like below

Parent 

    - Child A

      -- child A1

      -- child A2

         -- child A21

         -- child A22

         -- child A23

      --child A3

    - Child B

      --child B1

      --Child B2

      --Child B3

         Plz help me...

Regards,

Pravin

Edited by kongondo
@Pravin. I moved this here in this module's support forum

Share this post


Link to post
Share on other sites

Page Field Select Creator is not designed for adding multiple trees of parents/children/grandchildren.  Are you actually setting up a page field, or do you just want a quick batch way of creating these for general content?

If the latter, then take a look at these modules instead:

http://modules.processwire.com/modules/batch-child-editor/

http://modules.processwire.com/modules/process-batcher/

If the former, can you please let us know your use case in a little more detail.

Share this post


Link to post
Share on other sites

Page Field Select Creator is not designed for adding multiple trees of parents/children/grandchildren.  Are you actually setting up a page field, or do you just want a quick batch way of creating these for general content?

If the latter, then take a look at these modules instead:

http://modules.processwire.com/modules/batch-child-editor/

http://modules.processwire.com/modules/process-batcher/

If the former, can you please let us know your use case in a little more detail.

Hi Adrian,

    Thanx for you help.  I will explain my requirement. I want to display my clients sectorwise, technologywise, Sorting can be done on clients page using checkbox or any other option. Each client will have its individual page. 

Regards,

Pravin

Share this post


Link to post
Share on other sites

I think you can still use this module to set up the page field and the Parent / Child A / Child B components of the tree, but to get the grandchildren: child A1 etc, you will need to add those by some other means - either manually or via one of the modules I mentioned.

Remember that this module is just a shortcut method for creating Page Fields and their linked pages. You should still understand how they work and also realize that once created, all settings and content pages can be manually adjusted. Does that make sense?

Share this post


Link to post
Share on other sites

I think you can still use this module to set up the page field and the Parent / Child A / Child B components of the tree, but to get the grandchildren: child A1 etc, you will need to add those by some other means - either manually or via one of the modules I mentioned.

Remember that this module is just a shortcut method for creating Page Fields and their linked pages. You should still understand how they work and also realize that once created, all settings and content pages can be manually adjusted. Does that make sense?

Ok..I will do it..

Regards,

Pravin

Share this post


Link to post
Share on other sites

TL;DR; Selecting a new Radio and saving, the previous one was getting reselected upon refresh. Fix, cleared all browser cache.

I had just created the field, so maybe I had a somehow polluted cache, weird. My setup, in case relevant, using clamp and Chrome on a Mac, after creating a set of Radio's, all worked AOK, no errors or odd behaviour, except, usually changing radio and saving the page the Radio was reverting back to the one it had been before.

Cleared Chrome cache and totally fixed.

Edit: DOH! I think this may have been due to Admin being signed in on another tab—how embarrassing...

Edited by alan
DOH!

Share this post


Link to post
Share on other sites

Hi Adrian,

I think it would be good to provide a dedicated field for setting the parent page title rather than setting it the same as the field title.

An example: I'm creating a select field to choose a geographical region. Only one region may be selected, so the field title should be "Region". Each individual page represents a region and together they make up the set of regions, so it makes sense to me that the parent of those pages should be titled "Regions" and not "Region".

  • Like 1

Share this post


Link to post
Share on other sites

The current version of the module isn't creating any option pages when using the standard "title only" option for Select Options. The parent page is created but no child pages.

Settings:

2018-11-06_175634.thumb.png.a0e2cc799ce1d7da77e280879af1b4c3.png

Result:

2018-11-06_175700.png.d21c269e17d0bdca1926ac25de8e92c7.png

  • Like 1

Share this post


Link to post
Share on other sites

@Robin S - would you mind checking the previous version? Not sure whether something new in this module might have broken it or possibly a change in PW.

Share this post


Link to post
Share on other sites

Actually please try a couple of versions back also. I'll certainly get this fixed when I'm back on the 12th, but it would be good to have things working for you before then. Also if you want to submit a PR for your feature request above is be happy to accept it. Perhaps discuss a little with @Jonathan Lahijani because I know he is planning some new features also. 

Share this post


Link to post
Share on other sites

Hi @Robin S - I have fixed the bug regarding child page creation - I think it was a change to "empty" in PHP 7 that was the cause.

I'm in transit now, but I can take a look at the new option for being able to set the parent page title in the next few days.

  • Like 1

Share this post


Link to post
Share on other sites
On 11/5/2018 at 8:26 PM, Robin S said:

I think it would be good to provide a dedicated field for setting the parent page title rather than setting it the same as the field title.

Done - let me know how it goes for you.

I also fixed some other PHP7 issues with the Option 2 approach.

  • Like 2

Share this post


Link to post
Share on other sites
On 11/12/2018 at 6:09 AM, adrian said:

I have fixed the bug regarding child page creation

On 11/12/2018 at 9:38 AM, adrian said:

Done - let me know how it goes for you.

Thanks for these updates - working perfectly now.

 

  • Like 1

Share this post


Link to post
Share on other sites
6 hours ago, Robin S said:

Thanks for these updates - working perfectly now.

 

Great - thanks for testing.

I just committed another minor update that renames and reorders some of the settings and divides them into "required" and "optional" to make things a little more logical and quicker to complete.

  • Like 1

Share this post


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

I just committed another minor update that renames and reorders some of the settings and divides them into "required" and "optional" to make things a little more logical and quicker to complete.

Nice one.

I have another enhancement in mind but perhaps you wouldn't agree with the premise. The default Child Template Suffix is "Items" so I guess you like to name the child templates with the plural, but to me the parent template should be plural and the child template should be singular. And ideally the singular wouldn't be created by appending the word "item" but would be a bit smarter. So if the noun is "car" then the parent template is "Cars" and the child template is "Car". And as a trickier example, if the noun is "bacterium" then the parent template is "Bacteria" and the child template is "Bacterium".

An an experiment I added pluralize.js to the module and it's working great, with ProcessPageFieldSelectCreator.js consisting of:

$(window).load(function() {
    $('#Inputfield_fieldLabel').bind('keyup change', function() {
    	var field_label = $('#Inputfield_fieldLabel').val();
    	var plural = pluralize(field_label);
    	var singular = pluralize(field_label, 1);
	    $('#Inputfield_parentTemplate').val(plural);
	    $('#Inputfield_childTemplate').val(singular);
	    $('#Inputfield_parentPageTitle').val(plural);
    });
});

Of course the user would want to double-check that the plural/singular forms are what they want, but this addition could save time if you are creating a lot of select fields (which is something I needed to do recently). The pluralize library looks like it handles non-English languages too but I couldn't find documentation on that and I'm not competent to test that myself.

What do you think?

  • Like 1

Share this post


Link to post
Share on other sites

Hi Robin,

I don't actually ever use the "_items" suffix myself - I always go with "cars" and "car" for the parent and child templates, respectively. That approach was to make things as logical as possible without the user having to change these settings.

I am definitely keen to take a different approach though and the pluralize library seems like a good option. I see that it contains lots of rules for non-standard "s" suffixes, although it doesn't look like there any non-English ones provided.

The other concern I have is the "Singular words with no plurals" list (https://github.com/blakeembrey/pluralize/blob/298eb67f19369dd30207c0817eda4f0045c6c1a7/pluralize.js#L393) - won't these result in the parent and child templates having the same name? Do we just need a check to make sure they're not the same and if so empty the child temptate name field and prevent the form from submitting until it is completed?

Any thoughts?

  • Like 1

Share this post


Link to post
Share on other sites

@Robin S - I went ahead and added the pluralize.js library. I have also added a check so that if the parent and child templates are the same, then the child template name is removed so that the form won't submit and you need to manually set them. A simple example to test this is using "Sheep" for the Field Label. In this situation I would just manually name the parent template to "sheeps" and be happy with that, but I didn't want to assume anything, hence the approach I took.

Let me know what you think.

  • Like 1

Share this post


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

I see that it contains lots of rules for non-standard "s" suffixes, although it doesn't look like there any non-English ones provided.

Yeah, it's not clear exactly which languages are supported but the example in the docs...

Quote

pluralize('蘋果', 2, true) //=> "2 蘋果"

...makes me think there is some non-English language support.

52 minutes ago, adrian said:

I have also added a check so that if the parent and child templates are the same, then the child template name is removed so that the form won't submit and you need to manually set them.

Good solution.

Thanks for adding this feature.

  • Like 1

Share this post


Link to post
Share on other sites

@Robin S and anyone else interested - there have been several small updates over the last week. Some reorganization of the form and some tweaks to the pluralize functionality, including now automatic selection of the page field value type and input field type based on the plurality of the field label.

Anyway, please update to the latest and let me know what you think of the new tweaks.

  • Like 2

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