Jump to content
Nico Knoll

MarkupSEO - The all-in-one SEO solution for ProcessWire.

Recommended Posts

HI Nico, thanks for the response. I was running 0.60, I upgraded to 0.8.2 and it seems to have fixed the issue.

Also in the google preview mode: if your URL is somewhat long will overlap on top of the Meta description. (it's a CSS issue, could always do a nowrap on the URL, or tuncate it, i'm not sure what google does.) just making you aware of the issue.

Great plugin, really liking the the ability to set character limits. Great work!

post-1913-0-09064000-1425315785_thumb.jp

Share this post


Link to post
Share on other sites

Thank you for the kind words. Could you add the issue on github?

Share this post


Link to post
Share on other sites

Hey Nico

The solution to the preview URL wrapping over the text below for your module is this code below:

span.SEO_google_link {
  position: relative;
  overflow: hidden;
  white-space: nowrap;
  background-color: #fff;
}
span.SEO_google_link:after {
  content: "";
  pointer-events: none;
  position: absolute;
  width: 50px;
  height: 100%;
  top: 0;
  right: 0;
  background-image: -webkit-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -moz-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -ms-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: -o-linear-gradient(right, #ffffff, rgba(255, 255, 255, 0));
  background-image: linear-gradient(to left, #ffffff, rgba(255, 255, 255, 0));
}

All credit to this guy who I've been working with for a while: https://processwire.com/talk/user/2562-jw/

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

at first, thanks a lot for this useful module!

I'm trying to figure out, how I can set the title for the homepage by hand, while using {title} - {sitename} automatically for all other pages. {title} - {sitename} automatically for all other pages is working fine, but the homepage shows always "Home | " before the sitename. Even though I have entered (under the homepage SEO tab) the title that I want, manually.  I prefer the sitename only for the homepage. I am sure that this can be easily solved somehow, but I don't get it :-/

Thanks for help!

Share this post


Link to post
Share on other sites

I would recommend you to turn off the SEO auto title function and do it yourself using the SEO parameters. Like this:

<title><?php echo ($page->id == '1') ? $page->seo->title : $page->seo->title.' - '.$config->seo->sitename; ?></title>

Share this post


Link to post
Share on other sites

Hi Nico,

thanks a lot for the lightspeed fast reply! What you recommend is working pretty fine! Thank you! :-)

  • Like 1

Share this post


Link to post
Share on other sites

Hi Nico,

First, thanks for this great module, nice job.

Just one thing about Open Graph metas : shouldn't it use <meta property> instead of <meta name> ?

Share this post


Link to post
Share on other sites

Hey people, 

i try to chose the SmartKeywords with an tags (page | multiplearray) field.

http://prntscr.com/7d7yi5

what i have to change that i get as Keywords the title of the choosen pages ? 

currently i have the id's in the code 

<meta name="keywords" content="1088|1091|1082|1083|1084|1085|1086">

where i have to make changes in the Module  ?

	// case 'keywords': 
					 	if($configData['keywords']) {
					 		$pageData['keywords'] = $configData['keywords'];
					 	} elseif($configData['keywordsSmart'] && $page->get(implode('|', $configData['keywordsSmart'])) != '') {
					 		$pageData['keywords'] = strip_tags($page->get(implode('|', $configData['keywordsSmart'])));
					 	}
					 break; 

or here 

// Default Keywords
		$field = $modules->get("InputfieldText");
		$field->name = "keywords";
		$field->label = __("Keywords");
		$field->description = "";
		$field->value = $data['keywords'];
		$field->columnWidth = '50%';
		$field->showIf = 'useParents=0';
		$fieldset->add($field);

		$field = $modules->get("InputfieldAsmSelect");
		$field->name = "keywordsSmart";
		$field->label = __("Smart Keywords");
		$field->description = __("We will use those fields (in this particular order) if you don't fill in the keywords field");
		foreach($fields as $selectField) $field->addOption($selectField->name);
		$field->value = $data['keywordsSmart'];
		$field->columnWidth = '50%';
		$field->showIf = 'useParents=0';
		$fieldset->add($field); 

Nobody an solution for me ?? 

Edited by iNoize

Share this post


Link to post
Share on other sites

Havent installed it yet, but is this module ready for multilingual sites?

Best regards

Share this post


Link to post
Share on other sites

@Juergen: Yes, most of it. If you install the module there is a short explanation on the bottom of the config page.

Share this post


Link to post
Share on other sites

I have the Title Format option set to

{title}, {sitename}

How would I make the module use a filed called 

Long_Title instead of title but only is Long_Title is set

I tried the following using a pipe

{Long_Title | title}, {sitename}

Share this post


Link to post
Share on other sites

Can someone assist with some SEO Module questions I have?

By default, the SEO tags are outputting by default just before the </head>.

I'd like them to render instead right after the opening <head>

If I want to choose exactly where they render, someone posted that this work

 <?php echo wire('page')->seo->render; ?>

On my site, this works but renders the SEO fields twice. In the default location (before the closing HEAD) and in the preferred position after the opening HEAD.

My second question is if the following (and only) How to use is still correct?

$page->seo // includes all the default values mixed with the page related seo data

// e.g.:
$page->seo->title
$page
->seo->keywords

// for rendering:
$page->seo->render

I might be doing this wrong but including any of the following renders nothing

<?php
echo $page->seo;
?>

or 

<?php
echo $page->seo->title;
?>

or
<?php
$page->seo->render;
?>

Thanks - appreciate it.

Share this post


Link to post
Share on other sites

Well 

<?php echo wire('page')->seo->render; ?>

or 

<?php

echo $page->seo->render;
?>

are the way to go. 

In your settings you can either enable automatically insertion of the meta fields (so you dont need to do this) or you can enable "manual" and then you will need this code (or you're rendering the tags in some other way)

Share this post


Link to post
Share on other sites

In your settings you can either enable automatically insertion of the meta fields (so you dont need to do this) or you can enable "manual" and then you will need this code (or you're rendering the tags in some other way)

Ah, thanks Nico. That was it :)

Share this post


Link to post
Share on other sites

Hallo,

till today I used version 0.3.0.

Now I have deleted this and replaced it with 0.6.0. Since this I miss the SEO-tab.

What makes the SEO-tab apear again?

Hi,

I have the same problem now after updating to Version 0.8.2.

After I have specified the templates no SEO-Tab apear again.

What can I do get my seo inputs again?

Share this post


Link to post
Share on other sites

@guenther55: Go to the settings page and select the templates that should get seo fields

Share this post


Link to post
Share on other sites

@guenther55: Go to the settings page and select the templates that should get seo fields

I did this and now I select an other page once more, but no Seo tab!

I got the same error as @Tyssen and I am not able to deinstall the modul!

My solution for now: in site/modul directory I reactivated the 0.3.0 Version - seo tab and all inputs are back! The old version works for me and I dont see really need to update.

But I hope you can find the bug and maybe I can update with a next Version in future.

Share this post


Link to post
Share on other sites

Did just PR the german translation of this great module...;)

https://github.com/Manfred62/pw-modules-lang-de/pull/1

proud to contribute with some translation.

One Feature request comes in my mind - that would be a nice to have - and for my installations i probably would challange this with some little hooks on page saving...and some hacking - but within the moduel it would be much better.

feature of the "smart" title|description would be:

->if some smart fields are set

-> that on first page publish

-> if no SEO fields are filled out by the user

->the smart title|desc should filled in the seo_ fields

 This has the benefit that the Google Preview would work and simple editors see what really would generated at frontend -> and they can improve this output with own entries in the seo_fields....

i think this would be a hook after page save and Page::statusUnpublished.....but i'm not so expirenced to edit such a complex module...i'm just able to hack a little bit with my (german: gefährlichem Halbwissen) ;)

regards mr-fan

  • Like 1

Share this post


Link to post
Share on other sites

some little example code how i hacked the "prefilling" option into the seo_fields from own content fields....if i've the time i transform it to a simple module with some settings for the fallback fields...what this code does:

it take a look only if a user publish a page and if seo_title , desc, keywords are filled....and if not it uses several text fields that the templates provide as an fallback that the seo_ entries not empty - so you think why - The smart settings in the module do that on frontend, too!

Yes but a editor that takes a look at the SEO Tab see it empty with some strange example text....and i wanna let see him what will be the output in frontend. I don't like empty fields while in frontend some magic works that nobody see at a first glance.

This is what i meant with - fill the "smart" things in the page fields if the user doesn't set them...or i'am thinking to complicated here?

regards mr-fan

code runs in admin.php - some functions for better striptags and some other functions to get the right output....

/**
 * Hook for changing seo_* fields if empty on Page Publish
 */

$pages->addHookAfter('saveReady', null, 'changeSeoFields');
function changeSeoFields(HookEvent $event) {
	$page = $event->arguments[0];
	//for this template only
	if($page->template == 'artikel'|| $page->template == 'seite') {
		// page is about to be published
		if($page->isChanged('status') && !$page->is(Page::statusUnpublished)) {
			// check if seo_title fields are exist and if they are empty
			if (!$page->seo_title) {
				//get the default value that would used as fallback
				if ($page->headline) {
					//Headline field is used for seo_title
					$default_title = ripTags($page->headline);
				} else {
					//Headline field empty - page title is used
					$default_title = ripTags($page->title);
				}
				//set seo_title on publishing
				$page->set ('seo_title', $default_title);
			}
			// check if seo_description fields are exist and if they are empty
			if (!$page->seo_description) {
				//get the default value that would used as fallback
				if ($page->kurztext) {
					$default_desc = ripTags($page->kurztext);
				} else {
					//is there a main content block as pagetable field pt_inhalt?
					if(count($page->pt_inhalt)>0) {
						//get the first text field in the pagetable and use it for the seo description
						$first_item = $page->pt_inhalt->get("template=part_text|part_text_image_left|part_text_image_right");
						$first_content = ripTags($first_item->text);
						$default_desc = wordLimiter($first_content, 160);
					}
				}
				//set seo_description on publishing
				$page->set ('seo_description', $default_desc);
			}
			// check if seo_keywords fields are exist and if they are empty
			if (!$page->seo_keywords) {
				//get the string that should be used to generate automatical keywords for this page
				//we use all textfields in the pagetable from the main content and collect them
				$keyword_texts = '';
				//is there a main content block as pagetable field pt_inhalt?
				if(count($page->pt_inhalt)>0) {
					foreach ($page->pt_inhalt as $keyword_text) {
						if ($keyword_text->title) $keyword_texts .= $keyword_text->title;
						if ($keyword_text->text) $keyword_texts .= $keyword_text->text;
						if ($keyword_text->text2) $keyword_texts .= $keyword_text->text2;
						if ($keyword_text->text3) $keyword_texts .= $keyword_text->text3;
					}
				} else {
					$keyword_texts = $page->headline.' '.$page->kurztext.' '.$page->title;
				}
				//rip tags
				$keyword_string = ripTags($keyword_texts);

				$default_keywords = extractKeywords($keyword_string);

				//set seo_title on publishing
				$page->set ('seo_keywords', $default_keywords);
			}
		}
	}
}

Share this post


Link to post
Share on other sites

Where I could find the echos in the module? For example if I want to change a meta tag name, maybe for example from <meta name="description" to <meta name="DC.description" ?

When I change

$field->name = "description";

in line 574 nothing happens.

I would not really change anything - regardless of it, would it be possible?

The module has no custom template, right?

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...