Jump to content
tpr

AdminOnSteroids

Recommended Posts

Fortunately I have a maximum of 1 dev site and 1 live, and I mostly work on the dev and merge changes. But I see your pain :) This is where your red-colored admin header will be of great help :)

  • Like 1

Share this post


Link to post
Share on other sites

v054 is up. There were many updates under the hood so make sure to clear browser and module cache.

  • module settings are exported to settings.php on uninstall and restored on install
  • load admin.js and admin.css from /site/templates/ directory if exist
  • new tweak "NavItems" (experimental): add pages to main nav or sidebar (depending on theme)
  • HTML classes added by AOS are added by PHP instead JavaScript: faster and eliminates initial page jump so the loader is no longer needed
  • loader removed
  • added "cog" icon to footer to jump to AOS settings
  • fix: keep sidebar menu colors for non-inline mode (Reno theme)
  • module CSS classnames were abbreviated
  • Like 2

Share this post


Link to post
Share on other sites

You do realise that if you (and Adrian with Tracy) keep developing your modules at this rate, they will become sentient before I do.

  • Like 4

Share this post


Link to post
Share on other sites

No, it's the other way: we just try to bring you the most of what the module is capable before you get sentient :)

  • Like 2

Share this post


Link to post
Share on other sites

hi tpr,

short (maybe) bugreport: i think the field-name-tooltips do not get loaded when using ajax collapsed fields. can you confirm that?

Share this post


Link to post
Share on other sites

Yes, it fails because the labels aren't surrounded by span tags but can't figure out why. I'll try to find it out or solve this by Js.

Share this post


Link to post
Share on other sites

Here's another one:

Screen Shot 2016-08-31 at 8.35.19 AM.png

Seems to happen after a field has been collapsed.

  • Like 1

Share this post


Link to post
Share on other sites

Yep, just discovered that, it's been fixed, thanks.

Anyone knows why ajax-loaded fields doesn't allow modifying the label with Inputfield::render (or renderValue)? I can add link to the inputfield and other things too but this one doesn't work. Its value is set before thea ajax event runs, and of course it doesn't modify the existing label markup on the page. But where does it come from then?

I could solve this issue with JS but it's not pretty.

Share this post


Link to post
Share on other sites

Hi tpr,

for me v054 gives an error just after updating:

Parse error: syntax error, unexpected '.', expecting ',' or ';' in /Users/armin/Websites/pwreiter/site/assets/cache/FileCompiler/site/modules/AdminOnSteroids/AdminOnSteroids.module on line 23

I'm running on PW 3.0.32 in local environment (MAMP). I had no issues with past versions of AdminOnSteroids.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks, that was a PHP version syntax error which was fixed.

v055 is up:

  • module settings restore is optional (disabled by default)
  • JS workaround for field edit links for ajax-loaded fields
  • syntax error fix (thanks to TomasKostadinov)
  • Like 1

Share this post


Link to post
Share on other sites

Just wanted to let you know that the sticky header isn't sticking for me with the latest 3.0.32 devns and the default theme.  Seems like it started after I upgraded to 3.0.32.  I'm also using the latest AOS.  I have hard refresh the browser several times.

Share this post


Link to post
Share on other sites

I can't reproduce this. Have you tried clearing the module cache (at the bottom of the Modules page)?

If that doesn't help, could you post the body and html classes your admin has? 

Share this post


Link to post
Share on other sites

Strange.  It still didn't work.  I clicked the clear compiled files button at /admin/module/.  I also did a module refresh.  I'm using the latest Google Chrome on a mac.

Here are my body classes when editing a page.

id-10 template-admin hasWireTabs AdminThemeDefault ProcessPageEdit-id-1002 ProcessPageEdit-template-basic-page pw-ready InputfieldColumnWidthsInit

Share this post


Link to post
Share on other sites

Thanks - could you post the classes on the "html" tag? That would be more helpful.

Share this post


Link to post
Share on other sites

I was afraid of that :) Anyway, try v056, hopefully this is solved now. You should see classes appear on the html element.

Share this post


Link to post
Share on other sites

I just updated to v056 and here are my html element classes

<html class=" headSticky HoverDropdown moduleCompact moduleModal" lang="en">

and

<body class="id-10 template-admin hasWireTabs AdminThemeDefault ProcessPageEdit-id-1015 ProcessPageEdit-template-left-sidebar pw-ready InputfieldColumnWidthsInit">

So I have classes now, but the header still isn't sticking.  Sorry... I'm trying to find the problem as well.

Share this post


Link to post
Share on other sites

The default theme is missing the "AdminThemeDefault" class on the html element.  After I added that manually it worked.

Share this post


Link to post
Share on other sites

Actually I bet what is happening is the AOS css is targeting the html element when it should be targeting the body element on line 2166 of AdminOnSteriods.scss

Share this post


Link to post
Share on other sites

After reading the comment in the scss file

// AdminTweaks (default theme tweaks)
// note: the default theme adds theme name class only to body, AOS adds to html

maybe AOS isn't adding the class "AdminThemeDefault" to the html element in the default admin theme in AdminOnSteriods.module line 243?

Share this post


Link to post
Share on other sites

It's intentional to use html.AdminThemeDefault (as you figured out already).

What I don't get how your html classes doesn't contain 'AdminThemeDefault' because it should be added by AOS.

echo wire('user')->admin_theme;

This should echo "AdminThemeDefault", could you try it?

Share this post


Link to post
Share on other sites

I added that snippet to a template file, but it didn't output anything.  I also have Tracy debugger and tried using the php console, but it didn't output anything either.

Share this post


Link to post
Share on other sites

No idea then atm... do you have other PW installation where you could check AOS?

  • Like 1

Share this post


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

What I don't get how your html classes doesn't contain 'AdminThemeDefault' because it should be added by AOS.

I've just updated to 0.5.6, and I do get the AdminThemeReno class and the sticky header.

  • Like 1

Share this post


Link to post
Share on other sites

Well it's the AdminThemeDefault class what's in question when using the default theme.

  • Like 1

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory (alpha version only available via GitHub) SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...