Jump to content
tpr

AdminOnSteroids

Recommended Posts

You mean mark deleted all + sorting buttons?

The first one alone seems superfluous as there is already a way to do it, even if it's not that obvious (double click on trash icon). But with sorting buttons it makes more sense. So you give me permission to use your module's code?

  • Like 1

Share this post


Link to post
Share on other sites

Sure! Feel free to take (and improve) it

  • Like 1

Share this post


Link to post
Share on other sites

... and what is about a text input filter box, like with my experiment on the croppable image input?

new-imagefield-and-extensions-01.gif

Share this post


Link to post
Share on other sites

I've already thought of a filter box. Here's a screencap of its current state but it's still in an early stage. It's capable of searching image names, descriptions (multilanguage) and tags, and multiple strings at once (separated by spaces).

Filtering worked fine only until name/tag/description were unchanged because filter targets were added on load. I solved this by clicking or focusing on the filter box re-adds all the filter targets. In fact all the filters are added only on the first click so if you don't use the filter it won't add too much overhead.

post-3156-0-66280600-1464901467_thumb.gi

  • Like 5

Share this post


Link to post
Share on other sites

! This sounds very good ! - Multilanguage and Descriptions and Tags and multiple Searchphrases - !

Man, you are awesome! ^-^  

I have seen some third party JS / jQuery scripts that do sorting and filtering, but the good ones wasn't OpenSource, and / or to bloated. Your solution sounds very good.

There are one thing I thought of while playing with that: would it be possible to filter for portrait and landscape oriented images? - or for the smallest / highest height or width?

And ahm, if you need beta tester, just call. :)

Share this post


Link to post
Share on other sites

Nothing extraordinary here :) I will try to polish things a bit today and upload a new version. There are a few additions I have in mind to the filter but it's main feature should work fine.

Landscape/portrait and size filters could go to the sorting buttons bernhard suggested, once I get to that.

  • Like 1

Share this post


Link to post
Share on other sites

v012 is uploaded with the new filterbox feature. I get the onleave confirmation message after using the field and tryng to leave the page, if anyone knows an easy way to solve this that would be welcomed.

post-3156-0-92713400-1464945544_thumb.gi

  • Like 5

Share this post


Link to post
Share on other sites

Another cosmetic fix for the filterbox: show only if there are at least 2 items to filter. It's evaluated dynamically on uploading images, so if the field is empty or contains only one image it will be hidden.

post-3156-0-40507400-1465045066_thumb.gi

Now it's "close to perfect" according to my set of standards :)

  • Like 3

Share this post


Link to post
Share on other sites

@tpr: I have one wish and an observation to share. :)

My wish is: "Please can we have in AdminReno-CompactHeader-view the toggle icon for the sidebar?" If one do not use autohide for the sidebar it currently is missing with the compact header view.

---

For me, on Windows 7 with Firefox, I do not have a sticky header with the default Admintheme.

The mastheads position is set to relative, I think it must be fixed. The classes of the html element are

<html class="aos_fixScrollbarJump aos_fileFieldToolbar aos_filterbox aos_stickyHeader aos_PagePreviewLink" lang="en">

Do you need more Infos?

  • Like 1

Share this post


Link to post
Share on other sites

I'll check the fixed pos, thanks.

You can toggle the sidebar with the right-left arrows in the Reno theme, isn't that suffice? I agree that it's not very obvious.

  • Like 2

Share this post


Link to post
Share on other sites

Oh! Thats perfect! I didn't know it. - Now I don't need the toggle-icon anymore. :)

Many thanks!

  • Like 2

Share this post


Link to post
Share on other sites

Haha that was worth the question :) It's 1/2 request done and I haven't even got home :)

  • Like 1

Share this post


Link to post
Share on other sites

Filterbox everywhere!

A major update to the filterbox: now available for file fields too. This was my original intention and now it's real :)

Admin theme default sticky header is also fixed. I switched to array an of classes instead simple string concat but forgot to update the default admin theme part.

  • Like 3

Share this post


Link to post
Share on other sites

It's me again :) - Thanks for the changes and new additions.

The sticky header in DefaultAdminTheme is working now, but only for screens >= 960px :)

Share this post


Link to post
Share on other sites

Here is perhaps one of the last additions to filterbox - datalist:

post-3156-0-04082600-1465295064_thumb.gi

Only image name or file name is displayed because using value+text didn't work in Firefox. Anyway, it can be a handy helper as it is.

  • Like 2

Share this post


Link to post
Share on other sites

Well, for filtering items :) E.g if you have many images or documents uploaded and you would like to find a specific one. Or if you go to the Language Translator, there can be many translation files and it can be hard finding the one you need without filtering.

  • Like 2

Share this post


Link to post
Share on other sites

i get the point for files. but i've never needed to filter images :) but the day will come, i'm sure ;)

Share this post


Link to post
Share on other sites

Maybe it makes more sense if you use image tags, or descriptions.

Share this post


Link to post
Share on other sites

v016 is uploaded to GitHub, containing the datalist feature for filterbox + a display bug fix reported by matjazp.

  • Like 2

Share this post


Link to post
Share on other sites

Filtering for filenames with images will / is be one of the most used functions of all for me. :)

If you have done the images your self and use a naming convention, this is the fasted way to find specific images / images groups out of hundreds. Also, with an own naming convention, (and knowing the images), you don't need to tag the images. :lol:

Thanks @tpr!

  • Like 3

Share this post


Link to post
Share on other sites

@tpr, maybe a new feature request:

In Editpage mode, a HotKey for saving: ctrl+s

But one that alltimes work, regardless if one are on the edit page, in a CKeditor field or another Editorfield. I know that there is a module from Soma with AdminHotkeys, but IIRR, it doesn't work when editing in a CKEditor field. But most of all, I would need it there!

Share this post


Link to post
Share on other sites

Thanks! Glad to hear you can make use of it.

Just tried the ctrl-s combo and I got it working. Here is a snippet I have atm if you can't wait:

$(document).ready(function () {

    var saveButton = $('#submit_save');

    CKEDITOR.on('instanceReady', function (evt) {

        var editor = evt.editor;

        editor.document.on('keydown', function (e) {

            if (e.data.getKeystroke() == CKEDITOR.CTRL + 83) {

                e.data.$.preventDefault();

                saveButton.trigger('click');
                return false;
            }
        });
    });
});
  • Like 3

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...