Jump to content

Recommended Posts

15 hours ago, tpr said:

I think the admin UI could be re-arranged into a table layout:

  • first column: action names
  • second column: description/notes
  • third column: applied roles + and Edit button, that opens a modal or perhaps only unhides the role asmSelector. Alternatively you can set the asmSelect to operate in "inline" mode, I've experimented with that and it worked.

I know it would take some time, but sooner or later this has to be done :)

 

You like to keep me busy don't you :)

How's this?

Screen Shot 2016-12-21 at 4.26.13 PM.png

That along with a few tweaks/fixes has been committed.

Don't forget to fork and contribute :)

  • Like 5
Link to post
Share on other sites

Here are is a SCSS snippet if you would like to use inline roles (I'm not liking those big green asm items). It also enables removing roles by clicking on its label (not only on its icon), "user" icon instead trash and there's a line-through effect on hover too. You can use an online tool to make CSS from it.

Spoiler

table.adminactionsconfig {
  .Inputfield[id^="wrap_"] {
    background: transparent !important;
  }
  .InputfieldContent, label {
    padding: 0.25em 0.25em 0 !important;
    border: none !important;
    background: transparent !important;
  }
  .asmList {
    margin-top: 0.25em !important;
  }
  .asmListItem {
    padding-left: 8px !important;
    margin-right: 8px;
    display: inline-block !important;
    width: auto !important;
    font-size: 14px;
    background: transparent !important;
    border-color: transparent !important;
    color: inherit !important;
    &:hover {
      .asmListItemLabel {
        text-decoration: line-through !important;
      }
    }
    .asmListItemRemove {
      left: 0 !important;
      right: 0 !important;
      bottom: 0;
      top: 1px;
      &:not(:hover) {
        i {
          &:before {
            content: '\f007';
          }
        }
      }
    }
    i {
      margin-left: 2px;
      &:not(:hover) {
        color: #EA2262;
      }
    }
  }
}

 

 

adminactions-roles.gif

  • Like 3
Link to post
Share on other sites

Thanks @tpr - I have implemented that, although I was a little hesitant. I certainly like the look, but I was worried about the consistency of the interface compared to what we're used to with ASM Selects. Curious why you haven't done this for the roles settings in AOS?

Link to post
Share on other sites

Thanks! Good question - actually I haven't thought about that before your question. Perhaps because I didn't know that asmSelects can be used without the sort feature (although there's no need for that in AOS at all).

Link to post
Share on other sites

The latest AOS contains this tweaked role selector appearance. Thanks for the tip! :)

The only difference is that I use the "user" icon even on hover, I think the line-through is enough signal for the removal.

Link to post
Share on other sites

Merry Christmas, @adrian!

Want to try to use your action module in a slightly different way. I need to be able to execute actions from outside of PW (from emails). I am planning to solve this task kind of like in this module: I will have a page for each callable-from-outside action with some random security string and some options.

But I want to try to make it a little more customizable. I plan to write new actions for Admin Actions module, call them from API like you said it is possible to and pass options stored in some field of the callable-from-outside action page.

Do you see any caveats? Can you suggest a field to store options? Is there a way to turn off auto-backup feature (at least for the from-API usage or by configuration)?

  • Like 1
Link to post
Share on other sites

Hi @Ivan Gretsky

I think I would store the options in a textarea in json format so you can easily convert to an array to pass to the action via the API call.

Are you planning on having the security string in the link from the email and handling the authentication in the logic on your pages? 

Currently the automatic backup can't be turned off, but I agree that this should be possible. I'll do it as a configurable option and also add an option to turn it off via an API call.

Let me know if you come across any issues once you start setting this up and I'll see what I can do to make AdminActions work as needed for you.

  • Like 2
Link to post
Share on other sites

I did already managed to write a simple action and launch it via the API. I am currently going with a json in a textarea (but also looking at this field).

  1. Mandatory backup is problem 1.
  2. I had to give admin-action permission to the guest user. Not sure how dangerous is that. Is there a way to get around it?
  3. I am planning to have some security string stored in a dedicated field on the callable-from-outside action page which the token input value will have to match. Is there anything else you recommend?
  4. Not sure what you mean under handling authentication. Currently the script is running from the guest user.
Link to post
Share on other sites

Hi @Ivan Gretsky - I've added some options for controlling the automatic backup (not committed yet) and I am thinking about the guest user access for making calls to actions via the API. I am considering a couple of different options and will put together something in the next couple of days. Hope that works for your timeframe?

 

  • Like 1
Link to post
Share on other sites

Hi @Ivan Gretsky - ok, a new version has been committed that adds a new module config setting for determining whether database backups will be automatic, optional, or disabled.

1) Automatic - database backup will happen without user intervention.

2) Optional - adds a new checkbox at the bottom of every action's "options" form before the user clicks "Execute Action". 

3) Disabled - this means no database backup will occur.

If you do want to do a backup when calling an action via the API, simply add a new item to the options array: 

'dbBackup' => true

 

I am still working on figuring out the best approach for guest access. The biggest problem I see is that adding the "admin-actions" permission to the guest role means that any logged in user can now see the Setup > Admin Actions menu, even though they don't have permission to view or execute any of the actions.

I have been playing around with adding a new helper module to handle the API calls, rather than calling the main ProcessAdminActions module directly, but there are a couple of inheritance issues I am not thrilled about, so looking into other options. Will hopefully have a good solution soon.

Please let me know if the backup side of things handles your needs on that front.

 

  • Like 3
Link to post
Share on other sites

Hi everyone,

I have committed a new version that takes care of @Ivan Gretsky's issues with guest access for calling actions via the API.

The new version also includes the ability to add actions to the Setup > Admin Actions submenu which could be really handy for quick access to key actions that you use regularly. At the moment you could add them all if you want, but perhaps in the future we'll have too many to make this usable, which is why I have made these configurable.

Screen Shot 2017-01-02 at 7.52.53 AM.png

 

See the new "In Menu" column:

Screen Shot 2017-01-02 at 7.53.40 AM.png

  • Like 6
Link to post
Share on other sites

Thank you @adrian! It is amazing to watch something being created with such an amazing pace by people like you and ryan. And so much to learn from. I recommend everybody to go through these guys' code to learn how you can be really powerful using ProcessWire.

Another little idea. Not sure it is necessary, but seems logical to me to separate "core" actions and those specific to the site. Like core ans site modules. I can see this module to be a base to easily create little things that would other way need their own process modules. In that case, most of the time I would use only custom actions... A filter option or a tab. What do you think?

I know, that for everybody but admin I can achieve about the same with by-action role assignment. But as I almost always login a superuser myself...

  • Like 4
Link to post
Share on other sites
6 hours ago, Martijn Geerts said:

Just to chime in: Fantastic Module @adrian

Thanks @Martijn Geerts - glad you're finding it useful - I appreciate the feedback!

 

20 hours ago, Ivan Gretsky said:

Another little idea. Not sure it is necessary, but seems logical to me to separate "core" actions and those specific to the site. Like core ans site modules. I can see this module to be a base to easily create little things that would other way need their own process modules. In that case, most of the time I would use only custom actions... A filter option or a tab. What do you think?

Hi @Ivan Gretsky - just to clarify - are you talking about simply separating the "core" actions in the module's "action" folder from those "site specific" ones in the /site/templates/AdminActions/ folder?

I think tabs sounds like a good approach - I'll take a look at doing that. Also something else to consider is the tables filter feature of @tpr's awesome AOS module - that will make finding actions nicer once there are lots more, although to be honest sometimes I just like good old CTRL/CMD + F :)

 

20 hours ago, Ivan Gretsky said:

I know, that for everybody but admin I can achieve about the same with by-action role assignment. But as I almost always login a superuser myself...

Just an FYI - if you don't want certain/any core actions available, you can remove the superuser role from those actions and they won't clog up your list of actions.

  • Like 1
Link to post
Share on other sites

How about letting a dedicated AdminActions.module handle all the serious work (e.g. like WireActions), so actions are also triggerable via the api? I can imagine that some actions might be useful to be run as part of a migration (shameless plug :D) and not just via the backend.

  • Like 1
Link to post
Share on other sites
22 hours ago, LostKobrakai said:

How about letting a dedicated AdminActions.module handle all the serious work (e.g. like WireActions), so actions are also triggerable via the api? I can imagine that some actions might be useful to be run as part of a migration (shameless plug :D) and not just via the backend.

 

They are already triggerable via the API: 

$options = array(
   'field' => 99, 
   'sourcePage' => 1131, 
   'destinationPage' => 1132
);
$modules->get("ProcessAdminActions")->CopyFieldContentToOtherPage($options);

I did think about separating into a core AdminActions.module and then have the ProcessAdminActions.module run on top of that, but went for the self-contained approach.

Let me know if this doesn't suit your needs though and I can revisit separating them out.

Link to post
Share on other sites
On 1/2/2017 at 11:01 AM, Ivan Gretsky said:

Another little idea. Not sure it is necessary, but seems logical to me to separate "core" actions and those specific to the site.

Hi @Ivan Gretsky - I have implemented this - now both the modules settings and the Setup > AdminActions are split into "Site" and "Core" tabs. I haven't committed just yet. I will PM you the new version. Would appreciate it if you could test and let me know if it suits your needs and if you find any problems.

Thanks!

  • Like 2
Link to post
Share on other sites

@Ivan Gretsky - I ended up doing some more tweaking on this and decided to commit it so you can get the new version from the modules directory now. Here's a screenshot of the tabs in action:

Screen Shot 2017-01-06 at 10.57.11 PM.png

 

I have also added a new: FTP Files to Page action based on this request: 

It works with files and images and looks like this:

Screen Shot 2017-01-06 at 6.57.31 PM.png

  • Like 2
Link to post
Share on other sites

@adrian, I know function names are case-insensitive, but maybe you could change this line  from

 $destinationPage->$fieldName->add($item->getPathName());

to...

 $destinationPage->$fieldName->add($item->getPathname());// @note: lower 'n' in getPathname

to match what's in the docs...Just me being silly.:)

  • Like 1
Link to post
Share on other sites

Thanks @kongondo - I was PHP was strict on function name case!

I think I inadvertently copied the case of $fieldName through to the getPathname() method.

Anyway, it's fixed in the latest version - thanks for noticing and pointing it out.

  • Like 1
Link to post
Share on other sites

Just added a new "Email Batcher" action, which has the following features:

  • Select recipients by user role, or using a pages selector for any pages on the site
  • Parsing of field tags in the body so you can do something like: Dear {first_name}
  • Option to send a test email
  • HTML body, with automated text only version also sent
  • Special {fromEmail} and {adminUrl} tags.
  • Ability to hook EmailBatcher::parseBody to apply other custom replacements

Don't forget TracyDebugger's Mail panel when testing - it will capture the outgoing emails (so they won't actually be sent):
http://processwire.com/blog/posts/introducing-tracy-debugger/#mail-panel

joxi_screenshot_1484004786187.png

 

 

 

  • Like 4
Link to post
Share on other sites

Another quick update. Both the new "Copy Repeater Items To Other Page" and "Copy Table Field Rows To Other Page" actions now include an optional selector so you can define what repeater items / table rows will be copied.

 

  • Like 5
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...