tpr

AdminOnSteroids

Recommended Posts

10 minutes ago, tpr said:

I guess there's nothing more in the logs that you already wrote. Was it a ML site btw, and if yes, how any languages? Php version? 

Yes, 3 languages, PHP 7.0.7.

I am going to bed now. See you tomorrow.

Share this post


Link to post
Share on other sites

No issues with me either, I just started a new profile with 3.0.98 and latest AOS and all works fine, I can switch languages from admin etc. 

  • Like 1

Share this post


Link to post
Share on other sites

@tpr :

I've had a little time now, and i found the line which is causing the trouble in my installation.

Around Line 391 in AOS 1.8.9. The commented line "//theo"

        // add to init() to change early
        if ($this->isMultiLang) {
            if (in_array($subModule, $enabledSubmodules)) {
                if (in_array('adminLangSwitcher', $configData[$subModule])) {
                    if (isset($_COOKIE["aos_lang_id"])) {
                        $lang_id = $_COOKIE["aos_lang_id"];
                       //theo $this->wire('user')->language = $lang_id;
                    }
                }
            }
        }

It seems as if this comes too early here. Not sure.

Do you have an idea what is going on here?

 

Share this post


Link to post
Share on other sites

Hummm, now it works. Very strange, almost scaring...  :huh:

Maybe there was sth. wrong with a previously set cookie?

 

 

Share this post


Link to post
Share on other sites

Hey guys,

It was hard not to notice the often updates of this AMAZIN' module and I was wondering if there is a changelog where I could read more about it before deciding to do an upgrade?

Share this post


Link to post
Share on other sites
50 minutes ago, MilenKo said:

I was wondering if there is a changelog where I could read more about it before deciding to do an upgrade?

I would definitely recommend installing: http://modules.processwire.com/modules/module-release-notes/ so you can see what's changed when using the PW Upgrade module: http://modules.processwire.com/modules/process-wire-upgrade/

  • Like 2

Share this post


Link to post
Share on other sites

As always a fast and efficient reply. I never thought of looking for a release notes module, but it is a great addition. Thanks guys!

  • Like 2

Share this post


Link to post
Share on other sites

@tpr About the language switcher problem mentioned before:

The problem is with the cookie "aos_lang_id".

If it contains a value for the language (like e.g. 1010) which does not correspond to a language id of your current installation, then then PW backend crashes.

This may happen, if you run multiple PW instances on localhost.

A check for the existence of the id you get from the cookie would help imo.

Thank you.

 

  • Like 1

Share this post


Link to post
Share on other sites

Nice find, thanks. I've changed to an arbitrary cookie but couldn't get any errors though. Could you try wrapping the lin in question with this and see if the problem goes away?

if ($this->wire('pages')->get('template=language,id=' . $lang_id)) {
	$this->wire('user')->language = $lang_id;
}

 

Share this post


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

Nice find, thanks. I've changed to an arbitrary cookie but couldn't get any errors though. Could you try wrapping the lin in question with this and see if the problem goes away?


if ($this->wire('pages')->get('template=language,id=' . $lang_id)) {
	$this->wire('user')->language = $lang_id;
}

 

 

No, it does not help.

Still getting: 

Quote

Fatal error: Exception: Method Permission::translator does not exist or is not callable in this context

Thank you.

Share this post


Link to post
Share on other sites

@theo Thanks - does it help if you change "get" to "findOne"?

I'm experimenting with a new sticky pagelist action, loosely based on the ProcessPageListMultipleSorting module. The idea is to create a global "sticky" field and hook into ProcessPageList::find to prepend sort=-sticky to the original selector (keeping template and page level sort intact). This way un-stickying a page will restore the original sort order.

When sticky-ing a page it finds the sibling with the highest sticky value and sets it to an even greater value, so it will go to the top. It works fine so far, the minor glitch is that if you would like to move eg the second to topmost sticky page to top you'll need to unstuck first and then re-sticky (or edit the sticky field value manally). I find the idea to add extra move up/down sticky actions an overkill.

The order also can be queried on the frontend because the new sticky field is a real field.

aos-sticky.gif.23b68900338ecc00b1f7fa7566d93021.gif

  • Like 1

Share this post


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

@theo Thanks - does it help if you change "get" to "findOne"?

 

 

I think the check for "NullPage" was wrong. We have to check for id<>0

https://processwire.com/api/ref/null-page/

Like this it works.

$item= $this->wire('pages')->get('template=language,id=' . $lang_id);
if($item->id) {
  $this->wire('user')->language = $lang_id;
}

Thank you.

  • Like 1

Share this post


Link to post
Share on other sites

Is anyone interested in the sticky implementation shown two posts above? I think it's a simple but reliable implementation that can be handy not only in the admin but on frontend too.

  • Like 1

Share this post


Link to post
Share on other sites

I've added the new sticky pagelist action, @theo's langswitcher fix, Tracy panel z-index fix (hopefully) and other minor fixes in v1.9.1.

I noticed that I was using one SCSS mixin too many times (for icon-only pagelist actions) and it contained rules that I could apply to items outside the mixin. After cleaning this up the final CSS shrinked from 127 to 93 Kb so it was worth the trouble.

I removed the js lib "perfect scrollbar" that was used to replace the browser scrollbar with a mini one (RenoTweaks). From now on AOS uses CSS to achieve the same thing, and is available in Chrome only (you can find it under Misc). It's a sacrifice but results in much leaner code, is controlled by the browser so it's unlikely to break, and modifies every scrollbar in the admin. For example they are available in Tracy panels too and also in CKEditors (the latter required additional efforts though):

aos-miniscrollbarseverywhere.thumb.png.e77b436cfb4a4e334755bc1e1483d31b.png

Documentation is in progress, as usual :) 

  • Like 5

Share this post


Link to post
Share on other sites

Thanks for the remainder @Robin S. I've replaced the character icon with an SVG. I've committed the changes, no version bump.

Perhaps I would have used FontAwesome if it would have been possible to set it as a background-image but that's not the case. I've tried adding the SVG variant of the FA search icon but then searched for a slimmer one. There are only a few icons in AOS and I wouldn't like to increase the overall module size. 

  • Like 2

Share this post


Link to post
Share on other sites

In v1.9.3 I switched to the $datetime api var in pagelist markup and introduced %modifiedUser% and %createdUser% tokens.

As a result it is possible to display relative date like this:

plistmarkup-relativedate.png.cea445ef5d0bfaddefb21dbec6fe59c1.png

I never thought about this but it came from a request and seems like a nice addition. In fact I only knew that a relative date function exists in PW but not that it's also an api var. I was even happier when I learned that I need only slightly change the code to support both relative and the existing date formats with $datetime->date().

Full changelog:

  • pagelist markup: switch to $datetime api var (allows relative datetime strings too)
  • pagelist markup: add %createdUser% and %modifiedUser% tokens
  • pagelistUnselect: fix Uikit theme spacing issue (reported by Robin S)
  • CKEditor plugin Link Files Menu: apply fix from Robin S from his original module (ajax response not working for non-superusers)
  • Like 4

Share this post


Link to post
Share on other sites

hey @tpr could you please add "noAutosize" class support for textarea autosize feature? line 1766 in aos.js (and maybe also some lines below)

autosizeTextareas = target.querySelectorAll('textarea:not(.noAutosize)');

Otherwise it does autosize on my custom textareas, thanks :)

This does not seem to work :( Could you please add a way to exclude custom textareas from this feature? Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

Hi @tpr, a feature request: could you add a cache-busting query string (e.g. using filemtime) to the assets added from the "Asset Paths" section of AOS? Thanks!

  • Like 1

Share this post


Link to post
Share on other sites

@bernhard 

It does seem to work - or do you mean you are not able to add the .noAutosize classes?

@Robin S 

Just added the cache bust strings to assetpaths, thanks for the suggestion. Will be available in v1.9.4.

Here is a preview of the Fields page with additional data like inputfield classes, description, notes and IDs. It seems impossible to add column headers to the extra columns but i think it's quite obvious even without them.

fields-setup-page.thumb.png.a546756e947029475bc643b633d0a246.png

  • Like 3

Share this post


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

It does seem to work - or do you mean you are not able to add the .noAutosize classes?

You are right, my mod works. Just edited aos.js instead of aos.min.js and that had no effect 🙂 Could you please change both occurances of querySelectorAll('textarea') to querySelectorAll('textarea:not(.noAutosize)') as requested?

Thanks!

 

Share this post


Link to post
Share on other sites

Version 1.9.4 is available:

  • new: extra columns on Fields setup page showing description, notes, id and inputfield class (Misc)
  • skip autosizing textareas having "noAutosize" classname (requested by bernhard)
  • add cache busting string to assetPaths (requested by Robin S)
  • check if $_SERVER['HTTP_REFERER'] exists before redirect (reported by Robin S)
  • fix 1px title field misalignment caused by casechanger (reported by Robin S)
  • Like 4

Share this post


Link to post
Share on other sites

Hi all,

on a fresh PW 3.0.98 installation using Default Admin theme and site-default profile I have installed AOS 1.9.4 as the only site module.

Two observations:

(1) When in PageListTweaks I check Always show pagelist actions, in the page tree there are no line breaks any more between the entries - see attached screenshot. How do I get them back?

(2) Having checked Sticky header in Admin tweaks, when on the settings page of the module I click the cog of a Submodule, the sticky header would overlay the top lines of the options of the chosen submodule.

Not big problems - many thanks for this incredibly useful module!

screenshot-1.jpg

Share this post


Link to post
Share on other sites

Hi,

(1) I could reproduce, thanks. For a quick fix use this, or wait for a new version:

html.pListShowActions .content .PageList .PageListItem { width: 100%; }

(2) I'm aware of this, will try to fix with some CSS.

I recommend using Reno or Uikit theme, most AOS features are targeted/tested in them.

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 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://modules.processwire.com/modules/rock-finder/
      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 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 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