Jump to content
adrian

Redirect Id Based Urls

Recommended Posts

This module redirects ID based URLs to the full SEO friendly URL
 
 
Very simple module that alllows you to link to pages with their page ID in the URL. The ID can be in any location in the URL.
 
There is a config option to simply load the content to the ID based URL, rather than redirecting to the original PW url if you prefer. If you use this option, the module adds a canonical link to the page to help identify the ID based URL as a duplicate of the proper PW url so Google won't penalize you for duplicate content.
 
For example you could do any of the following, where 1058 is the ID of the page you want to load:
 
At the moment for this to work, the page ID segment of the URL must be the only segment that is all numerical, otherwise, anything goes.
 
The reason for this module is mostly as a way to have a very simple shortlink to any page on the site, but it also allows for structuring URLs however you want with any content you want. I guess this could be abused and potentially bad for SEO!
 
I am not sure if this is a good way to do this, so I would definitely appreciate any feedback.
  • Like 5

Share this post


Link to post
Share on other sites

I thought of this already, but gave up on the idea because it allows anyone to start trying random numbers and get pages that you don't want accessible to everyone. One way of avoiding this would vbe to have a global checkbox field that you would have to check to activate the shortlink to that page.

Share this post


Link to post
Share on other sites

Hey diogo - I agree that could be an issue, but surely if pages are viewable then they will be indexed by search engines anyway. The module does check to make sure the page is not an admin page and that it is viewable for the user. Maybe that's not enough?

I'd be happy to add the checkbox idea though if you think that would help. Perhaps a "disable if checked" approach, or maybe a module config setting to change the behavior of the page specific checkbox - either check to enable, or check to disable, so there is the option to go either way.

Another option might be to require it to be enabled on a per template basis - an ASM field in the module config would allow you to specify templates that would work.

Edited by adrian

Share this post


Link to post
Share on other sites

The page is not indexed if there's nothing linking to it. I would have the links disabled by default at least and the checkbox to enabled them, and maybe the possibility of enabling by template (as you said) or by parent because it makes all the sense to enable all descendants of a page (articles page for instance). Like this, you could enable the links to all the site just by enabling the descendants of home. Or am I complicating? :)

Share this post


Link to post
Share on other sites

Hey Adrian, thanks for the Module, if I read that right, it looks like functionality I remember from Textpattern? If so then it was something I was trying to do (very poorly) in this thread, linked just in case it's any help (can't believe it will be tho ;))—actually that thread title is misleading, the post I was referring to was this one on that thread.

Edited by alanfluff

Share this post


Link to post
Share on other sites

IF this module ends up being is a goer (security implications sorted n'all) would it be possible to have some way in the admin of letting the user copy the short url to that page. I can see where this would come in handy for a site or two.

Share this post


Link to post
Share on other sites

@diogo - I have added support for limiting this functionality to only those selected templates (in the module config settings). I was also trying to add support for by page, but have come across a very strange thing - I can't seem to get an array of pages using wire('pages'). I get:

Trying to get property of non-object in /share/www/usaus-h2o-dev/site/modules/ProcessRedirectIds/ProcessRedirectIds.module on line 179

I have commented out this section of the code for the moment, but if you have any ideas why this isn't working, I'd love to hear them :)

@alanfluff - thanks for that link - I think this module will take care of what you are looking to do.

@Marty Walker - I have added a new tab to page edit screen in the admin called ShortLinks that lists a few key links for that page that the user might be interested in. The last example I give on that tab makes me wonder whether this module should actually be renamed to something that mentions permalinks.

I am not sure where to go with this now - I will definitely be using this for an upcoming site, but I would really like some feedback from some other PW gurus, especially Ryan, as to whether this should be a released module and whether you guys think this idea of a permalink like:

http://www.mysite.com/1234/articles/my-article-title/

is a good idea to be promoting or not. I know that Page Path History does an amazing job already of handling changes to page names and parents. So would the idea of using this module to create this style of permalink be redundant, or just bad practice?

Thanks for any feedback.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian This module is exactly what I was looking at doing before, but done better, so thanks again.

I've not read up on Page Path History but I see your question re that or this module. I like the idea of this module, my only comment would be that perhaps the approach the BBC take might be better, it's the same as yours but instead of

http://www.mysite.com/1234/articles/my-article-title/ 

they use

http://www.mysite.com/articles/my-article-title-1234

I assume as the result may be slightly better SEO-wise.

Edited by alanfluff

Share this post


Link to post
Share on other sites
I can't seem to get an array of pages using wire('pages'). I get:

What's the idea on these lines?

foreach(wire('pages') as $p) {
            $fieldEnabledPages->addOption($p->name);
        }

Grab all the pages?

funny, wire("pages") or even wire("pages")->find() also don't return anything to me (the same happens with $pages on templates, by the way), but wire("pages")->find("sort=sort") does. Maybe you can try that.

try:

foreach(wire("pages")->find("sort=sort") as $p) {
            $fieldEnabledPages->addOption($p->name);
        }

Anyway, I'm not sure if it is a good idea to iterate all the pages of the site in a module because it might cause problem on bigger sites.

  • Like 1

Share this post


Link to post
Share on other sites

@alan - I have added support for your suggested URL structure. Please test when you get a chance and let me know how it goes for you.

@diogo - thank you for the testing. The ->find("sort=sort") works for me too - any ideas why it doesn't work as normal?

Good point about iterating all those pages on a large site - that definitely won't work well at all. I have changed config setting to a InputfieldPageListSelectMultiple and it seems to work well now.

So now it is possible to limit the redirection of these links by template and or page/page parent.

Any other thoughts/ideas? 

Share this post


Link to post
Share on other sites

I asked Ryan about this module and he is happy with it going in the modules directory, so I have submitted it:

http://modules.processwire.com/modules/process-redirect-ids/ 

It is fine to have it run on all your pages/templates (the default), but don't forget to check out the module config settings where you can limit this. Remember it is only called by pages that return a 404 so I don't believe there should be any overhead on normal page loads.

So please feel free to start using it and let me know if you have any improvements you'd like to see.

  • Like 1

Share this post


Link to post
Share on other sites

Sorry I didn't get to test it Adrian, I'm sure it would have been a redundant test and I'll be trying this out next site I build, congrats on the Module and thanks!

Share this post


Link to post
Share on other sites

This module accomplishes exactly what I was looking for today. Thank you very much Adrian for making this available.

  • Like 1

Share this post


Link to post
Share on other sites

IF this module ends up being is a goer (security implications sorted n'all) would it be possible to have some way in the admin of letting the user copy the short url to that page. I can see where this would come in handy for a site or two.

Is this really such a security risk..? ...that people could guess IDs? It's not about whether those pages are indexed by Google; the same risk definitely applies to the default slug-based permalinks -- like Adrian said, he'd assume they would already be publicly inaccessible from the server-side, me too; it's no more secure than not doing so and leaving the regular slugs (unless you have yours or your titles randomly generated as complex strings). Or am I missing something?

Anyway I can't wait to try this out, thanks much.

Share this post


Link to post
Share on other sites

@hellomoto,

I don't really think there is a security risk, especially given that you can limit this module's actions to specific templates and pages if you wish.

Anyway, hope it works as you expect!

Share this post


Link to post
Share on other sites

Hey! Ok so it doesn't quite work as I expected, though it does work great... but what I'm looking to do is actually use the IDs for pages of one of my templates. 

I have it set up to Redirect (default), Rewrite Links checked, Rewrite Format = /sales/listings/{$page->make->name}/{$page->model->name}/{$page->id}/

/sales/listings/ is the path preceding each listing anyway, which is the template I have the rewrite enabled for.

So it works in my listings index on the frontend, but then those links redirect to their default URLs. I thought this might be accomplished with Load selected for Redirect Type instead of Redirect, but that gives me this error:

Compile Error: Cannot redeclare browserTitle() (previously declared in /.../site/templates/includes/functions.php:5) (line 10 of /.../site/templates/includes/functions.php)

Lines 5 and 10 are the beginning and ending of that function... So I don't know why that would be happening...

Update: I changed my header to include_once the functions. This is fixed :)

But what I really want is to redirect the default URL for each listing to the one I design. Like from the backend, the links still go to /sales/listings/{$page->name}/ when I want them to be what I set too, or at least redirect to what I set. I want the URL I set to be the absolute one. Anyone know how? Thanks.

Share this post


Link to post
Share on other sites

The Load option should do exactly what you are looking for. 

You shouldn't have the /sales/listings at the beginning of the rewrite format - just use:

/{$page->make->name}/{$page->model->name}/{$page->id}/

I haven't tested thoroughly with adding extra path segments like you are doing, but it seems to be working fine here. Typically I just put dashes between the components.

Glad you sorted out the include_once issue :)

To get the View links when editing a page to also be rewritten, make this change to line 115:

     if($page->id!=1 && $page->template != 'admin') {

to:

     if($page->id!=1) {

I did a quick test and I don't think there are any issues with this, but would appreciate you testing it before I make it live.

Share this post


Link to post
Share on other sites

I just tried out the module and I can confirm that it works just like it says.
 
I'm new to Processwire, so forgive me if what I'm suggesting is to much.  I come from the Drupal land.  In Drupal, all pages have a id called an nid(node id).  With core Drupal you can visit any page with /node/10003 and it will redirect you to that page.  When links from the editor are inserted into a textarea, they look like /node/10003.  When the page is viewed, the https://www.drupal.org/project/pathologic module converts those types of links into their aliased name(like /my-cool-page).

I believe Concrete5 does the same thing with it's core page link abstractor.
 
Couple of things/possible suggestions:
Is there a way to rewrite links that are inserted via the wysiwyg editor into a textarea?  For instance, clicking on the link icon in ckeditor opens a modal dialog where you can select a page, but when you select a page it inserts something like /parent/child-page instead of /1002.  If it just inserted /1002 then the editors wouldn't need to look at the short links tab because this module would automatically handle everything.
 
Maybe there can be a way to use a text formatter module to convert links like /1002 to /parent/child-page when outputting the page like https://www.drupal.org/project/pathologic?
 
Drupal also adds the following to the page to assist with SEO:
<link rel="canonical" href="https://www.mywebsite.com/my-cool-page" />
<link rel="shortlink" href="https://www.mywebsite.com/node/4796" />

Processwire looks really good, but I can't imagine not having some kind of way to handle links breaking when the site tree changes.  For big departmental or documentation websites, this happens all the time.  P.S. I have seen the other two modules page-link-abstractor and page-path-history.

Hope that helps, thanks for sharing your module I think it is definitely moving in the right direction!

Share this post


Link to post
Share on other sites

Maybe it would be possible to add another option to the ProcessPageEditLink module? something like "Absolute page id"? that would insert links like /1002

VHn4uyk6EykY7Eyx0YuTB5KlgMRPBn.png

Share this post


Link to post
Share on other sites

Hi @gmclelland - to be honest I don't really use this module for replacement of the main links - I only use it as a means of providing a shorter URL if required.

I actually think that the Page Path History module does an excellent job of preventing broken links. I have never actually been a fan of Drupal's /node/nnnn/ links, but in previous custom systems I have built, I have included the page ID as part of the URL, like: mydomain.com/nnnn-title-of-my-page/ which this module allows.

As for changing the insert link - this should already work - at least it does for me:

post-985-0-07407300-1449739560_thumb.png

Sorry if I am missing your point - in a bit of a hurry!

PS Did you select the "Rewrite Links" in the module settings?

Share this post


Link to post
Share on other sites

Oh... That's what that setting does.   :)  Yes, it works for me.  Thanks for pointing me in the right direction.  The only thing missing now is maybe some kind of text formatter module that would convert /1002 type links to /my-cool-page?

I've only used Page Path History once a while back, but it seems like Page Path History module is just covering up the problem by creating a ton of redirects without fixing the source of the problem which is the content is linking to the wrong page?  In Drupal, your not supposed to see the node/1002 links on the frontend.  Instead, you see the node's alias which would be something like /my-cool-page.

Their is a https://www.drupal.org/project/redirect module that is used to store changes of the node's alias.  For example, changing /my-cool-page to /my-cooler-page, but that is really only useful for when other websites link to the node's alias.  Internal links in text areas are always like node/1002 and then transformed on output into /my-cool-page.

As far as I know the systems that do this are modx, concrete5, Drupal.

Anyways, thanks again for responding.  I appreciate your help.

Share this post


Link to post
Share on other sites

As far as I'm concerned, redirects are pretty quick, and so using normal page links in CKEditor along with PagePathHistory should be more than sufficient for managing this. A Textformatter module would also indeed solve the problem, but there isn't one as yet.

Also not a fan of ID-based URIs - I just don't see the purpose...

Share this post


Link to post
Share on other sites

I have seen several drupal sites where the link in the html is still the /node/nnnn - does that mean they don't have it configured correctly or is this just something that is unavoidable in some cases, in which case that seems worse from an SEO point of view to me than just redirecting outdated links with PagePathHistory keeping in mind that there won't likely be that many changes - seems better than redirecting every /node/ link if it isn't being rewritten properly before the HTML is generated.

However, a textformatter to rewrite ID links made by this module wouldn't be hard to put together - in fact I bet you could steal some code from the Link Abstractor module - which btw is now deprecated.

If go to tackle this and need some help, please let us know and we'll help you get it working.

Share this post


Link to post
Share on other sites

Thanks adrian for the help.

I have seen several drupal sites where the link in the html is still the /node/nnnn - does that mean they don't have it configured correctly 

Yes, that can happen if you don't set any page aliases with the https://www.drupal.org/project/pathauto module.  The Pathauto module is used on pretty much every Drupal site.

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