Jump to content
netcarver

ProcessDiagnostics

Recommended Posts

Introducing ProcessDiagnostics and it's helper module suite. (Is this ProcessWire's first community-created module suite?)

post-465-0-19487500-1401132201_thumb.png post-465-0-70031800-1401214763_thumb.jpg

Description

This suite adds a page under the setup menu that displays information about your installation. Each section's data is provided by a specialist diagnostic helper module but it is all collected and displayed by ProcessDiagnostics.

The ProcessDiagnostics module itself does not encode any knowledge about what makes up a good or bad setting in PW - (that's done by the helper modules) - but it does the following...

  • Gather the diagnosics (thanks to PW's hook system)
  • Display the collected diagnostics
  • Provide helper functions for describing some common things
  • Dispatch actions to diagnostic provider modules (again thanks to PW's hook system)

And eventually it will:

  • Allow control of the verbosity of the output
  • Allow the output to be emailed to a sysop
  • Store the results between visits to the page
  • Detect differences between results at set times
  • Send a notification on detection of changes

Although I am curating the collection, anyone is welcome to fork the repo, make changes in a topic branch, and submit pull requests. I've already had submissions from horst and Nico.

Diagnostic Providers

The current diagnostic providers include...

DiagnosePhp - Simple diagnostics about the PHP envirnoment on the server

DiagnoseModules - An ajax based module version checker by @Nico

DiagnoseImagehandler - Lets you know about GD + Imagick capabilities by @horst

DiagnoseDatabase - Checks each DB table and lets you know what engine and charset are in use

DiagnoseWebserver - Checks the webserver setup

DiagnoseFilesystem - Looks at how your directory and files are configured and warns of permission issues (currently incomplete)

There is also a bare bones demonstration diagnostic module...

DiagnoseExample - minimal example to get module authors started.

Translations

English & German (thank you @Manfred62!)

Help translating this suite to other languages is always welcome.

On The Net

Check out Nico's blog post about this suite on supercode.co!

  • Like 21

Share this post


Link to post
Share on other sites

As of v0.0.2 you should be able to hook ProcessDiagnostics::CollectDiagnostics() to either append or modify collected diagnostic data as required. Minimal cell highlighting now added for failure lines (see picture in the opening post.)

  • Like 1

Share this post


Link to post
Share on other sites

Steve,

I am wondering if it is useful to also include the CHMOD values (777, etc)? Just thinking out loud...

Very, very trivial request: Please change Ok to OK...  :lol:  :P  ;)

  • Like 1

Share this post


Link to post
Share on other sites

@kongondo

Done and done as v0.0.3. Initial post updated to show output.

  • Like 1

Share this post


Link to post
Share on other sites

@Steve: maybe sooner or later it would be good to group the diagnostics ( $results['group_name'][] = ...), what do you think?

Here is a snippet for php version that has max memory and system info. Take from it what you think is useful.

I will provide one other for images stuff.

    protected function getPhpDiagnostics() {

        $ver     = null;   // string  PHP Version
        $mem     = null;   // string  Max Memory for PHP
        $api     = null;   // string  full api info
        $sys     = null;   // string  full sys info

        ob_start();
        phpinfo(INFO_GENERAL);
        $buffer = str_replace("\r\n", "\n", ob_get_contents());
        ob_end_clean();

        $ver = phpversion();

        $mem = trim(ini_get('memory_limit'));

        $pattern = preg_match('#</td>#msi', $buffer)===1 ? '#>Server API.*?</td><td.*?>(.*?)</td>#msi' : '#\nServer API.*?=>(.*?)\n#msi';
        $api = preg_match($pattern, $buffer, $matches)===1 ? trim($matches[1]) : null;

        $pattern = preg_match('#</td>#msi', $buffer)===1 ? '#>System.*?</td><td.*?>(.*?)</td>#msi' : '#\nSystem.*?=>(.*?)\n#msi';
        $sys = preg_match($pattern, $buffer, $matches)===1 ? trim($matches[1]) : null;

        // build results array version

        $pwver = $this->config->version;
        $php53 = version_compare($ver, '5.3.8', '>=');
        if(!$php53) {
            $res = version_compare($pw, '2.4.0', '<');  // I don't know which is the last PW version that can run with 5.2.x
            $action = $res ? '' : $this->_('Explanation of any problem or action needed to correct.');
        }
        else {
            $res = true;
            $action = $this->_(sprintf('running ProcessWire %s with PHP %s is fine', $pwver, $ver));
        }
        $results['php'][] = array(
            'title'  => $this->_('PHP Version'),
            'value'  => $ver,
            'status' => $res ? $this->_('Ok') : $this->_('Fail'),
            'action' => $action
        );

        // build results array PHP Handler

        $res = true;
        $action = '';
        $results['php'][] = array(
            'title'  => $this->_('PHP Handler'),
            'value'  => $api,
            'status' => $res ? $this->_('Ok') : $this->_('Fail'),
            'action' => $action
        );

        // build results array PHP max memory

        $res = true;
        $action = '';
        $results['php'][] = array(
            'title'  => $this->_('PHP max Memory'),
            'value'  => $mem,
            'status' => $res ? $this->_('Ok') : $this->_('Fail'),
            'action' => $action
        );

        // build results array PHP system info

        $res = true;
        $action = '';
        $results['php'][] = array(
            'title'  => $this->_('System Information'),
            'value'  => $sys,
            'status' => $res ? $this->_('Ok') : $this->_('Fail'),
            'action' => $action
        );

        return $results;
    }
  • Like 4

Share this post


Link to post
Share on other sites

just a question: shouldn't this module show up in the setup section? Is there something to be done to see the results? Using latest dev of PW.

Hint: to make it full translatable you have to use a newline, otherwise it will not be found (see example):

line 170: 'value'  => $rewrite_ok ? $this->_('Installed') : $this->_('Not installed'),

// must be

line 170: 'value'  => $rewrite_ok ? $this->_('Installed') : 
                                    $this->_('Not installed'),
  • Like 3

Share this post


Link to post
Share on other sites

@horst

Thanks for taking the time to submit this!  Perhaps this can become the first community developed module for PW if others want to get involved too :)

Splitting the results into sections looks like a good idea - I'll work that into the display code. In the meantime, I've added several class variables that we can use for the 'OK', 'Failure' and (new) 'Warning' messages.  Going forward, if people could use self::$ok, self::$fail or self::$warn for the 'status' entry that will simplify things.

@Manfred62

Thank you for the feedback, I was unaware of the need to separate different strings with linebreaks for the translator to find them.

Regarding the location of the diagnostics output page; yes, it should show up under the Setup menu.  At least, it does on my fairly recent dev version (not the latest though.)

Edited to add: Updated the opening post image.

  • Like 3

Share this post


Link to post
Share on other sites

Could some one add a check if /site/install/ is deleted? Because it's a potential risk to leave it.

  • Like 2

Share this post


Link to post
Share on other sites

@Steve, for what is the parent::init() parent::install() in the install routine?

When I try to install the module my server (apache windows) crashes and after reloading the browserpage I have the module installed but not the Diagnostics Page created.

I haven't investigated much further, but the code where it comes to the interrupt is not in your module, but is it needed / common usage to do the call for parent::install?

Also if it is common, if something break like in my situation, the uninstall routine of your module (and every other module where this happens) is affected when it try to delete a page that wasn't created.

Would it be better to check if $p->id > 0 before trying to delete, and in the init() or ready() if the Diagnostics Page exists?

---

Another one I have from @adrian: on some servers the phpinfo() could be disabled, therefor a check for it would be good. I have forgotten to implement it in my previously posted code:

        /**
         * returns if function is disabled in php
         *
         * @return boolean: true, false
         */
        static protected function isDisabled($function) {
            $disabled_functions = explode(',' , str_replace(' ', '', strtolower(ini_get('disable_functions'))));
            return in_array(strtolower($function), $disabled_functions);
        }
Edited by horst
  • Like 2

Share this post


Link to post
Share on other sites

Also it could be good to add some or many (?) checks into it that are normally run with the installer?

This could be very useful when people just ftp-ing their site-profile from dev to live and send a mysql_dump along the same way.

Edited by horst
  • Like 1

Share this post


Link to post
Share on other sites

@horst

I'm not sure re the call to the parent install routine. Will look into it. In the meantime, you are right about adding a check on the page id before trying to delete the page on uninstall. I do plan on cribbing some of Ryan's pre- and post-install code to see if we can re-use it usefully in the module.

BTW, I don't have a windows machine to test this on so anything you turn up will be useful.

@Nico

Noted. Thank you.

  • Like 1

Share this post


Link to post
Share on other sites

Here is the getImagesDiagnostics():

    protected function getImagesDiagnostics() {

        // check for GD-lib

        if(!function_exists('gd_info')) {
            #$results['images'][] = array(
            $results[] = array(
                'title'  => $this->_('GD library'),
                'value'  => $ver,
                'status' => self::$fail,
                'action' => $this->_('There seems to be no GD-library installed!')
            );
        }
        else {
            $gd  = gd_info();
            $ver = isset($gd['GD Version']) ? $gd['GD Version'] : $this->_('Version-Info not available');
            $jpg = isset($gd['JPEG Support']) ? $gd['JPEG Support'] : false;
            $png = isset($gd['PNG Support']) ? $gd['PNG Support'] : false;
            $gif = isset($gd['GIF Read Support']) && isset($gd['GIF Create Support']) ? $gd['GIF Create Support'] : false;
            $freetype = isset($gd['FreeType Support']) ? $gd['FreeType Support'] : false;

            // GD version
            #$results['images'][] = array(
            $results[] = array(
                'title'  => $this->_('GD library'),
                'value'  => $ver,
                'status' => self::$ok,
                'action' => ''
            );

            // PHP with GD bug ?
            if((version_compare(PHP_VERSION, '5.5.8', '>') && version_compare(PHP_VERSION, '5.5.11', '<'))) {
                if(version_compare($this->config->version, '2.4.1', '<')) {
                    #$results['images'][] = array(
                    $results[] = array(
                        'title'  => $this->_('GD library Bug'),
                        'value'  => 'possible bug in GD-Version',
                        'status' => self::$warn,  // @steve: or better use self::fail ?
                        'action' => $this->_('Bundled GD libraries in PHP versions 5.5.9 and 5.5.10 are known as buggy. You should update A) your PHP version to 5.5.11 or newer, or B) the ProcessWire version to 2.4.2 or newer')
                    );
                }
            }

            // GD supported types
            foreach(array('JPG', 'PNG', 'GIF', 'FreeType') as $v) {
                $name = $this->_(sprintf('GD %s Support', $v));
                $v = strtolower($v);
                $value = $$v ? $this->_('supported') :
                                $this->_('not supported');
                $status = $$v ? self::$ok : self::$fail;
                #$results['images'][] = array(
                $results[] = array(
                    'title'  => $name,
                    'value'  => $value,
                    'status' => $status,
                    'action' => ''
                );
            }
        }

        // check if we can read exif data

        $res = function_exists('exif_read_data');
        $action = $res ? '' : $this->_("This is not needed for ProcessWire core, but maybe needed with third party modules");
        #$results['images'][] = array(
        $results[] = array(
            'title'  => $this->_('Exif read data'),
            'value'  => $res ? $this->_('available') :
                               $this->_('not available'),
            'status' => $res ? self::$ok : self::$warn,
            'action' => $action
        );

        // check if Imagick is supported

        if(!class_exists('Imagick')) {
            #$results['images'][] = array(
            $results[] = array(
                'title'  => $this->_('Imagick Extension'),
                'value'  => 'not available',
                'status' => self::$warn,
                'action' => $this->_('This is not needed for ProcessWire core, but maybe needed with third party modules')
            );
        }
        else {
            if(self::isDisabled('phpinfo')) {
                #$results['images'][] = array(
                $results[] = array(
                    'title'  => $this->_('Imagick Extension'),
                    'value'  => 'is available',
                    'status' => self::$warn,
                    'action' => $this->_('Odd, retrieving phpinfo on your server is disabled! We cannot get further informations here.')
                );
            }
            else {
                #$results['images'][] = array(
                $results[] = array(
                    'title'  => $this->_('Imagick Extension'),
                    'value'  => 'available',
                    'status' => self::$ok,
                    'action' => ''
                );
                ob_start();
                phpinfo();
                $buffer = ob_get_clean();
                $pattern = '/>imagick<.*?<table.*?(<tr>.*?<\/table>)/msi';
                preg_match($pattern, $buffer, $matches);
                if(isset($matches[1])) {
                    $buf = trim(str_replace('</table>', '', $matches[1]));
                    $a = explode("\n", strip_tags(str_replace(array("\r\n", "\r", '</td><td'), array("\n", "\n", '</td>###<td'), $buf)));
                    $info = array();
                    foreach($a as $line) {
                        if(preg_match('/ImageMagick supported formats/i', $line)) continue;
                        $tmp = explode('###', $line);
                        $k = trim($tmp[0], ': ');
                        $v = str_replace(' http://www.imagemagick.org', '', trim($tmp[1]));
                        #$results['images'][] = array(
                        $results[] = array(
                            'title'  => $k,
                            'value'  => $v,
                            'status' => self::$ok,
                            'action' => ''
                        );
                    }
                }
            }
        }

        return $results;
    }
  • Like 2

Share this post


Link to post
Share on other sites

@horst

It turns out that the call to parent::init() in the init() method does things like automatically including the ProcessDiagnostics.css file in the page output. Well, at least I know now. :)

  • Like 1

Share this post


Link to post
Share on other sites

Oh, my fault. It was a typo: I meant in the parent::install() function, not the init(). Sorry.

Share this post


Link to post
Share on other sites

You are right - class process's install() does nothing. I've removed the parent::install() call.

  • Like 1

Share this post


Link to post
Share on other sites

@horst

Added your Image diagnostics and implemented sections. I updated the image in the opening post to show the results.

  • Like 4

Share this post


Link to post
Share on other sites

Nice one Steve!

I used to love this feature in Textpattern. I'm on holiday next week, but I'll check in to see the goodness you all have come up with when I get back.

  • Like 1

Share this post


Link to post
Share on other sites

@netcarver: Nice, but you don't have to delete "site-default" - only "/site/install/" because site default get's renamed to site while installing.

  • Like 1

Share this post


Link to post
Share on other sites

@Steve: great!

Will you add the handler (apache_module or fcgi) and the MaxMemory to the PHP section?

Share this post


Link to post
Share on other sites

@Nico

Done. See opening post image.

@horst

Done. Ditto.

  • Like 2

Share this post


Link to post
Share on other sites

Great one. I was thinking about having this is PW just a couple days ago... and if you wait long enough someone else will do it :P

I think this would be a must have in Core.

  • Like 3

Share this post


Link to post
Share on other sites

 I think this would be a must have in Core.

Exactly!

Share this post


Link to post
Share on other sites

If it's going to be a core module maybe you could even add a "modules" section and show if there are updates for your installed modules. Maybe even with a link to the update if there is one. Shouldn't be that hard to write because module updates are included in the core since 2.3 or 2.4. :)

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 jploch
      Hey folks,
      for a module (a pagebuilder based on PageTable) I need to save some settings as JSON. The values are saved for each page table item (a pw page). It's working well, but I am looking for ways to improve the structure I have. As I'm not that experienced with JSON, maybe someone more experienced can take a look and tell me if my approach is good practice. 

      My goal is to make all the items accessible by page id, without looping over them (using objects instead of arrays):
      // access from template with pw page var $jsonObject->items->{$page}->cssClass; Her is an example of my JSON structure:
      { "items": { "3252": { "id": "3252", "cssClass": "pgrid-main", "breakpoints": { "base": { "css": { "grid-column-end": "auto", "grid-row-end": "auto", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "60px", "padding-right": "60px", "padding-top": "60px", "padding-bottom": "60px", "background-color": "rgb(255, 255, 255)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3686": { "id": "3686", "cssClass": "test_global", "breakpoints": { "base": { "css": { "grid-column-end": "-1", "grid-row-end": "span 1", "grid-column-start": "1", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3687": { "id": "3687", "cssClass": "block_editor-3687", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } }, "3696": { "id": "3696", "cssClass": "block_editor-3696", "breakpoints": { "base": { "css": { "grid-column-end": "span 2", "grid-row-end": "span 1", "grid-column-start": "auto", "grid-row-start": "auto", "align-self": "auto", "z-index": "auto", "padding-left": "0px", "padding-right": "0px", "padding-top": "0px", "padding-bottom": "0px", "background-color": "rgba(0, 0, 0, 0)", "color": "rgb(0, 0, 0)" }, "size": "@media (min-width: 576px)", "name": "base" } } } }, "breakpointActive": "base", "breakpointActiveSize": "@media (min-width: 576px)" }  
    • By jploch
      Fieldtype Page Table Grid
      This is a sneak preview of a side project I've been working on for quite some time now. A lot of work and thought has gone into this, so I will most likely release this as a commercial module at some point in the near future. 

      As a designer (and developer) I get the appeal of a WYSIWYG editor. After playing around with some WYSIWYG page builder tools, I always felt something was wrong about them. So I decided to build my own PW version based on PageTable.

      Here is a small demo (using AdminThemeCanvas, but its working with other admin themes as well) :
      There is also a complete website that I built for a friend of mine using this module and some custom blocks.
      Concept
      This fieldtype shares a lot of features with PageTableExtended: it's also an extension of PageTable and renders the block templates in the backend and frontend (native PW templates and fields). You can also add your own css via module settings.
      The difference is, this fieldtype also gives you the ability to rearrange and resize elements in a visual way as well as enable inline editing for text, ckeditor and file fields. Similar (and promising) attempts have been made, but I wanted something based on native CSS grid instead of a CSS framework...so I built my own version. Most CSS frameworks are based on flexbox, which is great for layouting elements horizontally. With CSS grid, you can place elements horizontally and vertically, allowing for layouts that were not previously possible with CSS. Similar to webflow, this fieldtype uses javascript (in the backend) to let you manipulate CSS grid in a visual way to design fully responsive websites (or parts of them). It should still be possible to include a CSS framework if you like (just add the classes to your block markup and include the CSS via module settings).
      The CSS grid layout manipulations are saved in a single field as a JSON array and used to generate a dynamic stylesheet that you simply include in your main template (no inline styles). The styles are saved within the breakpoint you select and cascade down to smaller breakpoints. That means you can specify just the basic breakpoint and adjust other breakpoints if needed. The exception is the mobile breakpoint which will display everything in one column as a default (you can change the layout here too).
      The fieldtype also comes with an optional style panel to manipulate some additional CSS properties directly on the page. You can customize the panel or disable it completely from the module settings (and just use a CSS file that you include via module settings). The style panel is based on inputfields (nothing is saved to the database). This means that you just have to install the module and all fields are available to all blocks automatically (this can be customized). It also has the benefit that your installation is not flooded with fields; this module only installs one field.
      Don't want to give your customer all that power? Design features can be disabled for certain roles. The grid editor role can just edit the content and use the inline editing feature to edit content quickly. You can then also grant access individually to the style panel, resize or drag functionality.
      Features
      Blocks are just pages Blocks are defined by native PW templates and fields Manipulate CSS grid in a visual way to design fully responsive websites (or parts of them) Design features can be disabled for certain roles Inline editing of text, ckeditor and file fields The layout is 100% CSS grid (very small css file size) Simply drag and resize to manipulate grid items directly inside the backend Manipulate grid columns and rows directly on the page (use any number of columns you want) All style manipulations are saved as JSON and used to generate a dynamic stylesheet that you just include in your main template (no inline styles) Nested groups/grids (child pages of nested blocks are created under group parent) Global blocks work with page reference field (changes on one page, changes all blocks on all pages) Manual and auto placement of grid items Define custom icons for your blocks via native template settings (template -> advanced -> icon) Option to load lazysizes in the backend to enable lazy loading of assets with class lazyload Works with all default and ui-kit based admin themes If you have any questions or feedback, let me know.
    • By bernhard
      I built this module because I needed a versatile solution to replace tags and simple if-blocks in some E-Mails and PDF documents.
      If you only need to replace static tags (no if-conditions), then you can use default PW api and need no module:
      $str = "My favourite color is {color}."; $texttools = $sanitizer->getTextTools(); echo $texttools->populatePlaceholders($str, ['color' => 'red']); // output: My favourite color is red. Usage:
      See the two example Files in the folder /replacements

       
      Methods:
      replacementsTable()
      Renders an overview of all available replacements (see the example in the Module's config file:
       
      Create new Replacements:
      Simply copy the sample file and adopt to your needs.
       
      Download:
      https://gitlab.com/baumrock/RockReplacer
    • By bernhard
      DEPRECATED
      I'm using this module in several projects, but it will likely not see any updates in the future. I'm not happy with it and I'm looking for ways to develop better solutions. RockTabulator was my first try, but I'm also not 100% happy with that. The tabulator library is great, but my module implementation is not. I hope to get a good solution soon, but it will be a lot of work...
      ---
      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/FieldtypeRockGrid
      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
      German Translation File: site--modules--fieldtyperockgrid--fieldtyperockgrid-module-php.json
      Changelog: https://gitlab.com/baumrock/FieldtypeRockGrid/raw/master/changelog.md
       
      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 (please contact me via PM).
       
      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 Paul Greinke
      Hi there. I wrote a custom module for one of my projects. In fact I maybe want to use my module in other projects too. In order to be variable and customizable  I need to implement some custom hooks into my module. So I can afterwards hook into the my functions in order to modify them to match the needs of the new project.
      I tried simply defining functions with the '__' prefix. But that did not work. I'm imagining something like the following:
      <?php class MyClass { public function ___someFunction() { // Do something } } // ready.php $this->addHookBefore('MyClass::someFunction', function($event) { // some customization }); Is there a way to accomplish that? 
×
×
  • Create New...