Jump to content

Inputfield ACE Extended


owzim

Recommended Posts

  • 2 weeks later...

just tried your module and i love it! great for my geowire project where i'm working on an update right now. i wanted to suggest a fullscreen mode, but i saw it's already on your roadmap... +1 for that. would really be great :)

thanks for the awesome work!

Link to comment
Share on other sites

  • 1 month later...

Maybe this can be useful to people. It replaces a normal textarea in the backend with an ace instance.

class AdminHelper extends WireData implements Module{

	const phpFirstLine = "<?php //autmatically added but not saved";

	public function init() {
		// Inputfield Ace Extended for editing page fields
		$this->addHookAfter('InputfieldPage::getConfigInputfields', $this, 'makePHPFieldACEField');
		$this->addHookBefore('ProcessField::executeSave', $this, 'removeLeadingTag');
	}

	public function makePHPFieldACEField($event){
		$form = $event->return;

		$field = $form->get("findPagesCode");

    $ace = $this->modules->get("InputfieldAceExtended");
    // foreach (get_object_vars($field) as $key => $name) {
    //     $obj->$key = $name;
    // }
    $ace->setAttributes($field->getAttributes());
    $ace->setArray($field->getArray());
		$ace->modes = array("php");
		$linecount = substr_count($ace->attr("value"), "\n");

		// Preserve collapsed mode and do not add when build for saving
		if($ace->attr("value") !== "" && !$this->input->post->findPagesCode)
			$ace->attr("value", self::phpFirstLine."\n\n".$ace->attr("value"));
		$ace->rows = $linecount ? $linecount : 4;

		$field->parent->insertAfter($ace, $field);
		$field->parent->remove($field);

		$event->return = $form;
	}

	public function removeLeadingTag($event){
		if($this->input->post->findPagesCode && strpos($this->input->post->findPagesCode, self::phpFirstLine) !== false){
			$this->input->post->findPagesCode = trim(str_replace(self::phpFirstLine, "", $this->input->post->findPagesCode));
		}
	}
}
Edited by LostKobrakai
Small update
  • Like 2
Link to comment
Share on other sites

pretty interesting - what would be a good use case for this method, as opposed to making the field itself an AceExtended field? I might be being thick, but am not getting that...

  • Like 1
Link to comment
Share on other sites

The custom php code field for page fields is sometimes a little more complex on a current project and I wanted it to sport an better editing interface and syntax highlighting. My module does convert the standart textarea there to an ace textarea. There isn't a field behind this form, where one could simply change the inputfielClass for. So it's useful for all the process module forms.

Link to comment
Share on other sites

  • 3 months later...
  • 6 months later...

hi owzim,

i've used your module in the past quite a lot without problems. thank you for that. :)

now i tried to use it in the new matrix repeater on 3.0.12 and this is what it looks like:

post-2137-0-07256300-1458818415_thumb.pn

seems to work fine with 3.0.12 when you add it in the normal way to a template. in the repeater it does not support code highlighting and also the settings will get lost on save.

any chance that we get an update on this? although i have to say it is not critical for me as this is only ment to copy&paste some code to my blog and i will not write much code directly there...

edit: note that i also tried setting "PHP" not "plain text" as the screenshot shows...

  • Like 2
Link to comment
Share on other sites

  • 2 months later...
  • 5 months later...

@Robin S thanks for the report. I will add an extra json settings field for modes in the field config. I am sick right now but I'll look into it, later this week.

Edit: Can't test right now, but you might be able to set this in the advanced options of the field config.

  • Like 1
Link to comment
Share on other sites

15 minutes ago, owzim said:

I will add an extra json settings field for modes in the field config. I am sick right now but I'll look into it, later this week.

Thanks! Hope you feel better soon.

39 minutes ago, owzim said:

edit: can't test right now, but you might be able setting this in the advanced settings of the field config.

I tried a few things but I don't have a good grasp of how the recommended way to set inline mode...

session.setMode({path:"ace/mode/php", inline:true})

...relates to the module's implementation of Ace. The only thing I could find relating to the PHP inline mode is in mode-php.js:

...
"ace/mode/php-inline"
...

So maybe this is an alternative way to set PHP inline mode? Hard to make sense of it with the source being minified.

Link to comment
Share on other sites

  • 7 months later...

Great plug in.  Working great.  Noticed an issue when trying to use it on a multi language textarea.  I only put html in the "English" field and after save this is what you get.  No big deal I just wanted to make you aware of it if you weren't already.

(see attached screen shot)5981f48995689_ScreenShot2017-08-02at10_47_02AM.thumb.png.67ffcd6ed434a54307433a78204865b8.png

Link to comment
Share on other sites

  • 1 month later...
On 3/24/2016 at 2:22 PM, bernhard said:

i tried to use it in the new matrix repeater on 3.0.12 and this is what it looks like:

post-2137-0-07256300-1458818415_thumb.pn

I'm having the same issue.

It appears that this happens because Repeater fields add new items using AJAX, and InputfieldAceExtended loads its scripts with $config->scripts in render() method. But it doesnt work as PW does not consider rendering the scripts in $config->scripts when loading an input with AJAX. Quick solution is to append <script> and <link> or <style> tags after inputfield markup. From a quick search, native and profields don't seem to have this issue because they use the scripts that are loaded on backend by default.

I think solution is up to @ryan at this point. When rendering the field PW should output scripts & styles too.

// InputfieldWrapper.php
public function ___renderInputfield(Inputfield $inputfield, $renderValueMode = false) {
    // ...
    if($ajaxInputfield) {
        
        $inputfieldID = $inputfield->attr('id');
        
        if($ajaxID && $ajaxID == $inputfieldID) {
            // render ajax inputfield
            $editable = $inputfield->editable();
            if($renderValueMode || !$editable) {
                echo $inputfield->renderValue();
            } else {
                echo $inputfield->render();
                echo "<input type='hidden' name='processInputfieldAjax[]' value='$inputfieldID' />";
                // Get scripts from $this->config->scripts and output to browser
            }
            exit;
        //...

 

  • Like 3
Link to comment
Share on other sites

42 minutes ago, abdus said:

From a quick search, native and profields don't seem to have this issue because they use the scripts that are loaded on backend by default.

10 minutes ago, bernhard said:

I might be wrong but I think scripts get loaded when added inside the init method of the inputfield

I believe this is what Inputfield::renderReady() is for: adding dependencies to $config->scripts and $config->styles, and also adding JS objects to ProcessWire.config via $config->js().

But I think all this is not well understood by module developers, myself included. Would be great to get a tutorial some time, maybe in a weekly blog post @ryan?

 

  • Like 2
Link to comment
Share on other sites

For inputs that are loaded without ajax, scripts work fine, because they're served inside the whole page markup

But for ajax inputs that's not the case.

Here's the response to an AJAX request. I removed class, id, name, and for attributes because they were taking up too much space. The only script is at the end which initializes tabs and submit buttons.

Spoiler

<p>1024</p>
<form>
    <ul uk-grid>
        <li>
            <label><i></i> Content<i></i></label>
            <div>
                <ul uk-grid>
                    <li>
                        <label><span>Markdown {&bull; New}</span><i></i></label>
                        <div>
                            <ul uk-grid>
                                <li><label>loaded_repeater1114<i></i></label><div><input value="1" type="hidden" /></div></li>
                                <li><label>Sort<i></i></label><div><input value="0" type="hidden" /></div></li>
                                <li><label><span>Delete<i></i></span></label><div><label><input type='checkbox' value="1114" /><span>Delete</span></label></div></li>
                                <li><label>publish_repeater1114<i></i></label><div><input value="1" type="hidden" /></div></li>
                                <li>
                                    <ul uk-grid>
                                        <li><label><i></i> Content<i></i></label><div>
                                            <div data-input data-field>
                                                    <ul uk-grid>
                                                        <li><label><i></i> Options<i></i></label>
                                                            <div><span><span>Theme</span> <span><select><option
                                                                    value='tomorrow'>Tomorrow</option><option
                                                                    value='chrome'>Chrome</option><option
                                                                    value='monokai'>Monokai</option><option
                                                                    value='twilight'>Twilight</option></select></span></span><span><span>Language</span> <span><select><option value='plain_text'>Plain Text</option><option
                                                                    value='css'>CSS</option><option
                                                                    value='html'>HTML</option><option
                                                                    value='javascript'>JavaScript</option><option
                                                                    value='json'>JSON</option><option value='markdown'>Markdown</option><option
                                                                    value='php'>PHP</option><option
                                                                    value='yaml'>YAML</option><option value='python'>Python</option></select></span></span><span><span>Font size</span> <span><input
                                                                    value="14" type="number"
                                                                    min="10" max="28"
                                                                    size="10"/></span></span>
                                                            </div></li></ul><div>
                                                        <div></div>
                                                    </div>
                                                    <textarea rows="5"></textarea>
                                            </div>
                                        </div></li></ul></li></ul></div></li></ul></div></li>
        <li><div><button value="Save" type="submit"><span>Save</span></button></div></li>
        <li><label>id<i></i></label><div><input value="1024" type="hidden" /></div></li>
    </ul>
    <input type='hidden' value='Wbzssyv52R1o8qZzfEHZRFjKz/pwLU9b' />
</form>
<script>
    initPageEditForm();
</script>

 

Link to comment
Share on other sites

For inputs that are loaded without ajax, scripts work fine, because they're served inside the whole page markup

But for ajax inputs that's not the case.

Here's the response to an AJAX request. I removed class, id, name, and for attributes because they were taking up too much space. The only script is at the end which initializes tabs and submit buttons.

Spoiler

<p>1024</p>
<form>
    <ul uk-grid>
        <li>
            <label><i></i> Content<i></i></label>
            <div>
                <ul uk-grid>
                    <li>
                        <label><span>Markdown {&bull; New}</span><i></i></label>
                        <div>
                            <ul uk-grid>
                                <li><label>loaded_repeater1114<i></i></label><div><input value="1" type="hidden" /></div></li>
                                <li><label>Sort<i></i></label><div><input value="0" type="hidden" /></div></li>
                                <li><label><span>Delete<i></i></span></label><div><label><input type='checkbox' value="1114" /><span>Delete</span></label></div></li>
                                <li><label>publish_repeater1114<i></i></label><div><input value="1" type="hidden" /></div></li>
                                <li>
                                    <ul uk-grid>
                                        <li><label><i></i> Content<i></i></label><div>
                                            <div data-input data-field>
                                                    <ul uk-grid>
                                                        <li><label><i></i> Options<i></i></label>
                                                            <div><span><span>Theme</span> <span><select><option
                                                                    value='tomorrow'>Tomorrow</option><option
                                                                    value='chrome'>Chrome</option><option
                                                                    value='monokai'>Monokai</option><option
                                                                    value='twilight'>Twilight</option></select></span></span><span><span>Language</span> <span><select><option value='plain_text'>Plain Text</option><option
                                                                    value='css'>CSS</option><option
                                                                    value='html'>HTML</option><option
                                                                    value='javascript'>JavaScript</option><option
                                                                    value='json'>JSON</option><option value='markdown'>Markdown</option><option
                                                                    value='php'>PHP</option><option
                                                                    value='yaml'>YAML</option><option value='python'>Python</option></select></span></span><span><span>Font size</span> <span><input
                                                                    value="14" type="number"
                                                                    min="10" max="28"
                                                                    size="10"/></span></span>
                                                            </div></li></ul><div>
                                                        <div></div>
                                                    </div>
                                                    <textarea rows="5"></textarea>
                                            </div>
                                        </div></li></ul></li></ul></div></li></ul></div></li>
        <li><div><button value="Save" type="submit"><span>Save</span></button></div></li>
        <li><label>id<i></i></label><div><input value="1024" type="hidden" /></div></li>
    </ul>
    <input type='hidden' value='Wbzssyv52R1o8qZzfEHZRFjKz/pwLU9b' />
</form>
<script>
    initPageEditForm();
</script>

 

Link to comment
Share on other sites

7 minutes ago, Robin S said:

I believe this is what Inputfield::renderReady() is for: adding dependencies to $config->scripts and $config->styles, and also adding JS objects to ProcessWire.config via $config->js().

True, but still, inside InputfieldWrapper.php where a field is determined to be rendered with ajax or not, it calls renderReady(), it has no effect because Inputfield::renderReady() still uses $config->styles and $config->scripts (via Modules::loadModuleFileAssets() method), and only the inputfield markup is output to the browser.

//  InputfieldWrapper::renderInputfield
$inputfield->renderReady($this, $renderValueMode);
// ...
if($ajaxID && $ajaxID == $inputfieldID) {
    // render ajax inputfield
    $editable = $inputfield->editable();
    if($renderValueMode || !$editable) {
        echo $inputfield->renderValue();
    } else {
        echo $inputfield->render();
        echo "<input type='hidden' name='processInputfieldAjax[]' value='$inputfieldID' />";
    }
    exit;

}

 

// Inputfield.php
public function renderReady(Inputfield $parent = null, $renderValueMode = false) {
   if($parent) {}
   if($renderValueMode) {}
   $result = $this->wire('modules')->loadModuleFileAssets($this) > 0;
   if($this->wire('hooks')->isMethodHooked($this, 'renderReadyHook')) {
      $this->renderReadyHook($parent, $renderValueMode);
   }
   return $result;
}

 

// Modules.php
/**
 * Load module related CSS and JS files (where applicable)
 * 
 * - Applies only to modules that carry class-named CSS and/or JS files, such as Process, Inputfield and ModuleJS modules. 
 * - Assets are populated to `$config->styles` and `$config->scripts`.
 * 
 * #pw-internal
 * 
 * @param Module|int|string $module Module object or class name
 * @return array Returns number of files that were added
 * 
 */
public function loadModuleFileAssets($module) {}
Link to comment
Share on other sites

17 minutes ago, abdus said:

True, but still, inside InputfieldWrapper.php where a field is determined to be rendered with ajax or not, it calls renderReady(), it has no effect because Inputfield::renderReady() still uses $config->styles and $config->scripts (via Modules::loadModuleFileAssets() method), and only the inputfield markup is output to the browser.

You'd think so, but test it and I think you'll find that assets added in renderReady() are always loaded when the inputfield may appear in Page Edit, even if AJAX-loaded. So for example, you can put an inputfield with a JS dependency such as PageAutocomplete in a repeater, and put that repeater inside another repeater (so the PageAutocomplete inputfield is definitely not being rendered initially) and you'll find that the PageAutocomplete JS dependency is included in Page Edit. PW seems to be smart like that.

  • Like 2
Link to comment
Share on other sites

1 hour ago, Robin S said:

So for example, you can put an inputfield with a JS dependency such as PageAutocomplete in a repeater, and put that repeater inside another repeater (so the PageAutocomplete inputfield is definitely not being rendered initially) and you'll find that the PageAutocomplete JS dependency is included in Page Edit. PW seems to be smart like that.

Hmm, you're right. Scripts are output inside <head> during page load.

Then it's developer's responsibility to make sure that inputfields are initialized correctly. This requires a <script> tag to be appended to inputfield markup, which sets up the inputfield with given ID. This would also mean having to save the state somewhere (data attributes, ProcessWire.config etc) to prevent initializing an inputfield twice. Or using a library to listen to DOM mutations and initializing the inputfields inside.

https://github.com/muicss/sentineljs

I agree that a guideline/tutorial from @ryan would be great.

  • Like 2
Link to comment
Share on other sites

in my last update from InputfieldHandsontable I inject the scripts in the init method: https://gitlab.com/baumrock/FieldtypeHandsontable/blob/master/InputfieldHandsontable.module#L26-35

field-specific CSS is loaded inside the render method with jquery like this: https://gitlab.com/baumrock/FieldtypeHandsontable/blob/master/InputfieldHandsontable.module#L61-69

+1 for a comprehensive tutorial on this :)

thanks @abdus sentineljs looks nice!

  • Like 2
Link to comment
Share on other sites

Hi, I ran into this issue a while back and remember fixing it but haven't pushed to master. I will have to look into it. I think it might work on the dev branch, not sure though.

Edit: yup it's fixed on the dev branch. I use it on a production site, but I appreciate any quick testing in your environments, so that I can merge it into master, if no further issues arise.

Thanks for reporting!

  • Like 1
Link to comment
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 FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...