tpr

AdminOnSteroids

Recommended Posts

Just read your comment here and found out AOS now has some profound documentation.

You're a monster, @tpr! The wiki is awesome! I saw it and said to myself: "Ha, but he probably does not have changelog!" But I was wrong (and astonished)!

I think the main PW repo could benefit from a CHANGELOG.md like this. Especially that there are enough of nice changes to be mentioned almost every week. Sorry for offtop))

 

  • Like 3

Share this post


Link to post
Share on other sites

Hi @tpr

Has this been reported yet?

FileFieldTweaks-icons-cover-trash.gif.82c156a8277d7fba8408f3b7f80db804.gif

FileFieldTweaks icons cover the trash icon making it "impossible" (for a client...) to delete. Turning off the options temporarily fixed the delete issue, but the download icon is a good feature, we are missing it... :) 

Share this post


Link to post
Share on other sites

Yep, several times :) though the download icons was not harmed at all :)

Update to v151 to fix.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks for the quick update! I didn't even had time to blink :)

  • Like 1

Share this post


Link to post
Share on other sites
On 8/14/2017 at 6:24 PM, tpr said:

Yep, several times :) though the download icons was not harmed at all :)

Update to v151 to fix.

speaking of download icons – there is a (probably not used much, but nonetheless awesome) module called Secure File - for that module, the download button doesn't work, i guess AOS is not compatible with that module; I disabled the "Add Asset Download Button", since that module already provides a download link for the file. Just wanted to post that here in case someone else uses secure file and comes across the non-working download (if they have AOS add asset download enabled)...

  • Like 2

Share this post


Link to post
Share on other sites

@tpr - nice job on the AddNewChildFirst functionality - very cool!

A couple of minor things:

1) This sentence needs the "of" added:

"Add new page as first child instead of last"

2) There are several locations where the PW file compiler is causing problems in your text, eg:

59a4889a73ff6_ScreenShot2017-08-28at2_18_03PM.png.a77f6cbe63377658dda2807f446511dd.png

This is due to this bug: https://github.com/processwire/processwire-issues/issues/98

I have come across this in my own modules and I just end up re-wording things to avoid parentheses near PW variable names, but of course it would be great if this could be fixed properly, but I don't think it's high on Ryan's priorities.

  • Like 1

Share this post


Link to post
Share on other sites

Actually just found an easy solution for these, eg:

replace:

Shortcuts to templates and fields(SuperUser only)

with:

Shortcuts to templates and fields (SuperUser only)

Note that it has to be a   - an ordinary space won't work.

Share this post


Link to post
Share on other sites

Thanks @adrian, I haven't came across these issues, good to know.

The AddNewChildFirst submodule works pretty neat, thanks for your contributions in this topic - I only collected all the goodies from there :)

  • Like 2

Share this post


Link to post
Share on other sites

Is it just me who has strange looking AdminDataTable filter box in AOS 1.5.2? See:

aos-table-filter.jpg.7270d1eb0ce696f4cc7a4f6646fa8137.jpg

I tried different browsers in incognito/private browsing but it stays like that :( The label introduced is not too useful btw, it takes up space however most users can recognize a filter box these days.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, that's coming from the latest PR I merged yesterday, will fix soon.

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr

I'm having a real pita issue when AOS is enabled. In the screen capture when the mouse pointer stops I single click as well. Whenever I click into the editor the content moves. I could have clicked on the toolbar items too, as it jumps back to its proper position in that case too:

ckeditor-jumping.thumb.gif.f2deedb0ba0745058ce3c62552742866.gif

The moving content of the editor makes it hard to edit things. I tried disabling all CKE plugins I had turned on in the AOS settings but that did not make any difference. I can only get rid of this behavior if I disable AOS.

Unluckily this glitch is not present all the time, making it time consuming to test it. Sometimes the content jumps, other times it does not. I could not see a pattern in this, looks like it is randomly happening.

I also tried without the custom editor css I use but did not help either, it happens without that one too.

Has anyone ever seen this?

Share this post


Link to post
Share on other sites

This is the "Sticky CKE toolbar" feature located in the RenoTweaks. I'm also using it and most of the ime it works fine but sometimes there's a jump when the toolbar goes to fixed position and its height is changing. There's a "Fixed" CKEditor plugin that never worked well for me (even with the fix in their forums) so I revisited this again today and found a nice and easy solution using position:sticky. This works in latest browsers only but I think it's still better than the current one - no hacky JS/CSS, and works with multiple editors too.

I'll upload this new version soon, until that you can uncheck this feature.

aos-sticky-cke-toolbar.gif

  • Like 2

Share this post


Link to post
Share on other sites

v1.5.4 is available with the fixed sticky CKE toolbar and some other fixes.

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr. Do you know how to set another theme for Codemirror? If I use it, my HTML source code becomes unreadable of the theme (which seems to be moono-lisa).

 

chrome_2017-09-07_14-40-29.png

Share this post


Link to post
Share on other sites

v1.5.7 is up, containing the Trash pagelist action for non-SuperUsers too (from Robin S), with an inline confirm feature:

aos-user-trash.gif.bba2f9dce2d34245d33c9211ea968ca1.gif

  • Like 4

Share this post


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

v1.5.7 is up, containing the Trash pagelist action for non-SuperUsers too (from Robin S), with an inline confirm feature:

Who-hoooo, I've been dreaming of this! Thank you very much, Sir!

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Hi @tpr Tiny issue today which was "discovered" by me long time ago, I just did not find the time to post it... Do you happen to have Forgot Password module installed? Button centering is missing here:

aos-forgot-password-button.gif.215bce50f0b71834e8226e07a44c12a1.gif

Share this post


Link to post
Share on other sites

I saw this once but I was lazy to make the adjustments :) will do later

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr - there also seems to be an issue with the Reno tweaks. When guest is using Reno, for the login, and I've turned on the fixed header, the "Login" header is offset by the width of the sidebar, which does not exist on the login screen, so it just has an empty space to the left.

Share this post


Link to post
Share on other sites

Are you using the latest version? A similar bug was fixed there and I can't reproduce.

If it still exists, could you send a screenshot of your RenoTweaks? And is "Center login form" (under Misc) checked?

Share this post


Link to post
Share on other sites

I'm using PW 3.0.62 and the latest (1.5.7) version of AOS, and I get this error message when I try and go to the Users page – Error: Using $this when not in object context (line 722 of /var/www/xxx/modules/AdminOnSteroids/AdminOnSteroids.module)

Share this post


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

Are you using the latest version? A similar bug was fixed there and I can't reproduce.

If it still exists, could you send a screenshot of your RenoTweaks? And is "Center login form" (under Misc) checked?

Ah, you're quite right - was one of my sites that hasn't upgraded yet (missed it!).

Thanks :)

  • Thanks 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 dreerr
      TemplateEnginePug (formally TemplateEngineJade)
       
      This module adds Pug templates to the TemplateEngineFactory. It uses https://github.com/pug-php/pug to render templates.
      doctype html html(lang='en') head meta(http-equiv='content-type', content='text/html; charset=utf-8') title= $page->title link(rel='stylesheet', type='text/css', href=$config->urls->templates . 'styles/main.css') body include header.pug h1= $page->title if $page->editable() p: a(href=$page->editURL) Edit Project on GitHub: github.com/dreerr/TemplateEnginePug
      Project in modules directory: modules.processwire.com/modules/template-engine-pug/
       
      For common problems/features/questions about the Factory, use the TemplateEngineFactory thread.
       
    • By tpr
      ProcessNetteTester
      Run Nette Tester tests within ProcessWire admin.
      (continued from here)

      Features
      AJAX interface for running Nette Tester tests, in bulk or manually display counter, error message and execution time in a table run all tests at once or launch single tests show formatted test error messages and report PHP syntax errors stop on first failed test (optional) hide passed tests (optional) display failed/total instead passed/total (optional) re-run failed tests only (optional) auto scroll (optional) include or exclude tests based on query parameters start/stop all tests with the spacebar reset one test or all tests (ctrl+click) https://modules.processwire.com/modules/process-nette-tester/
      https://github.com/rolandtoth/ProcessNetteTester
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module:

    • By tpr
      Update 2018-07-09: ProcessNetteTester module is available in the Modules Directory and on GitHub.

      This is a short tutorial on how to use Nette Tester with ProcessWire.
      As you will see it's very easy to setup and use and it's perfect for testing your code's functionality. With bootstrapping ProcessWire it's also possible to check the rendered markup of pages using the API, checking page properties, etc. It's also a great tool for module developers for writing better code. 
      While there will be nothing extraordinary here that you couldn't find in Tester's docs this can serve as a good starting point.
      Prerequisites: PHP 5.6+
      01 Download Tester
      Go to https://github.com/nette/tester/releases and download the latest release (currently 2.0.2). Download from the link reading "Source code (zip)". You can use composer also if you wish.
      02 Extract Tester files
      Create a new directory in your site root called "tester". Extract the zip downloaded here, so it should look like this:
      /site /tester/src /tester/tools /tester/appveyor.yml /tester/composer.json /tester/contributing.md /tester/license.md /tester/readme.md /wire ... 03 Create directory for test files
      Add a new directory in "/tester" called "tests". Tester recognizes "*.Test.php" and "*.phpt" files in the tests directory, recursively. 
      04 Create your first test
      In the "tests" directory create a new "MyTest.php" file.
      The first test is a very simple one that bootstraps ProcessWire and checks if the Home page name is "Home". This is not the smartest test but will show you the basics.
      Add this to "/tester/tests/MyTest.php":
      <?php namespace ProcessWire; use \Tester\Assert; use \Tester\DomQuery; use \Tester\TestCase; use \Tester\Environment; require __DIR__ . '/../src/bootstrap.php'; // load Tester require __DIR__ . '/../../index.php'; // bootstrap ProcessWire Environment::setup(); class MyTest extends TestCase {     // first test (step 04)     public function testHomeTitle()     {         $expected = 'Home'; // we expect the page title to be "Home"         $actual = wire('pages')->get(1)->title; // check what's the actual title Assert::equal($expected, $actual); // check whether they are equal     }     // second test will go here (step 06)     // third test will go here (step 07) } // run testing methods (new MyTest())->run(); I've added comment placeholders for the second and third tests that we will insert later.
      05 Run Tester
      Tester can be run either from the command line or from the browser. The command line output is more verbose and colored while in the browser it's plain text only (see later).
      Running from the command line
      Navigate to the "/tester" directory in your console and execute this:
      php src/tester.php -C tests This will start "/tester/src/tester.php" and runs test files from the "/tester/tests" directory. The "-C" switch tells Tester to use the system-wide php ini file, that is required here because when bootstrapping ProcessWire you may run into errors (no php.ini file is used by default). You may load another ini file with the "-c <path>" (check the docs).
      If the title of your Home page is "Home" you should see this:

      If it's for example "Cats and Dogs", you should see this:

      Running from the browser
      First we need to create a new PHP file in ProcessWire's root, let's call it "testrunner.php". This is because ProcessWire doesn't allow to run PHP files from its "site" directory.
      The following code runs two test classes and produces a legible output. IRL you should probably iterate through directories to get test files (eg. with glob()), and of course it's better not allow tests go out to production.
      <?php ini_set('html_errors', false); header('Content-type: text/plain'); echo 'Starting tests.' . PHP_EOL; echo '--------------------------' . PHP_EOL; $file = __DIR__ . '/PATH_TO/FirstTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; $file = __DIR__ . '/PATH_TO/SecondTest.php'; echo basename($file) . ' '; require $file; echo '[OK]' . PHP_EOL; echo '--------------------------' . PHP_EOL; echo 'Tests finished.'; exit; Navigate to "DOMAIN/testrunner.php" in your browser to execute the file. If every test succeeds you should get this:

      If there are failed tests the execution stops and you can read the error message. If there were more tests (eg. ThirdTest), those won't be displayed under the failed test.

      06 DOM test
      This test will check if a page with "basic-page" template has a "h1" element. We will create the page on the fly with ProcessWire's API. To keep things simple we will add the new test as a new method to our MyTest class.
      Add this block to the MyTest class:
      public function testBasicPageHeadline() {     $p = new Page();     $p->template = 'basic-page';     $html = $p->render();     $dom = DomQuery::fromHtml($html);     Assert::true($dom->has('h1')); } This will most likely be true but of course you can check for something more specific, for example "div#main". Note that we have used the DomQuery helper here (check the "use" statement on the top of the file).
      07 Custom function test
      You will probably want to make sure your custom functions/methods will work as they should so let's write a test that demonstrates this.
      I don't want to complicate things so I'll check if the built-in "pageName" sanitizer works as expected. Add this to the myTest class:
      public function testPageNameSanitizer() {     $expected = 'hello-world';     $actual = wire('sanitizer')->pageName('Hello world!', true);     Assert::equal($expected, $actual); } This should also be true. Try to change the expected value if you are eager to see a failure message.
       
      08 Next steps
      You can add more methods to the MyTest class or create new files in the "tests" directory. Check out the range of available Assertions and other features in the docs and see how they could help you writing more fail-safe code.
      Once you make a habit of writing tests you'll see how it can assist making your code more bulletproof and stable. Remember: test early, test often 🙂
      If you find out something useful or cool with Tester make sure to share.
    • 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.
      Description from PW Weekly:
       
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread: