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 bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
       
    • By Soma
      LogMaintenance
      A simple ProcessWire module to give some maintenance control over log files. I found myself often having lots of log files for different things that can grow more or less quickly to a size where they can be difficult to maintain. The built in Logger of PW does a good job of giving you the possibility to delete or prune logs. But it has to be done manually and sometimes a log grows into millions of lines, which makes it often impossible to even prune it as it's too large.
      LogMaintenance uses LazyCron to run the maintenance task and there's several settings you can setup on a global or per log basis.
      Archive: will create zip files for each log file in logs/archive/ folder and add the log each time the maintenance is run to a subfolder containing the datetime.
      Lines: keeps logs to a certain number of lines 
      Days: keeps the log to a certain number of days
      Bytes: keeps the log to a certain amount of bytes
      Each setting is checked from top down, the first setting to contain something is used. So if you check the "Archive" option, all other settings are ignored and logs are archived everytime the LazyCron is executed. If you want to keep your logs to a certain amount of bytes just leave all other settings to 0 or blank.
      Per Log Settings
      There's a textarea that you can use to setup a config for a specific log file one per line. All the logs you define here ignore the global settings above. The syntax for the settings is:
      logname:[archive]:[lines]:[days]:[bytes] 
      errors:1:0:0:0 // would archive the errors log messages:0:10000:0:0 // will prune the errors log to 10000 lines  
      The module can be found on github for you to check out. It's still fresh and I'm currently testing.
      https://github.com/somatonic/LogMaintenance
    • By teppo
      Fieldtype Page IDs is a third party Fieldtype that, simply put, stores Page references as integers (Page IDs).
      This fieldtype was built as a quick and dirty workaround for Page Reference fields' inability handle self-references due to circular reference issues. A project I've been working on for a while now includes a combination of RepeaterMatrix content blocks and tagging/categorization system that would've resulted in a lot of duplicate pages (and plenty of unnecessary manual work for content editors) had I used built-in Page Reference fields, and thus a new Fieldtype felt like the most sensible approach.
      Fieldtype Page IDs was designed to be loosely compatible with Page References in order to make conversions between the two feasible, but it is quite limited feature wise:
      largely due to the fact that stored values are actually just integers with no connection to Pages whatsoever some advanced selectors and related features are not supported, and page values can't be directly accessed configuration settings are limited to the bare essentials (selector string and Inputfield class) only a handful of Inputfields (AsmSelect, Checkboxes, Text) are (currently) supported Anyway, in case you need to store Page IDs (and Page IDs only) and are happy with the limitations mentioned above, feel free to give this Fieldtype a try. It has been working fine for me in one particular project, but hasn't been tested that much, so please tread carefully – and let me know if you run into any issues.
      GitHub repository: https://github.com/teppokoivula/FieldtypePageIDs
      Modules directory: https://modules.processwire.com/modules/fieldtype-page-ids/
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.4. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • 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://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      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/