Jump to content
tpr

AdminOnSteroids

Recommended Posts

I've updated to work with Batch Child Editor's title fields.

  • Like 5

Share this post


Link to post
Share on other sites

If I enable "Disable filename truncation for File fields", the download icon is missing. I also have enabled Asset download button and Move to first/last buttons).

image.thumb.png.ef10ef0d064f3d2ad632fba8dca642cc.png

  • Like 1

Share this post


Link to post
Share on other sites

It was a z-index issue and should be fixed in v2.0.2, thanks for reporting.

  • Like 2

Share this post


Link to post
Share on other sites

Hi, when applying CodeMirror in AOS, when viewing source the text is black on a dark background. Nothing I've tried seems to be able to override this (custom stylesheets etc). Any ideas?

 

Capture3.PNG

  • Like 1

Share this post


Link to post
Share on other sites
31 minutes ago, Pete said:

Any ideas?

It happens if the CKEditor skin is set to default. Probably @tpr always sets it to LightWire that is why he has not yet noticed it, I guess....

Share this post


Link to post
Share on other sites

This also happens on LightWire actually when using the UIKit admin theme.

The CSS class that overrides the colour is this:

image.png

It's bizarre that I can't override it even when using a custom CKE CSS file and adding color: #fffff !important (I kinda thought !important would do the trick).

Share this post


Link to post
Share on other sites

I see. I'm still on Reno, and get white text when LightWire is being used.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks - that definitely narrows it down to Uikit then. One step closer 🙂

  • Like 1

Share this post


Link to post
Share on other sites

Hey @tpr there are settings in AoS for PageListTweaks: Always show pagelist actions and Always show extra actions.

Could you make them work also in a ListerPro?

On 9/21/2018 at 11:57 AM, Pete said:

There's a UIKit admin theme bug when you switch on AoS - see here: https://github.com/processwire/processwire-issues/issues/706

The bug doesn't exist when you switch AoS off so just needs some style tweaks somewhere in AoS but I didn't investigate further than that sorry.

I can confirm this bug.

Share this post


Link to post
Share on other sites

I know about that bug, will check later. As for ListerPro, the problem is that I still don't own a copy of it so it's hard to fix. If you happen to make a PR, that would be great.

Share this post


Link to post
Share on other sites

The overlapped header button and the CodeMirror black font color issues should be fixed in v2.0.4. As for the latter, if you set a light CodeMirror theme then you should manually override the font color with a custom CSS. I also made the CodeMirror editor text a bit larger and force word-wrapping.

  • Like 1

Share this post


Link to post
Share on other sites

Hello there. I am not sure if the issue I experience is a bug of AOS or there is some weird setting I have, but I noticed that on a PW latest version with just AOS installed, when I select the Sticky header option and scroll down the page a bit, the submenu's are not showing until I scroll back up where they are dropped originally. Any ideas on how to have that fixed as it is not that convenient to have the sticky header if you are not seeing your menu and still need to scroll back up to make it appear?

 

 

PW-AOS-01.png

PW-AOS-02.png

Share this post


Link to post
Share on other sites

@MilenKo This is because these dropdowns are positioned via JavaScript (inline CSS) and it happens when you hover on the menu. This makes this weird behaviour that I have noticed as well but never examined it. As a simple fix I made those dropdown menus fixed positioned too in v2.0.5.

Share this post


Link to post
Share on other sites

Hey @tpr - no big deal, but the most recent version of PW has broken the layout slightly when using AOS's compact header option.

Share this post


Link to post
Share on other sites

You mean the header height? As I see it's only a matter of adding min-height: 54px to height: 54px to the CSS.

  • Like 1

Share this post


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

You mean the header height? As I see it's only a matter of adding min-height: 54px to height: 54px to the CSS.

Yep, that seems to fix it.

  • Like 1

Share this post


Link to post
Share on other sites

Hey @tpr - I've started seeing something weird in the page tree with hidden pages. They don't show until I mouse over the tree itself:

 

Let me know if you can't reproduce and I'll try to narrow it down for you.

BtPLBJP455.gif.3ed017def91ff5de412470333aec6c11.gif

Share this post


Link to post
Share on other sites

Hey everybody and @tpr maybe you want to vote for a pull request I made:

Expose actual user and role/s through ProcessWire.config javascript object https://github.com/processwire/processwire/pull/127

This would allow for example AdminOnSteroids to activate some features only if a specific user-role or user is active. But it is not exclusive for AoS.

I really don't know if you should vote for the pull request or the feature-request or if Ryan cares about the votes.

Share this post


Link to post
Share on other sites

@tpr There is a bug with displaying roles. I remember there was a select, so you can select which roles benefit from a specific setting. But under what conditions do these selects appear?

I have one ProcessWire installation with latest AoS and AdminThemeUikit, where the roles select should be available, but does not show up, although it is there.

image.png.00653871817a14a065cafd383aad53ba.png

This seems to come from the asmSelect class. When I remove the class, the select appears.

image.png.fe31e921cc72097110f71166bd68e598.png

With the old Default AdminTheme there appears a small triangle.

image.png.b2c9ac2e7214d1bf47454c57d6a301a3.png

Share this post


Link to post
Share on other sites

@adrian You're right, I cannot duplicate 🙂 I'm not PWing nowadays too much but so far I haven't had such issue with hidden pages.

@jmartsch Thanks, I think I found why the roles select wasn't displayed to you. It uses AOS's "Add placeholder to asmSelect" (under AsmTweaks), so if you do not check that you won't see the ROLES label. Plus UIkit uses a background-image to show the arrows for the select boxes and AOS was overriding it with a white background color, that's why they were not visible to you. Try v2.0.6 where you can see at least the arrows even if AsmTweaks is disabled.

  • Like 1

Share this post


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

@adrian You're right, I cannot duplicate 🙂 I'm not PWing nowadays too much but so far I haven't had such issue with hidden pages.

I don't think I have seen it before either, but on the site in question, it is triggered by the "Show Page IDs" option. If I turn that off, it works as expected.

Share this post


Link to post
Share on other sites

@tpr Thanks for the update, the arrows now show up,

image.png

but I think the UI could be improved and is also erroneous if you assign multiple roles. 

What do you think about this?

image.png.cdd0dd25f6b42c5532fec47c05972cef.png

 

Share this post


Link to post
Share on other sites

I'm fine with the inline roles, there's an Uikit CSS rule that makes them not wrapping in multiple lines. I'll remove that, thanks for the report.

Share this post


Link to post
Share on other sites

Hi  @tpr I've had a problem when using the skip trash feature of AOS with ProCache,

here is Ryan's explanation:

Quote

A couple suggestions. Avoid skipping the trash if possible. The trash is there for a reason, and there's a reason the core doesn't have a skip trash option. Consider that a 3rd party advanced power user tool that can have side effects, as it does here. If you are deleting pages from the API (skipping trash) you might want to clear the entire document cache after you are done by going into the admin in Setup > ProCache

Is this feature only enabled for super users or for everyone in the admin? Maybe it would be better to trash pages first and delete them thereafter (automatically) rather than skipping the trash?

Here is the complete post:

Quote

When it comes to clearing caches, ProCache is designed for the admin workflow. In your case a 3rd party module added a "Skip Trash" option that goes outside the intended admin workflow, so that's not something that ProCache is going to know about. If a page is deleted, ProCache is going to wipe any caches present for that Page either way. But it's not efficient for ProCache to execute clearing behaviors affecting other pages on $pages->delete() calls because these are usually performed in bulk, like when emptying trash. Not to mention they can be recursive. So if ProCache is executing multi-page cache clearing rules on every delete() call there's a real potential for significant overhead increase and potentially interfere with or prevent bulk delete() operations. 

A couple suggestions. Avoid skipping the trash if possible. The trash is there for a reason, and there's a reason the core doesn't have a skip trash option. Consider that a 3rd party advanced power user tool that can have side effects, as it does here. If you are deleting pages from the API (skipping trash) you might want to clear the entire document cache after you are done by going into the admin in Setup > ProCache. Or if you want to do it from the API you can do $procache->clearAll(); 

If you wanted multi-page cache clearing behaviors to be executed on every $pages->delete() call, this is where things get a little dangerous as there can be side effects as described above. But if you wanted to experiment with it, it could be done with a hook. You would save or trash a page before deleting it using a hook like this:


$pages->addHookBefore('deleteReady', function($event) {
  $page = $event->arguments(0);
  $page->save();
}); 

While I don't recommend this in general, if your case has really simple cache clearing behaviors that don't involve lots of pages, then it may be just fine. 

Are you aware of that?

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   1 member

  • Similar Content

    • By bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • 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:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...