Jump to content
tpr

AdminOnSteroids

Recommended Posts

20 hours ago, bernhard said:

Hi @tpr

any chance we can get a fix for this issue in AOS as long as it is not fixed in the core? https://github.com/processwire/processwire-issues/issues/812#issuecomment-520855872

Thx 🙂 

It doesn't diminish your request, but Interestingly I have an issue where AOS actually causes a horizontal scrollbar to appear on desktop on some pages - as soon as I disable AOS it goes away. I haven't narrowed down the cause, but something worth thinking about in all this.

  • Like 1

Share this post


Link to post
Share on other sites

@tpr There's something in AoS that interferes with the brandnew toggle fieldtype. See here for description. 

Share this post


Link to post
Share on other sites

Hey @tpr,

I'm also experiencing a different issue with AoS and the new toggle fieldtype.

When entering the new toggle field to display results in the admin Page List (template->advanced->list of fields to display), if the page tree is not already open, the 'edit' string is attached to the string of text, when you open up a branch.  If the tree is already opened however, it is fine.

Please see the attached image.

Thanks!

toogle_page_tree.png

Share this post


Link to post
Share on other sites

I see, and it's caused by the template and field edit links submodule. I've tried a few things like prioritizing hooks and changing the execution order but no luck so far.

Share this post


Link to post
Share on other sites

@tpr Thanks for this great module!

But I think the CKE plugin Linkhover cannot be used with PW anymore. At some point PW or the CKE module implemented the linkhover on their own, and now if you doubleclick a link in your text its title attribute is replaced with the URL. A normal click in the text and then Edit works, but not the doubleclick.

Tested on PW 3.0.123 - 3.0.145 with AOS 2.0.20

Share this post


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

if you doubleclick a link in your text its title attribute is replaced with the URL

@tpr, I have added a fix for this in v0.0.2 of the Link Hover plugin if you want to update the version included in AOS: https://github.com/Toutouwai/linkhover

2 hours ago, Klenkes said:

At some point PW or the CKE module implemented the linkhover on their own

Not as far as I can see. Without the Link Hover plugin installed there is no equivalent functionality to show the link URL on hover. Thanks for the bug report though.

  • Like 3

Share this post


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

I have added a fix for this in v0.0.2 of the Link Hover plugin if you want to update the version included in AOS: https://github.com/Toutouwai/linkhover

Thank you. Works great again.

11 hours ago, Robin S said:
13 hours ago, Klenkes said:

At some point PW or the CKE module implemented the linkhover on their own

Not as far as I can see. Without the Link Hover plugin installed there is no equivalent functionality to show the link URL on hover. Thanks for the bug report though.

You are right. I got confused.

Share this post


Link to post
Share on other sites

Hey @tpr just wanted to ask if there is any harm in having all config inputfields toggled visible? AOS has so many options, it's always hard to remember where an option is hidden. Using the browser search this would be a lot easier (eg find "middle" when you want to activate some middle click magic)

eDm7WWT.png

Share this post


Link to post
Share on other sites

There's no harm but then I would have to modify the current submodule toggle (and role setting) behavior. The idea was to enable/disable a submodule in the top section and hide the corresponding settings section below.

If I would remove the "show if" conditionals to show all settings, one wouln't know whether the submodule he is configuring is enabled or not (without scrolling to the top to check). Perhaps the easier solution would be to add some kind of text or icon to indicate the on/off state.

 

Share this post


Link to post
Share on other sites

@tpr I don't remember if I have posted this already some time ago... The option "disable all admin animations" practically makes the vec-dialogs unusable. The dialog will appear, but won't disappear when you choose either of the options. You then have no choice than to hard-reload the page. Maybe a word of caution would be nice in the settings. I stumbled over this a long time ago, and recently forget how to fix it.

  • Like 1

Share this post


Link to post
Share on other sites
On 2/8/2020 at 4:41 PM, tpr said:

If I would remove the "show if" conditionals to show all settings, one wouln't know whether the submodule he is configuring is enabled or not

So why not let them all enabled by default?

Share this post


Link to post
Share on other sites

Is it possible to overwrite the use of Purifier and ACF in a CKE field with the overwrite function of AOS?
I need to disable them on one page with a known ID.

Like this:

$fieldoverrides['Diable ACF an Purifier for Privacy Policy'] = array(
"?page" => "id=1035",
"?field" => "body",
"removePlugins" => "Purifier,ACF"
);

Well it doesn't work, because ACF and Purifier are not plugins...

Share this post


Link to post
Share on other sites
On 2/13/2020 at 3:57 PM, Klenkes said:

Well it doesn't work, because ACF and Purifier are not plugins...

Sure, because they are field settings.

This feature wasn't tested and used too many times (by myself) but when I opened a local PW site I usually use for testing, the following was filled int he FieldOverrides textarea in AOS:

[Enable any markup in any CKEditor]
?field = "inputfieldClass=InputfieldCKEditor"
useACF = 0
usePurifier = 0

Apparently it works, but it's important to know how. AOS is loaded in the admin only, so if you override a field like this, you won't see useACF=0 if you dump the field settings in the frontend (eg. with Tracy). But in the admin the value is overriden, so you can add any markup and it will be saved to the DB. On the contrary, if you decide to remove this override later on, the data won't be changed in the DB automatically unless you re-save the page again.

  • Like 2

Share this post


Link to post
Share on other sites

Oh yes, of course, you are right. It's a setting!
I was so caught up in removing plugins on this template and removing buttons on toolbars on another template.

Usually I wouldn't disable security features that but in this case the editors are trustworthy and it's only on 1 page.

Thank you for this extraordinary module!

Share this post


Link to post
Share on other sites

Glad it helped. I know it can be a powerful feature even though I haven't had a chance to use too much.

You may also take the relatively new built-in extended template overrides into account (available when $config->advanced = true). But that would need another template to use so AOS is more flexible.

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 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: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • 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 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...