Jump to content
adrian

Admin Actions

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

Share this post


Link to post
Share on other sites

Looks really sharp!  I'll print a screenshot and put it under the Christmas tree :)

One thing though. Doesn't cook coffee :)

  • Like 1

Share this post


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

Share this post


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?

Share this post


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).

Share this post


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.

Share this post


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

Share this post


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

Share this post


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.

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


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.

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


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

Share this post


Link to post
Share on other sites

Just added a new "Copy Repeater Items To Other Page" action.

It lets you append or overwrite items from a repeater on one page to one on another.

  • Like 2

Share this post


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

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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...