kongondo

Module: RuntimeMarkup Fieldtype & Inputfield

Recommended Posts

Posted (edited)
On 4/21/2018 at 12:39 AM, adrian said:

Is there any reason they can't just return true, rather than returning $this->renderMarkup($page, $field); ?

Hi @adrian,

 ___wakeupValue is needed for frontend access. I am assuming some people use the field in the frontend.   ___sleepValue should be able to work with return true only. I'll have to investigate deeper though. The whole module is based on Ryan's concat field. These methods were copied as is (or almost) from that module. So, his module must be having the same issues then.

I'll have a look sometime. Still no ETA though, sorry.

Edited by kongondo
  • Like 2

Share this post


Link to post
Share on other sites

Taking a further look, I agree that wakeupValue is needed in case someone does use on the frontend, but I can't see a need for loadPageField() - so if it was limited to just wakeupValue then it would reduce processing of the code to just once.

  • Like 2

Share this post


Link to post
Share on other sites
Posted (edited)
On 3/16/2018 at 4:30 PM, adrian said:

I am noticing that the renderMarkup() method is called many times on the currently edited page and it's also called on page reference fields on the page being edited. This makes for a lot of calls to this method that don't seem necessary as far as I can tell. Do you think this can be improved?

As an example, I put: bd($page->id); at the top of that method and saw this:

@adrian,

I have tested and cannot replicate this. I tested with both single and multi page reference fields using different inputs (Asm, Checkboxes, etc). I also tested using render via code and via wire('files')->render('some-file'). This is what I get if I put bd($page->id) at the top of renderMarkup().

rm-dump-tracy.png.1513da23878639171af413146d9e11b2.png

1367 is the ID of the page being edited. The pages saved in the page reference fields are not called.

Edit

I think there is something else going on in your install. There is nothing peculiar about the field. Apart from renderMarkup(), all the other methods are ProcessWire Field methods. Theoretically, it means if a bug exists, then all Fields should be exhibiting the same behaviour.

 

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
11 hours ago, adrian said:

but I can't see a need for loadPageField() - so if it was limited to just wakeupValue then it would reduce processing of the code to just once.

loadPageField() is required to stop the field from visiting the database. There is a comment right there in the method :).

Quote

// generate value at runtime rather than loading from DB

If we remove the method, it will just call its parent loadPageField() (Fieldtype.php). Hence, we override it. We can have it return true. That results in renderMarkup() being called once only (rather than twice currently - once each for wakeupValue() and loadPageField()).

Edited by kongondo

Share this post


Link to post
Share on other sites

I've tried to change the title of the page and it works

$page->set('title', 'New title');
$page->save();
return "";

but when I try to change an inputfield of type text it doesn't

$page->my_field = '22223333';
// $page->my_field->attr('value', '22223333'); neither works
$page->save();
return "";

any advice, thanks.

Share this post


Link to post
Share on other sites

Using Runtimemarkup I've tried to change the title of the page and it works

$page->set('title', 'New title');
$page->save();
return "";

but when I try to change an inputfield of type text it doesn't

$page->my_field = '22223333';
// $page->my_field->attr('value', '22223333'); neither works
$page->save();
return "";

any advice, thanks.

Share this post


Link to post
Share on other sites

Thanks flydev, is not the case, but give this module a try  it opens up a new world.

Share this post


Link to post
Share on other sites

I just tested and it work well. And yes, look a cool module 🙂

 

settingruntimetest.thumb.png.35e15754e89db4db033a1ac2ef18b30f.png

 

runtimetest.thumb.png.375d408a8729b69eb13ed05ee96fd714.png

 

  • Like 2
  • Thanks 1

Share this post


Link to post
Share on other sites

I created a new field and you're right it works, I'll check it thoroughly, many thanks.

  • Like 1

Share this post


Link to post
Share on other sites

Is any way to get the value of a field (Runtimemarkup) from a template :

$out .= strtoupper(dechex(strtotime(date("Y-m-d H:i:s", $page->created))));
return $out;

 

I'm getting the following error:

Field 'code_codigo' is runtime and not queryable

Share this post


Link to post
Share on other sites

Looking at the code, it seem not :

public function getMatchQuery($query, $table, $subfield, $operator, $value) {
		// we don't allow this field to be queried
		throw new WireException("Field '{$query->field->name}' is runtime and not queryable");
}

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)

@Manol,

It seems your question has been answered?

Moderator Note

Please don't start different topics about the same issue. Also, use this module's support forum for all questions related to it. I have merged your other topic here.

 

Edited by kongondo

Share this post


Link to post
Share on other sites
Posted (edited)
1 hour ago, Manol said:

Is any way to get the value of a field (Runtimemarkup) from a template :

Yes you can get the value. See the examples in the first page, first post of this topic. However, you cannot use a selector to query the value.

1 hour ago, flydev said:

Looking at the code, it seem not :

Yes, you cannot use a selector to query it, but you can access the value.

Edited by kongondo
  • Like 1

Share this post


Link to post
Share on other sites
On 7/23/2017 at 3:04 PM, kongondo said:

For frontend, only pasted PHP code option is supported. My take is that this module is primarily used for the backend. Use of the render files option is geared for creating complex and/or more flexible backend apps as opposed to frontend usage. I have no intention of changing this behaviour.

Would be nice if it is consistent – I use this Field for both, backend and frontend and would love to have the code inside php files.

Share this post


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

Would be nice if it is consistent – I use this Field for both, backend and frontend and would love to have the code inside php files.

@Noel Boss see the dev version

Share this post


Link to post
Share on other sites
On 6/4/2018 at 6:21 PM, Macrura said:

the dev version

This is the description for the dev version. Did not work for me. Ended up with the master and:

namespace Processwire;
return wireRenderFile('fields/'.$field->name, ['page' => $page]);

 

Share this post


Link to post
Share on other sites
51 minutes ago, Noel Boss said:

This is the description for the dev version. Did not work for me. Ended up with the master and:


namespace Processwire;
return wireRenderFile('fields/'.$field->name, ['page' => $page]);

 

whatever version i'm using works great and has the option to use files and not pasted code, in the field config.. i thought it was the dev branch.. very stable and i have it running on 5 projects now, basically this is a completely indispensable module, i usually end up with on average 10-15 RM fields on any given project..

  • Like 1

Share this post


Link to post
Share on other sites
On 6/6/2018 at 5:06 PM, Macrura said:

basically this is a completely indispensable module

True, it's a great module. But does it work for you in the frontend with files? Because as @kongondo said here:

 

Quote

For frontend, only pasted PHP code option is supported.

 

  • Like 1

Share this post


Link to post
Share on other sites
Posted (edited)
6 hours ago, Noel Boss said:

This is the description for the dev version. Did not work for me. Ended up with the master and:


namespace Processwire;
return wireRenderFile('fields/'.$field->name, ['page' => $page]);

 

Works fine for me here with the dev version, but should also work with the master version (IIRC - sorry, it's been a while since I touched this). Tested in PW 3.0.85. Here's my copy pasted PHP code:

// both of these work
/*namespace Processwire;
return wireRenderFile('runtime-markup-wirerender-test');
*/
return ProcessWire\wireRenderFile('runtime-markup-wirerender-test');

The above allows you to have your code inside PHP files. This is the pasted PHP option. It is supported in both front- and back-end. It also allows you to use PHP files, but indirectly. It is not to be confused by the other (currently dev) option of directly rendering PHP files (i.e., just stating name of the PHP file and its path.

Are you getting any errors? Tracy?

In the template file I echo the field's value like so:

 

echo $page->runtime_markup;

 

Edited by kongondo

Share this post


Link to post
Share on other sites

Hi @kongondo 

No, this works just fine. But this is "pasted PHP code" – since you introduced the option to specify files on the dev Version, it would be nice to use this option also in the frontend;

Current status:

Dev Version:

– include files using module: Backend √ + Frontend X
– Past Code: Backend √ + Frontend √

Master Version:

– Include files using module: Backend X + Frontend X
– Past Code: Backend √ + Frontend √

Desired status 😉

Master Version:

– include files using module: Backend √ + Frontend √
– Past Code: Backend √ + Frontend √

Share this post


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

No, this works just fine. But this is "pasted PHP code" – since you introduced the option to specify files on the dev Version, it would be nice to use this option also in the frontend;

OK. I'll have a look. Could you please file it as a request on GitHub? It will help remind me, thanks.

  • Like 1

Share this post


Link to post
Share on other sites

Thank you Kogondo! BTW, this is one of the most useful Modules out there! Thank you for developing it!

  • Like 1

Share this post


Link to post
Share on other sites

Thank you for developing this useful module, now i can send email to certain user from admin easily, inspired from here :

For those who need more explanation:
Button is actually <a href> to template which will open new page (yes very ugly behaviour, read below) contain custom php code , not inside <form> action because <form> not allowed inside textarea.

To prevent opening new page when click the button, make an <iframe> inside the template as a target button, that's it, beautifully execution like native form in admin page.
 

  • Like 2

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 blad
      Hi guys!
      I just uploaded a module to explore files based on elFinder. By default it will show the "Files" folder.
      Screenshots:

      Video:
       
      To do:
       More options To fix:
       The function of rotating or scaling an image fails  Image editors V 1.01 (view issue)
      Fixed the bug working with the Multi-Language support ( translation of folders ). Fixed the name of elfinder.en  Github:
      https://github.com/LuisSantiago/ProcessElFinder/
      I hope you like it.
    • 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/