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
      I'm really in love with FormBuilder, but the one thing missing to match all my end users' expectations were repeatable field groups. Think repeaters, in ProcessWire terms. Our primary application of PW is our corporate intranet, so "lines" of fields are quite common in the forms I build. We have all kinds of request forms where the information for a varying number of colleagues needs to be entered (from meal order to flight booking request) and where it is simply impractical to send a form for each, and I don't want to clutter my forms with multiple instances of fields that may only get used ten percent of the time.
      That's why I started to build FormBuilderMultiplier (link to GitHub).
      What it does:
      Adds an option to make a regular Fieldgroup repeatable Lets you limit the number of instances of a Fieldgroup on the form Adds an "Add row" button the form that adds another instance of the Fieldgroup's fields Adds a counter suffix at the end of every affected field's label Stores the entered values just like regular fields Makes the entered values available in preview and email notifications Supports most text based fields, textareas and selects (really, I haven't had enough time to test all the available choices yet) What it doesn't do (yet):
      Support saving to ProcessWire pages (i.e. real Repeaters) I haven't tested all the validation stuff, Date/Time inputs etc. yet, but since I'm utterly swamped with other stuff at work, I didn't want to wait until I have it polished. Any feedback is welcome. There might also be some issues with different output frameworks that I haven't encountered yet. The forms I work with mostly use UIKit.
      Status:
      Still alpha, so test well before using it in the field.
      Known issues:
      When rows are added, the form's iframe needs to be resized, which isn't completely clean yet.
      How it works:
      The Fieldgroup settings are added through regular hooks, as is the logic that adds the necessary field copies for processing the form and displaying previews.
      "Multiplied" field instances are suffixed with _NUM, where NUM is an incremental integer starting from 1. So if you have add two fields named "surname" and "givenname" to a fieldgroup and check the "multiply" checkbox, the form will initially have "surname_1" and "givenname_1" field (I'm still considering changing that to make the risk to shoot oneself into the foot by having a regular "surname_1" field somewhere else in the form less likely).
      When a "row" is added, the first row is cloned through JS and the counter in the fields' IDs, names and "for" attributes as well as the counter in the label are incremented before appending the copies to the Fieldset container in the form.
      To keep backend and frontend in sync, a hidden field named [name of the fieldset]__multiplier_rows is added to the form. Both the backend and the frontend script use this to store and retrieve the number of "rows".
      ToDo:
      Naturally, add the option to store the data in real repeaters when saving to pages. Do a lot of testing (and likely fixing). Make a few things (like the "Add row" button label etc.) configurable in field(set) context. Add a smooth API to retrieve the multiplied values as WireArrays. The mandatory moving screenshot:

    • By MoritzLost
      Hello there,
      I'm working on a tiny textformatter module that searches the text for titles of other pages on your site and creates hyperlinks to them. I'm not sure if something like this exists already, but I haven't found anything in the module directory, so I wrote my own solution 🙂
      It's not properly tested yet and is still missing some functionality I would like to implement, so at the moment it should be considered in BETA. Features include limiting the pages that will get searched by template, and adding a custom CSS class to the generated hyperlinks. As I'm writing this I noticed that it will probably include unpublished and hidden pages at the moment, so yeah ... it's still in development alright 😅
      You can download the module from Github:
      https://github.com/MoritzLost/TextformatterPageTitleLinks
      There's some more information in the readme as well.
      Anyway, let me know what you think! I'm happy about any feedback, possible improvements or ideas on how to improve the module. Cheers.
    • By adrian
      This module provides a way to rapidly generate Page fields and the required templates and pages for use as a drop down select (or any other Page field type).
      This module will let you create a full page field setup in literally a few seconds 
      To use, run Page Field Select Creator from the Setup Menu
      Enter a Field Title, eg: Room Types Select Options - These will become the child pages that will populate the page field select options. There are two different options.
       
      Option 1. TITLE FIELD ONLY - enter one option per line, eg:
       
      Single
      Double
      Suite
       
       
      Option 2. MULTIPLE FIELDS - the first line is used for the field names and the first field must be 'Title'. Subsequent lines are the values for the fields, eg:
       
      Title, Number of Beds, Number of People, Kitchen Facilities
      Single, 1, 1, Fridge Only
      Double, 2, 2, Fridge Only
      Suite, 3, 6, Full Kitchen
        Choose the parent where the page tree of options will be created, eg a hidden "Options" parent page Select a "Deference in API as" option depending on your needs Choose the input field type Check whether "Allow new pages to be created from field?" should be enabled. As an example, if you entered "Room Types" as the field title, you would end up with all of the following automatically created:
      a fully configured page field called: room_types MULTIPLE FIELDS OPTION - 3 additional fields - number_of_beds, number_of_people, kitchen a parent template called: room_types a child template called: room_types_items (with either just a title field, or with the 3 additional fields as well) a parent page called: Room Types a series of child pages named and titled based on the per line entries in the Select Options textarea The templates are configured such that the "room_types_items" child template can only have the main "room_types" template as a parent, and vice versa.

      Then all you have to do is add the newly created page field to any template you want and you're ready to go!
       
      You can grab it from:
       
      Modules directory: http://modules.processwire.com/modules/process-page-field-select-creator/
      Github: https://github.com/adrianbj/ProcessPageFieldSelectCreator
       

    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://github.com/BernhardBaumrock/RockFinder
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • 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)