Jump to content
MadeMyDay

Module: PageTableExtended

Recommended Posts

Perhaps read the documentation first: http://processwire.com/api/fieldtypes/images/

As I said: If your image field is called "myImageField" (I actually don't know how you called it, you mix a lot of names up there ;) ) and is set to a single image, you have to wrap in an image tag: 

<img src='{$myImageField->url}' alt=''>

The code I posted originally was my template. That only fits if you name your fields likewise. This only should demonstrate how that thing works. Your fields are probably named different, so you have to adjust your templates.

Share this post


Link to post
Share on other sites

A small sidenote request:

I think it would be really great if you or someone else could supply eventually a basic set of demo templates for this module.

Nothing fancy, no css, just the proper php and markup with maybe a few comments where to put what.

Thanks for your consideration

Share this post


Link to post
Share on other sites

Nope, I used only my correct image field names.

I read about outputting images before and used this already extensively on a recent website.

Thanks to PW I already made friendship with include, echo, foreach, if, get, and quite a few more, but I saw nowhere a tutorial about using fieldnames in curly brackets  {$image_1->url}. Are these special module tags or just plain php?

Anyway, thanks for your input so far.

Maybe I'll start fresh all over in a few days and see if it gets better somehow.

Share this post


Link to post
Share on other sites
but I saw nowhere a tutorial about using fieldnames in curly brackets  {$image_1->url}. Are these special module tags or just plain php?

No, this is plain PHP. Since 5.3. I think and if short tags are activated in php.ini, which it is mostly. So <?php echo $var; ?> is the same as <?= $var ?>  is the same as echo "$var". Double quotes are necessary, echo '$var' won't work. The curly brackets are for encapsulating object references or functions. echo "$image->url" won't work, while echo "{$image->url}" will.

Share this post


Link to post
Share on other sites

I have a fresh install (PW 2.5.3) and wanted to try out this module (version 0.2.0, installed through ModulesManager), but I keep getting this error: 

Error: Call to a member function of() on a non-object (line 101 of /Volumes/schijf/Users/eelke/Documents/Werk/Server/vida/site/modules/FieldtypePageTableExtended/InputfieldPageTableExtended.module) 
This error message was shown because you are logged in as a Superuser. Error has been logged.

My configuration is really simple:

- Template "Slide"

- Field "title"

- Field "image" (single image field)

 

- Template "Home"

- Field "title"

- Field "slideshow" (PageTableExtended, set to select "Slide" templates)

 

- For testing purposes "Slideshow"'s Table fields has been set to just include the Title column

- No extra CSS / other templates location has been set

- A stand-alone page using Slide works fine

- When disabling the "Render Layout instead of table rows?" option everything works fine

This is the complete Slide template (no header/footer is added) :

<?=$page->title?><br>
<?=$page->image->url?>

(Expected behaviour here is of course not to see the image rendered, but to get the filename).

Share this post


Link to post
Share on other sites

Please grab a new copy / checkout the branch again. Or just delete line 101, it made more trouble than had benefits ;)

Share this post


Link to post
Share on other sites

Good news everyone, I figured out what's going on here.

My problem only occurred when there were no pages linked. 

I could bypass the problem by first adding a slide, and only after that turning on the Render Layout toggle. 

Turns out the problem lies on line 101 as per warning, as this bit is outside the foreach-loop that defines $parsedTemplate.

       $parsedTemplate->page->of(false); // set OutputFormatting back to false, just in case

Moving this line to line 90 (inside the foreach) fixed it. 

Share this post


Link to post
Share on other sites

MademyDay, this is a fantastic addition to the sytem, thanks for all your hard work.

Just a question, do you personally see this more as something where you'd try and fully replicate your front-end output or just a means of displaying things in the backend in a more pleasing way? (I guess answer is probably both...)

Share this post


Link to post
Share on other sites

Thx André.

Just a question, do you personally see this more as something where you'd try and fully replicate your front-end output or just a means of displaying things in the backend in a more pleasing way? (I guess answer is probably both...)

yep, both ;) My initial need for this was to have a possibility for clients to mix different layout templates. PageTable does exactly that while keeping the flexibility of normal templates. So the functionality was there but for not so tech-savvy clients it was too less visual. They want to see what they create. So this module was born. It is now your decision if you want an exact 1:1 copy of the frontend which results in more work but a nicer Interface or if you just want them to keep track of their edits/additions. I use the module in three sites at the moment (not public yet but one is shown in the video above). I generally wouldn't promise a 1:1 view of the frontend because clients then tend to "style" the content by themselves.  I have one client who always tries to fit the length of text lines in two columns. If the interface would kind of promise to be an 1:1 copy of the frontend (which it NEVER can be) it would be a false safety so I'd rather suggest to keep the layout model in this module but make no promises about exact styling.

  • Like 2

Share this post


Link to post
Share on other sites

Got a wee problem here.

If I use This in a template

<?php

if($options["pageTableExtended"]){

echo "<h3>{$page->headline}</h3>";

} else {

// load of other stuff

}

It is not rendering the headline field.

If I remove the IF then it works.

Turning debug mode on in the admin gives me:

Notice: :  Undefined index: pageTableExtended in /home/joss/public_html/site/templates/image.php  on line 3

What I do wrong?

Share this post


Link to post
Share on other sites

Hey Joss,

sorry, totally oversaw your posting. Could you give some more information (more code)? Not sure why the error is given in the image.php...

Share this post


Link to post
Share on other sites

Oh, damn - I am going to have to go back and look. I have been working on some D&B arrangements and got sidetracked (at my age too!)

Share this post


Link to post
Share on other sites

Okay, I have a template called image.php that is used for creating a page with a single image and things like description and a load of rubbish.

However, these pages are really there to make up a gallery using Page Table Extended - but they have their own template file so they can be seen outside of the gallery on the site. Nothing complicated.

The template had headers and footers and tons of rubbish that is no good for page table extended, so have I use your thing:

<?php

if($options["pageTableExtended"]){

/* The gallery images are used in a page table extended in admin.

We cant display those with all the head and foot!

So in this section we do an alternate markup

*/

echo "<h3>{$page->headline}</h3>";


} else {

/* Back to the normal markup */

include("./includes/head.inc");


include("./includes/scripts.inc");

include("./includes/foot.inc");

}

But, when I go and look at the page in the admin that used the page table extended field, it does not display the headline, but just the error as above. 

I haven't added all the other fields yet, I am keeping it simple just to get it working.

Boy, this rioja is good!

Share this post


Link to post
Share on other sites
Boy, this rioja is good!

Man, this Cabernet, too! And you are totally right. It obviously doesn't work with the current version. Seems I broke too much last time when merging stuff. Will take a look and report back (but not tonight, see first 4 words of this posting) :)

Share this post


Link to post
Share on other sites

Fair enough - I have, ummm, other things to do right now anyway....  :-[

Share this post


Link to post
Share on other sites

I also see that NOTICE. With using isset I got it go away. Not sure your switch still works with isset, I did not code the front end output yet.

By the way: what is the recommended way to output the content? 

I am really fallen in love with this extended module. I see the huge benefits. Very smart.

I want to use ist that way - like in the example movie - that the pagetable elements render as inluded "blocks". Like the repeater field did it.

masterpage

- block

- block

Do you have a code example? I am curious how $page works in that context (does it refers to masterpage or block)...

And how does the find work - does it find the masterpage if the searched for content is in a block?

(Too bad that there is no full example/tutorial online yet - I found only fragments of explanations spread all over the forum.)

Share this post


Link to post
Share on other sites

Update:

rendering is so easy I could not believe it. The code worked for me (in case anyone has the same question):

foreach ($page->my_pagetable as $block) {
$block->render();
}

Now I could see for myself:  isset makes the NOTICE go away but the clever switch trick from Joss does not work either. :(

EDIT:

This switch seems to work for now:

<?php if(strpos($_SERVER['REQUEST_URI'],wire('pages')->get(wire('config')->adminRootPageID)->url) !== false) : ?>

Credits to Nico

Share this post


Link to post
Share on other sites

I tried to update from 0.2.0 to 0.2.2 and have an issue: "Path to Templates" does not work as before.

I have a template directory "controllers/", which contains a template called "image-text.php". The "image-text.php" template has set "router.php" as alternative template name.

With 0.2.2, if I try to edit the page which has the pagetable field, I get the message

TemplateFile: Filename doesn't exist: [...]/site/templates/controller/router.php"

Sure, should be "[...]/site/templates/controller/image-text.php

If I comment out line 50 in 0.2.2 and insert

$parsedTemplate = new TemplateFile($this->config->paths->templates . $this->pathToTemplates  . $p->template->name . ".php");

(the line 50 from 0.2.0) all is well again.

Share this post


Link to post
Share on other sites

adrianmak,

Have you installed this and given it a try? It's fairly straightforward (and really cool). 

Share this post


Link to post
Share on other sites

First: thx for the great module, I can scrap my first attempt to something similar!

Second: are there any thoughts on adding an option to add an already existing 'page' to the PageTableExtended field in the admin.

Since I build a type of 're-usable widgets' for my client, they want to re-use already created 'pages', thus re-using content.

Right now you can only create new 'pages', or I missed something along the way? :-)

I might dive in myself and see if I can add that myself, if time will let me, but I wonder how many others might consider this a welcome addition?

And should that become a PageTableExtendedExtension or a new version of PageTableExtended

Share this post


Link to post
Share on other sites

First: thx for the great module, I can scrap my first attempt to something similar!

Second: are there any thoughts on adding an option to add an already existing 'page' to the PageTableExtended field in the admin.

Since I build a type of 're-usable widgets' for my client, they want to re-use already created 'pages', thus re-using content.

Right now you can only create new 'pages', or I missed something along the way? :-)

I might dive in myself and see if I can add that myself, if time will let me, but I wonder how many others might consider this a welcome addition?

And should that become a PageTableExtendedExtension or a new version of PageTableExtended

Have a read of this thread about the main PageTable field: https://processwire.com/talk/topic/8177-page-table-howto/

It is possible to automatically add existing pages if they are under the same parent. If they aren't then you can add them with a small bit of API code which Macrura shows in that thread.

Hope that helps!

Share this post


Link to post
Share on other sites

Hey,

the green buttons at the end of the Table: why theres not displaying the template-name (in your screenshot)?

I'd like to have something too, because users want to see something like "Text with to columns" instead of "layoutbox-text-columns_2".

How this works? Is there a solution in processwire, also for "Add New"-Elements.

Thank You!

qualtext

git1.jpg

Edited by Qualtext

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no JavaScript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode. There are 4 different view modes.
      View mode "Day" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...