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 2

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 3

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?

  • Like 1

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.

  • Like 1

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.

 

  • Like 1

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 2
  • 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"}

 

 

  • Like 1

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

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

Share this post


Link to post
Share on other sites
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

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 joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
×
×
  • Create New...