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 Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...