tpr

AdminOnSteroids

Recommended Posts

10 minutes ago, tpr said:

I guess there's nothing more in the logs that you already wrote. Was it a ML site btw, and if yes, how any languages? Php version? 

Yes, 3 languages, PHP 7.0.7.

I am going to bed now. See you tomorrow.

Share this post


Link to post
Share on other sites

No issues with me either, I just started a new profile with 3.0.98 and latest AOS and all works fine, I can switch languages from admin etc. 

  • Like 1

Share this post


Link to post
Share on other sites

@tpr :

I've had a little time now, and i found the line which is causing the trouble in my installation.

Around Line 391 in AOS 1.8.9. The commented line "//theo"

        // add to init() to change early
        if ($this->isMultiLang) {
            if (in_array($subModule, $enabledSubmodules)) {
                if (in_array('adminLangSwitcher', $configData[$subModule])) {
                    if (isset($_COOKIE["aos_lang_id"])) {
                        $lang_id = $_COOKIE["aos_lang_id"];
                       //theo $this->wire('user')->language = $lang_id;
                    }
                }
            }
        }

It seems as if this comes too early here. Not sure.

Do you have an idea what is going on here?

 

Share this post


Link to post
Share on other sites

Hummm, now it works. Very strange, almost scaring...  :huh:

Maybe there was sth. wrong with a previously set cookie?

 

 

Share this post


Link to post
Share on other sites

Hey guys,

It was hard not to notice the often updates of this AMAZIN' module and I was wondering if there is a changelog where I could read more about it before deciding to do an upgrade?

Share this post


Link to post
Share on other sites
50 minutes ago, MilenKo said:

I was wondering if there is a changelog where I could read more about it before deciding to do an upgrade?

I would definitely recommend installing: http://modules.processwire.com/modules/module-release-notes/ so you can see what's changed when using the PW Upgrade module: http://modules.processwire.com/modules/process-wire-upgrade/

  • Like 2

Share this post


Link to post
Share on other sites

As always a fast and efficient reply. I never thought of looking for a release notes module, but it is a great addition. Thanks guys!

  • Like 2

Share this post


Link to post
Share on other sites

@tpr About the language switcher problem mentioned before:

The problem is with the cookie "aos_lang_id".

If it contains a value for the language (like e.g. 1010) which does not correspond to a language id of your current installation, then then PW backend crashes.

This may happen, if you run multiple PW instances on localhost.

A check for the existence of the id you get from the cookie would help imo.

Thank you.

 

  • Like 1

Share this post


Link to post
Share on other sites

Nice find, thanks. I've changed to an arbitrary cookie but couldn't get any errors though. Could you try wrapping the lin in question with this and see if the problem goes away?

if ($this->wire('pages')->get('template=language,id=' . $lang_id)) {
	$this->wire('user')->language = $lang_id;
}

 

Share this post


Link to post
Share on other sites
33 minutes ago, tpr said:

Nice find, thanks. I've changed to an arbitrary cookie but couldn't get any errors though. Could you try wrapping the lin in question with this and see if the problem goes away?


if ($this->wire('pages')->get('template=language,id=' . $lang_id)) {
	$this->wire('user')->language = $lang_id;
}

 

 

No, it does not help.

Still getting: 

Quote

Fatal error: Exception: Method Permission::translator does not exist or is not callable in this context

Thank you.

Share this post


Link to post
Share on other sites

@theo Thanks - does it help if you change "get" to "findOne"?

I'm experimenting with a new sticky pagelist action, loosely based on the ProcessPageListMultipleSorting module. The idea is to create a global "sticky" field and hook into ProcessPageList::find to prepend sort=-sticky to the original selector (keeping template and page level sort intact). This way un-stickying a page will restore the original sort order.

When sticky-ing a page it finds the sibling with the highest sticky value and sets it to an even greater value, so it will go to the top. It works fine so far, the minor glitch is that if you would like to move eg the second to topmost sticky page to top you'll need to unstuck first and then re-sticky (or edit the sticky field value manally). I find the idea to add extra move up/down sticky actions an overkill.

The order also can be queried on the frontend because the new sticky field is a real field.

aos-sticky.gif.23b68900338ecc00b1f7fa7566d93021.gif

  • Like 1

Share this post


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

@theo Thanks - does it help if you change "get" to "findOne"?

 

 

I think the check for "NullPage" was wrong. We have to check for id<>0

https://processwire.com/api/ref/null-page/

Like this it works.

$item= $this->wire('pages')->get('template=language,id=' . $lang_id);
if($item->id) {
  $this->wire('user')->language = $lang_id;
}

Thank you.

  • Like 1

Share this post


Link to post
Share on other sites

Is anyone interested in the sticky implementation shown two posts above? I think it's a simple but reliable implementation that can be handy not only in the admin but on frontend too.

  • Like 1

Share this post


Link to post
Share on other sites

I've added the new sticky pagelist action, @theo's langswitcher fix, Tracy panel z-index fix (hopefully) and other minor fixes in v1.9.1.

I noticed that I was using one SCSS mixin too many times (for icon-only pagelist actions) and it contained rules that I could apply to items outside the mixin. After cleaning this up the final CSS shrinked from 127 to 93 Kb so it was worth the trouble.

I removed the js lib "perfect scrollbar" that was used to replace the browser scrollbar with a mini one (RenoTweaks). From now on AOS uses CSS to achieve the same thing, and is available in Chrome only (you can find it under Misc). It's a sacrifice but results in much leaner code, is controlled by the browser so it's unlikely to break, and modifies every scrollbar in the admin. For example they are available in Tracy panels too and also in CKEditors (the latter required additional efforts though):

aos-miniscrollbarseverywhere.thumb.png.e77b436cfb4a4e334755bc1e1483d31b.png

Documentation is in progress, as usual :) 

  • Like 5

Share this post


Link to post
Share on other sites

Thanks for the remainder @Robin S. I've replaced the character icon with an SVG. I've committed the changes, no version bump.

Perhaps I would have used FontAwesome if it would have been possible to set it as a background-image but that's not the case. I've tried adding the SVG variant of the FA search icon but then searched for a slimmer one. There are only a few icons in AOS and I wouldn't like to increase the overall module size. 

  • Like 2

Share this post


Link to post
Share on other sites

In v1.9.3 I switched to the $datetime api var in pagelist markup and introduced %modifiedUser% and %createdUser% tokens.

As a result it is possible to display relative date like this:

plistmarkup-relativedate.png.cea445ef5d0bfaddefb21dbec6fe59c1.png

I never thought about this but it came from a request and seems like a nice addition. In fact I only knew that a relative date function exists in PW but not that it's also an api var. I was even happier when I learned that I need only slightly change the code to support both relative and the existing date formats with $datetime->date().

Full changelog:

  • pagelist markup: switch to $datetime api var (allows relative datetime strings too)
  • pagelist markup: add %createdUser% and %modifiedUser% tokens
  • pagelistUnselect: fix Uikit theme spacing issue (reported by Robin S)
  • CKEditor plugin Link Files Menu: apply fix from Robin S from his original module (ajax response not working for non-superusers)
  • Like 4

Share this post


Link to post
Share on other sites

hey @tpr could you please add "noAutosize" class support for textarea autosize feature? line 1766 in aos.js (and maybe also some lines below)

autosizeTextareas = target.querySelectorAll('textarea:not(.noAutosize)');

Otherwise it does autosize on my custom textareas, thanks :)

This does not seem to work :( Could you please add a way to exclude custom textareas from this feature? Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr, a feature request: could you add a cache-busting query string (e.g. using filemtime) to the assets added from the "Asset Paths" section of AOS? Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

@bernhard 

It does seem to work - or do you mean you are not able to add the .noAutosize classes?

@Robin S 

Just added the cache bust strings to assetpaths, thanks for the suggestion. Will be available in v1.9.4.

Here is a preview of the Fields page with additional data like inputfield classes, description, notes and IDs. It seems impossible to add column headers to the extra columns but i think it's quite obvious even without them.

fields-setup-page.thumb.png.a546756e947029475bc643b633d0a246.png

  • Like 3

Share this post


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

It does seem to work - or do you mean you are not able to add the .noAutosize classes?

You are right, my mod works. Just edited aos.js instead of aos.min.js and that had no effect 🙂 Could you please change both occurances of querySelectorAll('textarea') to querySelectorAll('textarea:not(.noAutosize)') as requested?

Thanks!

 

Share this post


Link to post
Share on other sites

Version 1.9.4 is available:

  • new: extra columns on Fields setup page showing description, notes, id and inputfield class (Misc)
  • skip autosizing textareas having "noAutosize" classname (requested by bernhard)
  • add cache busting string to assetPaths (requested by Robin S)
  • check if $_SERVER['HTTP_REFERER'] exists before redirect (reported by Robin S)
  • fix 1px title field misalignment caused by casechanger (reported by Robin S)
  • Like 4

Share this post


Link to post
Share on other sites

Hi all,

on a fresh PW 3.0.98 installation using Default Admin theme and site-default profile I have installed AOS 1.9.4 as the only site module.

Two observations:

(1) When in PageListTweaks I check Always show pagelist actions, in the page tree there are no line breaks any more between the entries - see attached screenshot. How do I get them back?

(2) Having checked Sticky header in Admin tweaks, when on the settings page of the module I click the cog of a Submodule, the sticky header would overlay the top lines of the options of the chosen submodule.

Not big problems - many thanks for this incredibly useful module!

screenshot-1.jpg

Share this post


Link to post
Share on other sites

Hi,

(1) I could reproduce, thanks. For a quick fix use this, or wait for a new version:

html.pListShowActions .content .PageList .PageListItem { width: 100%; }

(2) I'm aware of this, will try to fix with some CSS.

I recommend using Reno or Uikit theme, most AOS features are targeted/tested in them.

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 BitPoet
      MediaLibrary
      Update: MediaLibrary can now be found in the official module list.
      Out of necessity, I've started to implement a simple media library module.
      The basic mechanism is that it adds a MediaLibrary template with file and image fields. Pages of this type can be added anywhere in the page tree.
      The link and image pickers in CKEditor are extended to allow quick selection of library pages from dropdowns. In the link picker this happens in the MediaLibrary tab, where you can also see a preview of the selected image. In the image picker, simply select a library from the dropdown at the top, everything else is handled by standard functionality.
      I've put the code onto github. This module is compatible with ProcessWire 3.
      Steps to usage:
      Download the module's zip from github (switch to the pw3 branche beforehand if you want to test on PW 3.x) and unpack it into site/modules Click "Modules" -> "Refresh" in the admin Click "Install" for MediaLibrary For testing, create a page with the MediaLibrary template under home (give it an expressive title like 'Global Media') and add some images and files Edit a differnt page with a CKEditor field and add a link and an image to see the MediaLibrary features in action (see the screencap for details) Optionally, go into the module settings for MediaLibrary Note: this module is far from being as elaborate as Kongondo's Media Manager (and doesn't plan to be). If you need a feature-rich solution for integrated media management, give it a look.
      Feel free to change the settings for MediaFiles and MediaImages fields, just keep the type as multiple.
      There are some not-so-pretty hacks for creating and inserting the correct markup, which could probably be changed to use standard input fields, though I'm a bit at a loss right now how to get it to work. I've also still got to take a look at error handling before I can call it fit for production. All feedback and pointers are appreciated (that's also why I post this in the development section).

      Edit 09.03.2016 / version 0.0.4: there's now also a "Media" admin page with a shortcut to quickly add a new library.

      Edit 01.05.2016:
      Version 0.0.8:
      - The module now supports nested media libraries (all descendants of eligible media libraries are also selectable in link/image picker).
      - There's a MediaLibrary::getPageMediaLibraries method you can hook after to modify the array of available libraries.
      - You can switch between (default) select dropdowns or radio boxes in the module configuration of MediaLIbrary to choose libraries.
      Edit 10.10.2018:
      Version 0.1.3:
      - Dropped compatibility for ProcessWire legacy versions by adding namespaces
      - Allow deletion of libraries from the Media overview admin page
      - Added an option to hide media libraries from the page tree (optionally also for superusers)
    • By Robin S
      This module corrects a few things that I find awkward about the "Add New Template" workflow in the PW admin. I opened a wishlist topic a while back because it would good to resolve some of these things in the core, but this module is a stopgap for now.
      Originally I was going to share these as a few standalone hooks, but decided to bundle them together in a configurable module instead.
      Add Template Enhancements
      A module for ProcessWire CMS/CMF. Adds some efficiency enhancements when adding or cloning templates via admin.

      Features
      Derive label from name when new template added: if you like to give each of your templates a label then this feature can save some time. The label can be added automatically when templates are added in admin, in admin/API, or not at all. There are options for underscore/hyphen replacement and capitalisation of the label. Edit template after add: when adding only a single template, the template is automatically opened for editing after it is added. Copy field contexts when cloning: this copies the field contexts (a.k.a. overrides such as column width, label and description) from the source template to the new template when using the "Duplicate/clone this template?" feature on the Advanced tab. Copy field contexts when duplicating fields: this copies the field contexts if you select the "Duplicate fields used by another template" option when adding a new template. Usage
      Install the Add Template Enhancements module.
      Configure the module settings according to what suits you.
       
      https://github.com/Toutouwai/AddTemplateEnhancements
      https://modules.processwire.com/modules/add-template-enhancements/
    • By Mike Rockett
      As I mentioned in this issue, I've create a new textformatter for ParsedownExtraPlugin, which adds some oomph to your markdown.
      Repo: Parsedown Extra Plugin
      Unlike the built-in textformatter for Parsedown and Parsedown Extra, this should be used when you want to use Extra with additional configuration/customisation.
      Some examples:
      ### Test {.heading} - A [external link](https://google.com/){.google} with `google` as a class that opens in a new tab if the config property is set. - [Another link](/page){target=_blank} that opens in a new tab even though it isn't external. ```html .html <p>Test</p> ``` There's some config options available to you, such as setting attributes on all/external images and links, setting table and table-cell alignment classes, adjusting footnote classes and IDs, adding <code> attributes to their parent <pre> elements, and changing the <code> class if your syntax highlighter does not use language-*.
      I was thinking about adding the ability to make links open in a new tab by appending a plus to the link syntax, but only external links should be opening in a new tab anyway. Further, this would add extra, unnecessary processing time.
      Please let me know if you bump into any problems. ☺️
    • By Mike Rockett
      TextformatterTypographer (0.4.0 Beta)
      A ProcessWire wrapper for the awesome PHP Typography class, originally authored by KINGdesk LLC and enhanced by Peter Putzer in wp-Typography. Like Smartypants, it supercharges text fields with enhanced typography and typesetting, such as smart quotations, hyphenation in 59 languages, ellipses, copyright-, trade-, and service-marks, math symbols, and more.
      Learn more on my blog
      It's based on the PHP-Typography library found over at wp-Typography, which is more frequently updated and feature rich that its original by KINGdesk LLC.
      The module itself is fully configurable. I haven't done extensive testing, but there is nothing complex about this, and so I only envisage a typographical bug here and there, if any.
      Please do test it out and let me know what you think.
      Also note that I have indicated support for PW 2.8, but I haven't tested there as yet. This was built on PW 3.0.42/62.
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.50
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy!