Settings Factory

[gornycreative]

On 10/5/2020 at 8:26 AM, gmclelland said:

@gornycreative - If you are using Cloudflare - you may want to set some rules as seen here:

 

That's good. I was early on with cloudflare and have only recently gotten back into it to see how incredible their platform has grown to.

I had a pull the levers push the buttons fire drill prior to core updates but it looks like this may help that situation a lot! Thanks.

[webaff]

Hi,

can we use field sets to structure our settings gui?
What would the JSON syntax for InputfieldFieldset look like?

Thanks

[Macrura]

There should be examples of fieldsets defined in the samples folder, but using PHP. I don't think you can do fieldsets fro JSON defined settings, but the tabs fieldsets example shows "Advanced Settings" which are each in a fieldset.

[webaff]

Thank you @Macrura for your pointing me to the PHP sample.

[netcarver]

Hi @Macrura just trying this out (yeah, I know I'm late to the party) and it works great. I have just put in an issue on github for your consideration.

[Macrura]

thanks - i saw that, and commented over there.

[Ivan Gretsky]

@adrian, could you please share the way you use Image Reference inputfield with Settings Factory as you mentioned earlier in this thread?

[wbmnfktr]

Maybe I've said it somewhere before but this is such a nice timesaver, which is also transportable through projects. Great addition.

Thank you @Macrura!

[Clarity]

Hello, @Macrura!

When I use .php file, I get an error: 'Cannot instantiate abstract class ProcessWire\Inputfield'. Can you please tell me how I can overcome this error?

[Macrura]

@Clarity

Can you post the contents of your PHP file?
Are you using any namespace?
What version of ProcessWire are you on?

There is an example settings file in the module, you can copy to your templates folder somewhere and then specify that file for the settings. If that file doesn't work, then something must have changed in the core. It works for me under PW 3.0.178.

[Clarity]

Thank you! Finally, I found the root of the problem. I didn't add "return $inputfields;" to the end of file.

 

I'm not using a namespace explicitly. ProcessWire version is 3.0.199 dev, and everything works fine now.

[Macrura]

53 minutes ago, Clarity said:

Thank you! Finally, I found the root of the problem. I didn't add "return $inputfields;" to the end of file.

I'm not using a namespace explicitly. ProcessWire version is 3.0.199 dev, and everything works fine now.

awesome! Thanks for using the module - hope it helps and is useful!

[Clarity]

Hello, @Macrura!

Haven't you added the possibility to handle repeaters with this module with updates? I've read at the beginning that it was impossible, but something might change with time.

[Macrura]

@Clarity - Settings Factory should technically support what any module config would; i've never seen repeater fields used in a module config screen, probably because repeaters require the use of hidden pages. So for now this module would need to stay limited to those fields whose values can be stored in text/json;

[Clarity]

Thank you about the information! Can you please tell whether it is possible to use ProField: Multiplier for this module? I'm getting an error "ProcessSettingsFactory: Fieldtype is not set".

[Macrura]

On 7/15/2022 at 10:04 AM, Clarity said:

Thank you about the information! Can you please tell whether it is possible to use ProField: Multiplier for this module? I'm getting an error "ProcessSettingsFactory: Fieldtype is not set".

when you do the code to add it, you would need to specify the Fieldtype to multiply, so that needs to be one of the options,

'fieldtypeClass': 'FieldtypeText' in the json or wherever...

(haven't tested this, but looking at the module, it does need the "fieldtype to multiply" to be expressly set)

[Clarity]

Thanks for the advice, but it doesn't work for me. The error remains the same. My settings/settings.php is like that:

<?php

 

$inputfields = array(

    array(

        "name" => "emails",

        "label" => "Emails",

        "type" => "InputfieldMultiplier",

        "fieldtypeClass" => "FieldtypeText",

        "schemaClass" => "FieldtypeText",

        "qtyMin" => 3,

        "qtyMax" => 6,

        "width" => "100",

        "description" => "",

        "collapsed" => 0,

        "placeholder" => "",

        "columnWidth" => 50

    ),

    array(

        "name" => "phones",

        "label" => "Phones",

        "type" => "InputfieldMultiplier",

        "fieldtypeClass" => "FieldtypeText",

        "schemaClass" => "FieldtypeText",

        "qtyMin" => 3,

        "qtyMax" => 6,

        "width" => "100",

        "description" => "",

        "collapsed" => 0,

        "placeholder" => "",

        "columnWidth" => 50

    )

);

 

return $inputfields;

 

Can you please say what I'm doing wrong?

[Macrura]

I have no idea if it will work – module config fields can't use a database table, they have to be able to store in JSON, so it would take some research and experimentation to see if it is even possible to use this field type in a module config. So setting schemaClass would have no effect.

Most module configs that use repeatable interfaces are done with custom javascript, as far as I have seen. (For example use a text field for the first one, and then a hidden field to store the repeatable values; use JS to allow the users to add an inputfield, and then join all of the values together in pipe delimited hidden field..)

[froot]

I have a weird issue, some values aren't saved. There is no error or whatever, it actually says: Saved: Einstellungen (that's the name of my page), but after saving, the field is empty again. The same file (the php file with all the custom fields that is needed for the settings-factory to work) works on a different PW installation, but not here. Any ideas why?

EDIT: I uninstalled and reinstalled the module, now not one value gets saved on my custom settings factory page. Still with no error, just the success message: Saved: Einstellungen

Might that have to do with some php settings? Thanks for help!

[Macrura]

Hi @fruid - sorry to hear about this! Could you send me the PHP file to have a look at it? Also let me know your PW, PHP and MySQL versions and i'll take a look. You never know, something could have changed with the PW version or PHP 8, and we need to make sure this module keeps working!

- Marc

[froot]

58 minutes ago, Macrura said:

Hi @fruid - sorry to hear about this! Could you send me the PHP file to have a look at it? Also let me know your PW, PHP and MySQL versions and i'll take a look. You never know, something could have changed with the PW version or PHP 8, and we need to make sure this module keeps working!

- Marc

hi, thanks for getting back, I think I know where the issue is, I posted about it somewhere before. The issue must be, that my page using the SettingsFactory-process is hidden. If it's hidden, it cannot save values, only if it's unhidden it can save.

[Macrura]

Thanks - i will check and see if this can be fixed, or I'll add info to the instructions about hidden pages.

[gornycreative]

This module has been very useful. As I have been playing around more with module configurations for my own work I have started using $wire->file methods to find files and populate options for dropdowns for my modules.

Regarding Settings Factory, I have set manual select options in the past, but it would be great to know if logic can be placed in the settings file to generate options using wire objects.

I realize the PHP style settings factory configuration file uses InputfieldWrapper, etc. The settings file itself isn't namespaced and doesn't seem to instantiate anything. $wire->file itself, in the context of the settings file, seems to be null.

Are there any objects available to use to manipulate file via the wire object (find files, grab config paths), or would I need to write those functions with php?

Have you used logic to dynamically build select options?

Thanks again! ~J

[Macrura]

@gornycreative can you post a link to some info about the $wire->file methods? - i couldn't find it in the docs and haven't had time to go look at the core source code.

-marc

 

[gornycreative]

@Macrura sorry I meant $wire->files... I did end up finding a way to do what I needed to although I came across a few interesting issues that I can't really explain.

The functions were from a module context, so I had to pull them abstract them away from $this and just tried to manipulate them directly, since it seemed like a $wire object should still exist.

When I ran a db($wire->files) the bar dump said that this did represent a WireFileTools object, but the find() method was faulting, saying that the object was null when I tried to use $wire->files->find($something, $somewhere). Are the API helpers only available in certain contexts?

What I ended up doing was the following:

First, I brought my functions into a separate _theme_fn.php file. If I included them in the main Inputfields generating file, I got a cannot redeclare error, perhaps the settings factory config file is iterated in some way. I put both my settings factory config file and the external functions file in the PW namespace.

Second, in the external functions file I brought in a $wf = wire('files') and $wc = $wire('config') to the functions which allowed me to grab default paths, run the file searches and create the appropriate select options arrays.

Third, in the main settings factory file, did an include_once on the functions file and then I just set variables to call those functions and then inserted that into options.

This lets me generate select options arrays dynamically.

If you want a concrete example, let me know.

It is hard for me to determine sometimes whether I am able to use an API variable or have to actually call functions to create my own object on the customization side. Front end side and modules seem much clearer.