Jump to content

Module: Matrix Fieldtype & Inputfield


Recommended Posts

  • 4 months later...

Hey kongondo - I have just started using this on a site for the first time - it is going to be awesome!

The one thing I would like to be able to do though is have better control over the row/column selectors. What I need to do is be able to limit the matches to children of the current page because I will be using this field on several page trees on the site that have the same structure, so a template selector will grab all these pages, not just the one under the current parent. I think if the PW core supported 'page' as an argument that could be used for the parent selector I'd be OK.

parent=page, template=rows_template

Perhaps your module could have an extra config settings to limit to the current page? Or perhaps an option to use custom php code to find the pages - like you can when defining a page field. Is that something you'd be willing to support?

Any other thoughts on how to make this work?

Thanks again for your work on this!

PS Another feature suggestion - any chance of adding a browser warning alert for the reset button? I know that nothing is actually lost until the page is saved, but I bet some users will think they have lost everything already and start typing again, not realizing they can simply reload the page. Maybe the button could also be named "Clear Data" or something more descriptive than "Reset".

My thoughts continue :) I am not sure how to handle this, but I have a checkbox field on each of the pages that make up the columns - this is to determine whether the page should actually be included in the table. The thing I worry about is someone unintentionally unchecking this which will result in data loss the next time the page with the Matrix table field is edited and saved. Other than a warning in the description/notes of the checkbox field, I am not sure how to protect against this. Could you module perhaps warn when rows/column are about to be discarded - with an alert that actually says which ones are being deleted from the matrix table? Any other ideas?

Also, what about an API method to create data - it would be nice to make it easier to create an import routine from an existing database.

  • Like 1
Link to post
Share on other sites
  • 2 weeks later...

@Adrian,

Thanks for the suggestions. I am trying to create some time this week to look at these and other pending issues RE my other modules....I know I have been saying this a lot lately but other things/distractions beyond my control keep cropping up..... :-)

  • Like 3
Link to post
Share on other sites
  • 2 weeks later...
  • 2 months later...

Update: version 0.0.3

Small but important update to correct oversight whereby records with empty values were being saved to the database, thx @netcarver.

Hey kongondo - I know you are super-busy at the moment, but I actually have a use case where it would be much easier if it did store empty values. Because I am foreaching through column names I actually ended up having to put "ND" (for No Data) in the cells to get the desired result. This isn't a huge problem because I control the data going into the Matrix tables, but I think it might be a nice option to have.

Thanks! 

  • Like 2
Link to post
Share on other sites

Something else I am going to need shortly is the ability to check whether the CSV import appends rows, or overwrites - I actually haven't tested - does it currently append, or overwrite? Maybe if append, then it's ok because you can use the "Reset" to clear and then it is effectively an overwrite.  

Also, the ability to export to CSV would be very handy - it would be much easier to make major edits via Excel and then import when done.

Just some ideas for when you're bored, although I might need these sooner than later - if so I'll send you a PR.

  • Like 1
Link to post
Share on other sites

Hey kongondo - I know you are super-busy at the moment, but I actually have a use case where it would be much easier if it did store empty values. Because I am foreaching through column names I actually ended up having to put "ND" (for No Data) in the cells to get the desired result. This isn't a huge problem because I control the data going into the Matrix tables, but I think it might be a nice option to have.

Thanks! 

Do you mean to allow empty values in both CSV imports and manual entered values? Both should be quite easy to implement. I think I'll implement them as separate options though.

Something else I am going to need shortly is the ability to check whether the CSV import appends rows, or overwrites - I actually haven't tested - does it currently append, or overwrite? Maybe if append, then it's ok because you can use the "Reset" to clear and then it is effectively an overwrite.  

Also, the ability to export to CSV would be very handy - it would be much easier to make major edits via Excel and then import when done.

Just some ideas for when you're bored, although I might need these sooner than later - if so I'll send you a PR.

Overwrite vs Append:

Off the top of my head I think it overwrites. I'll have to confirm this one. 

Export to CSV:

Good idea. Added to my @todo

Link to post
Share on other sites

@adrian,

Just to let you know that I've added all your requests the module's GitHub issues so that I don't forget. As for the append vs overwrite issue, append seems to be quite tricky. It would need to find the last populated row and append from there. But finding out what the last row can be tricky, especially where we also allowed 'empty values'. I don't know if this makes sense. Anyway, will have a think about this one. Btw, the suggestion about custom PHP code to find row/column matrix pages is a powerful one and will lead to many possibilities, thanks.

Link to post
Share on other sites

@adrian,

Just to let you know that I've added all your requests the module's GitHub issues so that I don't forget. As for the append vs overwrite issue, append seems to be quite tricky. It would need to find the last populated row and append from there. But finding out what the last row can be tricky, especially where we also allowed 'empty values'. I don't know if this makes sense. Anyway, will have a think about this one. Btw, the suggestion about custom PHP code to find row/column matrix pages is a powerful one and will lead to many possibilities, thanks.

Thanks kongondo - I saw all those posted issues!

I haven't thought about the issues involved in making append work, but I do think it is pretty critical functionality. Currently unintentional data loss is very possible and I would assume that append was actually the default behavior. 

Thanks very much for looking into the custom PHP code option!

Link to post
Share on other sites
  • 1 month later...

Great stuff this... great stuff indeed.

One question, would it be possible to pick a specific value from the matrix?

So on a certain page, I would like to spit out the value at row 2, column C, without having to loop the whole pricetable to find that specific value.

My current implementation is quite inefficient:

    foreach ($accommodation->pricetable AS $p) {
        if ($p->row == $weekPage->id && $p->column == $pricePage->id) {
            echo $p->value;
        }
    }

Thanks for a great module!

  • Like 1
Link to post
Share on other sites

Sorry for the late response. I don't quite follow your question. Did you find a solution?

I am busy with other projects and didn't check it again but i will check it. For the moment i don't have a solution.

Link to post
Share on other sites

One question, would it be possible to pick a specific value from the matrix? So on a certain page, I would like to spit out the value at row 2, column C, without having to loop the whole pricetable to find that specific value.

Currently no (unless there is some selectors I don't know about). It is something I have been thinking about, creating a method() to accomplish this. I think it would make this module even more powerful. It wouldn't be too complicated to implement, I think; Just a simple raw SQL PDO query. Implementation would be similar to a get and a find (for many).

Edit: Silly me; half asleep probably. This already works. See next post

I also think for the row and columns, one should be able to search not only by ID but by $page and title. E.g. find the price (value) of a product that is 'red' (title [row]) in colour and 'small' (title [column]) in size. Could you please file your query as a request in GitHub so that I don't forget? Thanks. I can't promise when I'll be able to get to it though, unfortunately.

Edited by kongondo
Correct answer in my subsequent post
  • Like 1
Link to post
Share on other sites

Currently no (unless there is some selectors I don't know about). It is something I have been thinking about, creating a method() to accomplish this. I think it would make this module even more powerful. It wouldn't be too complicated to implement, I think; Just a simple raw SQL PDO query. Implementation would be similar to a get and a find (for many). I also think for the row and columns, one should be able to search not only by ID but by $page and title. E.g. find the price (value) of a product that is 'red' (title [row]) in colour and 'small' (title [column]) in size. Could you please file your query as a request in GitHub so that I don't forget? Thanks. I can't promise when I'll be able to get to it though, unfortunately.

I must have been half-asleep when I answered this one.  :lol:. Sorry for  wasting your time with the GitHub issue. This already works (in fact, there is an example in README). See examples below. The last example answers your question.

Here 'catalogue' is the name of the matrix field on the current page

//find all values for one row
$results = $page->catalogue->find("row=1024");

//find all values for one column
$results = $page->catalogue->find("column=1035");

//finding by object; no need for $p->id for 'column' or 'row'
$p = wire('pages')->get('template=basic-page, title=Sizes');
$results = $page->catalogue->find("column=$p, value>=67");//finding by object; no need for $p->id

foreach ($results as $r) echo $r->value . '<br>';

//alternatively user toString() formatted output
echo $results;

//get a specific matrix value (single intersection)
$result = $page->catalogue->get("column=1034, row=1020");
echo $result->value;

Will update the docs with these examples.

Edited by kongondo
Link to post
Share on other sites

Toying with the idea of having 'non-page columns and rows mode'. In this mode, if you upload a csv file, the first row will be treated as column headers and first column as row headers/labels

Link to post
Share on other sites

Update version 1.0.1 (Dev only for now)

Note: Haven't had time to update README

Changes

  1. As requested, added ability to find column/row pages using custom PHP code. Thanks @adrian. This is a really powerful feature. Note that the order of precedence for the 3 methods to return row/column pages is: 1. Selector 2. Custom PHP code 3. Page field (3 is greatest).
  2. Browser warning alert for reset button + rename the button (@adrian). Done + enhancement by @mackski, the button styling now matches other PW buttons
  3. Added two properties: rowLabel and columnLabel (in memory only; not saved to DB) to return user-friendly row/column header info. E.g. echo matrix->rowLabel could render 'Red' or 'Large' instead of echo matrix->row that would instead render the page's ID. These are searchable in-memory ONLY, e.g. $results = $page->results->find("columnLabel=Maths").
  4. Added two methods getRow() and getColumn() for mainly syntactic convenience. These do in-memory searches. Can search by path, title, ID, page object (see examples below).

Examples

columnLabel

//find all results for one column - using 'user friendly selector';
$results = $page->results->find("columnLabel=Maths");//@note: in-memory selector
echo '<h3>The are the results of: ' . $results->first()->columnLabel . '</h3>';//maths results
foreach ($results as $r) echo $r->rowLabel . ': ' . $r->value . '<br>';//student name: score

rowLabel

$results = $page->results->find("rowLabel=Maurice|Joel|Mi Mong");//@note: in-memory selector
#$results = $page->results->find("");//will show all
echo '<h3>The are the MULTIPLE results for several students</h3>';
$row = array();
foreach ($results as $r) {

	if(!in_array($r->row, $row)) {
		echo '<h4>' . $r->rowLabel . '</h4>';//echo'es student name (e.g. Joel)
		$row[] = $r->row;
	}
	echo $r->columnLabel . ': ' . $r->value . '<br>';//echo'es each subject's results, e.g. Maths: 70
}

getRow()//accepts 3 arguments selector value, limit, sort

#$p = $pages->get(1088);
#$results2 = $page->results->getRow($p->id);//get by ID
#$results2 = $page->results->getRow($p->title);//get by Title
#$results2 = $page->results->getRow('Joel');//get by Title (case sensitive)
#$results2 = $page->results->getRow($p);//get by Page
#$results2 = $page->results->getRow($p->path);//get by Path
$results2 = $page->results->getRow(1087);//get by ID//get by ID
#$results2 = $page->results->getRow('/students/richard/');//get by Path
#$results2 = $page->results->getRow($p, 4, 'random');//get by Page, limit to 4 random values
#$results2 = $page->results->getRow($p, 4, 'asc');//get by Page, limit to 4 values, sort ascending
#$results2 = $page->results->getRow($p, 3, 'desc');//get by Page, limit to 3 values, sort descending
#$results2 = $page->results->getRow($p->title, 4);//get by Page title, limit to 4
#$results2 = $page->results->getRow($p, '', 'asc');//get by Page, no limit, sort ascending
#$results2 = $page->results->getRow($p->path, '', 'desc');//get by Path, no limit, sort descending

echo '<h3>The are the results for: ' . $results2->first()->rowLabel . '</h3>';//student name
foreach ($results2 as $r) echo $r->columnLabel . ': ' . $r->value . '<br>';//subject: score

getColumn()//accepts 3 arguments selector value, limit, sort

Similar to getRow() except for columns

$results3 = $page->results->getColumn('/subjects/physics/');
echo '<h3>The are the results for: ' . $results3->first()->columnLabel . '</h3>';//Subject
foreach ($results3 as $r) echo $r->rowLabel . ': ' . $r->value . '<br>';//student:score

Some feature requests still pending + thinking whether to implement findRows() and findColumns().

Please test and let me know (if you can, both fresh install and upgrades [test on non-critical data please])

Edited by kongondo
Added a few more examples
  • Like 3
Link to post
Share on other sites

Update version 1.0.2 (Dev only for now)

Note: Haven't had time to update README
 
Change
  1. Added method getValue() to get the value at the given coordinates(row, column). This is an extended syntactic alias for $page->matrix->get('row=1045, column=1098'). It is more versatile, taking two parameters (row, column), allowing you to get a value by specifying its row and column ID (integer), path, title or Page object.
Examples: getValue() (matrix field called 'results' with student names for rows and subjects for columns)
//get by path
#$result = $page->results->getValue('/students/ishak/', '/subjects/physics/');
//get by title		
#$result = $page->results->getValue('Ishak', 'Physics');//note title is case sensitive
//get by ID		
#$result = $page->results->getValue(1062, 1082);

//### get by Page
#$r = $pages->get(1064);//results row
#$c = $pages->get(1083);//results column

//pass Page object
#$result = $page->results->getValue($r, $c);
//pass Page title
#$result = $page->results->getValue($r->title, $c->title);
//pass Page ID
#$result = $page->results->getValue($r->id, $c->id);
//pass Page path
#$result = $page->results->getValue($r->path, $c->path);

###############

//get by mixed parameters
#$result = $page->results->getValue('Ishak', '/subjects/history/');
#$result = $page->results->getValue('/students/sarah/', 'French');//note title is case sensitive
#$result = $page->results->getValue($r, 'Music');
#$result = $page->results->getValue('Amani', $c->path);
$result = $page->results->getValue('James', $c->id);

if($result) echo '<strong>' . $result->rowLabel . ' </strong>scored ' . $result->value . ' in ' . $result->columnLabel;
else echo 'No result found';
Please test and let me know how it goes, thanks.
  • Like 1
Link to post
Share on other sites

Update version 1.0.3 (Dev only for now)
 
Note: Haven't had time to update README
 
Changes

  1. Export to CSV feature: Can export whole matrix (default) or limit to specified row range (e.g. start at row#2 and end at row#10 ). These are set in the collapsed fieldset 'Import/Export CSV Data' below the matrix. Exported CSV files include timestamp in the file name.
  2. Some CSS styling for buttons.
  3. Option: Set alert message to show after clicking 'clear data' button. If message set, show alert if no message specified, do not show any alert. Note: now using a custom popup rather than the ugly + annoying browser popup :-).
  4. Option: Save empty values. Default is no; do not save empty values. Current status shown at the top and bottom of the matrix table.
  5. Option: Show row numbers. Default is no, do not show row numbers.
  6. Fixed a bug where older saved values would still appear after one switched to using custom PHP code to return rows and columns.
  7. Added checkboxes for row selections (see #8).
  8. Clear Data: Rather than wholesale clearance, button will only clear values of selected rows (see #7). Will show a popup if you try to clear without first selecting at least one row.
  9. Fixed some minor bugs in situations where there would be more than one matrix table on a page.
  10. Some stylistic changes to rendered fields in line with above changes.
  11. Code re-factoring.

post-894-0-48872200-1446177788_thumb.png

Edited by kongondo
  • Like 5
Link to post
Share on other sites

Thanks kongondo - I saw all those posted issues!

I haven't thought about the issues involved in making append work, but I do think it is pretty critical functionality. Currently unintentional data loss is very possible and I would assume that append was actually the default behavior. 

Thanks very much for looking into the custom PHP code option!

@adrian: I think I misunderstood what you meant by append. I assumed you meant tucking new values at the end of the matrix starting from the last empty row. What I think you actually meant was for each value,  'if new value is empty, keep old value. If new value is not empty, overwrite old value'. Is that correct?

Link to post
Share on other sites

Expounding on the above...in 'append mode' there's two possible ways to determine when a value should be appended or a db value left alone (i.e. it is not being updated).

  1. This is as I describe above, If there is a BLANK/EMPTY value coming in, we assume we want to keep the db value, so we don't change it; OR
  2. If a corresponding value DOES NOT EXIST in the new values coming in (sort of like null), then we keep the db value. In this approach, it means if an EMPTY corresponding value is coming in, we empty the existing db value. 

The problem with #1 is that it won't account for scenarios where you actually want an incoming blank value to wipe out a corresponding db value. Of course this can be accomplished by manually deleting said values in the table itself rather than the CSV import but it could get tedious. Maybe #2 is the more natural way to do it. However, it is the more difficult way (currently) since it would require new CSV values coming in differently. Consider a matrix like this:

              Small      Medium    Large

Red       12           11             13

Green    15           9               8

Blue       7             14             6

Currently, data import does not allow Row (Red, Green, Blue) and Column (Small, Medium, Large) labels/headers in the imported CSV data. As you know, data comes in like this (considering the above table):

12,11,13

15,9,8

7,14,6

This won't work for #2 since there is no way of telling what a null value is. If data came in like this

Red Small 12

Red Large 13

Green Small 15

Green Medium 9

Green Large 13

Blue Medium 14

...then, we would be able to tell that Red Medium, Blue Small and Blue Large were null because they are not part of the incoming dataset. In that case, we wouldn't touch the corresponding db values. However, I don't think this is the natural/normal way of structuring CSV data (verbosity). So, for now, unless I find another way or am nissing something obvious, I am sticking with #1 for append mode.

Edited by kongondo
Clarifications..
  • Like 1
Link to post
Share on other sites

Kongondo - you raise some good points around the issue of appending when importing. I don't think I really thought it through myself when I mentioned it in the first place - of course this is not a normal field type where you can just append new rows. The row must already be part of the matrix. I was talking about appending new rows. In my current use case, each year there will be a new "year" row that will appear in the matrix. I would like users to potentially be able to import a CSV of the data for that row. Of course importing for one row may not be worth the effort, but in some cases I can have up to 20 columns, so it might just be worth it. In that case, I would want "import" to just append the new row to the blank year that is in the matrix table.

Here's my matrix so you can see what I am talking about:

post-985-0-68088200-1446497099_thumb.png
 

However, I don't think this is the natural/normal way of structuring CSV data (verbosity).

 
I am not sure I agree with this - if I had a dataset in excel I would definitely have the years in the first column.
 
I agree that there are issues around how to structure the CSV to be imported - my initial thought is that it would be nice if it could (or must) contain the year in the first "column". I think it is a bit weird that you can't export from a matrix field and then import the same CSV file back into the matrix field, because of that first column issue. Maybe "ignore first column" and while you are at it, "ignore first row" options would be good - make sense?
 
I am concerned about the current behaviour though, because at the moment, any import completely wipes the existing data - I don't think this is a good situation.
 
Some other thoughts on your recent dev additions:

  • my initial thought is that checking rows would mean that only those rows would be exported - I didn't realized that I had to enter row numbers - could this be changed to respect checked rows as well? It would be nice if Matrix supported Shift+Click for selecting a block of rows like the PW does.
  • I think your new modal alert box needs some css tweaks - might be on your list, but thought I'd mention anyways.

This is getting better all the time - really super useful for my needs - thanks again!

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 monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
    • By tcnet
      PageViewStatistic for ProcessWire is a module to log page visits of the CMS. The records including some basic information like IP-address, browser, operating system, requested page and originate page. Please note that this module doesn't claim to be the best or most accurate.
      Advantages
      One of the biggest advantage is that this module doesn't require any external service like Google Analytics or similar. You don't have to modify your templates either. There is also no Javascript or image required.
      Disadvantages
      There is only one disadvantage. This module doesn't record visits if the browser loads the page from its browser cache. To prevent the browser from loading the page from its cache, add the following meta tags to the header of your page:
      <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate" /> <meta http-equiv="Pragma" content="no-cache" /> <meta http-equiv="Expires" content="0" /> How to use
      The records can be accessed via the Setup-menu of the CMS backend. The first dropdown control changes the view mode.

      Detailed records
      View mode "Detailed records" shows all visits of the selected day individually with IP-address, browser, operating system, requested page and originate page. Click the update button to see new added records.

      Cached visitor records
      View modes other than "Detailed records" are cached visitor counts which will be collected on a daily basis from the detailed records. This procedure ensures a faster display even with a large number of data records. Another advantage is that the detailed records can be deleted while the cache remains. The cache can be updated manually or automatically in a specified time period. Multiple visits from the same IP address on the same day are counted as a single visitor.

      Upgrade from older versions
      Cached visitor counts is new in version 1.0.8. If you just upgraded from an older version you might expire a delay or even an error 500 if you display cached visitor counts. The reason for this is that the cache has to be created from the records. This can take longer if your database contains many records. Sometimes it might hit the maximally execution time. Don't worry about that and keep reloading the page until the cache is completely created.
      Special Feature
      PageViewStatistic for ProcessWire can record the time a visitor viewed the page. This feature is deactivated by default. To activate open the module configuration page and activate "Record view time". If activated you will find a new column "S." in the records which means the time of view in seconds. With every page request, a Javascript code is inserted directly after the <body> tag. Every time the visitor switches to another tab or closes the tab, this script reports the number of seconds the tab was visible. The initial page request is recorded only as a hyphen (-).

      Settings
      You can access the module settings by clicking the Configuration button at the bottom of the records page. The settings page is also available in the menu: Modules->Configure->ProcessPageViewStat.
      IP2Location
      This module uses the IP2Location database from: http://www.ip2location.com. This database is required to obtain the country from the IP address. IP2Location updates this database at the begin of every month. The settings of ProcessPageViewStat offers the ability to automatically download the database monthly. Please note, that automatically download will not work if your webspace doesn't allow allow_url_fopen.
      Dragscroll
      This module uses DragScroll. A JavaScript available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability in view mode "Day" to drag the records horizontally with the mouse pointer.
      parseUserAgentStringClass
      This module uses the PHP class parseUserAgentStringClass available from: http://www.toms-world.org/blog/parseuseragentstring/. This class is required to filter out the browser type and operating system from the server request.
×
×
  • Create New...