tpr

AdminOnSteroids

Recommended Posts

I don't have ListerPro but I can add this line if you say it fixes it. I've searched for 100% width in AOS but it seems that it's coming from ListerPro, right?

  • Like 1

Share this post


Link to post
Share on other sites
5 minutes ago, tpr said:

I've searched for 100% width in AOS but it seems that it's coming from ListerPro, right?

Yes, the full rule is...

#ProcessListerResults select, #ProcessListerResults textarea, #ProcessListerResults input[type="url"], #ProcessListerResults input[type="email"], #ProcessListerResults input[type="text"] {
    width: 100%;
}

...in ProcessPageListerPro.css

So you could override that specific rule or use a more generic rule like in my previous post to try and force the filterbox input to always be width:auto - whichever you think best. Thanks.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, I've added width: auto to the CSS (no version change).

  • Like 2

Share this post


Link to post
Share on other sites

Hi @tpr, would it be possible to get the field edit links that show on hovering a field label to work on fields that are inside repeater items?

Ooh, and another idea re: field edit links. What if Ctrl-click brought up the settings for the field in the template context? (i.e. the template overrides)

Edit: one more thing...

The "Configure" anchor links in the Submodules panel do not scroll me to the right options panel, but scroll down quite a bit further. Tested in Firefox and Chrome on Windows.

2017-03-02_111131.png.4ce64634529330936de7ef2d95b313e9.png

  • Like 1

Share this post


Link to post
Share on other sites

No issues here with the scroll (Chrome/FF).

I have plans to modify the field edit link tooltip, then I'll try to make them work in repeaters too, and perhaps add a template context feature too.

  • Like 3

Share this post


Link to post
Share on other sites
16 minutes ago, tpr said:

No issues here with the scroll (Chrome/FF).

I have tracked the issue down to the "Tooltips" submodule - when this submodule is disabled the Configure anchor links scroll to the wrong place (in the default Admin theme anyway).

BTW, have been meaning to ask this for a while: is it possible to use the "Restore settings on next install" feature to copy AOS settings from one site to another? Or some other way to quickly replicate AOS settings on another site?

Share this post


Link to post
Share on other sites

Thanks, will check it.

Yes, you can copy the settings.php file to the new site, but first check the checkbox and save AOS, then uninstall, and only then copy it over. Then if you install the old settings should be loaded.

A better method that I use recently is the Module Toolkit module where you can export modules with their settings to the new site. There's a JSON copy to clipboard option so all you need is copy-paste that. Modules are re-downloaded from the modules directory so core modules are not supported atm but it's still an incredible time saver.

  • Like 1

Share this post


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

Yes, you can copy the settings.php file to the new site, but first check the checkbox and save AOS, then uninstall, and only then copy it over.

Okay, thanks for the info. It would be neat if there was a feature allowing to export/import (copy/paste) the settings JSON without needing to uninstall/reinstall. As new AOS features are rolled out quite regularly (which is awesome) I often want to synchronise my new settings across many sites.

Share this post


Link to post
Share on other sites
Just now, Robin S said:

Okay, thanks for the info. It would be neat if there was a feature allowing to export/import the settings JSON without needing to uninstall/reinstall. As new AOS features are rolled out quite regularly (which is awesome) I often want to synchronise my new settings across many sites.

Like  this?

 

  • Like 3

Share this post


Link to post
Share on other sites
3 minutes ago, adrian said:

Like  this?

Yes! I had forgotten about your thread there. That is still a work in progress and not released yet, right, or did I miss it? I think AOS and Tracy are the main modules where I find myself wanting a quick way to sync settings, but would definitely be cool to have that available for any module.

Share this post


Link to post
Share on other sites
7 minutes ago, Robin S said:

Yes! I had forgotten about your thread there. That is still a work in progress and not released yet, right, or did I miss it? I think AOS and Tracy are the main modules where I find myself wanting a quick way to sync settings, but would definitely be cool to have that available for any module.

It's fully functional. I'll PM it to you to try out. I'd be curious to get your feedback, and then maybe I'll just release it, maybe on its own, or maybe packaged with Module Toolkit, along with core module support to address @tpr's request.

  • Like 1

Share this post


Link to post
Share on other sites

Hey @tpr - FYI with the new Pages > Tree functionality that Ryan just committed. AOS is resulting in this:

58c0395e5cd34_ScreenShot2017-03-08at9_02_24AM.png.95e77b4f8b57213b63cb0386589aa7df.png

Share this post


Link to post
Share on other sites

Thanks, it's mostly PageList IDs that is causing this and perhaps PageListThumbs. I'll check it soon.

  • Like 1

Share this post


Link to post
Share on other sites

Seems like the "class" attribute is the culprit, I guess there's some regex going on later somewhere but  haven't checked.

Could you try replacing this line with this? It seems to fix the issue in all 3 themes.

$event->return = "<span data-pid='$page->id'>$markup</span>";

 

  • Like 1

Share this post


Link to post
Share on other sites
5 hours ago, tpr said:

Seems like the "class" attribute is the culprit, I guess there's some regex going on later somewhere but  haven't checked.

Could you try replacing this line with this? It seems to fix the issue in all 3 themes.


$event->return = "<span data-pid='$page->id'>$markup</span>";

 

Works for me!

  • Like 1

Share this post


Link to post
Share on other sites

FYI - there are still some issues with the new tree submenus - some unpublished pages just appear blank. Note "Resources" is blank:

58c2f296db0dc_ScreenShot2017-03-10at10_37_38AM.png.2f257adcd14a9b1cd062dc422aeeca5e.png

If you can't reproduce, let me know and I'll see if I can figure out why it's only some unpublished pages that are doing this.

Share this post


Link to post
Share on other sites

It seems to be the "double span" issue again. Could you try replacing the same line as in my post above with this:

$event->return = str_replace('<span ', '<span data-pid="' . $page->id . '" ', $event->return);

 

  • Like 1

Share this post


Link to post
Share on other sites
55 minutes ago, tpr said:

It seems to be the "double span" issue again. Could you try replacing the same line as in my post above with this:


$event->return = str_replace('<span ', '<span data-pid="' . $page->id . '" ', $event->return);

 

That seems to take care of things!

Share this post


Link to post
Share on other sites

Thanks, but unfortunately there were other issues with the current approach. In v130 (just uploaded) all should be fine, and pagelist IDs are visible in the new Tree menu too.

aos-pagelistthumbs.png.714eb37d0c341498003f5ae1b4c5d65c.png

This version also contains the option to align the top nav to the left in the default admin theme (idea & request by @Robin S - thanks!).

  • Like 2

Share this post


Link to post
Share on other sites

New feature in v131: new move to first/last buttons for file/image fields (FileFieldTweaks). This adds up/down icons (right-left in case of images) that you can use to move items to the first or last position.

aos-first-last-buttons.gif.a5b701884faa04a1ae7247de29efc168.gif

  • Like 5

Share this post


Link to post
Share on other sites

v133 contains a new CKE plugin Code Snippet which lets you insert rich code snippets with syntax highlighting into the editor. The plugin uses highlight.js.

On the frontend you'll need to include highlight.js assets and initialize (see more at higlightjs.org):

Quote

<link rel="stylesheet" href="/path/to/styles/default.css">
<script src="/path/to/highlight.pack.js"></script>
<script>hljs.initHighlightingOnLoad();</script>

To customize the languages available for selection and the theme, add this to /site/templates/admin/cke.js file (this is the auto-loaded configuration file for CKEditor, you can modify it in the Asset Paths section in AOS):

CKEDITOR.editorConfig = function (config) {

    config.codeSnippet_theme = 'foundation';

    config.codeSnippet_languages = {
        apache: 'Apache',
        css: 'CSS',
        html: 'HTML',
        ini: 'INI   ',
        javascript: 'JavaScript',
        scss: 'SCSS',
        php: 'PHP',
        sql: 'SQL',
    };
};

 

aos-cke-codesnippet-editor.png.cf90dbbc2601bd7f12810adcd2741862.png

 

aos-cke-codesnippet-dialog.png.418e975ea9a2c397e5e43df7926cab38.png

 

  • Like 4

Share this post


Link to post
Share on other sites

v134 has a new option for FileFieldTweaks: disable filename truncation for File fields.

Thanks @BitPoet for the right track and @Robin S for the request. This was something bugged me for some time but was lazy to investigate :)

aos-untruncate.png

  • Like 5

Share this post


Link to post
Share on other sites

hi @tpr,

it would be nice to have a "fullscreen" button for some of my inputfields in my current project. it seems to be quite easy to make the inputfields content div fullscreen like this:

.fullscreen {
    height: 100%;
    width: 100%;
    left: 0;
    top: 0;
    overflow: scroll;
    position: fixed;
    z-index: 999;
}

i need it for my datatables fields, but i'm thinking if that would maybe also interesting for other fields. that's why i thought creating a module. and then i thought that could maybe be interesting for AOS as well. like having a toggle icon to make CKE fields fullscreen?

with fullscreen i mean full browser window ;)

what do you think?

Share this post


Link to post
Share on other sites

For ckeditor there is already a Maximize plugin in aos (ckeaddons).

As for the other fields the biggest issue is the button placement, or finding another solution to trigger. I think such features would fit to the drop down idea I plan to add to field labels - when my time allows :)

  • Like 1

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 daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      I've updated the module to 0.0.3. I removed the instructions from this forum, so I don't have to maintain it on multiple places. Just checkout the readme on github 🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github. 
    • By blynx
      Hej,
      A module which helps including Photoswipe and brings some modules for rendering gallery markup. Feedback highly appreciated
      (Also pull requests are appreciated 😉 - have a new Job now and don't work a lot with ProcessWire anymore, yet, feel free to contact me here or on GitHub, Im'm still "online"!)

      Modules directory: http://modules.processwire.com/modules/markup-processwire-photoswipe
      .zip download: https://github.com/blynx/MarkupProcesswirePhotoswipe/archive/master.zip
      You can add a photoswipe enabled thumbnail gallery / lightbox to your site like this. Just pass an image field to the renderGallery method:
      <?php $pwpswp = $modules->get('Pwpswp'); echo $pwpswp->renderGallery($page->nicePictures); Options are provided like so:
      <?php $galleryOptions = [ 'imageResizerOptions' => [ 'size' => '500x500' 'quality' => 70, 'upscaling' => false, 'cropping' => false ], 'loresResizerOptions' => [ 'size' => '500x500' 'quality' => 20, 'upscaling' => false, 'cropping' => false ], 'pswpOptions' => (object) [ 'shareEl' => false, 'indexIndicatorSep' => ' von ', 'closeOnScroll' => false ] ]; echo $pswp->renderGallery($page->images, $galleryOptions); More info about all that is in the readme: https://github.com/blynx/MarkupProcesswirePhotoswipe
      What do you think? Any ideas, bugs, critique, requests?
      cheers
      Steffen
    • By bernhard
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180516 change sql query method, bump version to 1.0.0 180515 multilang bugfix 180513 beta release <180513 preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By flydev
      OAuth2Login for ProcessWire
      A Module which give you ability to login an existing user using your favorite thrid-party OAuth2 provider (i.e. Facebook, GitHub, Google, LinkedIn, etc.)..
      You can login from the backend to the backend directly or render a form on the frontend and redirect the user to a choosen page.
      Built on top of ThePhpLeague OAuth2-Client lib.
      Registration is not handled by this module but planned.
       
      Howto Install
      Install the module following this procedure:
       - http://modules.processwire.com/modules/oauth2-login/
       - https://github.com/flydev-fr/OAuth2Login
      Next step, in order to use a provider, you need to use Composer to install each provider
      ie: to install Google, open a terminal, go to your root directory of pw and type the following command-line: composer require league/oauth2-google
      Tested providers/packages :
          Google :  league/oauth2-google     Facebook: league/oauth2-facebook     Github: league/oauth2-github     LinkedIn: league/oauth2-linkedin
      More third-party providers are available there. You should be able to add a provider by simply adding it to the JSON config file.

      Howto Use It
      First (and for testing purpose), you should create a new user in ProcessWire that reflect your real OAuth2 account information. The important informations are, Last Name, First Name and Email. The module will compare existing users by firstname, lastname and email; If the user match the informations, then he is logged in.
      ie, if my Google fullname is John Wick, then in ProcessWire, I create a new user  Wick-John  with email  johnwick@mydomain.com
      Next step, go to your favorite provider and create an app in order to get the ClientId and ClientSecret keys. Ask on the forum if you have difficulties getting there.
      Once you got the keys for a provider, just paste it into the module settings and save it. One or more button should appear bellow the standard login form.
      The final step is to make your JSON configuration file.
      In this sample, the JSON config include all tested providers, you can of course edit it to suit your needs :
      { "providers": { "google": { "className": "Google", "packageName": "league/oauth2-google", "helpUrl": "https://console.developers.google.com/apis/credentials" }, "facebook": { "className": "Facebook", "packageName": "league/oauth2-facebook", "helpUrl": "https://developers.facebook.com/apps/", "options": { "graphApiVersion": "v2.10", "scope": "email" } }, "github": { "className": "Github", "packageName": "league/oauth2-github", "helpUrl": "https://github.com/settings/developers", "options": { "scope": "user:email" } }, "linkedin": { "className": "LinkedIn", "packageName": "league/oauth2-linkedin", "helpUrl": "https://www.linkedin.com/secure/developer" } } }  
      Backend Usage
      In ready.php, call the module :
      if($page->template == 'admin') { $oauth2mod = $modules->get('Oauth2Login'); if($oauth2mod) $oauth2mod->hookBackend(); }  
      Frontend Usage
      Small note: At this moment the render method is pretty simple. It output a InputfieldForm with InputfieldSubmit(s) into wrapped in a ul:li tag. Feedbacks and ideas welcome!
      For the following example, I created a page login and a template login which contain the following code :
      <?php namespace ProcessWire; if(!$user->isLoggedin()) { $options = array( 'buttonClass' => 'my_button_class', 'buttonValue' => 'Login with {provider}', // {{provider}} keyword 'prependMarkup' => '<div class="wrapper">', 'appendMarkup' => '</div>' ); $redirectUri = str_lreplace('//', '/', $config->urls->httpRoot . $page->url); $content = $modules->get('Oauth2Login')->config( array( 'redirect_uri' => $redirectUri, 'success_uri' => $page->url ) )->render($options); }
      The custom function lstr_replace() :
      /* * replace the last occurence of $search by $replace in $subject */ function str_lreplace($search, $replace, $subject) { return preg_replace('~(.*)' . preg_quote($search, '~') . '~', '$1' . $replace, $subject, 1); }  
      Screenshot
       



    • By gRegor
      Updated 2018-05-06:
      Version 2.0.0 released
      Updated 2017-03-27:
      Version 1.1.3 released
      Updated 2016-04-11:
      Version 1.1.2 released

      Updated 2016-02-26:
      Officially in the module directory! http://modules.processwire.com/modules/webmention/

      Updated 2016-02-25:
      Version 1.1.0 is now released. It's been submitted to the module directory so should appear there soon. In the meantime, it's available on GitHub: https://github.com/gRegorLove/ProcessWire-Webmention. Please refer to the updated README there and let me know if you have any questions!
      ------------
      Original post:
       
      This is now out of date. I recommend reading the official README.
       
      I've been working on this one for a while. It's not 100%, but it is to the point I'm using it on my own site, so it's time for me to release it in beta. Once I finish up some of the features described below, I will submit it to the modules directory as a stable plugin.
      For now, you can install from Github. It works on PW2.5. I haven't tested on PW2.6, but it should work there.
      Feedback and questions are welcome. I'm in the IRC channel #processwire as well as #indiewebcamp if you have any questions about this module, webmention, or microformats.
      Thanks to Ryan for the Comments Fieldtype which helped me a lot in the handling of webmentions in the admin area.
      ProcessWire Webmention Module
      Webmention is a simple way to automatically notify any URL when you link to it on your site. From the receiver's perspective, it is a way to request notification when other sites link to it.
      Version 1.0.0 is a stable beta that covers webmention sending, receiving, parsing, and display. An easy admin interface for received webmentions is under development, as well as support for the Webmention Vouch extension.
      Features
      * Webmention endpoint discovery
      * Automatically send webmentions asynchronously * Automatically receive webmentions * Process webmentions to extract microformats   Requirements * php-mf2 and php-mf2-cleaner libraries; bundled with this package and may optionally be updated using Composer. * This module hooks into the LazyCron module.   Installation Github: https://github.com/gRegorLove/ProcessWire-Webmention

      Installing the core module named "Webmention" will automatically install the Fieldtype and Inputfield modules included in this package.   This module will attempt to add a template and page named "Webmention Endpoint" if the template does not exist already. The default location of this endpoint is http://example.com/webmention-endpoint   After installing the module, create a new field of type "Webmentions" and add it to the template(s) you want to be able to support webmentions. Sending Webmentions
      When creating or editing a page that has the Webmentions field, a checkbox "Send Webmentions" will appear at the bottom. Check this box and any URLs linked in the page body will be queued up for sending webmentions. Note: you should only check the "Send Webmentions" box if the page status is "published."   Receiving Webmentions This module enables receiving webmentions on any pages that have have "Webmentions" field, by adding the webmention endpoint as an HTTP Link header. If you would like to specify a custom webmention endpoint URL, you can do so in the admin area, Modules > Webmention.   Processing Webmentions (beta) Currently no webmentions are automatically processed. You will need to browse to the page in the backend, click "Edit," and scroll to the Webmentions field. There is a dropdown for "Visibility" and "Action" beside each webmention. Select "Process" to parse the webmention for microformats.   A better interface for viewing/processing all received webmentions in one place is under development.   Displaying Webmentions (beta) Within your template file, you can use `$page->Webmentions->render()` [where "Webmentions" is the name you used creating the field] to display a list of approved webmentions. As with the Comments Fieldtype, you can also generate your own output.   The display functionality is also under development.   Logs This module writes two logs: webmentions-sent and webmentions-received.   Vouch The Vouch anti-spam extension is still under development.   IndieWeb The IndieWeb movement is about owning your data. It encourages you to create and publish on your own site and optionally syndicate to third-party sites. Webmention is one of the core building blocks of this movement.   Learn more and get involved by visiting http://indiewebcamp.com.   Further Reading * http://indiewebcamp.com/webmention * http://indiewebcamp.com/comments-presentation * http://indiewebcamp.com/reply