Jump to content
tpr

Module(tte): InputfieldURLChecker

Recommended Posts

InputfieldURLChecker

This is a tiny module to add a URL check button to InputfieldURL. It's live, meaning that it opens what you just typed in, and visible only if the field is non-empty. It's as unobtrusive as can :)

Modules directory

GitHub

It would be the best if something similar would be built-in to PW.

post-3156-0-39566700-1445099748_thumb.gi

There will be probably some tweaks and settings in the future. Suggestions welcome (even for module name).

Edited by tpr
  • Like 10

Share this post


Link to post
Share on other sites

v0.7 is ready. Download link in the first post.

Configuration

post-3156-0-44779500-1445162194_thumb.pn

Changelog

  • fixed link height when URL field is under admin tab (works with ajax-loaded tabs)
  • fixed link height when first tab didn't have any URL field
  • namespaced JS
  • new option: ctrl+shift+click and ctrl+shift+enter modes
  • new option: force http prefix
  • new option: limit module to list of enabled fields

What I plan to add in the future is opening links in a lightbox, and perhaps allowing all 3 modes to be used at the same time. But I think I'll do these only if there's a demand.

  • Like 2

Share this post


Link to post
Share on other sites

Very nice! I don't think you can call it modulette anymore :)

Share this post


Link to post
Share on other sites

It's still a modulette compared to other heavyweight modules :)

The first post contains the link to the GitHub page (v0.8). There was a small code optimization but otherwise it's the same as v0.7.

  • Like 1

Share this post


Link to post
Share on other sites

Hi,

a very useful Modul(ette). :)

Primarily, it is not the "amount" of code what tells about the "weight" of a module. :lol:

------

BTW, when having a look at Github, I spotted DIRECTORY_SEPARATOR in URLs for script and style loading. Shouldn't it be a simple / (slash) instead?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! DIRECTORY_SEPARATOR was indeed unnecessary, I guess it was a victim of a copy-paste operation :)

Unfortunately there were other bugs to fix. Just realized there are ajax-loaded FIELDS too and not only tabs. Now these are covered too (v0.85).

Positioning of the links was improved too, and fixed the issue when the field had description or notes.

Later I'll add enabled_templates function to make it more versatile, plus make field value clickable if the field is set to "closed + locked".

If I knew there are so many field options to take into account I probably won't start this module :)

  • Like 2

Share this post


Link to post
Share on other sites

v0.9 is up:

  • new option: enabled templates
  • linkify locked field:

post-3156-0-67391400-1445258920_thumb.pn

  • Like 1

Share this post


Link to post
Share on other sites

I was about to ask help here but finally solved things on my own (and looking into other modules).

v0.92 allows using the module on all admin pages. So far it was only added to pages where ProcessPageEdit could hook to, so for example now it is available on other modules's settings pages, or the new module install screen:

InputfieldURLChecker.gif

New (default) option was added: button-left - this is handier because the button is not on the far-right end of the input.

Also the appearance was changed a bit: colored arrow appears only on hover, otherwise remains gray. The button itself is visible all the time, even if the field is empty.

The height of the button was also fixed by adding a dummy url field on start, just to measure its height (and then it's removed). Other measurements were unfortunately buggy.

I'm still looking for a better module name, though I kinda like the abbreviation "TUF", which is used heavily in the JS for naming.

Locked fields got an underline on hover, just to make them more usable.

  • Like 2

Share this post


Link to post
Share on other sites

Tremendous Url Field ?  :)

  • Like 1

Share this post


Link to post
Share on other sites

Not exactly the one I'm after, but thanks :) Keeping the first characters is a good idea, I'll go on that route :)

  • Like 1

Share this post


Link to post
Share on other sites

Okay, settled with "InputfieldURLChecker" as the module name as I found no better one.

In the last few days the module got some major updates:

  • allow button and hotkey modes to be used together
  • asmSelect fields for enabled fields/templates
  • add "placeholder" to asmSelect fields
  • make strings translatable (with __FILE__ textdomain)
  • JS optimizations/fixes

Check the github repo for the details - the options page screenshot shows most of them.

  • Like 4

Share this post


Link to post
Share on other sites

Great!

Please, can you add it to the modules directory too?

It's done in less then 2 minutes, as you have it in a github repo. :)

  • Like 1

Share this post


Link to post
Share on other sites

I'm experimenting with loading the URL in an iframe, sliding in from the right side of the browser window. It works in most cases but fails if the target site's X-Frame-Options is set to SAMEORIGIN, like here on this forum. Unfortunately this is something that cannot be check on the client side. However, I will keep this feature with a note in the readme.

post-3156-0-85631800-1445866999_thumb.gi

Share this post


Link to post
Share on other sites

I'm not having any luck getting this to work... no arrow is shown;

I'm on Mac, Firefox, Chrome, but no luck;

templates and fields all setup....

no js errors..

Any idea what might be the cause, or how to troubleshoot?

TIA

Share this post


Link to post
Share on other sites

I just installed from the module directory (entered the classname "InputfieldURLChecker") and worked fine.

I'm on Win but I don't think that could be an issue. What FF/Chrome versions are you using?

I guess you tried it on az URL type field and not on a regular InputfieldText.

In the module settings, have you added anything to the "Enabled templates" and "Enabled fields" area? If so, the module will be active only in those templates/fields, and unavailable elsewhere.

Also make sure the Mode is set to "Button" and not hotkey.

On the admin page where you expect the button to appear, check the page source if it contains "IUC"  within a script tag in the head.

Share this post


Link to post
Share on other sites

hey tpr - thanks and also let me thank you for this module, it looks great, and you have put a lot of work into it - it will be really handy for this project i'm working on where we need to check that links to external sites are working/correct!

So i checked everything and troubleshot it to where i have narrowed down the issue to the field restriction - if that is set, then it doesn't work; setting the template restriction works... being that i don't really need to restrict by field, i'm all good, but i can further assist with this issue if you need more info.

thanks again!

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, version 1.0.5 is up on GitHub with the fix.

  • Like 2

Share this post


Link to post
Share on other sites

I will rewrite half of the module to take advantage of InputfieldUrl::render, which would make things simpler. Now JavaScript makes all the heavyweight stuff which works, but it's too clunky here and there.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, version 1.0.5 is up on GitHub with the fix.

great - thanks! Checked it and it's all working now...

Also looking forward to the next version!

Share this post


Link to post
Share on other sites

Just committed v1.1.0 to the dev branch at GitHub:

https://github.com/rolandtoth/InputfieldURLChecker/tree/dev

This is 99% the same in functionality but under the hood it uses InputfieldURL::render and InputfieldURL::renderValue.

The only new feature is that locked field urls now respect the module setting "Target", so clicking on them may open in an iframe if setting so.

Locked url fields with description or notes was linkified incorrectly in the previous (JS-only) version, as all the field contents were wrapped in a link, not only the url. Now it's handled beautifully with the renderValue hook.

Using backend hooks made it much simpler and reliable to deal with template/field restrictions, and probably there will be more benefits in further developments.

  • Like 4

Share this post


Link to post
Share on other sites

Is there a way to specify array in field name? I have this in getDefaultData:

static public function getDefaultData() {
        return array(
            'InputfieldURLChecker'         => array(
                'IUC_mode'              => array(
                    'button'
                ),
                'IUC_button_position'   => 'button-left',
                'IUC_target'            => 'new-window',
                'IUC_force_http'        => 1,
                'IUC_enabled_templates' => array(),
                'IUC_enabled_fields'    => array()
            )
	)
}

Now if I make a  field and set its name to 'IUC_mode' and save the module, the $data in getModuleConfigInputfields($data) will NOT have 'IUC_mode' under 'InputfieldURLChecker' (but a flat array).

I have tried this, but no joy:

$f = wire('modules')->get('InputfieldCheckboxes');
$f->name = 'InputfieldURLChecker["IUC_mode"]';
...

 

Share this post


Link to post
Share on other sites

Hi @tpr.

Thanks for the module.

I have spent some time to understand why the module doesn't work and the issue is that only ProcessPageEdit and ProcessProfile processes are allowed.

But I have several process modules that handle page edit of custom page types.  It would be great if we could control this option in the module config.

There is $modules->findByPrefix("), so maybe you can provide such options with ASM select by $modules->findByPrefix("Process");

Thanks. 

Share this post


Link to post
Share on other sites

Thanks. Are you using AdminOnSteroids? Because this module is not updated for a while since I added it to AOS.

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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-07-03 -- SnipWire 0.8.7 (beta) released! Fixes some small bugs and adds an indicator for TEST mode 2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  

       
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By Sten
      Hello
      Till now I hacked something with the twig template but it works no more with new PW versions so I look forward to create a module. I am working on a site in multiple languages : French, English, Italian, German, Spanish, Portuguese, Hebrew, Russian. The new posts are entered in any language with a field for language. Till now, I got twig files to get the translations with constants defined for each part of the pages.
      So I'd like to create a module to include theses files added according to the url /fr/en/...
      Have you some observations to do before I begin about the direction to take ?
      Thank you
    • By ukyo
      Mystique Module for ProcessWire CMS/CMF
      Github repo : https://github.com/trk/Mystique
      Mystique module allow you to create dynamic fields and store dynamic fields data on database by using a config file.
      Requirements
      ProcessWire 3.0 or newer PHP 7.0 or newer FieldtypeMystique InputfieldMystique Installation
      Install the module from the modules directory:
      Via Composer:
      composer require trk/mystique Via git clone:
      cd your-processwire-project-folder/ cd site/modules/ git clone https://github.com/trk/Mystique.git Module in live reaction with your Mystique config file
      This mean if you remove a field from your config file, field will be removed from edit screen. As you see on youtube video.
      Using Mystique with your module or use different configs path, autoload need to be true for modules
      Default configs path is site/templates/configs/, and your config file name need to start with Mystique. and need to end with .php extension.
      Adding custom path not supporting anymore !
      // Add your custom path inside your module class`init` function, didn't tested outside public function init() { $path = __DIR__ . DIRECTORY_SEPARATOR . 'configs' . DIRECTORY_SEPARATOR; Mystique::add($path); } Mystique module will search site/modules/**/configs/Mystique.*.php and site/templates/Mystique.*.php paths for Mystique config files.
      All config files need to return a PHP ARRAY like examples.
      Usage almost same with ProcessWire Inputfield Api, only difference is set and showIf usage like on example.
      <?php namespace ProcessWire; /** * Resource : testing-mystique */ return [ 'title' => __('Testing Mystique'), 'fields' => [ 'text_field' => [ 'label' => __('You can use short named types'), 'description' => __('In file showIf working like example'), 'notes' => __('Also you can use $input->set() method'), 'type' => 'text', 'showIf' => [ 'another_text' => "=''" ], 'set' => [ 'showCount' => InputfieldText::showCountChars, 'maxlength' => 255 ], 'attr' => [ 'attr-foo' => 'bar', 'attr-bar' => 'foo' ] ], 'another_text' => [ 'label' => __('Another text field (default type is text)') ] ] ]; Example:
      site/templates/configs/Mystique.seo-fields.php <?php namespace ProcessWire; /** * Resource : seo-fields */ return [ 'title' => __('Seo fields'), 'fields' => [ 'window_title' => [ 'label' => __('Window title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'attr' => [ 'placeholder' => __('Enter a window title') ] ], 'navigation_title' => [ 'label' => __('Navigation title'), 'type' => Mystique::TEXT, // or InputfieldText 'useLanguages' => true, 'showIf' => [ 'window_title' => "!=''" ], 'attr' => [ 'placeholder' => __('Enter a navigation title') ] ], 'description' => [ 'label' => __('Description for search engines'), 'type' => Mystique::TEXTAREA, 'useLanguages' => true ], 'page_tpye' => [ 'label' => __('Type'), 'type' => Mystique::SELECT, 'options' => [ 'basic' => __('Basic page'), 'gallery' => __('Gallery'), 'blog' => __('Blog') ] ], 'show_on_nav' => [ 'label' => __('Display this page on navigation'), 'type' => Mystique::CHECKBOX ] ] ]; Searching data on Mystique field is limited. Because, Mystique saving data to database in json format. When you make search for Mystique field, operator not important. Operator will be changed with %= operator.
      Search example
      $navigationPages = pages()->find('my_mystique_field.show_on_nav=1'); $navigationPages = pages()->find('my_mystique_field.page_tpye=gallery');
    • By Robin S
      This is a module I made as an experiment a while ago and never got around to releasing publicly. At the time it was prompted by discussions around using Repeater fields for "page builder" purposes, where the depth feature could possibly be used for elements that would be nested inside other elements. I thought it would be useful to enforce some depth rules and translate the depth data into a multi-dimensional array structure.
      I'm not using this module anywhere myself but maybe it's useful to somebody.
      Repeater Depth Helper
      This module does two things relating to Repeater fields that have the "Item depth" option enabled:
      It enforces some depth rules for Repeater fields on save. Those rules are:
      The first item must have a depth of zero. Each item depth must not be more than one greater than previous item depth. It provides a RepeaterPageArray::getDepthStructure helper method that returns a nested depth structure for a Repeater field value.
      Helper method
      The module adds a RepeaterPageArray::getDepthStructure method that returns a multi-dimensional array where the key is the page ID and the value is an array of nested "child" items, or null if there are no nested children.
      Example

      The module doesn't make any assumptions about how you might want to use the depth structure array, but here is a way you might use it to output a nested unordered list.
      // Output a nested unordered list from a depth structure array function outputNestedList($depth_structure, $repeater_items) { $out = "<ul>"; foreach($depth_structure as $page_id => $nested_children) { $out .= "<li>" . $repeater_items->get("id=$page_id")->title; // Go recursive if there are nested children if(is_array($nested_children)) $out .= outputNestedList($nested_children, $repeater_items); $out .= "</li>"; } $out .= "</ul>"; return $out; } $repeater_items = $page->my_repeater; $depth_structure = $repeater_items->getDepthStructure(); echo outputNestedList($depth_structure, $repeater_items);
       
      https://github.com/Toutouwai/RepeaterDepthHelper
      https://modules.processwire.com/modules/repeater-depth-helper/
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
×
×
  • Create New...