thetuningspoon

Page Field Edit Links

Recommended Posts

Page Field Edit Links


This module is based on--and is the successor to--Macrura's AdminPageSelectEditLinks (https://processwire.com/talk/topic/8477-adminpageselecteditlinks-module-for-enabling-edit-links-on-multipage-selects/)

Page Field Edit Links adds modal editing capability to ProcessWire's Page fields in the admin editor, allowing editors to easily view and edit the content of any page(s) that have been selected, as well as create new pages without leaving the current screen. Edit links are updated in real time when new pages are added to the field. Compatible with all available types of Inputfields including Select, SelectMultiple, Checkboxes, Radios, AsmSelect, PageListSelect, PageListSelectMultiple, and PageAutocomplete.

post-449-0-43262100-1431099269_thumb.png

  • Like 20

Share this post


Link to post
Share on other sites

Tried it on 2.6 and can't find the "show edit links?" option :( looked for it at page body field edit screen in "global" and in "template specific" mode...

Share this post


Link to post
Share on other sites

Hi BernhardB - The "Show edit links?" option should appear at the bottom of the "Input" tab in the global settings for the field. I'm a bit confused when you say "page body field" since the body field would be typically associated with a textarea and not a Page field.

Let me know if you are still having issues and I will look further into it.

  • Like 1

Share this post


Link to post
Share on other sites

want to say many thanks to @thetuningspoon for putting this together, and doing all the work of submitting to the directory. It's surely a useful module (use it almost every site), and we hope that all y'all will like it..

  • Like 4

Share this post


Link to post
Share on other sites

There is a small glitch with the version number that leads to a version mismatch in ModuleManager, which interprets it as 0.0.2 and 2.0 and permanently wants me to update. I am not a module coder but I think that 

 'version' => 200, 

would fix this.

  • Like 2

Share this post


Link to post
Share on other sites

If anyone has trouble with this on 2.5 stable, let me know. I had some trouble with an install this morning and am looking into it.

Share this post


Link to post
Share on other sites

I've a minor suggestion. It would be nice to make the link not wrap between the icon and the text. 

Share this post


Link to post
Share on other sites

I've a minor suggestion. It would be nice to make the link not wrap between the icon and the text. 

so you mean put the

<i class='fa fa-edit'></i>

before/outside of the anchor element?

Share this post


Link to post
Share on other sites

Nope I meant "wrap" as "line-wrap". On narrow fields sometimes the icon is still in the first line, while the text is already wrapped to the next one.

Share this post


Link to post
Share on other sites

so maybe for single page selects, changing to a block element?

Share this post


Link to post
Share on other sites

@thetuningspoon: thanks for module! very appreciated thing!

However current limitations don't give me a change to use it in production.

Do you plan to fix specifically this: "When using PageListSelect, PageListSelectMultiple, and PageAutoComplete, if there is more than one page field on a given edit page and at least one of them has the edit link feature enabled, all of the Page fields using those inputs will show the edit links."?

Also, I'd kindly ask to leave opportunity to edit locked visibility Page fields as "locked" here means that field cannot be changed, not content of its page. 

Share this post


Link to post
Share on other sites

Hi valan,

Have you tested the module yet to see if it will work for your needs? I'm not sure I fully understand your question, but it sounds like you want to be able to set the visibility property of a particular page field to "Open when populated and not editable (locked)" but still have the edit link show? Is that correct?

The issue with this and with the other limitation you asked about is the fact that PW doesn't always provide the necessary CSS/JS hooks to be as granular as I would like (strangely, it does for some of the inputfields but not others). Ryan may have fixed this in 2.6, but I haven't had a chance to look at it again. I would like to fix this at some point, if possible!

  • Like 1

Share this post


Link to post
Share on other sites

@thetuningspoon: yes, I've tested module. Limitations stop broad usage of such needed module in production env. May I suggest you to request Ryan needed hooks? I guess Ryan should be aware/agree and put it in "todo" list first. I'm sure all PW devs will support prioritization.) Thanks!

Share this post


Link to post
Share on other sites

Somehow the module seems to not work on user pages. I've users with an alternative user template, that holds a select pagefield. But even thought the checkbox to add the link is checked, there's nothing rendering.

Share this post


Link to post
Share on other sites

Just to confirm, is the page field you're working with an inputfieldSelect (drop down html select) or something else?

Currently I need to update the module to work with Ryan's new singular inputfieldAutocomplete, but it sounds like this is a different issue.

Share this post


Link to post
Share on other sites

hi,

this feature would fit perfectly in a project i'm developing right now on 2.6.13 with a autocomplete pagefield. unfortunately it does not work with the new condensed format of single page selects! https://processwire.com/blog/posts/new-ajax-driven-inputs-conditional-hooks-template-family-settings-and-more/#improvements-to-the-page-autocomplete-input

on multiple selects it works as expected and it's really helpful!!

thanks for the module and i hope there's an easy fix for that :)

edit: what do you think about a link to a modal to ADD a new page to a defined parent. i know one can define "allow adding of pages" but i think there are situations where that is not really user friendly or even not possible because you have some required fields that you can't populate in one line of a pagefield. at least in my scenario (invoicing app) it would be great to have the possibility to create a new invoice, select the receipient and if it's a new client have the possibility to click on "create new" and it opens a modal where you can fill in all the necessary data.

in this scenario it would just need an additional field for storing the parent of the newly created pages. but maybe a more flexible solution would be to define the parent dynamically (like "return $page->siblings('title=clients');" or the like)

what do you think? dreaming of something like "page field enhanced" :D;)

  • Like 1

Share this post


Link to post
Share on other sites

Hi BernhardB,

I'm aware of the issue and actually have an update to support the single page autocompletes which I'm already using on one of my projects, but haven't gotten around to merging it with the Github project yet.

Believe it or not, I've also been experimenting with adding an "add new" link just like you suggested here. The biggest problem I'm having with this is figuring out how to automatically populate the field with this new page once it's published. I'll have to study how Ryan does this when creating a new field in the template editor.

  • Like 1

Share this post


Link to post
Share on other sites

sounds good :)

Believe it or not, I've also been experimenting with adding an "add new" link just like you suggested here. The biggest problem I'm having with this is figuring out how to automatically populate the field with this new page once it's published. I'll have to study how Ryan does this when creating a new field in the template editor.

i've not even thought about updating the pagefield automatically when one has added a new item, but that would definitely make sense. good luck with ryans code ;)

Share this post


Link to post
Share on other sites

Ok, updates!

  • Regular asm inputfields now work dynamically without the need for a page save
  • Compatible with the new singular autocomplete fields
  • Links are now fully configurable on a field-by-field basis
  • Implemented preliminary "Add New" functionality to enable adding pages via modal window right from the field
  • Changed "Edit" link labels to "View" (just my preference... but maybe this could be made configurable down the road)
  • Code cleanup and optimization

Note that after you upgrade you may have to re-set your page fields (just the edit link checkbox, not the whole field).

post-449-0-59535900-1439865375_thumb.png

post-449-0-08167000-1439865392_thumb.png

  • Like 6

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)