Jump to content

Recommended Posts

How could we add a repeater-field to our module configuration pages? I tried to add it like any other input field, but no success! (Just as a sidenote: Unfortunately my php skills are really restricted)

This is my current state, but it just throws an exception:

Error: Exception: Unknown column 'field_title.count' in 'field list' (in wire\core\Database.php line 118)
public static function getModuleConfigInputfields(array $data) {
 
    $data = array_merge(self::getDefaultData(), $data);
    $inputfields = new InputfieldWrapper();
 
 
    ...
 
 
    $field = wire("fields")->get("title");
    $field->type = $modules->get("FieldtypeRepeater");
 
    $repeater = wire("modules")->get("InputfieldRepeater");
    $repeater->name = "somethingUnique";
    $repeater->add($field);
    $repeater->page = wire("page");
    $inputfields->add($repeater);
 
 
    ...
 
 
    return $inputfields;
}

Any idea what I'm doing wrong, or how we could achive this?

Share this post


Link to post
Share on other sites

Are you wanting to add an existing repeater field, or create a new one (including all it's subfields) from scratch and then add that to the module config page. I am guessing the latter, but just wanted to confirm first.

Share this post


Link to post
Share on other sites

Are you wanting to add an existing repeater field, or create a new one (including all it's subfields) from scratch and then add that to the module config page. I am guessing the latter, but just wanted to confirm first.

Yeah, you are on the right track. I just asked me how to to create a new repeater, including some fields, via pure API. (And without adding them first to any existing page, except the module-configuration page. Don't if it is already possible?!)

Thanks so far :)

Share this post


Link to post
Share on other sites

Ok, well this will hopefully get you started. I haven't seen much on the forum or the docs about doing this. This code is an adaption from what I have just put together to support repeaters in the page tree migrator module. Because the migrator needs to take the IDs from existing repeaters, convert them to names, and then back to IDs, I think what I ended up having to do was probably more complicated than what should be needed in your situation. It worked perfectly for my needs and from some quick testing I think version should work for your needs, but there might be a much simpler way to do it. You will need to adjust the first three lines, and then the lines under both the //Add fields to.. comments. 

This code creates the repeater field, the necessary fieldgroup and template, but you would still need to add the actual repeater field to the required template, but I get the feeling you have that sorted already with the code you posted.

$titlefield = wire("fields")->get("title");
$bodyfield = wire("fields")->get("body");
$repeater_name = "newrepeater";

$f = new Field();
$f->type = $this->modules->get("FieldtypeRepeater");
$f->name = $repeater_name;

$repeater_fg = new Fieldgroup();
$repeater_fg->name = "repeater_$repeater_name";

//Add fields to fieldgroup - add others as necessary
$repeater_fg->append($titlefield);
$repeater_fg->append($bodyfield);

$repeater_fg->save();

$repeater_template = new Template();
$repeater_template->name = "repeater_$repeater_name";
$repeater_template->flags = 8;
$repeater_template->noChildren = 1;
$repeater_template->noParents = 1;
$repeater_template->noGlobal = 1;
$repeater_template->slashUrls = 1;
$repeater_template->fieldgroup = $repeater_fg;

$repeater_template->save();

$repeater_page = "for-field-{$f->id}";
$f->parent_id = $this->pages->get("name=$repeater_page")->id;
$f->template_id = $repeater_template->id;
$f->repeaterReadyItems = 3;

//Add fields to the repeater - add others as necessary
$f->repeaterFields = $titlefield;
$f->repeaterFields = $bodyfield;

$f->save();
  • Like 3

Share this post


Link to post
Share on other sites

Ok, well this will hopefully get you started. I haven't seen much on the forum or the docs about doing this. This code is an adaption from what I have just put together to support repeaters in the page tree migrator module. Because the migrator needs to take the IDs from existing repeaters, convert them to names, and then back to IDs, I think what I ended up having to do was probably more complicated than what should be needed in your situation. It worked perfectly for my needs and from some quick testing I think version should work for your needs, but there might be a much simpler way to do it. You will need to adjust the first three lines, and then the lines under both the //Add fields to.. comments. 

This code creates the repeater field, the necessary fieldgroup and template, but you would still need to add the actual repeater field to the required template, but I get the feeling you have that sorted already with the code you posted.

$titlefield = wire("fields")->get("title");
$bodyfield = wire("fields")->get("body");
$repeater_name = "newrepeater";

$f = new Field();
$f->type = $this->modules->get("FieldtypeRepeater");
$f->name = $repeater_name;

$repeater_fg = new Fieldgroup();
$repeater_fg->name = "repeater_$repeater_name";

//Add fields to fieldgroup - add others as necessary
$repeater_fg->append($titlefield);
$repeater_fg->append($bodyfield);

$repeater_fg->save();

$repeater_template = new Template();
$repeater_template->name = "repeater_$repeater_name";
$repeater_template->flags = 8;
$repeater_template->noChildren = 1;
$repeater_template->noParents = 1;
$repeater_template->noGlobal = 1;
$repeater_template->slashUrls = 1;
$repeater_template->fieldgroup = $repeater_fg;

$repeater_template->save();

$repeater_page = "for-field-{$f->id}";
$f->parent_id = $this->pages->get("name=$repeater_page")->id;
$f->template_id = $repeater_template->id;
$f->repeaterReadyItems = 3;

//Add fields to the repeater - add others as necessary
$f->repeaterFields = $titlefield;
$f->repeaterFields = $bodyfield;

$f->save();

Awesome, good stuff!

Seems to be the perfect starting point to work with repeaters to me... I'll take a look deeper in it, later this day. But nevertheless, thanks for the great adaption!

Cheers,

Yannick

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By teppo
      This module tracks changes, additions, removals etc. of public (as in "not under admin") pages of your site. Like it's name says, it doesn't attempt to be a version control system or anything like that - just a log of what's happened.
      At the moment it's still a work in progress and will most likely be a victim of many ruthless this-won't-work-let's-try-that-instead cycles, but I believe I've nailed basic functionality well enough to post it here.. so, once again, I'll be happy to hear any comments you folks can provide
      https://modules.processwire.com/modules/process-changelog/
      https://github.com/teppokoivula/ProcessChangelog
      How does it work?
      Exactly like it's (sort of) predecessor, Process Changelog actually consists of two modules: Process Changelog and Process Changelog Hooks. Hooks module exists only to serve main module by hooking into various functions within Pages class, collecting data of performed operations, refining it and keeping up a log of events in it's own custom database table (process_changelog.) Visible part is managed by Process Changelog, which provides users a (relatively) pretty view of the contents of said log table.
      How do you use it?
      When installed this module adds new page called Changelog under Admin > Setup which provides you with a table view of collected data and basic filtering tools See attached screenshots to get a general idea about what that page should look like after a while.
      For detailed installation instructions etc. see README.md.
       


    • By Mithlesh
      Changing it to null
    • By Gadgetto
      Status update links (inside this thread) for SnipWire development will be always posted here:
      2019-08-08
      2019-06-15
      2019-06-02
      2019-05-25
      If you are interested, you can test the current state of development:
      https://github.com/gadgetto/SnipWire
      Please note that the software is not yet intended for use in a production system (alpha version).
      If you like, you can also submit feature requests and suggestions for improvement. I also accept pull requests.
      ---- INITIAL POST FROM 2019-05-25 ----
      I wanted to let you know that I am currently working on a new ProcessWire module that fully integrates the Snipcart Shopping Cart System into ProcessWire. (this is a customer project, so I had to postpone the development of my other module GroupMailer).
      The new module SnipWire offers full integration of the Snipcart Shopping Cart System into ProcessWire.
      Here are some highlights:
      simple setup with (optional) pre-installed templates, product fields, sample products (quasi a complete shop system to get started immediately) store dashboard with all data from the snipcart system (no change to the snipcart dashboard itself required) Integrated REST API for controlling and querying snipcart data webhooks to trigger events from Snipcart (new order, new customer, etc.) multi currency support self-defined/configurable tax rates etc. Development is already well advanced and I plan to release the module in the next 2-3 months.
      I'm not sure yet if this will be a "Pro" module or if it will be made available for free.
      I would be grateful for suggestions and hints!
      (please have a look at the screenshots to get an idea what I'm talking about)
       




    • By apeisa
      Update 31.7.2019: AdminBar is now maintained by @teppo. Modules directory entry has been updated, as well as the "grab the code" link below.
      ***
      Latest screencast: http://www.screencas...73-ab3ba1fea30c
      Grab the code: https://github.com/teppokoivula/AdminBar
      ***
      I put this Adminbar thingy (from here: http://processwire.c...topic,50.0.html) to modules section and to it's own topic.
      I recorded quick and messy screencast (really, my first screencast ever) to show what I have made so far. You can see it from here: http://www.screencas...18-1bc0d49841b4
      When the modal goes off, I click on the "dark side". I make it so fast on screencast, so it might seem a little bit confusing. Current way is, that you can edit, go back to see the site (without saving anything), continue editing and save. After that you still have the edit window, but if you click "dark side" after saving, then the whole page will be reloaded and you see new edits live.
      I am not sure if that is best way: there are some strengths in this thinking, but it is probably better that after saving there shouldn't be a possibility to continue editing. It might confuse because then if you make edits, click on dark side -> *page refresh* -> You lose your edits.
      ***
      When I get my "starting module" from Ryan, I will turn this into real module. Now I had to make some little tweaks to ProcessPageEdit.module (to keep modal after form submits). These probably won't hurt anything:
      if($this->redirectUrl) $this->session->redirect($this->redirectUrl); if(!empty($_GET['modal'])) $this->session->redirect("./?id={$this->page->id}&modal=true"); // NEW LINE else $this->session->redirect("./?id={$this->page->id}");   and...
      if(!empty($_GET['modal'])) { $form->attr('action', './?id=' . $this->id . '&modal=true'); } else { $form->attr('action', './?id=' . $this->id); // OLD LINE }  
×
×
  • Create New...