Jump to content

Mystique (Fieldtype, Inputfield) build dynamic fields and store data by using config file


ukyo

Recommended Posts

16 hours ago, bernhard said:

Hi @ukyo,

I've just tried your module for the first time, but unfortunately it does not find any resources! This is the tracy dump:

PWaFGFU.png

Somehow the resources array is empty:

lrcMVym.png

I have the following files in my setup:


C:\laragon\www\kaum\site\modules\Mystique\configs\Mystique.example-dive.php
C:\laragon\www\kaum\site\templates\configs\Mystique.mystique.php

No matter what I try - the resources select is empty:

sxXg2TJ.png

I've even tried to do a $config->paths->normalizeSeparators() on the path without success (thought it might be a windows issue).

Thx for your help!

Hi @bernhard

Can you try @next branch https://github.com/trk/Mystique/tree/next, this will be next version.

  • Thanks 1
Link to comment
Share on other sites

Thx @ukyo,

it is, as I thought, a windows problem. I've tried the "next" branch - no change. It works on my linux server. Would be great to get a fix for this.

As you can see in my screenshot the strange thing is that the FilenameArray is populated on line ~118 but it is empty on line ~174 (where the select field on the input tab of the pw field should get populated).

Link to comment
Share on other sites

On 1/24/2020 at 3:01 PM, bernhard said:

Thx @ukyo,

it is, as I thought, a windows problem. I've tried the "next" branch - no change. It works on my linux server. Would be great to get a fix for this.

As you can see in my screenshot the strange thing is that the FilenameArray is populated on line ~118 but it is empty on line ~174 (where the select field on the input tab of the pw field should get populated).

@bernhard i don't have a Windows PC and can't test it, Can you try to change ready function for next branch :

    public function ready()
    {
        $path = $this->wire("config")->paths->siteModules . "**/configs/Mystique.*.php";
        $path .= "," . $this->wire("config")->paths->templates . "configs/Mystique.*.php";
        
        foreach (glob("{" . $path . "}", GLOB_BRACE) as $file) {

            $dirname = dirname(dirname($file));
            $base = strtolower(str_replace([dirname(dirname(dirname($file))), "/"], "", $dirname));
            $name = str_replace([dirname($file), "/", "Mystique.", ".php"], "", $file);

            $this->resources[$base][$name] = $file;
        }
    }

with

    public function ready()
    {
        $path = $this->wire("config")->paths->siteModules . "**" . DIRECTORY_SEPARATOR . "configs" . DIRECTORY_SEPARATOR . "Mystique.*.php";
        $path .= "," . $this->wire("config")->paths->templates . "configs" . DIRECTORY_SEPARATOR . "Mystique.*.php";
        
        foreach (glob("{" . $path . "}", GLOB_BRACE) as $file) {

            $dirname = dirname(dirname($file));
            $base = strtolower(str_replace([dirname(dirname(dirname($file))), DIRECTORY_SEPARATOR], "", $dirname));
            $name = str_replace([dirname($file), DIRECTORY_SEPARATOR, "Mystique.", ".php"], "", $file);

            $this->resources[$base][$name] = $file;
        }
    }

 

Link to comment
Share on other sites

  • 2 weeks later...
  • 3 weeks later...

hi @ukyo replying to this comment: https://processwire.com/talk/topic/8960-fieldtypefonticonpicker/?do=findComment&comment=198140

It's definitely the glob() that's causing the problem. These are the paths created by your module:

image.png.9f055e442442eaad41e83f0e5ab7805d.png

I wanted to fork your next branch, but github throws a 500 error when forking at the moment. But I'm not able to fix it anyhow, because I don't understand your code. This is what I have so far:


    /**
     * @inheritDoc
     */
    public function ready()
    {
        $paths = [];
        $paths[] = __DIR__ . "/configs/";
        $paths[] = $this->wire("config")->paths->templates . "configs/";
        
        bd($paths);
        foreach($paths as $path) {
            $opt = ['extensions'=>['php']];
            foreach($this->wire->files->find($path, $opt) as $file) {
                bd($file);
                // $dirname = dirname(dirname($file));
                // $base = strtolower(str_replace([dirname(dirname(dirname($file))), "/"], "", $dirname));
                // $name = str_replace([dirname($file), "/", "Mystique.", ".php"], "", $file);
    
                // $this->resources[$base][$name] = $file;
            }
        }
    }

zPmefTc.png

I don't understand what you are doing with all those dirname() basename() calls... Maybe you want to use pathinto() instead?

bd((object)pathinfo($file));

Re9G1Mi.png

Looking forward to finally testing your module 🙂 

  • Like 2
Link to comment
Share on other sites

Thanks @bernhard, I updated module with same finder function used on FontIconPicker module. I am using dirname function for getting module or templates folder names from file path.

2080283130_EkranResmi2020-02-2719_11_54.png.bbe05c705c70c0d704e01bfd8bd310aa.png

"Example : Dive" is title of config,  "(mystique)" is name of module folder 

  • Like 3
Link to comment
Share on other sites

Finally 🙂 Thank you!

3X0kd9I.png

Should the images field from the example Dive be working? When I upload an image the field seems to work but when the upload is done, the field resets itself. All other field data is saved correctly. Any ideas?

Link to comment
Share on other sites

16 hours ago, bernhard said:

Finally 🙂 Thank you!

3X0kd9I.png

Should the images field from the example Dive be working? When I upload an image the field seems to work but when the upload is done, the field resets itself. All other field data is saved correctly. Any ideas?

Image & File fields are not supported yet, i will check these fields later. Feel free to play with module for add support 🙂

Link to comment
Share on other sites

Ok, thx! So why is that field in the example file? For me as an enduser the experience was: "Oh, wow, that even supports image fields! Let's try it! [uploading] Hm... Doesn't work - maybe another thing that isn't working on Windows due to path issues?" 🙂 

PS: When are you planning to merge NEXT into MASTER?

  • Like 1
Link to comment
Share on other sites

1 hour ago, bernhard said:

Ok, thx! So why is that field in the example file? For me as an enduser the experience was: "Oh, wow, that even supports image fields! Let's try it! [uploading] Hm... Doesn't work - maybe another thing that isn't working on Windows due to path issues?" 🙂 

PS: When are you planning to merge NEXT into MASTER?

 Next version merged with master branch. Image field removed from example 😞 sorry about that. Module updated.

  • Like 1
Link to comment
Share on other sites

  • 3 weeks later...

Hi, tried last version. Two Bugs:
 

1- When update module old module files renamed to ".Mystique" folder and this folder still listing "Resource" list and not shown in editor.
2- useLanguages also has bug. If admin language not default language, default language value not saved properly.  Default language value gets it's value from selected language.

 

  • Like 1
Link to comment
Share on other sites

22 hours ago, fliwire said:

Hi, tried last version. Two Bugs:
 

1- When update module old module files renamed to ".Mystique" folder and this folder still listing "Resource" list and not shown in editor.
2- useLanguages also has bug. If admin language not default language, default language value not saved properly.  Default language value gets it's value from selected language.

 

Module updated, CHANGELOG

  • Like 2
  • Thanks 2
Link to comment
Share on other sites

template overwrite field input settings has bug. Selected resource is saving properly but when shown all inputs empty.  

Checked db value, db has also default input resource and home page resource. Expect only home page values. (counts in below code).

 

{"title":"","checkbox":"","headline":"","summary":"","fieldset":"","fieldset_title":"","fieldset_description":"","another_fieldset":"","another_fieldset_title":"","another_fieldset_description":"","content":"","__json":null,"__name":"example-dive","counts":"888888888","__resource":"settings"}

 

 

  • Like 1
Link to comment
Share on other sites

2 hours ago, fliwire said:

template overwrite field input settings has bug. Selected resource is saving properly but when shown all inputs empty.  

Checked db value, db has also default input resource and home page resource. Expect only home page values. (counts in below code).

 


{"title":"","checkbox":"","headline":"","summary":"","fieldset":"","fieldset_title":"","fieldset_description":"","another_fieldset":"","another_fieldset_title":"","another_fieldset_description":"","content":"","__json":null,"__name":"example-dive","counts":"888888888","__resource":"settings"}

 

 

19 days ago, I created an issue. Waiting for fix or a solution. 

Link to comment
Share on other sites

10 hours ago, fliwire said:

maybe you can look SeoMaestro source code, not have this problem.

Module updated, can you check ?

Its look like adding same method to Fieldtype class solve the problem.

Link to comment
Share on other sites

tested: resource showing propery but with empy values.  In database field saved with default resource and template resource.

 

{"title":"","title1033":"","title1185":"","__json":null,"__name":"settings","__path":"D:\/Laragon\/www\/protest\/site\/templates\/configs\/Mystique.settings.php","video":"11111111","video1033":"22222222","video1185":"333333333","__resource":"settings"}

 

Link to comment
Share on other sites

4 hours ago, fliwire said:

tested: resource showing propery but with empy values.  In database field saved with default resource and template resource.

 


{"title":"","title1033":"","title1185":"","__json":null,"__name":"settings","__path":"D:\/Laragon\/www\/protest\/site\/templates\/configs\/Mystique.settings.php","video":"11111111","video1033":"22222222","video1185":"333333333","__resource":"settings"}

 

Will check it

Link to comment
Share on other sites

  • 2 weeks later...

Hi.

I had the same problem like @fliwire with changed resource property in template context not getting saved and outputted correctly.

I changed the FieldtypeMystique::getBlankValue() method a bit:

public function getBlankValue(Page $page, Field $field)
{
    return new MystiqueValue($page, $page->template->fieldgroup->getField($field,true));
}

API Ref: https://processwire.com/api/ref/fieldgroup/get-field/
With this change you are getting the field in context of the current page template. Then you have the correct resource filename in $field->resource.
This works here in my setup, but I haven't been able to test much for now. Hope this does not break something else.

Anyway, thanks for this module. Looks very promising!

  • Like 1
Link to comment
Share on other sites

  • 2 weeks later...
On 4/10/2020 at 2:18 AM, gingebaker said:

Hi.

I had the same problem like @fliwire with changed resource property in template context not getting saved and outputted correctly.

I changed the FieldtypeMystique::getBlankValue() method a bit:


public function getBlankValue(Page $page, Field $field)
{
    return new MystiqueValue($page, $page->template->fieldgroup->getField($field,true));
}

API Ref: https://processwire.com/api/ref/fieldgroup/get-field/
With this change you are getting the field in context of the current page template. Then you have the correct resource filename in $field->resource.
This works here in my setup, but I haven't been able to test much for now. Hope this does not break something else.

Anyway, thanks for this module. Looks very promising!

Suggested fix applied, module updated.

  • Like 3
Link to comment
Share on other sites

  • 2 weeks later...

Hello, @ukyo!

I absolutely love your module. And trying to incorporate it in my site-building workflow. I did install it without a problem and am using it for storing some output settings with great success)

But today I found two (probably, related) bugs:

  1. I cannot create a new Page Reference field. I am getting this error: "Call to a member function getField() on null" (...\Mystique\FieldtypeMystique.module.php:71).
  2. I cannot view a list of pages with certain template (see the screenshot). The error message is the same.mystique.thumb.jpg.660ef9911db96c02569fca6ff185eee0.jpg

Do you understand what it is?

Link to comment
Share on other sites

On 6/20/2020 at 11:44 PM, Ivan Gretsky said:

Hello, @ukyo!

I absolutely love your module. And trying to incorporate it in my site-building workflow. I did install it without a problem and am using it for storing some output settings with great success)

But today I found two (probably, related) bugs:

  1. I cannot create a new Page Reference field. I am getting this error: "Call to a member function getField() on null" (...\Mystique\FieldtypeMystique.module.php:71).
  2. I cannot view a list of pages with certain template (see the screenshot). The error message is the same.mystique.thumb.jpg.660ef9911db96c02569fca6ff185eee0.jpg

Do you understand what it is?

I fixed this error, but i can't update module on module directory. There is an error on module directory at the moment.

170864102_EkranResmi2020-06-2219_47_18.png.5a36b1b6e0d0dac0b8d9c74915008faa.png

You can update module by directly downloading it from Github.

  • Like 2
Link to comment
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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for creating a new measurement object from the sum or difference between two other objects. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.
      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      Screencasts
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      Exclusions
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
       
      https://github.com/Toutouwai/RepeaterEasySort
      https://processwire.com/modules/repeater-easy-sort/
×
×
  • Create New...