Jump to content
tpr

AdminOnSteroids

Recommended Posts

I couldn't reproduce (latest Chrome and Firefox). Could you check what CSS rule is causing this? Apparently the page title is there but not visible because the page IDs are not aligned to the left. It could be also handy to see the markup of a failing pagelist item.

  • Like 1

Share this post


Link to post
Share on other sites

Well, I tested the admin with the following browsers:

Opera - Version:58.0.3135.107

Chrome - Version 73.0.3683.86 (Official Build) (64-bit)

Here is the markup of one of the hidden pages 404 Not found:

Spoiler

<div class="PageListItem PageListTemplate_404 PageListNoChildren PageListID27 PageListStatusHidden secondary PageListStatusSystem" data-numtotal="0" data-numchild="0"><a href="#" title="/http404/" class="PageListPage label"><span class="label_title" data-pid="27">404 Not Found</span></a><span class="PageListNumChildren detail"></span><ul class="PageListActions actions"><li class="PageListActionEdit"><a href="/admin/page/edit/?id=27" class="pw-modal pw-modal-large pw-modal-longclick" data-buttons="#ProcessPageEdit > .Inputfields > .InputfieldSubmit .ui-button">Edit</a></li><li class="PageListActionView"><a href="http://quebec.pw/http404/" class="pw-modal pw-modal-large pw-modal-longclick">View</a></li><li class="PageListActionNew"><a href="/admin/page/add/?parent_id=27">New</a></li><li class="PageListActionMove"><a href="#">Move</a></li><li class="PageListActionEdit"><a href="http://quebec.pw/admin/setup/template/edit?id=43" class="pw-modal pw-modal-large pw-modal-longclick" data-buttons="#ProcessPageEdit > .Inputfields > .InputfieldSubmit .ui-button">404</a></li><li class="PageListActionExtras ui-priority-secondary"><a href="#" class="clickExtras"><i class="fa fa-angle-right"></i></a></li></ul></div>

 

Here is a preview of all the rows to compare classes:

image.thumb.png.fb4ea83897b9a4dd467242d6862bc207.png

I checked a few classes and if I change the opacity from 0.6 to any number and back - it shows properly:

.PageList .PageListStatusHidden>a.PageListPage {
    opacity: .5;
}

Not sure why, but will test to remove all other modules to make sure that the issue is not caused by one of them.

P.S. To be sure it is not a local OS (Server 2016) or Browser issue, tested on another PC with Windows 10 and the result is still the same. As far as it is quite late now here, I will try to get an earlier version of the AOS and see if the issue would appear as well. Will keep you updated and thanks for checking it up.

  • Like 1

Share this post


Link to post
Share on other sites

So changing the opacity back and forth fixes it? That is weird, does it happen in incognito mode too?

Share this post


Link to post
Share on other sites

So, I've tried this morning to remove all the modules but the AOS and the hidden items still were hidden unless I move the mouse over them, but then after a page reload, they "hide" again.

I did test it in Incognito on both computers and still see the same thing.

After replacing the AOS 2.0.15 version with the 2.0.14 - it is all working fine so there must be something that is happening with the new version, but what and where is not clear yet. At least it is not related to my browser, computer and even the local server prior to the fact that it worked like a charm under 2.0.14 and it still does.

P.S. After an upgrade from 2.0.14 to 2.0.15 - the hidden pages get "hidden" again.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian Is it happening for you with 2.0.14? As with me it just started doing the same issue as you've reported, however with 2.0.14 it works fine. And as I said, what is even stranger, if I remove the class for hidden items in developers mode and put it back, it starts working, so it is only on the page loading that it happens. I know I should not say that, but it is a bit of a relief as it is not local on my side and I am not going crazy. Go figure 😉

P.S. Somehow it seems like I was wrong with the assumption about 2.0.14 as well as the admin was showing properly, but I forgot that I've disabled the show ID option. So it is not working with both unfortunately and I guess until it is clear what is causing, I could just live without showing the ID beside the page.

Share this post


Link to post
Share on other sites

@tpr - while we're at it, I am been having issues with page scrolling - when there are lots of fields or templates such that the dropdown menu extends beyond the viewport height, AOS prevents me from scrolling the page to access those items towards the bottom of the list. It is due to the UiKit sticky header setting.

Share this post


Link to post
Share on other sites

Well I don't know how could I fix the long menu issue, sticky works just this way.

@MilenKo Are you also on Mac? As I know adrian also is.

  • Like 1

Share this post


Link to post
Share on other sites

@tpr Nope, I am on Windows as I've mentioned it earlier (Server 2016 & Windows 10 latest upgrades) but testing it on Linux did the same. I can test it on Mac as well but am not sure that would fix it prior to the fact that @adrian already had the issue on his one.
 a

Share this post


Link to post
Share on other sites

This has something to do that the markup is different here, there is a span.label_title around the page title's text. This has came up earlier too but I couldn't figure out why.

I googled around and found a WebKit bug that could cause this. Could you try applying this CSS? If it works via devtools, please try adding this to aos.min.css (just append to the end):

.PageList .PageListItem {
    transform: scale3d(1,1,1);
}

Or if no joy, by adding backface-visibilty: hidden. Unfortunately because I can't reproduce I can't check.

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Hey @tpr I am super happy to confirm that adding the style to aos.min.css fixed the issue and now my Admin tree is back to its normal state 🙂 I guess we will see a new AOS release some time soon with the fix 😉 Thank you sincerely!

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, I've added this to v2.0.16, please try. It also contains a fix for the PHP notice @Brian Peat has come across.

  • Like 1

Share this post


Link to post
Share on other sites
14 hours ago, adrian said:

when there are lots of fields or templates such that the dropdown menu extends beyond the viewport height, AOS prevents me from scrolling the page to access those items towards the bottom of the list.

I've tried setting a max height on the dropdown menus so at least they were scrollable, but unfortunately the 3rd level menus that open to the right were cut off. They are absolutely positioned so I don't think this could be fixed. Btw I really don't like how the main menu markup is built in the admin, submenus are not part of the menu markup but they are positioned there on open. A simple CSS solution would be enough I think with proper nested markup, that would allow more customization.

  • Like 1

Share this post


Link to post
Share on other sites

@tpr - don't worry about the fixed header issue - maybe just remove the option unless you can get Ryan to change how the menus are built (although that seems unlikely).

Share this post


Link to post
Share on other sites

Recently I have been trying to improve the user friendliness of various page select fields, including single select and checkboxes.

The issue comes down to the fact that if say for example you have a single checkbox, you can explain what the effect of checking that box is. But if you are using checkboxes on a page select field, there is no way to have any extended information about the option. An example of where something like this is already in use is on the Status field - each option has the title of the option, e.g. Unpublished, and then additional info, like "Not visible on site". 

Currently my solution is to use a custom inputfield that extends the primary inputfield, which extends the attributes for each option, and then use javascript for handling the display.

  • On checkboxes, adding uk-tooltip to the checkbox labels with the data-description on the option becoming the tooltip content. (see screenshot below)
  • On single selects, i have some JS replace the field description with the info about the selected option. (see screenshot).

The reason i'm posting this here is to see if there is any simpler/better way to do this, e.g. hook into the creation of the options for any page field and add the custom attributes, without having to change the inputfield type. And i thought this could be a good candidate for AOS. To better illustrate how it works, i have included some screenshots and links to the repos for the select extended and checkboxes extended.

Select Extended:

nothing selected

973404192_Edit_Page__Home__dev_fredsherry_com.jpg.71caee0ca17733e006c248505b2e73ec.jpg

Option selected, with option's description showing:

1940487017_Edit_Page__Home__dev_fredsherry_com.jpg.685d6e65881215fedd580c055dfdb19e.jpg

https://github.com/outflux3/InputfieldSelectExtended

-----

Checkboxes Extended

hovering over any option shows the option's description:

 

hover_checkboxes.png.76af25d35fcec2203d9683ef73ab1c10.png

https://github.com/outflux3/InputfieldCheckboxesExtended

  • Like 3

Share this post


Link to post
Share on other sites
9 hours ago, Macrura said:

The reason i'm posting this here is to see if there is any simpler/better way to do this, e.g. hook into the creation of the options for any page field and add the custom attributes, without having to change the inputfield type.

I was going to write a tutorial but then I thought I might as well take the next step and turn it into a module:

If @tpr wants to include the functionality in AOS and people would prefer that rather than a standalone module then I'm fine with that. 🙂

  • Like 3

Share this post


Link to post
Share on other sites

Thanks for sharing!

28 minutes ago, Robin S said:

If @tpr wants to include the functionality in AOS

That would be a good thing for sure but even better would be to add it to the core 😉 

Share this post


Link to post
Share on other sites

Hi! Small request here, just added Input Mask to integer fields tweaking a little bit of lines in the module, maybe this should be enabled by default? Anyone see any possible issues, maybe on number type inputs? I think it's the type of field where it is particularly useful so you can filter nicely with selectors. (think of a price field)

Share this post


Link to post
Share on other sites

I don't use this feature very much but if you feel it would make a useful addition, create a PR (or show the changes in other ways) and I'll check.

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr

I have z-index issue with UIkit Sticky header being on. input.InputfieldDatetimeDatepicker has a higher z-index than the header. I quick fixed it with  #pw-mastheads {z-index:11 !important;} but I'm not quite sure what to do.

Share this post


Link to post
Share on other sites

Thanks, I just used the z-index: 11 you suggested in v2.017. There's a very high z-index on the datepicker calendar div added by AOS that was needed back then. This is still above the masthead on scroll but I think it's better not to change that.

There's also a bunch of new CKEditor plugins added in this version: 

  • Color Button
  • Color Dialog
  • Table Resize
  • Table Tools
  • Table Tools Toolbar
  • Like 2

Share this post


Link to post
Share on other sites

@tpr, would you consider adding an exclude class to the "Autosize textareas according to content" feature? Generally I like this feature but I have some modules with textareas in their config that contain a lot of content and would like to be able to exclude these from being autosized. So I was thinking there could be some special class that can be applied to textareas (e.g. "no-autosize") and the AOS feature when enabled would apply to all textareas without this class. What do you think?

  • Like 1

Share this post


Link to post
Share on other sites

There already is one, the textarea selector is "textarea:not(.noAutosize)". I haven't checked it yet but in theory it should work. Otherwise you could apply a max-height with CSS that could also help, or perhaps setting the height with !important.

  • Like 3

Share this post


Link to post
Share on other sites
3 hours ago, tpr said:

There already is one, the textarea selector is "textarea:not(.noAutosize)". I haven't checked it yet but in theory it should work.

Works great, thanks.

  • Like 1

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