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 BitPoet
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)