Jump to content
benbyf

New module MarkInPageTree

Recommended Posts

MarkInPageTree

New module which does what it says in the title. It adds an icon to a page on the page tree if -> a specific field is true and / or is a specified template.

For example I'm using it to add an icon to any page that has a checked (checkbox) exclusive field. This helps with admin clarity as you can see instantly which pages of the same template have differing content (i.e. are exclusive or not).

https://github.com/benbyford/MarkInPageTree

Screenshot 2016-12-09 14.33.45.png

  • Like 10

Share this post


Link to post
Share on other sites

How about using InputfieldSelector for the page selection and using InputfieldIcon for the icon selection?

  • Like 2

Share this post


Link to post
Share on other sites
Just now, LostKobrakai said:

How about using InputfieldSelector for the page selection and using InputfieldIcon for the icon selection?

Sure, how does one do that :)

Share this post


Link to post
Share on other sites

couldnt work it out, just gave me a field for searching the pages on the site but not selecting them... and it wouldnt show templates or fields.

I was able to use select multiple instead thought. For example:

$f = $this->modules->get('InputfieldSelectMultiple');
$f->attr('name', 'template');
$f->description =  $this->_("Template or templates of pages to trigger bulk email to users after new page published");
$f->addOption('', '');

foreach($this->templates as $template){
$f->addOption($template->name, $template->title);

 

Share this post


Link to post
Share on other sites

Updated and works well (needed to delete the extra fa- in the html as the icon selector adds the complete fontawesome name). Only thing I would change but unsure is whether you can have or selector somehow as it currenlty only adds icons to the selectors found pages not a template or a field for example. i.e. for mulitple selectors.

Share this post


Link to post
Share on other sites

Great idea and great module! Saves me some rather ugly additions to the displayed title page in the page tree.

One thing for the Christmas wish list: It would be even greater if the module would provide a way to set up several different rule sets. So you could set up different icons to mark different things.

  • Like 2

Share this post


Link to post
Share on other sites

not really sure how to make this happen... repeater? Anyone point me in the right direction to creating multiple additional fields to the module settings? so the module can have as many icon and template or field pairs as you want...?

Share this post


Link to post
Share on other sites

Multi-value fields in module config is a bit tricky, because almost everything multi-value in pw is based on pages, which you don't use here. It's probably simplest to add an integer field "number_of_configuration", which does, after it's saved, cause the field(s) for the page selection to be rendered that many times. In your modules code you'd also use that number for determining how often to loop though potential configurations.

Share this post


Link to post
Share on other sites

I would go with the "icon name = selector" route, in a simple textarea, one rule per row. Icon name would be the fontawesome name.

  • Like 2

Share this post


Link to post
Share on other sites

Happy Christmas everyone!

I had a bit of time to add tot his module :)

It now has textareas (thanks @tpr) in it's config which means it can now add as many icons and field and/or template pairs as you like. This means you could add one icon for pages of the template basic-page, and also add another icon for all pages with a counter etc...

Also... I've added a third textarea, allowing you to add a list of fields to show the data for IN the pagetree itself (see image below). In my example below I am able to show in the page tree by each page if they have a counter what the data is and whether the page has a field exclusive and its data.

Thanks for peoples help and hope it is useful. (updated on github)

Screenshot 2016-12-17 15.43.47.png

Screenshot 2016-12-17 15.43.27.png

  • Like 5

Share this post


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

Hello @benbyf

can you check the following message:

Screenshot_2.jpg

Thanks!

when are you getting this error? can you send me your settings. thanks

Share this post


Link to post
Share on other sites

No its a notice - it only shows up  as an error because I am running Tracy in strict mode.

These are my settings:

Screenshot_3.jpg

  • Like 1

Share this post


Link to post
Share on other sites

As a quick patch this fixes the error:

Change this:

$a[trim($cropItems[1])] = trim($cropItems[0]);

 

To this:

if(count($cropItems) > 1){
	$a[trim($cropItems[1])] = trim($cropItems[0]);
}

 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, and glad you're finding the module useful.

If you have any other bugs or fixes, please submit a issue or pull request on github

Share this post


Link to post
Share on other sites

Hi,

Thanks for this module, it's quite useful, and it's work very well. However, I still wondering which icons I can use? I can't find anywhere a list or a reference to an iconset used by the module. 

Mel

Share this post


Link to post
Share on other sites

Great module, thank you!

Is there a way to use separate variations of icons, e.g. "fas fa-check" vs. "far fa-check"?

P.S.: You might want to point to the icon cheatsheet in the module description. I was confused as well (newbie).

Share this post


Link to post
Share on other sites
On 9/7/2018 at 10:34 AM, Knubbi said:

Great module, thank you!

Is there a way to use separate variations of icons, e.g. "fas fa-check" vs. "far fa-check"?

P.S.: You might want to point to the icon cheatsheet in the module description. I was confused as well (newbie).

Both valid. PW comes with Fontawesome in the default admin so thats why its the deafult far icons. If you want to purchase new icons versions and replaces the files in your copy then that shoul work.

Will definitely change the description.

  • Like 1

Share this post


Link to post
Share on other sites

Hi Benbyf,

I'm really enjoying this module.  It really helps visualize how the page tree relates to the templates.  I'm using "template" in Data.

One request: It would be really helpful if you could add a permission so that only super users see the MarkInPageTree stuff in the Page Tree by default.  If other roles need to see the MarkInPageTree stuff in the Page Tree, a site admin could add a MarkInPageTree permission to that role.

The only caveat is that existing sites that have already installed this module will need to be updated to use the new permission.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      A community member raised a question and I thought a new sanitizer method for the purpose would be useful, hence...
      Sanitizer Transliterate
      Adds a transliterate method to $sanitizer that performs character replacements as defined in the module config. The default character replacements are based on the defaults from InputfieldPageName, but with uppercase characters included too.
      Usage
      Install the Sanitizer Transliterate module.
      Customise the character replacements in the module config as needed.
      Use the sanitizer on strings like so:
      $transliterated_string = $sanitizer->transliterate($string);
       
      https://github.com/Toutouwai/SanitizerTransliterate
      https://modules.processwire.com/modules/sanitizer-transliterate/
       
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version to 2.10, add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "http://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


    • By thomasaull
      I created a little helper module to trigger a CI pipeline when your website has been changed. It's quite simple and works like this: As soon as you save a page the module sets a Boolean via a pages save after hook. Once a day via LazyCron the module checks if the Boolean is set and sends a POST Request to a configurable Webhook URL.
      Some ideas to extend this:
      make request type configurable (GET, POST) make the module trigger at a specified time (probably only possible with a server cronjob) trigger manually Anything else? If there's interest, I might put in some more functionality. Let me know what you're interested in. Until then, maybe it is useful for a couple of people 🙂
      Github Repo: https://github.com/thomasaull/CiTrigger
    • By Robin S
      I created this module a while ago and never got around to publicising it, but it has been outed in the latest PW Weekly so here goes the support thread...
      Unique Image Variations
      Ensures that all ImageSizer options and focus settings affect image variation filenames.

      Background
      When using methods that produce image variations such as Pageimage::size(), ProcessWire includes some of the ImageSizer settings (height, width, cropping location, etc) in the variation filename. This is useful so that if you change these settings in your size() call a new variation is generated and you see this variation on the front-end.
      However, ProcessWire does not include several of the other ImageSizer settings in the variation filename:
      upscaling cropping, when set to false or a blank string interlace sharpening quality hidpi quality focus (whether any saved focus area for an image should affect cropping) focus data (the top/left/zoom data for the focus area) This means that if you change any of these settings, either in $config->imageSizerOptions or in an $options array passed to a method like size(), and you already have variations at the requested size/crop, then ProcessWire will not create new variations and will continue to serve the old variations. In other words you won't see the effect of your changed ImageSizer options on the front-end until you delete the old variations.
      Features
      The Unique Image Variations module ensures that any changes to ImageSizer options and any changes to the focus area made in Page Edit are reflected in the variation filename, so new variations will always be generated and displayed on the front-end.
      Installation
      Install the Unique Image Variations module.
      In the module config, set the ImageSizer options that you want to include in image variation filenames.
      Warnings
      Installing the module (and keeping one or more of the options selected in the module config) will cause all existing image variations to be regenerated the next time they are requested. If you have an existing website with a large number of images you may not want the performance impact of that. The module is perhaps best suited to new sites where image variations have not yet been generated.
      Similarly, if you change the module config settings on an existing site then all image variations will be regenerated the next time they are requested.
      If you think you might want to change an ImageSizer option in the future (I'm thinking here primarily of options such as interlace that are typically set in $config->imageSizerOptions) and would not want that change to cause existing image variations to be regenerated then best to not include that option in the module config after you first install the module.
       
      https://github.com/Toutouwai/UniqueImageVariations
      https://modules.processwire.com/modules/unique-image-variations/
    • By Sebi
      I've created a small module which lets you define a timestamp after which a page should be accessible. In addition you can define a timestamp when the release should end and the page should not be accessable any more.
      ProcessWire-Module: http://modules.processwire.com/modules/page-access-releasetime/
      Github: https://github.com/Sebiworld/PageAccessReleasetime
      Usage
      PageAccessReleasetime can be installed like every other module in ProcessWire. Check the following guide for detailed information: How-To Install or Uninstall Modules
      After that, you will find checkboxes for activating the releasetime-fields at the settings-tab of each page. You don't need to add the fields to your templates manually.
      Check e.g. the checkbox "Activate Releasetime from?" and fill in a date in the future. The page will not be accessable for your users until the given date is reached.
      If you have $config->pagefileSecure = true, the module will protect files of unreleased pages as well.
      How it works
      This module hooks into Page::viewable to prevent users to access unreleased pages:
      public function hookPageViewable($event) { $page = $event->object; $viewable = $event->return; if($viewable){ // If the page would be viewable, additionally check Releasetime and User-Permission $viewable = $this->canUserSee($page); } $event->return = $viewable; } To prevent access to the files of unreleased pages, we hook into Page::isPublic and ProcessPageView::sendFile.
      public function hookPageIsPublic($e) { $page = $e->object; if($e->return && $this->isReleaseTimeSet($page)) { $e->return = false; } } The site/assets/files/ directory of pages, which isPublic() returns false, will get a '-' as prefix. This indicates ProcessWire (with activated $config->pagefileSecure) to check the file's permissions via PHP before delivering it to the client.
      The check wether a not-public file should be accessable happens in ProcessPageView::sendFile. We throw an 404 Exception if the current user must not see the file.
      public function hookProcessPageViewSendFile($e) { $page = $e->arguments[0]; if(!$this->canUserSee($page)) { throw new Wire404Exception('File not found'); } } Additionally we hook into ProcessPageEdit::buildForm to add the PageAccessReleasetime fields to each page and move them to the settings tab.
      Limitations
      In the current version, releasetime-protected pages will appear in wire('pages')->find() queries. If you want to display a list of pages, where pages could be releasetime-protected, you should double-check with $page->viewable() wether the page can be accessed. $page->viewable() returns false, if the page is not released yet.
      If you have an idea how unreleased pages can be filtered out of ProcessWire selector queries, feel free to write an issue, comment or make a pull request!
×
×
  • Create New...