Jump to content
justb3a

Module: Image Extra

Recommended Posts

Hey @justb3a

I'm using your module together with matrix some repeaters fields at the moment and get the following notice:

Notice: Undefined index: title in C:\xampp\htdocs\intern\oneslider\site\modules\ImageExtra\ImageExtra.module on line 523

PW: 3.0.62 / ImageExtra: 1.0.6

Share this post


Link to post
Share on other sites
6 hours ago, mauricemoss said:

Hey @justb3a

I'm using your module together with matrix some repeaters fields at the moment and get the following notice:

Notice: Undefined index: title in C:\xampp\htdocs\intern\oneslider\site\modules\ImageExtra\ImageExtra.module on line 523

PW: 3.0.62 / ImageExtra: 1.0.6

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

  • Thanks 1

Share this post


Link to post
Share on other sites

I have a sudden problem with this module. The "Image extra fields" don't show up any more. Not on the Edit Page template, nor on the published page itself. There is the caption field enabled and two extra TextInputs. (see the attached image_extra_field_details.png) but they are not visible.

I have done this page for a library more than a year ago and they used it without a problem since then.

On the Page > Home -> Content ->  Edit (an item) which uses this module: there is only the image and a description field (like a normal image field) the other TextInputs are simply gone. (see the image_extra_field_page_edit.png).

Nobody has changed anything what so ever, I have checked the logs to be sure.

The page uses the Image Extra Module 1.0.0 and ProcessWire version 3.0.27

Any idea what the reason could be?

Thanks for any feedback.

P.S.

When I enable debug mode the only notice I get is :

Undefined index: vitrineimages in /home/bla/public_html/wire/modules/ImageExtra.module on line 826

but no error

The Admin->Modules->ImageExtra->Module information page shows:

Title Image Extra
Class ImageExtra
File /wire /modules /ImageExtra.module
Version 1.0.0
Installed 1 year ago
Summary Adds custom fields to image fields (including multi-language support)
Hooks To after.InputfieldImage::getConfigInputfields(), after.InputfieldImage::renderItem(), before.ProcessField::executeSave()
More Information https://github.com/justonestep/processwire-imageextra

 

image_extra_field_details.png

image_extra_field_page_edit.png

Share this post


Link to post
Share on other sites

Strange behavior in page select field: select links disappear immediately on hover.

Please help to fix!

 

Feb-10-2018-1_47-AM.gif

  • Like 1

Share this post


Link to post
Share on other sites

I have added an additional field called price, which starts with a $ symbol. Every time the page is saved, whether or not there is an output formatter set, an additional \ is added in front of the $ symbol, so if you save say five times you end up with \\\\\$

Share this post


Link to post
Share on other sites

After I installed this, I couldn't upload anything, all images failed to upload and the console output 

Failed to load resource: net::ERR_CONNECTION_RESET

for each. After uninstalling, image uploads work again

ProcessWire ver 3.0.89

Share this post


Link to post
Share on other sites
On 30.10.2017 at 9:35 PM, titanium said:

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

@justb3a

Same problem here with an image field in a repeater:

ErrorException: Undefined index: title in C:\laragon\www\XXX\site\modules\ImageExtra\ImageExtra.module:523

PW 3.0.95

Share this post


Link to post
Share on other sites

Hi.
I have a problem with the "link field" and PW 3.0.96 .
When I try to select a page (page tree) the "Choose" button disappears. Unfortunately it is no longer possible to make a selection.

Does anyone have the same problem or a quick solution for it?

I think the error is not the module, but the file "ProcessPageList.js"

Thanks,
Robert

  • Like 2

Share this post


Link to post
Share on other sites
On 3/24/2018 at 4:15 AM, ro-bo said:

Hi.
I have a problem with the "link field" and PW 3.0.96 .
When I try to select a page (page tree) the "Choose" button disappears. Unfortunately it is no longer possible to make a selection.

Does anyone have the same problem or a quick solution for it?

I think the error is not the module, but the file "ProcessPageList.js"

Thanks,
Robert

I'm on PW 3.0.104 and having the same problem.

Share this post


Link to post
Share on other sites
On 8/4/2017 at 1:50 PM, mr-fan said:

just tested with 3.0.65 and it seems that the pagelink field is not working?

imageextra.thumb.jpg.9ee7b8bd45060a8c970cea78bb8f1388.jpg

Best regards mr-fan

 

On 8/7/2017 at 5:22 PM, justb3a said:

Thanks @mr-fan: there was a little bug figuring out, whether the user is working in the backend or not (differentiate between int(0) und false :D ). The belonging JavaScript file wasn't loaded.

Hello, i am experiencing this problem as well. Unfortunately i have to consider myself an absolute beginner so i would be more than happy if someone could explain this solution in more detail. Thanks in advance!

Share this post


Link to post
Share on other sites

Sorry for spaming this thread but i am kinda stuck. As far as i understand this issue has fixed at some point. I only need a solution to apply image-links in pw and from what i read ImageExtra seems the way to go. It will work properly with image-fields but not within repeater-fields. I am using module version 1.0.6 with processwire 3.0.98. Any advise is highly appriciated. 😅

Share this post


Link to post
Share on other sites

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

Share this post


Link to post
Share on other sites
14 hours ago, alejandro said:

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

Are you by chance using the master instead of develop branch again?

Remember this was fixed on the develop branch:

 

Share this post


Link to post
Share on other sites
9 hours ago, adrian said:

Are you by chance using the master instead of develop branch again?

 

Yes, I upgraded to the latest version. Anyway, I've changed it to repeater field with image + page reference fields, so problem solved.

Share this post


Link to post
Share on other sites

Hey there,

I create all my fields with the Migrations module, so I create all my fields with the core functions.
Sadly, I'm having trouble creating "otherField" information with ImageExtra.

If I try this, the whole field is broken:

$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = "{\"cf_textformatter\":{\"copyright\":\"\"},\"cf_label\":{\"cf_label__copyright\":\"Copyright\"}}";
$myField->save();

Or with an array:

$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = [
	'cf_textformatter' => [
		'copyright' => ''
	],
	'cf_label' => [
		'cf_label__copyright' => ''
	]
];
$myField->save();

I always get this error:

ProcessWire: ProcessPageEdit: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_test_field.copyright' in 'field list'

 

Has anyone made any experience with this? Suggestions? 🙂

Thanks in advance!

Share this post


Link to post
Share on other sites
17 minutes ago, noodles said:

Hey there,

I create all my fields with the Migrations module, so I create all my fields with the core functions.
Sadly, I'm having trouble creating "otherField" information with ImageExtra.

If I try this, the whole field is broken:


$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = "{\"cf_textformatter\":{\"copyright\":\"\"},\"cf_label\":{\"cf_label__copyright\":\"Copyright\"}}";
$myField->save();

Or with an array:


$myField = $fields->get('test_field');
$myField->otherField = 'copyright';
$myField->otherFieldSettings = [
	'cf_textformatter' => [
		'copyright' => ''
	],
	'cf_label' => [
		'cf_label__copyright' => ''
	]
];
$myField->save();

I always get this error:


ProcessWire: ProcessPageEdit: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'field_test_field.copyright' in 'field list'

 

Has anyone made any experience with this? Suggestions? 🙂

Thanks in advance!

 

If I see it correctly, the "other field columns" will be added on a save hook via the $input->post data - which I don't have in my case.
In line 1213 it looks like I will have to alter the table in my script. 😞

Damn! 🙂 

Any sweeter way known by someone?

Share this post


Link to post
Share on other sites

I just pulled from the dev branch and still get the same error as before (right after new image upload)

$title = $language->title->getLanguageValue($language); // line 398

Call to a member function getLanguageValue() on string

And also: line 229-231: PHP Warning: stripos() expects parameter 1 to be string, array given

latest PW dev installed, PHP 7.2

Share this post


Link to post
Share on other sites

Hi there,

I set up the Image Extra Fields + multilang support. 

UNF the second language is not showing when switching to the other page language.
It always displays the default language.

Custom field name is "img_title";

Trying to output the field like this:

<?=$page->images->first()->img_title;?>

 

Share this post


Link to post
Share on other sites
On 7/19/2018 at 10:46 AM, alejandro said:

Hello,

I'm having the Select button disappearing, so I can't select anything. Is there a fix for this issue?

I'm using last version of the module.

Thanks!

 

Here is a little fix:

In your templates/admin.php add a custom css file:

$config->styles->add($config->urls->templates . "styles/admin.css");
require($config->paths->adminTemplates . 'controller.php'); 

in templates/styles/admin.css

.PageList .PageListItem:hover .PageListActions {
    display: inline-block !important;
}

Share this post


Link to post
Share on other sites

I really like this module. It's much cleaner for managing different alt-Text and caption than everything I tried before (extra fields, repeater, complex Hanna Code) but I ran into an issue on the second site I installed.

The image field I wanted to enhance was named Bilder (with uppercase). After adding extra field imgcaption the site stopped working and in debug mode it read something like field Bilder.imgcaption doesn't exist. After changing the field name to bilder (lowercase) and correcting my templates and Hanna Code everything worked again. Might be worth some warning in the documentation

  • Like 1

Share this post


Link to post
Share on other sites

I ran into an issue with multilanguage support.

Most sites I'm working need only one language, but for a german user interface I need the module Languages Support which automatically adds a description field for every language to an image field. I used to disable these extra language fields in the admin interface by setting disable multilanguage support in the input settings of the definition for my images-fields. After installing the Image Extra Module I added a caption field, which seemed to work fine: I could edit and process content of this new caption field.

Now I noticed that it is  possible to insert a new caption, but not to alter an existent one. I get a notice that the field was changed, but nothing happens. After checking the database I saw that there was a connection to multi-language support. Instead of a simple entry for new captions like "["Schloss Rheinsberg (Photo: xyz)"] an edited entry is like '{"0":"Das Refektorium","1019":"Das Refektorium"}'
When I enable multi language support for the image field I can see, that only changes in the field for the custom language (in my case german) are processed but do also change the value of the field in the default language (english) This is very confusing for authors.

As a workaround When changing the language of the admin to default instead of german everything works as expected.

Share this post


Link to post
Share on other sites
On 3/14/2019 at 3:18 PM, sujag said:

I ran into an issue with multilanguage support.

Most sites I'm working need only one language, but for a german user interface I need the module Languages Support which automatically adds a description field for every language to an image field. I used to disable these extra language fields in the admin interface by setting disable multilanguage support in the input settings of the definition for my images-fields. After installing the Image Extra Module I added a caption field, which seemed to work fine: I could edit and process content of this new caption field.

Now I noticed that it is  possible to insert a new caption, but not to alter an existent one. I get a notice that the field was changed, but nothing happens. After checking the database I saw that there was a connection to multi-language support. Instead of a simple entry for new captions like "["Schloss Rheinsberg (Photo: xyz)"] an edited entry is like '{"0":"Das Refektorium","1019":"Das Refektorium"}'
When I enable multi language support for the image field I can see, that only changes in the field for the custom language (in my case german) are processed but do also change the value of the field in the default language (english) This is very confusing for authors.

As a workaround When changing the language of the admin to default instead of german everything works as expected.

Yes we have also this problem. only solution is the workaround to set the users language to the default language 😞

Share this post


Link to post
Share on other sites
On 10/30/2017 at 9:35 PM, titanium said:

Hi @mauricemoss, there's already a PR for this issue here: https://github.com/justb3a/processwire-imageextra/pull/30

I hope @justb3a takes it into account for her next release.

I've got the same error here. I use the Image in a Repeater.

Is there any workaround at this time? Although the module works fine, to have an error is annoying.

Thanks for your help!

Share this post


Link to post
Share on other sites
On 3/16/2019 at 5:13 AM, MateThemes said:

I've got the same error here. I use the Image in a Repeater.

Is there any workaround at this time? Although the module works fine, to have an error is annoying.

Thanks for your help!

I have found a solution, that worked for me.

I just put in the module file at line 523 a isset statement:

/**
   * Hook format extra fields
   *
   * @param HookEvent $event
   */
  public function formatExtraValue(HookEvent $event) {
    $page = $event->arguments(0);

    if (!isset ($page->data['title'])) {
      $field = $event->arguments(1);
      $value = $event->arguments(2);
      $settings = $this->getOtherFieldSettings($field);

      if ($settings && $formatters = $settings->cf_textformatter) {
        foreach ($value as $v) {
          foreach ($this->additionalFields['other'][$field->name] as $otherField) {
            if (!array_key_exists($otherField, $formatters)) continue;
            $formatter = $formatters->$otherField;
            $currentValue = $v->$otherField;
            if ($formatter) $this->modules->get($formatter)->formatValue($page, $field, $currentValue);
            $v->$otherField = $currentValue;
          }
        }
      }
    }
  }

And this works for me.

 

Share this post


Link to post
Share on other sites
On 3/20/2019 at 6:39 PM, MateThemes said:

I have found a solution, that worked for me.

I just put in the module file at line 523 a isset statement:


/**
   * Hook format extra fields
   *
   * @param HookEvent $event
   */
  public function formatExtraValue(HookEvent $event) {
    $page = $event->arguments(0);

    if (!isset ($page->data['title'])) {
      $field = $event->arguments(1);
      $value = $event->arguments(2);
      $settings = $this->getOtherFieldSettings($field);

      if ($settings && $formatters = $settings->cf_textformatter) {
        foreach ($value as $v) {
          foreach ($this->additionalFields['other'][$field->name] as $otherField) {
            if (!array_key_exists($otherField, $formatters)) continue;
            $formatter = $formatters->$otherField;
            $currentValue = $v->$otherField;
            if ($formatter) $this->modules->get($formatter)->formatValue($page, $field, $currentValue);
            $v->$otherField = $currentValue;
          }
        }
      }
    }
  }

And this works for me.

 

This issue is solved, because the PR I submitted has now been accepted by @justb3a.

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 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-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 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 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • 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 If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...