Jump to content
ukyo

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

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

Share this post


Link to post
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).

Share this post


Link to post
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;
        }
    }

 

Share this post


Link to post
Share on other sites

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 1

Share this post


Link to post
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 2

Share this post


Link to post
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?

Share this post


Link to post
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 🙂

Share this post


Link to post
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?

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites
7 minutes ago, ukyo said:

Image field removed from example 😞 sorry about that.

THX! Nothing to be sorry about! Was just a suggestion for an improvement 🙂 This looks like a fantastic module. I'm testing 🙂 

  • Like 1

Share this post


Link to post
Share on other sites

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.

 

Share this post


Link to post
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 1
  • Thanks 2

Share this post


Link to post
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"}

 

 

Share this post


Link to post
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. 

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
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.

Share this post


Link to post
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"}

 

Share this post


Link to post
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

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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • 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-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 ----
       
×
×
  • Create New...