Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

On ‎01‎.‎09‎.‎2014 at 2:44 PM, MadeMyDay said:

Extends the Processwire PageTable field for rendering table row layouts

Where can i find the PageTable field?

Thanks, Felted

Share this post


Link to post
Share on other sites
Just now, felted said:

Where can i find the PageTable field?

Thanks, Felted

Should be in core distribution. But you have to install it first. It is called "ProFields: PageTable" afair.

  • Like 2

Share this post


Link to post
Share on other sites

Hello,

first time using PageTableExtended so far so good. I've created three diferent layouts with three diferent template files and I'm showing a list of all items on a parrent page with

<?php 
foreach($page->storitve_pagetablext as $pe){
  echo $pe->render(); 
} ?>

So what I would like to do is open each item in a different template (same template for all items) like (read more button) , can this be done somehow? Not in a layout given in PTE.

one of my layouts looks like this, expl.:

<div class="col-lg-5 col-xs-12">
   <div class="ro-service-1-item ro-service-1-v clearfix">
     <div class="ro-image ro-left"><img src="<?=$page->images->first->url?>" alt="service" class="img-responsive"/></div>
       <div class="ro-content">
         <h3 class="ro-hr-heading"><?=$page->title?></h3>
           <div class="ro-bgc-trans-5"><?=$page->body?><a href="<?= $page->url ?>" class="ro-more"><i class="fas fa-arrow-right"></i></a></div>
      </div>
    </div>
</div>

So my <?= $page->url ?> links to this template, I'd like to use diferent template for this. Hope you understand. Something like blog opening a detail page.

Thank you

R

Share this post


Link to post
Share on other sites

Sorry, I don't get it. You three different layouts for PTE, so far so good. Now you wanna do what? The read more link to a different page should point to a different template? Why not? For that URL the detail page template is used, isn't it?

  • Like 1

Share this post


Link to post
Share on other sites
1 minute ago, MadeMyDay said:

Sorry, I don't get it. You three different layouts for PTE, so far so good. Now you wanna do what? The read more link to a different page should point to a different template? Why not? For that URL the detail page template is used, isn't it?

hello,

with:

<?php 
foreach($page->storitve_pagetablext as $pe){
  echo $pe->render(); 
} ?>

I'm showing all my pages in one template like teasers. Just some small teaser text. I have some other fields added in PTE that are not shown here. So in the bottom of every item (layout) I have read more button with link "<?= $page->url ?>" wich opens the templates assigned to TPE that I don't want. I need to create another template (services-details) wich will fetch all the fields from this specific page (layout), hope u unerstand.

Here is the link to the site so you wil know what I mean.

LINK

You will se the "Beri več ->" link ... that should point to diferent template but would fetch fields from only that layout.

Thank you

R

 

Share this post


Link to post
Share on other sites

Could you explain the use case for me? Why are those fields not filled in the details template and you just pull them to the PTE template? So the PTE template for example just consists of a page select field. You select a page and the PTE template renders the information pulled from that page.

Share this post


Link to post
Share on other sites
8 minutes ago, MadeMyDay said:

Could you explain the use case for me? Why are those fields not filled in the details template and you just pull them to the PTE template? So the PTE template for example just consists of a page select field. You select a page and the PTE template renders the information pulled from that page.

not sure I follow, what you need here :undecided:

I want link to point to new "detail" template but contans fields from clicked page.

Share this post


Link to post
Share on other sites

I think you mix up things and usecases.

You wanna have a overview page like in your link - and you wanna details pages for every entry?

So you even don't need a PTE setup here.

just use a pagetree for this elements and set the templates for /storitve/ and /storitve/detail_what_ever/ and you are ready.

Editor only have to add pages under this tree - the short teaser is generated automagically no need for PTE here....this time.

regards mr-fan

if you wanna stick to your way you could check if you are on the overviewpage or on the PTE element page itself (check for $page->parent or page->id)...

Share this post


Link to post
Share on other sites

I guess you are talking about the

Quote

Pri nas si lahko pričeske uredijo vsi željni profesionalnega videza. Gospe, gospodje ali otroci, dobrodošli so vsi, ki dajo kaj nase. Imate željo po pričeski iz fotografije? Prinesite fotografijo in domov boste odšli s popolnoma enako, morda še lepšo. Dobrodošli! ;)

block and the corresponding detail page.

You seem to put the text in the pte template. Why not put a page select field to the pte template and put the content of that textblock where it belongs, to the detail page (let's call it "summary"). Assuming your detail template is "detail" and the pte template is "pte_textblock".

Add a page select to pte_textblock named "linkedPage". So in your pte_textblock template you have access to the fields of the detail page via

$page->linkedPage->summary and also to the read more destination via $page->linkedPage->url.

 

Ring a bell? ;)

 

  • Like 1

Share this post


Link to post
Share on other sites
On 7/4/2017 at 10:22 PM, DV-JF said:

I figured out a new problem:

I'm using repeaters in the layout template in order to give the editor the possibility to define some "same looking" boxes. Inside the repeaters there is amongst other things an image field. When I'm trying to resize it via the API like 


foreach($page->rep_imgTitleBody as $item) {
	$img = $item->sing_img->size(600,400)->url;
	$out = "<img src=\"{$img}\" alt=\"{$item->title}\">";
};

 

though it works on the frontend but in processwire backend I'm getting an error:

 

Any ideas?
 

2017-07-04 22_21_14-Edit Page_ Home • vieregg-design.de.jpg

I have the same problem when resizing images with the api.
Doing this, did not solve it for me:

$item->block_image->first()->size(100)->url

edit: it works when I set the image field as an array and loop through it.
but this is not ideal in my use case.

I would like to keep the field as an single image field, so the client can simply change the image by replacing an existing one.
This was also a suggested solution, but Iam not sure where I have to put this (inside my template for the pagetable items?):

<?php namespace ProcessWire;

if ($page->pageReference) {
    $refPage = $page->pageReference;
    $img = $refPage->image;
    echo $img->url;
}

 

Share this post


Link to post
Share on other sites

I have managed to build a pagebuilder with blocks using PageTableExtended.
Its working well and the customer is very happy with the look and usability.

All the pages that are created with my PageTable are living under
admin–>siteparts

Now I tried to make the blocks reusable on other pages using the PageReferenceField.
The problem is, the parent, where the pages from my PageTable are living, is set
to not be viewable by guest users to prevent these pages from being viewable on the frontend. 
Now they only show up on the Frontend when Iam logged In.

How can I prevent those pages to be accessed by URL, but
still be able to include these pages with the PageReferenceField?

Share this post


Link to post
Share on other sites
1 hour ago, jploch said:

How can I prevent those pages to be accessed by URL, but
still be able to include these pages with the PageReferenceField?

When a page is rendered by another page PW populates a "stack" of pages that called render in an $options variable. See Ryan's comment:

So if a page is accessed directly and not rendered by another page then the page stack will be empty (in fact the $options variable will not be set). So you can put the following at the top of template files that should not be directly viewable but only rendered as part of another page:

if(empty($options['pageStack'])) throw new Wire404Exception();

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

@Robin S
Thanks you are the best! works great!! 

Edit:

While these pages now redirect to a 404 page,
all pages using my pagetable block with the redirect stopt showing up in admin.
showing a red error message saying The process returned no content.
And the whole page is empty with nothing to edit. 😞
–––––



The next cool addition would be a way to clone block items.
Even nicer if these could be cloned to different pages as well and still be able to get edited on every page.

this is also discussed here:
But Iam not sure if I understand where to put LostKobrakai code or how to adapt this.

On 9/24/2014 at 4:30 PM, LostKobrakai said:

PageTables are handled the same as other pagefields. So you can just use something like this:


$selected_page = $pages->get("something"); // Get the Page
$selected_table_entry = $selected_page->table->eq(0); // Get the PageTable entry
$clone = $pages->clone($selected_table_entry); // Clone the entry

$new_page = $pages->get("something"); // Get the page to copy to
$new_page->table->add($clone); // Add the clone to the PageTable
$new_page->save();

 

Share this post


Link to post
Share on other sites
7 hours ago, jploch said:

While these pages now redirect to a 404 page,
all pages using my pagetable block with the redirect stopt showing up in admin.
showing a red error message saying The process returned no content.

I've never actually used this module, but looking at the module code I think this will work:

if(empty($options['pageTableExtended']) && empty($options['pageStack'])) throw new Wire404Exception();

 

  • Thanks 1

Share this post


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

I've never actually used this module, but looking at the module code I think this will work:


if(empty($options['pageTableExtended']) && empty($options['pageStack'])) throw new Wire404Exception();

 

That worked! Thanks for your help!

  • Like 1

Share this post


Link to post
Share on other sites

Hey Guys, first of all thanks for the awesome module!

I have two questions:
1) Do I have to create a php file for each template I integrate in the field or can I code it in the php file where I put the PTE field?
2) If I have a folder with many CSS like you can see in the picture, how should I proceed?

Thank you.
Have a nice day,

Michael

Capture.JPG

Share this post


Link to post
Share on other sites

My PTE is not working with markup regions

This post can be deleted.
My markup regions are working fine with PTE, I made a mistake in my code..

Share this post


Link to post
Share on other sites

I managed to render blocks from page reference fields inside PTE.
In my template for the page reference block I render the page like this:
$page->block_page->render();

But when I save the modal after I add/change a block I get the error and the changes only appear after I save the page with the regular Save button from the page:
Failed to ready module: FieldtypePageTable

This only happens if the PTE has a page reference block.
Any Ideas why this error is happening?

Share this post


Link to post
Share on other sites

Sorry, I never saw that error. 

Quote

This only happens if the PTE has a page reference block.

You mean a page reference field? I also use page reference fields a lot so this shouldn't be the root cause. Do you have an another PTE field active in that template? I know there might be problems if there is more than one PT/PTE field in one template.

Share this post


Link to post
Share on other sites
15 minutes ago, MadeMyDay said:

Sorry, I never saw that error. 

You mean a page reference field? I also use page reference fields a lot so this shouldn't be the root cause. Do you have an another PTE field active in that template? I know there might be problems if there is more than one PT/PTE field in one template.

Yes I mean page reference field.
There is only one PT/PTE field on the page.

When I remove the $page->block_page->render(); from the template for that block (with the page reference field), everything is working fine.
I use the page reference field to add blocks that where added to another page with PTE, so that the blocks can be reused on another page.
Hope that makes sense to you 🙂

Share this post


Link to post
Share on other sites

could you share some more code, esp. how you render the blocks in your template and how that specific block with the page reference looks like. Thanks!

Share this post


Link to post
Share on other sites

template for block with page reference field:

if($page->block_page) echo "{$page->block_page->render()}";

And on my template to render the site with PTE:

$content = "";
if(count($page->pagebuilder)>0){
     foreach($page->pagebuilder as $l){
         $content .= $l->render();
     }
}

include("./_main.php");

$content is a variable in _main.php where the whole markup for the site is rendert.

(All blocks for PTE are stored under admin->siteparts.
They are configured to automatically get a title)

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 bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/FieldtypeRockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support (please contact me via PM).
       
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
    • By adrian
      Hi everyone,
      Here's a new module that I have been meaning to build for a long time.
      http://modules.processwire.com/modules/process-admin-actions/
      https://github.com/adrianbj/ProcessAdminActions
       
      What does it do?
      Do you have a bunch of admin snippets laying around, or do you recreate from them from scratch every time you need them, or do you try to find where you saw them in the forums, or on the ProcessWire Recipes site?
      Admin Actions lets you quickly create actions in the admin that you can use over and over and even make available to your site editors (permissions for each action are assigned to roles separately so you have full control over who has access to which actions).
       
      Included Actions
      It comes bundled with several actions and I will be adding more over time (and hopefully I'll get some PRs from you guys too). You can browse and sort and if you have @tpr's Admin on Steroid's datatables filter feature, you can even filter based on the content of all columns. 

      The headliner action included with the module is: PageTable To RepeaterMatrix which fully converts an existing (and populated) PageTable field to either a Repeater or RepeaterMatrix field. This is a huge timesaver if you have an existing site that makes heavy use of PageTable fields and you would like to give the clients the improved interface of RepeaterMatrix.
      Copy Content To Other Field
      This action copies the content from one field to another field on all pages that use the selected template.
      Copy Field Content To Other Page
      Copies the content from a field on one page to the same field on another page.
      Copy Repeater Items To Other Page
      Add the items from a Repeater field on one page to the same field on another page.
      Copy Table Field Rows To Other Page
      Add the rows from a Table field on one page to the same field on another page.
      Create Users Batcher
      Allows you to batch create users. This module requires the Email New User module and it should be configured to generate a password automatically.
      Delete Unused Fields
      Deletes fields that are not used by any templates.
      Delete Unused Templates
      Deletes templates that are not used by any pages.
      Email Batcher
      Lets you email multiple addresses at once.
      Field Set Or Search And Replace
      Set field values, or search and replace text in field values from a filtered selection of pages and fields.
      FTP Files to Page
      Add files/images from a folder to a selected page.
      Page Active Languages Batcher
      Lets you enable or disable active status of multiple languages on multiple pages at once.
      Page Manipulator
      Uses an InputfieldSelector to query pages and then allows batch actions on the matched pages.
      Page Table To Repeater Matrix
      Fully converts an existing (and populated) PageTable field to either a Repeater or RepeaterMatrix field.
      Template Fields Batcher
      Lets you add or remove multiple fields from multiple templates at once.
      Template Roles Batcher
      Lets you add or remove access permissions, for multiple roles and multiple templates at once.
      User Roles Permissions Batcher
      Lets you add or remove permissions for multiple roles, or roles for multiple users at once.
       
      Creating a New Action
      If you create a new action that you think others would find useful, please add it to the actions subfolder of this module and submit a PR. If you think it is only useful for you, place it in /site/templates/AdminActions/ so that it doesn't get lost on module updates.
      A new action file can be as simple as this:
      class UnpublishAboutPage extends ProcessAdminActions { protected function executeAction() { $p = $this->pages->get('/about/'); $p->addStatus(Page::statusUnpublished); $p->save(); return true; } } Each action:
      class must extend "ProcessAdminActions" and the filename must match the class name and end in ".action.php" like: UnpublishAboutPage.action.php the action method must be: executeAction() As you can see there are only a few lines needed to wrap the actual API call, so it's really worth the small extra effort to make an action.
      Obviously that example action is not very useful. Here is another more useful one that is included with the module. It includes $description, $notes, and $author variables which are used in the module table selector interface. It also makes use of the defineOptions() method which builds the input fields used to gather the required options before running the action.
      class DeleteUnusedFields extends ProcessAdminActions { protected $description = 'Deletes fields that are not used by any templates.'; protected $notes = 'Shows a list of unused fields with checkboxes to select those to delete.'; protected $author = 'Adrian Jones'; protected $authorLinks = array( 'pwforum' => '985-adrian', 'pwdirectory' => 'adrian-jones', 'github' => 'adrianbj', ); protected function defineOptions() { $fieldOptions = array(); foreach($this->fields as $field) { if ($field->flags & Field::flagSystem || $field->flags & Field::flagPermanent) continue; if(count($field->getFieldgroups()) === 0) $fieldOptions[$field->id] = $field->label ? $field->label . ' (' . $field->name . ')' : $field->name; } return array( array( 'name' => 'fields', 'label' => 'Fields', 'description' => 'Select the fields you want to delete', 'notes' => 'Note that all fields listed are not used by any templates and should therefore be safe to delete', 'type' => 'checkboxes', 'options' => $fieldOptions, 'required' => true ) ); } protected function executeAction($options) { $count = 0; foreach($options['fields'] as $field) { $f = $this->fields->get($field); $this->fields->delete($f); $count++; } $this->successMessage = $count . ' field' . _n('', 's', $count) . ' ' . _n('was', 'were', $count) . ' successfully deleted'; return true; } }  
      This defineOptions() method builds input fields that look like this:

      Finally we use $options array in the executeAction() method to get the values entered into those options fields to run the API script to remove the checked fields.
      There is one additional method that I didn't outline called: checkRequirements() - you can see it in action in the PageTableToRepeaterMatrix action. You can use this to prevent the action from running if certain requirements are not met.
      At the end of the executeAction() method you can populate $this->successMessage, or $this->failureMessage which will be returned after the action has finished.
       
      Populating options via URL parameters
      You can also populate the option parameters via URL parameters. You should split multiple values with a “|” character.
      You can either just pre-populate options:
      http://mysite.dev/processwire/setup/admin-actions/options?action=TemplateFieldsBatcher&templates=29|56&fields=219&addOrRemove=add
      or you can execute immediately:
      http://mysite.dev/processwire/setup/admin-actions/execute?action=TemplateFieldsBatcher&templates=29|56&fields=219&addOrRemove=add

      Note the “options” vs “execute” as the last path before the parameters.
       
      Automatic Backup / Restore
      Before any action is executed, a full database backup is automatically made. You have a few options to run a restore if needed:
      Follow the Restore link that is presented after an action completes Use the "Restore" submenu: Setup > Admin Actions > Restore Move the restoredb.php file from the /site/assets/cache/AdminActions/ folder to the root of your site and load in the browser Manually restore using the AdminActionsBackup.sql file in the /site/assets/cache/AdminActions/ folder I think all these features make it very easy to create custom admin data manipulation methods that can be shared with others and executed using a simple interface without needing to build a full Process Module custom interface from scratch. I also hope it will reduce the barriers for new ProcessWire users to create custom admin functionality.
      Please let me know what you think, especially if you have ideas for improving the interface, or the way actions are defined.
       
       
    • By joshua
      ---
      Module Directory: https://modules.processwire.com/modules/privacy-wire/
      Github: https://github.com/blaueQuelle/privacywire/
      Packagist:https://packagist.org/packages/blauequelle/privacywire
      Module Class Name: PrivacyWire
      Changelog: https://github.com/blaueQuelle/privacywire/blob/master/Changelog.md
      ---
      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)
      - Functional
      - 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 data-attributes (data-type and data-category) are required 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>  
      I would love to hear your feedback 🙂
      CHANGELOG
      You can find the always up-to-date changelog file here.
    • By joshua
      As we often use Matomo (former known as Piwik) instead of Google Analytics we wanted to embed Matomo not only in the template code but also via the ProcessWire backend.
      That's why I developed a tiny module for the implementation.
      The module provides the possibility to connect to an existing Matomo installation with the classical site tracking and also via the Matomo Tag Manager.
      If you have also PrivacyWire installed, you can tell MatomoWire to only load the script, if the user has accepted cookies via PrivacyWire.
      To offer an Opt-Out solution you can choose between the simple Opt-Out iFrame, delivered by your Matomo installation, or a button to choose cookies via PrivacyWire.
      You'll find the module both in the module directory and via github:
      ProcessWire Module Directory MatomoWire @ GitHub MatomoWire @ Packagist ->installable via composer require blauequelle/matomowire I'm looking forward to hear your feedback!


×
×
  • Create New...