Jump to content

Recommended Posts

4 hours ago, LuisM said:

Adding the panels and groups worked fine but I cant get the colors on the Pie Chart Panel to work. 
All I get is a Pie with grey segments 😞

Just had a look. Your syntax for the dataset options is off: you need the remove the outer array around backgroundColor. Then it works as expected.

'data' => [
  'datasets' => [
    [
      'data' => [
        floor($normalTotal),
        floor($recurringTotal)
      ],
      'backgroundColor' => [
        'rgba(193, 66, 66, 1)',
        'rgba(193, 66, 66, 1)'
      ]
    ]
  ]
]

You're right though about the default colors not being applied to pie charts. I pushed release v0.6.12 that fixes that.

  • Like 1

Share this post


Link to post
Share on other sites
On 3/1/2020 at 9:04 AM, Sevarf2 said:

Since we are in the matter, the actions on each page, like "lock", "unpub" or "trash"... don't work, I got an alert with "undefined"

I pushed release v0.6.13 which fixes the page list action buttons (unpublish, hide, etc.)

  • Like 2

Share this post


Link to post
Share on other sites
1 hour ago, d'Hinnisdaël said:

Just had a look. Your syntax for the dataset options is off: you need the remove the outer array around backgroundColor. Then it works as expected.


'data' => [
  'datasets' => [
    [
      'data' => [
        floor($normalTotal),
        floor($recurringTotal)
      ],
      'backgroundColor' => [
        'rgba(193, 66, 66, 1)',
        'rgba(193, 66, 66, 1)'
      ]
    ]
  ]
]

You're right though about the default colors not being applied to pie charts. I pushed release v0.6.12 that fixes that.

🤦‍♂️

thanks...

Share this post


Link to post
Share on other sites

Thank you for a very nice module.

I am using a panel-list like this:

   $panels->add([
        'panel' => 'collection',
        'title' => 'Clients',
        'data' => [
            'collection' => 'template=client, limit=10',
            'sortable' => true,
            'pagination' => true,
            'columns' => [
                'title' => 'Title',
                'url' => 'URL',
                'modified' => 'Modified'
            ]
        ]
    ]);

 

There are 50 client-pages, but the limits it to 10 records.

The pagination shows like this:

image.png.09a6b0b8a4b2f77e6bc2bff7d9d6fcb0.png

Is it possible to have the pagination show "forward" and "back" links to navigate to next 10 records?

 

 

Share this post


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

Is it possible to have the pagination show "forward" and "back" links to navigate to next 10 records?

Actual pagination buttons aren't implemented at the moment. That footer is meant to provide clarity for editors that there's more records than the ones currently displayed.

I'd consider the dashboard more a jumping-off point for editors than a replacement for other admin views better suited to browsing pages (like the page tree or listers). Ideally, they'd spend as little time as necessary on the dashboard and then go off to do whatever needs to get done in other parts of the admin.

While I'm pondering whether adding this is a good idea (it is a useful feature!), there's two options:

1. Create a copy of the included collection panel and give it a stab yourself. It shouldn't be too difficult — the module supports reloading panels via AJAX and provides the necessary JS events. Have a look at the documentation section on creating custom panels or crack open the chart panel to see an example. Let me know how it goes or if the module is missing anything to get this working.

2. There is a (currently) undocumented parameter you can supply to display a ›View All‹ button next to the pagination info. The parameter name is list and it takes a page, page ID or selector. If it's an admin page (ProcessLister), it will link to that page. If it's a content page (e.g. your Clients parent page), it will open the page tree at that page.

$panels->add([
  'panel' => 'collection',
  'title' => 'Clients',
  'data' => [
    'collection' => 'template=client, limit=10',
    'sortable' => true,
    'pagination' => true,
    'columns' => [
      'title' => 'Title',
      'url' => 'URL',
      'modified' => 'Modified',

      // Display "View All" button in footer
      'list' => 1184, // ID of lister page
    ]
  ]
]);

 

  • Like 1
  • Thanks 1

Share this post


Link to post
Share on other sites

Hi @d'Hinnisdaël , thanks for this module! I'm trying it out now and collecting a couple of suggestions. I have encountered two small-ish bugs so far:

On Firefox, I get a horizontal overflow in Firefox with the 'Shortcuts' panel in 'list' mode and 'small' size. Doesn't happen in Chrome.

1088570459_Screenshot2020-04-02at17_28_49.thumb.png.8f9dae1e3c7049083b3e6d0e550b89d7.png

The following CSS fixes it for me (even though I haven't checked if it has other unintended consequences yet):

.Dashboard__panel {
	max-width: 100%;
}

I'm also getting two warnings with the 'Collections' panel when I try to output some text from a Textareas field. Here's the input for the collection panel:

'columns' => [
  'title' => wire('fields')->get('title')->getLabel(),
  'c_campaign_parameters.utm_source' => 'Campaign source'
],

This results in warnings (even though the output still works):

1×    PHP Warning: class_parents(): Class InputfieldText does not exist and could not be loaded in .../FieldtypeTextareas.module:1071

1×    PHP Warning: in_array() expects parameter 2 to be array, bool given in .../FieldtypeTextareas.module:1072

I'm not sure if this is a bug in your module or in the Textareas field 🙂 Can you take a look? Thanks!

Share this post


Link to post
Share on other sites
1 hour ago, MoritzLost said:

On Firefox, I get a horizontal overflow in Firefox with the 'Shortcuts' panel in 'list' mode and 'small' size. Doesn't happen in Chrome.

Sure. Happy to merge your fix.

The other one seems to be an issue with the Textareas module. I hope 👽

The dashboard module uses PW's internal $page->getText() method to resolve the dot syntax field name:  $page->getText($markup, false, true) (where $markup would be 'c_campaign_parameters.utm_source') Haven't worked with the textarea module so far, but it either doesn't cast strings by default or it overwrites the getText method.

Suggested fix in your case: create a custom hook property that casts the textarea field into a string manually, and then use that property for display in the dashboard panel.

  • Like 1

Share this post


Link to post
Share on other sites

@d'Hinnisdaël Great, thanks for your support! I'll install the new version tomorrow, and I'll try your suggestions for the Textareas field 🙂

Share this post


Link to post
Share on other sites

Thanks for the update @d'Hinnisdaël, the new version fixes the issue 🙂

As for the warnings with the Textareas field, that was indeed a bug with the Textareas module. I fact, I encountered this bug a year ago and Ryan fixed it already. Now if only I'd remembered to actually use the updated module ... 😛 Thanks for your help!

Share this post


Link to post
Share on other sites

Hi @d'Hinnisdaël

First of all congrats to this beautiful module. I have some suggestions and remarks:

  1. The panels do not have proper dependencies set. All panels are installable (and throw an exception, when installed):
    UshLncZ.png
    IMHO the Dashboard master module should be the only installable module.
     
  2. https://philippdaun.github.io/processwire-dashboard/#/configuration?id=dashboard-as-entry-point
    Any reason why you chose this version over a module setting (eg checkbox) that adds a hook? 
    I was hoping that your way of doing it would solve the problem that when clicking "Save & Exit" one would be redirected to the dashboard. But still one gets to the page tree. This also happens when trashing a page. This is one thing annoying me for a long time, but I didn't try to find a solution for it yet. Maybe you can have a look, because imho when having a dashboard it's more likely that one wants to see the dashboard than the page tree 🙂 

    Edit: Just saw that changing the main admin page's process does at least help after trashing pages 🙂 I think I'll also redirect all user requests from the page tree to the dashboard...

     
  3. DashboardPanelChart uses jsdelivr CDN to load chart.js - this means that the panel will not work on offline applications (intranet). I think it would be better to ship chartjs with the module. This brings me to the next and more important point:
     
  4. Have you thought of making panels Inputfields?

 

The last point needs some more words 🙂 

I really wonder (not to say dislike) why you made the dasboard work on your own panel implementations rather than using regular PW Inputfields. Please don't take this as devaluation of your module, but after all it's just a ProcessModule like all the other admin pages (just really looking a lot better!).

I've created a very simple Inputfield and posted a thread in the tutorials section:

Take this screenshot of the Grid Dashboard demo:

XOnBJ8F.png

This is VERY similar to your Dashboard module - with the big difference that it is based on PW Inputfields that can be used everywhere in the PW ecosystem! Your panels can not. As I said your module does indeed look a lot better than a regular PW form. For example as far as I know grid spacing is not possible using InputfieldFieldset. Also the admin width settings are somewhat limited (see this old issue on github).

But this is my point: Instead of creating a new module that handles things in its own ways it would be a lot better to improve or extend the PW internal tools. This means we could either create nicer CSS for PW Inputfields (here the InputfieldFieldset) or we could create an Inputfield that wraps other inputfields in a Uikit grid (as Uikit is already on board). This approach would also make it possible to use the "panels" that you create for your dashboard in other places like PW page edit screens or in other ProcessModules.

I really like the look & feel of your panels, so it would be great to be able to use them all over the PW backend and not only in your module!

Thx for creating and sharing this - I hope you get my point and I'm looking forward to hearing what you think about converting panels to Inputfields 🙂 

  • Like 1

Share this post


Link to post
Share on other sites

Hi @bernhard, thanks for your feedback, really appreciated. There's a few things to unpack here:

Module dependencies

The panel modules need to inherit from an actual class from a separate PHP file which made things more difficult than I'd like to admit. So right now I'm happy it's working properly at all. I wouldn't dwell on this issue too long since all modules are within a single folder and the naming is quite obvious. Might revisit this in the future.

Exit on save

I'd always expect »Exit & Save« on a page edit form to get me back to the page tree, since that's the level above. I'm happy to make that configurable, though.

Admin home process

Can you think of a way to permanently and consistently re-route everything to the admin homepage instead of the page tree? And then still have the page tree clickable as a stand-alone view? That would be a better solution that the current one for sure. I've had a previous version that changes the admin parent's process manually and changes it back on uninstall, but that was buggy as hell and really scared me.

Asset CDN

Good point about the intranet. I'm really uncomfortable bundling dependencies in projects. There's something quite icky about it and using a CDN feels like sort of a happy middle ground, but your point is valid.

Panels as Inputfield

I get what you're saying about not re-inventing the wheel. I'm afraid I have to disagree here, though.

Input fields primarily serve the need to create complex forms, to arrange components for user input. In ProcessWire, it's become common to use them for everything under the sun since they're as close to a universal layout component as it gets. Might be a misnomer in hindsight, but I don't feel like every layout panel in the admin needs to be an input panel. It's useful for sure, but I don't see the need to have every container in the backend inherit from the base Inputfield class. They come with a lot of additional logic that doesn't apply to simple output panels, like the collapsing stuff and the conditional display logic.

For context, the initial version of the module was created the way you suggested, using ProcessWire's input fields and fieldsets. There was just no way to make them look nice and behave the way the module required. Laying them out in a grid with proper spacing and responsive sizing was plain horrible. You're not only fighting a hundred separate existing CSS rules for margins and outlines but ProcessWire's internal JS for collapsing/uncollapsing/calculating of field widths on top. One of the requirements for me was to have 'renderless' panels without border, background or margin to achieve floating panels for charts. Undoing all the internal inputfield styling just wasn't something I was comfortable spending my time on.

Out of curiosity: what's a possible scenario for re-using a dashboard panel in some other part of the admin?

 

 

  • Like 1

Share this post


Link to post
Share on other sites
2 hours ago, d'Hinnisdaël said:

Module dependencies

The panel modules need to inherit from an actual class from a separate PHP file which made things more difficult than I'd like to admit. So right now I'm happy it's working properly at all. I wouldn't dwell on this issue too long since all modules are within a single folder and the naming is quite obvious. Might revisit this in the future.

I've also had those problems, I know that it's not really straight forward and limiting sometimes...

2 hours ago, d'Hinnisdaël said:

Can you think of a way to permanently and consistently re-route everything to the admin homepage instead of the page tree? And then still have the page tree clickable as a stand-alone view? That would be a better solution that the current one for sure. I've had a previous version that changes the admin parent's process manually and changes it back on uninstall, but that was buggy as hell and really scared me.

At the moment I have this in place and need to test it over the next weeks 🙂

$this->addHookBefore('ProcessPageList::execute', $this, 'redirectPageList');

/**
 * Redirect all PageList requests to Dashboard
 */
public function redirectPageList(HookEvent $event) {
  if($this->config->ajax) return;
  if($this->page->id > 3) return;
  $this->session->redirect($this->pages->get('name=ear')->url);
}

Edit: Just added the page id check, then all requests to "pages" will be redirected but one can show the pagelist by going to "pages > tree" 🙂 

2 hours ago, d'Hinnisdaël said:

Panels as Inputfield

I get what you're saying about not re-inventing the wheel. I'm afraid I have to disagree here, though.

Input fields primarily serve the need to create complex forms, to arrange components for user input. In ProcessWire, it's become common to use them for everything under the sun since they're as close to a universal layout component as it gets. Might be a misnomer in hindsight, but I don't feel like every layout panel in the admin needs to be an input panel. It's useful for sure, but I don't see the need to have every container in the backend inherit from the base Inputfield class. They come with a lot of additional logic that doesn't apply to simple output panels, like the collapsing stuff and the conditional display logic.

I try to answer that by asking you a question 🙂 I have several custom Process Modules. They are great, because I can control where they live (menu) and who can see them (access control). How would I display one of your - I say it again - really nice looking dashboard panels in one of my modules?

2 hours ago, d'Hinnisdaël said:

For context, the initial version of the module was created the way you suggested, using ProcessWire's input fields and fieldsets. There was just no way to make them look nice and behave the way the module required. Laying them out in a grid with proper spacing and responsive sizing was plain horrible. You're not only fighting a hundred separate existing CSS rules for margins and outlines but ProcessWire's internal JS for collapsing/uncollapsing/calculating of field widths on top. One of the requirements for me was to have 'renderless' panels without border, background or margin to achieve floating panels for charts. Undoing all the internal inputfield styling just wasn't something I was comfortable spending my time on.

I've just added a commit to my example module: https://github.com/BernhardBaumrock/InputfieldChartDemo/commit/3efa4bd8355bfe6e7499254cad58e70d3f283147

jjY8vlE.png

US8picG.gif

IMHO this is really close to what you built on your dashboard (at least as far as I understood it until now), but it uses PW core features and only a little extra markup: https://github.com/BernhardBaumrock/InputfieldChartDemo/blob/3efa4bd8355bfe6e7499254cad58e70d3f283147/ProcessInputfieldChartDemo.module.php#L139-L146

I agree that it is not the nicest thing to layout pages using InputfieldForm elements, but I think it would be the better way to push PW in that regard than creating custom solutions. We all know the benefits of using existing components:

  • showIf would work out of the box
  • collapsing works out of the box (ajax loading fields)
  • development is the same for dashboard panels and regular inputfields
  • panels can be used everywhere
  • styling applies automatically (imagine a custom admin theme using your dashboard panel...

To name just a few 🙂 What I mean is for example we could have something like InputfieldGrid that could work like this:

$grid = $modules->get('InputfieldGrid');
$grid->addColumn([
  'class' => 'uk-width-1-4@m',
  'children' => [
    [
      'type' => 'markup',
      'label' => 'one foo',
      'value' => 'one bar',
    ],[
      'type' => 'markup',
      'label' => 'one foo',
      'value' => 'one bar',
    ],
  ],
]);
$grid->addColumn([
  'class' => 'uk-width-3-4@m',
  'children' => [
    [
      'type' => 'markup',
      'label' => 'two foo',
      'value' => 'two bar',
    ],[
      'type' => 'markup',
      'label' => 'two foo',
      'value' => 'two bar',
    ],
  ],
]);
$grid->render();

That would be really easy to build and could - same as everything else - also be used on page edit screens etc.

 

2 hours ago, d'Hinnisdaël said:

Out of curiosity: what's a possible scenario for re-using a dashboard panel in some other part of the admin?

Scenario from todays work: I'm building a custom CRM for myself where I manage invoices and documents. After import they get flagged as TODO. Then I see them on the Dashboard:

f4mMgkY.png

When editing one of those pages I have basically the same Inputfield showing a list of all other todos:

UtnZYFf.png

 

Share this post


Link to post
Share on other sites
On 4/3/2020 at 11:59 AM, bernhard said:

I was hoping that your way of doing it would solve the problem that when clicking "Save & Exit" one would be redirected to the dashboard. But still one gets to the page tree. This also happens when trashing a page. This is one thing annoying me for a long time, but I didn't try to find a solution for it yet.

You can use a hook to redirect after "Save & Exit":

// the hook in a location like _init.php or in a module's init function
$this->addHookBefore('ProcessPageEdit::processSaveRedirect', $this, 'redirectAfterSave');

/**
   * redirects to the main ListerPro "Raumdatenblätter" after saving a page with template raum
   * @param HookEvent $event
   * @throws WireException
   * @throws WirePermissionException
   */
  public function redirectAfterSave(HookEvent $event)
  {
    $url = $event->arguments(0);
    $page = $event->object->getPage();
    if ($page->template == "raum" && !$page->isTrash()) {
      if ($url == "../") {
        $goto = wire("pages")->get('/raumdatenblatt/raumdatenblaetter/')->url;
        $event->arguments = array($goto);
      }
    }
  }

 

  • Like 2

Share this post


Link to post
Share on other sites

There is also a config setting for the adminRootPageID, but I would not recommend to change it, as a config comment states: "Values in this section are not meant to be changed". And some modules even use this setting, to find a subpage, for example PageLister Pro, which then would not work as expected anymore:

$admin = $this->wire('pages')->get($this->wire('config')->adminRootPageID);
$parent = $admin->child('name=page, include=all');

 

Share this post


Link to post
Share on other sites
22 hours ago, bernhard said:

At the moment I have this in place and need to test it over the next weeks 🙂

  Looks great! Let me know how it's faring and I'm happy to use that instead of the page's process setting.

22 hours ago, bernhard said:

I agree that it is not the nicest thing to layout pages using InputfieldForm elements, but I think it would be the better way to push PW in that regard than creating custom solutions. We all know the benefits of using existing components.

You're doing a good job convincing me here. It does make sense conceptually and thinking about the module ecosystem as a whole. That said, the module is currently at a point where I'm not missing much in terms of functionality and am not that keen on re-writing the whole output layer with no new features to show for it. And it's not like I have the time, with everybody currently wanting to expand their online stores... If anything, I'd put that on the list for version 1.0 as a summer/fall project since it'd be a breaking change either way. If you definitely need this and need it soon, I'm happy to accept a pull request.

Quote

How would I display one of your - I say it again - really nice looking dashboard panels in one of my modules?

But why would you want to re-use a dashboard panel in another module? That doesn't make sense to me. The way I see a dashboard working is the other way around: it displays a condensed form of information found elsewhere, e.g. shortcuts from all possible admin views, a single chart from a whole host of data, the most recent news pages from a whole archive of them, and so on. If anything, you'd re-use a fieldset from one of your modules in the dashboard. Using markup from an existing module in a dashboard panel is working just fine — with the exception of granular access control and conditional visibility. Which to me seem minor but might be a deal-breaker for more corporate-y types of applications.

  • Like 2

Share this post


Link to post
Share on other sites

Would you consider adding an insert action to the collection panel?  That way people can add children?

I love this! Thank you for releasing it!

Share this post


Link to post
Share on other sites
23 hours ago, joer80 said:

Would you consider adding an insert action to the collection panel?  That way people can add children?

The collection panel does allow for an ›Add New‹ button. It's just not documented at the moment.

You can either specify the child page's template or the parent page and it'll figure it out. For the template option to work, the child template must have a default parent defined. This should work:

$panels->add([
  'panel' => 'collection',
  'title' => 'Widgets',
  'data' => [
    'collection' => 'template=widget, limit=6',

    // Option A: Add to child template's defined parent page
    'template' => 'widget',

    // Option B: Add to specific parent page (page, ID or selector)
    'parent' => 'template=widget-list',
  ]
]);

 

  • Like 2

Share this post


Link to post
Share on other sites
16 minutes ago, d'Hinnisdaël said:

The collection panel does allow for an ›Add New‹ button. It's just not documented at the moment.

You can either specify the child page's template or the parent page and it'll figure it out. For the template option to work, the child template must have a default parent defined. This should work:


$panels->add([
  'panel' => 'collection',
  'title' => 'Widgets',
  'data' => [
    'collection' => 'template=widget, limit=6',

    // Option A: Add to child template's defined parent page
    'template' => 'widget',

    // Option B: Add to specific parent page (page, ID or selector)
    'parent' => 'template=widget-list',
  ]
]);

 

This is great!

Thanks!

Share this post


Link to post
Share on other sites

This is a nice module and I've added a number of panels successfully. However, I have a problem with the chart panel. My code is below (the data is just a test and will be replaced by integer variables):

    $reports->add([
        'panel' => 'chart',
        'title' => 'Contact bookings for ' . $property->title,
        'data' => [
            'chart' => [
                'type' => 'bar',
                'data' => [
                    'labels' => [4, 6],
                    'datasets' => [
                        'label' => 'count',
                        'data' => [1, 1],
                    ],
                ],
            ],
        ]
    ]);

I get a js error: 

DashboardPanelChart.js?v=0.6.14:121 Uncaught TypeError: e.data.datasets.forEach is not a function
    at Object.beforeUpdate (DashboardPanelChart.js?v=0.6.14:121)
    at Object.notify (chart.js@2.9.3:7)
    at Qe.update (chart.js@2.9.3:7)
    at Qe.construct (chart.js@2.9.3:7)
    at new Qe (chart.js@2.9.3:7)
    at n (DashboardPanelChart.js?v=0.6.14:123)
    at HTMLCanvasElement.<anonymous> (DashboardPanelChart.js?v=0.6.14:123)
    at Function.each (JqueryCore.js?v=1585265024:2)
    at init.each (JqueryCore.js?v=1585265024:2)
    at c (DashboardPanelChart.js?v=0.6.14:123)

 

Share this post


Link to post
Share on other sites
11 hours ago, MarkE said:

However, I have a problem with the chart panel. My code is below (the data is just a test and will be replaced by integer variables)

Chart.js expects an array at datasets, even if you just use a single one. It'll work once you wrap that in brackets again.

  • Like 1

Share this post


Link to post
Share on other sites
10 hours ago, d'Hinnisdaël said:

Chart.js expects an array at datasets, even if you just use a single one.

Many thanks - didn't spot that!

Share this post


Link to post
Share on other sites

Hi @d'Hinnisdaël, I have a couple more suggestions for the Shortcuts & Collection panels, hope you don't mind 🙂

Shortcuts: Warnings with array syntax
The documentation suggests this syntax for a shortcut with a custom icon (but without a summary):
[304, 'user'],                 // Override icon
This currently throws a warning because of this line which expects three array elements. Here's a quick fix to allow passing only the title, or the title and an icon:

list($shortcut, $icon, $summary) = array_pad($shortcut, 3, '');

Shortcuts: Summary should be removable
I would like to see an panel-wide option to not display a summary for any of the shortcuts. Currently the only way to remove the summary is to use the array syntax (see above). At least for my use-case, I don't really need the summaries and the default summaries are at best confusing, so I need to use the array syntax for every item.

Collection: Default to field label for headlines
Almost all the column definitions in my collection panel look like this:

'title' => wire('fields')->get('title')->getLabel(),

This is a minor nitpick and I appreciate the option to set a custom headline, but I feel like in most cases the field label (of the field the column displays) would be a sensible default for the headline. I think it would be a good idea to support a field-only syntax for the columns, where I only need to specificy a field and the headline gets automatically populated with the field label.

Again, thanks for the great module!

Share this post


Link to post
Share on other sites
On 5/4/2020 at 5:08 PM, MoritzLost said:

Hi @d'Hinnisdaël, I have a couple more suggestions for the Shortcuts & Collection panels, hope you don't mind 🙂

All of these are good points, actually. I'm surprised I missed the default field label thing, since it's kind of the standard behavior in most core modules and especially useful in multi-language environments. I'm currently short on time, but will tackle these as soon as things settle down.

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 David Karich
      ProcessWire InputfieldRepeaterMatrixDuplicate
      Thanks to the great ProModule "RepeaterMatrix" I have the possibility to create complex repeater items. With it I have created a quite powerful page builder. Many different content modules, with many more possible design options. The RepeaterMatrix module supports the cloning of items, but only within the same page. Now I often have the case that very design-intensive pages and items are created. If you want to use a content module on a different page (e.g. in the same design), you have to rebuild each item manually every time.
      This module extends the commercial ProModule "RepeaterMatrix" by the function to duplicate repeater items from one page to another page. The condition is that the target field is the same matrix field from which the item is duplicated. This module is currently understood as proof of concept. There are a few limitations that need to be considered. The intention of the module is that this functionality is integrated into the core of RepeaterMatrix and does not require an extra module.
      Check out the screencast
      What the module can do
      Duplicate multible repeater items from one page to another No matter how complex the item is Full support for file and image fields Multilingual support Support of Min and Max settings Live synchronization of clipboard between multiple browser tabs. Copy an item and simply switch the browser tab to the target page and you will immediately see the past button Support of multiple RepeaterMatrix fields on one page Configurable which roles and fields are excluded Configurable dialogs for copy and paste Duplicated items are automatically pasted to the end of the target field and set to hidden status so that changes are not directly published Automatic clipboard update when other items are picked Automatically removes old clipboard data if it is not pasted within 6 hours Delete clipboard itself by clicking the selected item again Benefit: unbelievably fast workflow and content replication What the module can't do
      Before an item can be duplicated in its current version, the source page must be saved. This means that if you make changes to an item and copy this, the old saved state will be duplicated Dynamic loading is currently not possible. Means no AJAX. When pasting, the target page is saved completely No support for nested repeater items. Currently only first level items can be duplicated. Means a repeater field in a repeater field cannot be duplicated. Workaround: simply duplicate the parent item Dynamic reloading and adding of repeater items cannot be registered. Several interfaces and events from the core are missing. The initialization occurs only once after the page load event Changelog
      2.0.0
      Feature: Copy multiple items at once! The fundament for copying multiple items was created by @Autofahrn - THX! Feature: Optionally you can disable the copy and/or paste dialog Bug fix: A fix suggestion when additional and normal repeater fields are present was contributed by @joshua - THX! 1.0.4
      Bug fix: Various bug fixes and improvements in live synchronization Bug fix: Items are no longer inserted when the normal save button is clicked. Only when the past button is explicitly clicked Feature: Support of multiple repeater fields in one page Feature: Support of repeater Min/Max settings Feature: Configurable roles and fields Enhancement: Improved clipboard management Enhancement: Documentation improvement Enhancement: Corrected few typos #1 1.0.3
      Feature: Live synchronization Enhancement: Load the module only in the backend Enhancement: Documentation improvement 1.0.2
      Bug fix: Various bug fixes and improvements in JS functions Enhancement: Documentation improvement Enhancement: Corrected few typos 1.0.1
      Bug fix: Various bug fixes and improvements in the duplication process 1.0.0
      Initial release Support this module
      If this module is useful for you, I am very thankful for your small donation: Donate 5,- Euro (via PayPal – or an amount of your choice. Thank you!)
      Download this module (Version 2.0.0)
      > Github: https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate
      > PW module directory: https://modules.processwire.com/modules/inputfield-repeater-matrix-duplicate/
      > Old stable version (1.0.4): https://github.com/FlipZoomMedia/InputfieldRepeaterMatrixDuplicate/releases/tag/1.0.4
    • By Robin S
      A new module that hasn't had a lot of testing yet. Please do your own testing before deploying on any production website.
      Custom Paths
      Allows any page to have a custom path/URL.
      Note: Custom Paths is incompatible with the core LanguageSupportPageNames module. I have no experience working with LanguageSupportPageNames or multi-language sites in general so I'm not in a position to work out if a fix is possible. If anyone with multi-language experience can contribute a fix it would be much appreciated!
      Screenshot

      Usage
      The module creates a field named custom_path on install. Add the custom_path field to the template of any page you want to set a custom path for. Whatever path is entered into this field determines the path and URL of the page ($page->path and $page->url). Page numbers and URL segments are supported if these are enabled for the template, and previous custom paths are managed by PagePathHistory if that module is installed.
      The custom_path field appears on the Settings tab in Page Edit by default but there is an option in the module configuration to disable this if you want to position the field among the other template fields.
      If the custom_path field is populated for a page it should be a path that is relative to the site root and that starts with a forward slash. The module prevents the same custom path being set for more than one page.
      The custom_path value takes precedence over any ProcessWire path. You can even override the Home page by setting a custom path of "/" for a page.
      It is highly recommended to set access controls on the custom_path field so that only privileged roles can edit it: superuser-only is recommended.
      It is up to the user to set and maintain suitable custom paths for any pages where the module is in use. Make sure your custom paths are compatible with ProcessWire's $config and .htaccess settings, and if you are basing the custom path on the names of parent pages you will probably want to have a strategy for updating custom paths if parent pages are renamed or moved.
      Example hooks to Pages::saveReady
      You might want to use a Pages::saveReady hook to automatically set the custom path for some pages. Below are a couple of examples.
      1. In this example the start of the custom path is fixed but the end of the path will update dynamically according to the name of the page:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'my_template') { $page->custom_path = "/some-custom/path-segments/$page->name/"; } }); 2. The Custom Paths module adds a new Page::realPath method/property that can be used to get the "real" ProcessWire path to a page that might have a custom path set. In this example the custom path for news items is derived from the real ProcessWire path but a parent named "news-items" is removed:
      $pages->addHookAfter('saveReady', function(HookEvent $event) { $page = $event->arguments(0); if($page->template == 'news_item') { $page->custom_path = str_replace('/news-items/', '/', $page->realPath); } }); Caveats
      The custom paths will be used automatically for links created in CKEditor fields, but if you have the "link abstraction" option enabled for CKEditor fields (Details > Markup/HTML (Content Type) > HTML Options) then you will see notices from MarkupQA warning you that it is unable to resolve the links.
      Installation
      Install the Custom Paths module.
      Uninstallation
      The custom_path field is not automatically deleted when the module is uninstalled. You can delete it manually if the field is no longer needed.
       
      https://github.com/Toutouwai/CustomPaths
      https://modules.processwire.com/modules/custom-paths/
    • By teppo
      Hey folks!
      I'm happy to finally introduce a project I've been working on for quite a while now: it's called Wireframe, and it is an output framework for ProcessWire.
      Note that I'm posting this in the module development area, maily because this project is still in rather early stage. I've built a couple of sites with it myself, and parts of the codebase have been powering some pretty big and complex sites for many years now, but this should still be considered a soft launch 🙂
      --
      Long story short, Wireframe is a module that provides the "backbone" for building sites (and apps) with ProcessWire using an MVC (or perhaps MVVM... one of those three or four letter acronyms anyway) inspired methodology. You could say that it's an output strategy, but I prefer the term "output framework", since in my mind the word "strategy" means something less tangible. A way of doing things, rather than a tool that actually does things.
      Wireframe (the module) provides a basic implementation for some familiar MVC concepts, such as Controllers and a View layer – the latter of which consists of layouts, partials, and template-specific views. There's no "model" layer, since in this context ProcessWire is the model. As a module Wireframe is actually quite simple – not even nearly the biggest one I've built – but there's still quite a bit of stuff to "get", so I've put together a demo & documentation site for it at https://wireframe-framework.com/.
      In addition to the core module, I'm also working on a couple of site profiles based on it. My current idea is actually to keep the module very light-weight, and implement most of the "opinionated" stuff in site profiles and/or companion modules. For an example MarkupMenu (which I released a while ago) was developed as one of those "companion modules" when I needed a menu module to use on the site profiles.
      Currently there are two public site profiles based on Wireframe:
      site-wireframe-docs is the demo&docs site mentioned above, just with placeholder content replaced with placeholder content. It's not a particularly complex site, but I believe it's still a pretty nice way to dig into the Wireframe module. site-wireframe-boilerplate is a boilerplate (or starter) site profile based on the docs site. This is still very much a work in progress, but essentially I'm trying to build a flexible yet full-featured starter profile you can just grab and start building upon. There will be a proper build process for resources, it will include most of the basic features one tends to need from site to site, etc. --
      Requirements and getting started:
      Wireframe can be installed just like any ProcessWire module. Just clone or download it to your site/modules/ directory and install. It doesn't, though, do a whole lot of stuff on itself – please check out the documentation site for a step-by-step guide on setting up the directory structure, adding the "bootstrap file", etc. You may find it easier to install one of the site profiles mentioned above, but note that this process involves the use of Composer. In the case of the site profiles you can install ProcessWire as usual and download or clone the site profile directory into your setup, but after that you should run "composer install" to get all the dependencies – including the Wireframe module – in place. Hard requirements for Wireframe are ProcessWire 3.0.112 and PHP 7.1+. The codebase is authored with current PHP versions in mind, and while running it on 7.0 may be possible, anything below that definitely won't work. A feature I added just today to the Wireframe module is that in case ProcessWire has write access to your site/templates/ directory, you can use the module settings screen to create the expected directories automatically. Currently that's all, and the module won't – for an example – create Controllers or layouts for you, so you should check out the site profiles for examples on these. (I'm probably going to include some additional helper features in the near future.)
      --
      This project is loosely based on an earlier project called pw-mvc, i.e. the main concepts (such as Controllers and the View layer) are very similar. That being said, Wireframe is a major upgrade in terms of both functionality and architecture: namespaces and autoloader support are now baked in, the codebase requires PHP 7, Controllers are classes extending \Wireframe\Controller (instead of regular "flat" PHP files), implementation based on a module instead of a collection of drop-in files, etc.
      While Wireframe is indeed still in a relatively early stage (0.3.0 was launched today, in case version numbers matter) for the most part I'm happy with the way it works, and likely won't change it too drastically anytime soon – so feel free to give it a try, and if you do, please let me know how it went. I will continue building upon this project, and I am also constantly working on various side projects, such as the site profiles and a few unannounced helper modules.
      I should probably add that while Wireframe is not hard to use, it is more geared towards those interested in "software development" type methodology. With future updates to the module, the site profiles, and the docs I hope to lower the learning curve, but certain level of "developer focus" will remain. Although of course the optimal outcome would be if I could use this project to lure more folks towards that end of the spectrum... 🙂
      --
      Please let me know what you think – and thanks in advance!
    • 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. There are 4 different view modes.
      View mode "Day" 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. View mode "Month" shows the total of all visitors per day from the first to the last day of the selected month. View mode "Year" shows the total of all visitors per month from the first to the last month of the selected year. View mode "Total" shows the total of all visitors per year for all recorded years. Please note that multiple visits from the same IP address within the selected period are counted as a single visitor.
      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.
      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 (-).
       
    • By MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
×
×
  • Create New...