Jump to content
adrian

Page Protector

Recommended Posts

Thanks - I couldn't get the $ppid variable either (similarly to $loginForm). Anyway, I think it's not that important, I can get the protected parent manually too and get content from it (even multilanguage).

It took some time I understood the module's workings but finally it's up and running the way I wanted, thanks for the help! :) 

Share this post


Link to post
Share on other sites
4 minutes ago, tpr said:

It took some time I understood the module's workings but finally it's up and running the way I wanted, thanks for the help! :) 

No problem!

Should I commit the version with $page->protected property then? I assume that is still something you need to get it working in your scenario?

Share this post


Link to post
Share on other sites

Sure, that will come handy, thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Hello.

First off all, thanks for that great module. 

My problem is the combination of the TemplateEngineFactory module and the PageProtector module. Both modules don't work together.

The problem is the Page::render, unfortunately both modules define a after hook. The TemplateEngineFactory always overwrites the PageProtector hook. 

[Page::render] => Array
(
    [0] => PageRender->renderPage() in PageRender.module
    [1] => PageProtector->protectedCheck() in PageProtector.module
    [2] => TemplateEngineFactory->hookRender() in TemplateEngineFactory.module.php
)

When I remove the TemplateEngineFactory module everything works correctly and the login page is displayed. If both modules are acitve the login page ist not displayed. 

Can someone help me? Both modules should work together...

Thanks!

Share this post


Link to post
Share on other sites

Hi @wbertl - firstly, welcome to the forums!

Please upgrade to the latest version which should fix the issue for you.

  • Like 1

Share this post


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

Hi @wbertl - firstly, welcome to the forums!

Please upgrade to the latest version which should fix the issue for you.

Hey adrian,

many thanks. It works now!

  • Like 1

Share this post


Link to post
Share on other sites

Howdy @adrian

I'm wondering why I get lots of "Saved module 'PageProtector' config data" entries in /site/assets/logs/modules.txt as I do not remember saving the module settings so frequently. If it is not my "fault", can you please take a look at how to "get rid of them" should they be generated "by mistake".

  • Like 1

Share this post


Link to post
Share on other sites
17 hours ago, szabesz said:

Howdy @adrian

I'm wondering why I get lots of "Saved module 'PageProtector' config data" entries in /site/assets/logs/modules.txt as I do not remember saving the module settings so frequently. If it is not my "fault", can you please take a look at how to "get rid of them" should they be generated "by mistake".

Thanks for noticing that - it should be fixed in the latest version.

Because there are settings for this module on every page (Settings tab), saving the page was saving the settings. Now I check to see if there are any changes before saving.

Please let me know if it works as expected for you.

  • Like 1

Share this post


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

it should be fixed in the latest version

Thanx a lot! I will update the site in question – and all its modules – on the weekend, and report back.

Share this post


Link to post
Share on other sites

Hi Everyone,

I was wondering if anyone can help me with a problem I'm having.

I'm currently using the Intermediate templating schema which you can choose from when first developing PW on localhost. 

Firstly, let me say this is a great module and thank you for developing it.

Secondly, to the problem, I'm trying to render login form via "$content .= loginForm;" however that doesn't appear to work and produces nothing but a blank page.

The only way the login form shows is without the _main.php layout by using the default "echo loginForm;" approach.

 

Share this post


Link to post
Share on other sites

Is the missing $ in your post a typo here in the forum?

You need:

$content .= $loginForm;

Also, it depends on how your _main.php is set up. Is $content the final variable that is echo'd at the end, or is it $out or something else? Of course you need to use the variable that is actually used in your _main.php file. $content is just an example.

  • Like 1

Share this post


Link to post
Share on other sites
29 minutes ago, adrian said:

Is the missing $ in your post a typo here in the forum?

 

yes that's a typo in the forum.
 

 

29 minutes ago, adrian said:

Also, it depends on how your _main.php is set up. Is $content the final variable that is echo'd at the end, or is it $out or something else? Of course you need to use the variable that is actually used in your _main.php file. $content is just an example.

Yes, $content is the main output variable coming from the _main.php file.

My loginForm template page works if i use :

<?php namespace ProcessWire;

echo $loginForm;

shows blank screen using:

<?php namespace ProcessWire;

$content = $loginForm;

Maybe i'm missing something simple...

Share this post


Link to post
Share on other sites
33 minutes ago, JasonS said:

Maybe i'm missing something simple...

I think we'd need to see your files to help any further.

Does populating $content with anything else actually get output on the end?

Share this post


Link to post
Share on other sites
4 minutes ago, adrian said:

Does populating $content with anything else actually get output on the end?

No, That's the confusing part. 

loginform.php

<?php namespace ProcessWire;

echo $loginForm;

_main.php
 

<?php namespace ProcessWire;

/**
 * _main.php
 * Main markup file
 *
 * This file contains all the main markup for the site and outputs the regions 
 * defined in the initialization (_init.php) file. These regions include: 
 * 
 *   $title: The page title/headline 
 *   $content: The markup that appears in the main content/body copy column
 *   $sidebar: The markup that appears in the sidebar column
 * 
 * Of course, you can add as many regions as you like, or choose not to use
 * them at all! This _init.php > [template].php > _main.php scheme is just
 * the methodology we chose to use in this particular site profile, and as you
 * dig deeper, you'll find many others ways to do the same thing. 
 * 
 * This file is automatically appended to all template files as a result of 
 * $config->appendTemplateFile = '_main.php'; in /site/config.php. 
 *
 * In any given template file, if you do not want this main markup file 
 * included, go in your admin to Setup > Templates > [some-template] > and 
 * click on the "Files" tab. Check the box to "Disable automatic append of
 * file _main.php". You would do this if you wanted to echo markup directly 
 * from your template file or if you were using a template file for some other
 * kind of output like an RSS feed or sitemap.xml, for example. 
 *
 * See the README.txt file for more information. 
 *
 */
?><!DOCTYPE html>
<html lang="en">
<head>
	<meta http-equiv="content-type" content="text/html; charset=utf-8" />
	<meta name="viewport" content="width=device-width, initial-scale=1" />
	<title><?php echo $title; ?></title>
	<meta name="description" content="<?php echo $page->summary; ?>" />
	<link href='//fonts.googleapis.com/css?family=Lusitana:400,700|Quattrocento:400,700' rel='stylesheet' type='text/css' />
	<link rel="stylesheet" type="text/css" href="<?php echo $config->urls->templates?>styles/main.css" />
</head>
<body class="<?php if($sidebar) echo "has-sidebar "; ?>">

	<a href="#main" class="visually-hidden element-focusable bypass-to-main">Skip to content</a>

<h1 align="center" class="logo-text">
      <a href="<?php echo $config->urls->root ?>" class="logo-link"><?php $page->sitename ?></a>
    </h1>

	<!-- top navigation -->
	<ul class='topnav' role='navigation'><?php
		// top navigation consists of homepage and its visible children
		foreach($homepage->and($homepage->children) as $item) {
			if($item->id == $page->rootParent->id) {
				echo "<li class='current' aria-current='true'><span class='visually-hidden'>Current page: </span>";
			} else {
				echo "<li>";
			}
			echo "<a href='$item->url'>$item->title</a></li>";
		}

		// output an "Edit" link if this page happens to be editable by the current user
		if($page->editable()) echo "<li class='edit'><a href='$page->editUrl'>Edit</a></li>";
	?></ul>

	<!-- search form
	<form class='search' action='<?php echo $pages->get('template=search')->url; ?>' method='get'>
		<label for='search' class='visually-hidden'>Search:</label>
		<input type='text' name='q' placeholder='Search' id='search' value='<?php echo $sanitizer->entities($input->whitelist('q')); ?>' />
		<button type='submit' name='submit' class='visually-hidden'>Search</button>
	</form>-->

	<!-- breadcrumbs -->
	<div class='breadcrumbs' role='navigation' aria-label='You are here:'><?php
		// breadcrumbs are the current page's parents
		//foreach($page->parents() as $item) {
			//echo "<span><a href='$item->url'>$item->title</a></span> "; 
		//}
		// optionally output the current page as the last item
		//echo "<span>$page->title</span> "; 
	?></div>

	<div id='main'>

		<!-- main content -->
		<div id='content'>
			<h1 align="center"><?php echo $title; ?></h1>
			<?php echo $content; ?>
		</div>

		<!-- sidebar content -->
		<?php if($sidebar): ?>
		<aside id='sidebar'>
			<?php echo $sidebar; ?>
		</aside>
		<?php endif; ?>

	</div>

	<!-- footer -->
	<footer id='footer'>
		<p>
		Powered by <a href='http://processwire.com'>ProcessWire CMS</a>  &nbsp; / &nbsp; 
		<?php 
		if($user->isLoggedin()) {
			// if user is logged in, show a logout link
			echo "<a href='{$config->urls->admin}login/logout/'>Logout ($user->name)</a>";
		} else {
			// if user not logged in, show a login link
			echo "<a href='{$config->urls->admin}'>Admin Login</a>";
		}
		?>
		</p>
	</footer>
	<script   src="https://code.jquery.com/jquery-3.2.1.min.js"   integrity="sha256-hwg4gsxgFZhOsEEamdOYGBf13FyQuiTwlAQgxVSNgt4="   crossorigin="anonymous"></script>
	<script>
	$('img').bind('contextmenu', function(e) {
    return false;
}); 
</script>

</body>
</html>

 

Share this post


Link to post
Share on other sites

Ok, I think the problem is that loginform.php needs to be:

$content = $loginForm;

which I think you have already tried, but just not in the code you just posted.

Also, is loginform.php selected in the module settings for the "Login Template" setting?

Also, because loginform.php is not an actual PW template, _main.php won't be automatically included, so you will need to manually add:

require_once '_main.php';

after you define $content, so this should do it:

<?php namespace ProcessWire;

echo $content = $loginForm;
require_once '_main.php';

 

Share this post


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

which I think you have already tried, but just not in the code you just posted.

yes i did. Didn't work.

1 hour ago, adrian said:

Also, is loginform.php selected in the module settings for the "Login Template" setting?

 

Yes, it is.
 

1 hour ago, adrian said:

<?php namespace ProcessWire; echo $content = $loginForm; require_once '_main.php';

I applied your code and doesn't work. I'll attach a screenshot of what I see.


 

Screenshot at Nov 04 22-20-23.png

Share this post


Link to post
Share on other sites

Sorry, my fault - you don't want to echo $content in loginform.php - you just want to set it - it needs to be echo'd in main.php if you want the login form to appear with your site html wrapper content.

Is this site online somewhere I could take a look?

Share this post


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

Is this site online somewhere I could take a look?

Unfortunately, no it isn't. Local webdev development on my machine.

Share this post


Link to post
Share on other sites

Hi adrian,
very usefull - thank you!!
Is it possible to have "allowed users" additionally to "Allowed Roles"?
I would like to give a specific user access to one specific page. With a role-access i couldn´t achieve that, because then many of the users with this role would have access to this page - and this is not desired.

Share this post


Link to post
Share on other sites
On 1/5/2018 at 8:15 AM, itsberni said:

Hi adrian,
very usefull - thank you!!
Is it possible to have "allowed users" additionally to "Allowed Roles"?
I would like to give a specific user access to one specific page. With a role-access i couldn´t achieve that, because then many of the users with this role would have access to this page - and this is not desired.

Hi @itsberni - I certainly could add it, but on sites with a lot of users, the interface for selecting allowed users would need careful attention.

Is there any reason you couldn't add a new custom role to just the specific user and use that role to provide access?

Share this post


Link to post
Share on other sites

Hi adrian!

i Could do that, of course. But i thought it would be easier to assign a spezific Page to a user.

i solved it now with a different approach. 

I added a page reference field to the User Template. In the template.php i check for the User and simultaneously if the visited page = the referenced page in the users entry. That works for me. nevertheless thank you!

  • Like 1

Share this post


Link to post
Share on other sites

HI @adrian,

I would like to try your PageProtector module but I have to know whether I can set the login (username-password pair) per page? If I understand it correctly, the username-password pair can be set globally and not for every single page.

Share this post


Link to post
Share on other sites
3 hours ago, LAPS said:

HI @adrian,

I would like to try your PageProtector module but I have to know whether I can set the login (username-password pair) per page? If I understand it correctly, the username-password pair can be set globally and not for every single page.

Each page can be restricted to a user role, so you could setup each page to be limited to a different role and assign these roles to separate users - I think this would give you what you want. But without knowing exactly your scenario, it's hard to know if this would be the best option or not. You might be better off with a custom module or a ready.php hook on Page::render and handle the logic that way.

image.png.2615acd8e2417d380aa768e522163254.png

  • Like 1

Share this post


Link to post
Share on other sites
On 5.11.2017 at 3:10 AM, adrian said:

Ok, I think the problem is that loginform.php needs to be:


$content = $loginForm;

which I think you have already tried, but just not in the code you just posted.

Also, is loginform.php selected in the module settings for the "Login Template" setting?

Also, because loginform.php is not an actual PW template, _main.php won't be automatically included, so you will need to manually add:


require_once '_main.php';

after you define $content, so this should do it:


<?php namespace ProcessWire;

echo $content = $loginForm;
require_once '_main.php';

 

I tried this too, but it seems to me the intermediate templating doesn't work with this module having defined my own login-page. I get errors pointing to undefined variables that are defined in _init.php. If I try to require the _init.php first, then add $loginForm to $content and then require_once _main.php, I get other errors that result from login.php template not being a PW template:

Class 'FilenameArray' not found in site/templates/_init.php

Have you really used login.php template with intermediate templating?

 

Share this post


Link to post
Share on other sites
On 1/27/2018 at 8:11 AM, lpa said:

Have you really used login.php template with intermediate templating?

Hi @lpa - sorry you're having trouble with this approach. I have definitely used it before with the "intermediate" approach, but it turns out I was doing things a little different in terms of how files were being prepended. I just tried with the regular intermediate templating approach and I could reproduce the errors you were seeing.

I have a fix in place for you though.

My login.php template file looks like this.

<?php
$content = $page->loginForm;
include '_main.php';

Obviously you can use whatever *.php file you want - selected from the module settings.

The key difference now is that you must use: $page->loginForm and not $loginForm

Please test the attached version (I don't want to commit just yet) and let me know how you go.

 

PageProtector.zip

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

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

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...