Jump to content
Orkun

Page Edit Per User Module - Specific PHP Selector for editable pages, Multi-User-System etc...

Recommended Posts

Hello Processwire Community

Lets say I have a Multi-User-System where I can create/update as "normal" user new events, dates, multimediapages, imagepages etc....

As Admin I can create organisers(owners) and assign them respectively to specific users.

Module for creating/updating pages: Fredi - Friendly Frontend Editor

Scenario: Add new Imagepage under Multimedia > Images

Important Fields

select_organiser(FieldtypePage)(btw. this field is assigned to the user template)

PHP-Selector for "select_organiser"

if(wire('user')->isSuperuser()){
    return $pages->find("template=organiser");
}
else{
    return $pages->find("template=organiser, id=".wire('user')->select_organiser);
}

Templates

image-index(is assigned to Image-Page)

-> Fields: only title

- > images-index.php

Only show the image pages which has the same organiser like the current user.

<?php
$out .="<h3>$title verwalten</h3>

				<div class='span11'>
					<div class='btn-pos-1 add'>"
					.$fredi->setText("<i class='fa fa-plus'></i> Bild erfassen")->hideTabs("children|delete|settings")->addPage("image", "title|select_organiser", $pages->get(1153)).
					"</div>
					<table id='example' class='row-border' cellspacing='0' width='100%'>
				        <thead>
				            <tr>
				              <th>ID</th>
				              <th>Bildname</th>
				              <th>Bild</th>
				              <th>Beschreibung</th>
				              <th>Veranstalter</th>
				              <th>aktualisiert</th>
				              <th></th>
				              <th></th>

				            </tr>
				        </thead>

				        <tbody>";

					        if($user->isSuperuser()){
					        	$images = $pages->find("template=image");
					        }
					        else{
					        	
					        	$images = $pages->find("template=image, select_organiser=$user->select_organiser");
					        }
					     
					        foreach ($images as $i_item) {
					        	if($i_item->image){
					        		$thumb = $i_item->image->size(50, 50);
					        	}
					        	$out .= "<tr>
					        	         <td>{$i_item->id}</td>
					        	         <td>{$i_item->title}</td>
					        	         <td><a class='large_img' href='{$i_item->image->url}' ><img src='{$thumb->url}' /></a></td>
					        	         <td>{$i_item->image_body}</td>
					        	         <td>{$i_item->select_organiser->title}</td>
					        	         <td>".date('Y-m-d', $i_item->modified)."</td>
					        	         <td><a href='{$i_item->url}'><i class='fa fa-eye'></i></td>
					        	         <td>".$fredi->setText("<i class='fa fa-pencil'></i>")->renderAll($i_item)."</td>
					        	         </tr>";
					        }
		$out .= "		</tbody>
			    	</table>
				</div>";

images(is assinged to children-items of Image-Page)

-> Fields: title, image, image_body, select_organiser

-> images.php

At the beginnnig of the template it checks if the select_organiser of the current user is the same as the select_organiser of the current image page.

<?php
if($user->select_organiser == $page->select_organiser || $user->isSuperuser()){

$out .= "<h3>{$page->parent->title} Details</h3>
         <div class='span8'>
            <table class='detail-view table table-striped table-condensed'>";

            $out .= "<tr class='odd'><th>ID</th><td>{$page->id}</td></tr>";

            //get all fields:
            $all_fields = $page->fields;

            foreach($all_fields as $field){
          

                if($field->type == "FieldtypeImage"){
                     $out .= "<tr class='odd'><th>{$field->label}</th><td>{$page->get($field->name)->url}</td></tr>";
                }
                else if($field->type == "FieldtypePage"){
                     $out .= "<tr class='odd'><th>{$field->label}</th><td>{$page->get($field->name)->title}</td></tr>";
                }
                else{

                  $out .= "<tr class='odd'><th>{$field->label}</th><td>{$page->get($field->name)}</td></tr>";
               }
            }

            $out .= "<tr class='odd'><th>erstellt</th><td>".date("Y-m-d H:i:s", $page->created)."</td></tr>
                     <tr class='even'><th>aktualisiert</th><td>".date("Y-m-d H:i:s", $page->modified)."</td></tr>
            </table>
        </div>

        <div class='span3'>
            <div id='sidebar'>
                <ul class='well nav nav-list' id='yw1'>
                    <li class='nav-header nav-header'>Aktionen</li>
                    <li><a href='{$page->parent->url}'><i class='fa fa-list'></i> Bilder auflisten</a></li>
                    <li>".$fredi->setText("<i class='fa fa-pencil'></i> Bild bearbeiten")->renderAll($page)."</li>
                </ul>
                <br />        
            </div>
        </div>";

}
else{
    $session->redirect($error404->url);
}

The Problem of this System is that the user still can access to image-pages in the backend that dont have the same organiser. Its only view protected.

So finally my Question: Can i specifiy a PHP-Selector for the editable pages for the Page Edit Per User Module.

Like:


return $pages->find("template=images, id=".wire('user')->select_organiser);

So that the user can edit the image - pages which has the same organiser like him?

Pagetree Structure and some screenshots of the interfaces for visualization:

Pagetree Structure:

Home(Login-Page)

   - Dashboard(Intro-Page)

     -- Events(visible for superuser and user with role: company)

     -- Agenda/Dates(visible for superuser and user with role: company)

     -- Multimedia(visible for superuser and user with role: company)

       --- Images(template: image-index)

          ---- example-img.jpg(template: image)

          ...

       --- Videos

     -- Profile(visible for superuser and user with role: company)

     -- Organisers(Only visible for Superuser)

        --- Organiser-Profiles

           ---- XYZ AG

           ...

        --- Adresses

        --- Locations

     -- Settings(Only visible for Superuser)

     -- Logout

Image - Overview Page

post-3125-0-57488000-1444212375_thumb.pn

Image - Detail Page

post-3125-0-88676900-1444212380_thumb.pn

PS: Sorry for the long post :P:lol:

Share this post


Link to post
Share on other sites

I thought that i could bypass the problem, when I only give view permission to the users with the role "company" so that they cant access the backend. But the problem is then, that they cant create/update pages from the Frontent with the modal edit windows of fredi.

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 benbyf
      Hi, Looking to create form elements on a page–some input with a colection of form inputs and the appropriate labels and variables for that input. I've used ProForms in the past and rolled out my own when creating simply one off forms, but I wonder if anyone has found a good way of allowing form creation on page editing so that clients can adhocly make and edit forms?
      Thanks
    • By Marvin
      Hello, i want to ask, i maintain a website that using a processwire and php, and i want to make an archive at my website using a subfolder system, but when i try,
      the sebfolder is show but when i click the files in that subfolder not show, and my browser just show me an error Invalid argument supplied for foreach(), i don't know why it error
      Here i attach my code and my screenshoot website :
      This is my code

      This is result of my website

      This is my error

       
       
    • By David Karich
      The Page Hit Counter module for ProcessWire implements a simple page view counter in backend. Page views of visitors are automatically tracked on defined templates, with monitoring of multiple page views. This gives you a quick overview of how many visitors have read a news or a blog post, for example, without first having to open complex tools such as Google Analytics. This module quickly provides simple information, e.g. for editors. Or, for example, to sort certain news by most page views. For example for "Trending Topics".

       
      Works with ProCache and AdBlockers. With a lightweight tracking code of only ~320 bytes (gzipped). And no code changes necessary! In addition GDPR compliant, since no personal data or IP addresses are stored. Only session cookies are stored without information. 
      In addition, there are some options, for example filtering IP addresses (for CronJobs) and filtering bots, spiders and crawlers. You can also configure the lifetime of the session cookies. Repeated page views are not counted during this period. It is also possible to exclude certain roles from tracking. For example, logged in editors who work on a page are not counted as page views.

      Sort by hits and access page views (hit value)
      Each trackable template has an additional field called phits. For example, you want to output all news sorted by the number of page views.
      // It is assumed that the template, e.g. with the name "news", has been configured for tracking. $news = $pages->find("template=news, sort=-phits"); To output the page views of a tracked page, use:
      echo $page->phits; Example: Reset counter per API
      $modules->get("PageHitCounter")->resetPageViews("template=whatever", false); Example: Tracking a page hit via API and jQuery
      If you want to track a template that does not represent a full page to automatically inject a tracking script, you can define allowed API templates in the module that you can track. Below is an example of how you can track a click on news tag using jQuery. This will allow you to find out which keywords are clicked the most. For example, you can sort and display a tag cloud by the number of hits. Suppose your keywords have the template "news_tag". The template "news_tag" was also configured in the Page Hit Counter Module as a trackable API template.
      Example PHP output of keywords / tags:
      // Required: the data attribute "data-pid" with the ID of the template to be tracked. echo $pages->find("template=news_tag, sort=-phits")->each("<a href='{url}' class='news_tag' data-pid='{id}'>{title}</a>"); Example Tracking Script with jQuery:
      /** * Required: Data attribute "data-pid" with the ID of the news tag template * Required: Send the POST request to the URL "location.pathname.replace(/\/?$/, '/') + 'phcv1'" * Required: The POST parameter "pid" with the ID of the template */ $(function(){ if($('a.news_tag').length > 0) { $('a.news_tag').each(function(){ var tPID = $(this).data("pid"); if(tPID) { $(this).on("click", function(){ $.post(location.pathname.replace(/\/?$/, '/') + 'phcv1', {pid: tPID}); }); } }); } }); So simply every click on a tag is counted. Including all checks as for automatic tracking. Like Bot Filtering, Session Lifetime, etc.
      Notice: Tracking with URL segments
      If the option "Allow URL Segments" is activated on a template, the hits are only counted if the base URL of the page is called. If you want the hit to be counted even when a segment is requested, you MUST configure the segments in the template configuration. How to do this can be found here. If you use dynamic segments, configure them as RegEx. There is currently no other option. The problem is that the Page Hit Counter hooked into the PageNotFound process. If URL segments are allowed but not defined, a 404 is never triggered. This means that the Page Hit Counter cannot be called.
      _______________________________________________________
      Background: This module is the result of a customer requirement, where the editors are overwhelmed with analytics or no tracking tools were allowed to be used. However, a way had to be found to at least count page views in a simple form for evaluations. Furthermore, by using ProCache, a way had to be found to count views of a page without clearing the cache.
      _______________________________________________________
      Pros
      Automatic Page View Tracking Lightweight tracking code, only ~320 bytes (gzipped) No code or frontend changes necessary Works with ProCache! Even if no PHP is executed on the cached page, the tracking works Works with browser AdBlockers No cache triggers (for example, ProCache) are triggered. The cache remains persistent GDPR compliant, session-based cookie only, no personal information Filtering of IPs and bots possible Exclude certain roles from tracking Ability to reset Page Views Works with all admin themes Counter database is created as write-optimized InnoDB API to track events for templates that are not viewable No dependencies on libraries, pure VanillaJS (Automatic tracking script) Works in all modern browsers Pages are sortable by hits Cons
      Only for ProcessWire version 3.0.80 or higher (Requires wireCount()) Only for PHP version 5.6.x or higher No support for Internet Explorer <= version 9 (Because of XMLHttpRequest()) No historical data, just simple summation (Because of GDPR) Segment URLs can only be counted if the segments are defined Planned Features / ToDos
      API access to hit values Since version 1.2.1 Possibility to sort the pages by hits (Request by @Zeka) Since version 1.2.0 Don't track logged in users with certain roles (Request by @wbmnfktr) Since version 1.1.0 Possibility to reset the counter for certain pages or templates (Request by @wbmnfktr) Since version 1.1.0 Better bot filter Since version 1.1.0 Disable session lifetime, don't store cookies to track every page view (Request by @matjazp) Since version 1.2.1 Option to hide the counter in the page tree (Request by @matjazp) Since version 1.2.1 Option to hide the counter in the page tree on certain templates Since version 1.2.1 API to track events for templates that are not viewable Since version 1.2.2 Changelog
      1.2.6
      Bug-Fix: Set the counter of a cloned page to 0 Enhancement: The function for resetting counters is now available in the module as a public function to reset counters via own scripts on the API side (Request by @VeiJari) Enhancement: Documentation improvement API reset 1.2.5
      Bug-Fix: When counting 404 hits, cookies are no longer set. The session lifetime is deactivated for the 404 page Enhancement: Documentation improvement regarding URL segments 1.2.4
      Bug-Fix: Resetting the counters on system pages (e.g. 404) does not work (Reported by wbmnfktr) Bug-Fix: Tracking endpoint is logged as 404 if module "Jumplinks" is installed (Reported by wbmnfktr) Enhancement: Corrected few typos (Merged from Sergio #6 – THX!) 1.2.3
      Bug-Fix: Tracking script triggers 404 if pages are configured without slash (#3) Reported by @maxf5 Enhancement: Reduction of the tracking script size if it's gzipped (~320 bytes) Enhancement: Documentation improvement Enhancement: Corrected few typos 1.2.2
      New feature: API to track events for templates that are not viewable Enhancement: Documentation improvement 1.2.1
      API access to hit values Use $page->phits Bug-Fix: No tracking on welcomepage (Reported by wbmnfktr; Thx to matjazp) Bug-Fix: Tracking script path on subfolders (Reported by matjazp) Bug-Fix: Tracking on pages with status "hidden" Enhancement: Change database engine to InnoDB for phits field Enhancement: Option to disable session lifetime set session lifetime to 0, no cookies Enhancement: Better installation check Enhancement: AJAX Request asyncron Enhancement: Reduction of the tracking script size by ~20% Enhancement: Option to hide the counter in the page tree You can output the counter with the field name "phits" Enhancement: Option to hide the counter in the page tree on certain templates Enhancement: Option for activate general IP validation Enhancement: Reduction of tracking overhead up to ~30ms Enhancement: Better bot list for detection 1.2.0
      New feature: Sort pages by hits – New field phits Migrate old counter data to new field 1.1.0
      New feature: Exclude tracking of certain roles New feature: Reset Page Views Better bot filter and detection 1.0.0
      Initial release Notes
      By default, the page views are stored as INT in the database. This allows a maximum counter value of 4.2 billion views (4,294,967,295) per page. If you need more, change the type to BIGINT directly in the database. But I recommend to use Google Analytics or similar tools if you have such a large number of users.
      _______________________________________________________
      Download GitHub: ProcessWire Page Hit Counter (Version 1.2.6)
      PW Module Directory: ProcessWire Page Hit Counter (Version 1.2.6)
      Install via ProcessWire (Classname): PageHitCounter
      _______________________________________________________
      Update information
      If you have used version 1.2.1 from the DEV branch, please replace it completely with the new master version.
    • By Mithlesh
      Hi there,
      My form is not getting submitted, it is showing:
      Unable to verify successful email delivery of this form submission.
      Attaching for your reference as well: 

      In the Backend, it is showing Connection timed out with smtp.gmail.com
      Pl guide me how to resolve that
×
×
  • Create New...