Jump to content
tpr

AdminOnSteroids

Recommended Posts

The search inputfield starts to cover the System Notification indicator under 1040px, and yes, below 960px the search inputfiled is gone. I think it is just quite ok if you focus on a viewport wider than 959px, however, it would be nice to have an easy to access (toggle-) button which can be clicked on mobile to disable/enable the module "temporarily". It can even be useful on a desktop, in order to quickly check out the unmodified admin or vice versa.

Share this post


Link to post
Share on other sites

I've made a quick toggle button that enables/disables the CSS (unreleased), but that's not really helpful because all the php and js stuff are in effect. Do you think a full module enable/disable button is needed? Otoh this toggle wouldn't help you much with the disappearing search field, that comes from the Reno theme as I see.

I have made a little tweak that fixes the issues you mentioned with the search field from about page width above 960px (it's available if you update the module).

  • Like 1

Share this post


Link to post
Share on other sites

In v044 I replaced the field edit link appearance to tooltips. In some cases the field names were overlapped by other items but in tooltip this doesn't occur.

There's also a tooltip for edit page template when hovering on the page title. In fact, the FieldEditLinks tweak was renamedt to FieldAndTemplateEditLinks as they share the same settings. The template edit feature is available for the default theme too.

aos-fieldtemplateeditlinks.gif

  • Like 3

Share this post


Link to post
Share on other sites

I was about to report/ask for these. You saved me some typing :D Thanks a lot!

  • Like 1

Share this post


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

I've made a quick toggle button that enables/disables the CSS (unreleased), but that's not really helpful because all the php and js stuff are in effect. Do you think a full module enable/disable button is needed?

Yes, that was the basic idea. I'm relatively new to PW, so sometimes I just cannot remember what the original admin looks like :) but as I mentioned before, if you "do not support" mobile viewports then it can be problematic if we cannot somehow disable the module in that case. Sure, one can always go to module settings, but it might be possible to speed things up...

6 hours ago, tpr said:

I have made a little tweak that fixes the issues you mentioned with the search field from about page width above 960px (it's available if you update the module).

Thanks. I did not realize it was a Reno bug(?).

Share this post


Link to post
Share on other sites

On mobile screen size AOS is simply not active, so you can see the original theme, at least for the CSS tweaks.

  • Like 1

Share this post


Link to post
Share on other sites

One more thing: when AOS is used to heavily customize the admin, one can easily see that it is enabled. But what if it's not so prominent? A globally accessible enable/disable button would also indicate in what state the admin is. Is it on steroids or not? It is an especially important question during the Summer Olympics :P

  • Like 1

Share this post


Link to post
Share on other sites

Not as fast as Bolt but here it is: enable/disable toggle in the footer (v045, SuperUsers only).

aos_toggle.png

  • Like 4

Share this post


Link to post
Share on other sites

You deserve the gold medal anyway! Works fine. Now I can easily create screenshots for forum support too, should I feel the need to :) (With AOS on it might generate some confusion to demo the admin... so this is just another case to justify the need of this feature...)

  • Like 3

Share this post


Link to post
Share on other sites
11 minutes ago, szabesz said:

so this is just another case to justify the need of this feature...)

Finally there's one :)

  • Like 1

Share this post


Link to post
Share on other sites

Version 046 is sponsored by @bernhard! :)

I got envy of his PageListSelectUnselectButton module so I decided to add something very similar to AOS :)

While the main functionality ("unselect") is the same it also adds a "Restore" button in case someone needs it.

 

aos_pagelistunselect.gif

 

Thanks again @bernhard!

  • Like 3

Share this post


Link to post
Share on other sites

Just added a few CSS tweaks to the Pagelistunselect tweak: less prominent Clear button appearance and when hovering on it the selected page name gets a line-through, which makes clearer what will happen on click. See the screencap above.

  • Like 1

Share this post


Link to post
Share on other sites

does it also support ajax fields?

ps: @Pete can you PLEASE set the limit for "short time frame for new posts" to zero for experienced forum members?

Share this post


Link to post
Share on other sites

It should - the screencap was filmed using a repeater field that is ajax-loaded. Otherwise, the markup is added by PHP so it's always there, plus the events are binded to $(document) so they should fire always.

  • Like 2

Share this post


Link to post
Share on other sites

v047 is up with improvements to the Pagelist thumbs submodule. Thumbnails can be aligned to the right so they don't create ragged lines of the page titles if there's no image or the images are of different widths:

aos_thumbs-left-right.png

 

Of course this partly could be eliminated if using the "circle" or "square" styles:

aos_thumbs-square-circle.png

 

You can set the thumbnails to link to the edit page if you wish.

Another addition is that if a multi-image field is specified as the image source, its first image will be used.

  • Like 2

Share this post


Link to post
Share on other sites

got this error when trying the thumbnails. guess there's a check missing if the field is empty?

2016-08-18 09_35_38-DB Backups • ProcessWire • mustangs2016.dev.png

Share this post


Link to post
Share on other sites

Great tweaks for the Pagelist thumbs! Although I have not yet found the time to try it out, I will surely do it one day :)

I have an issue to report too: one thing I use a lot is FieldAndTemplateEditLinks. Template links work, but Field links do not. The tooltip appears on hover, but nothing happens on click. It used to work, maybe two versions ago, I'm not really sure when though.

Share this post


Link to post
Share on other sites

2016-08-18 09_40_24-Mistelbach Mustangs Basketball.png

my field edit links look like this (not only in modal) on newest devns and default theme

Share this post


Link to post
Share on other sites

@szabesz 

That was a bug, thanks. Grab v048 to fix.

@bernhard 

I couldn't duplicate these issues. Try reinstalling the module (make sure to backup your settings for PageThumbs first).
Perhaps clearing compiled files would also help (bottom at Modules page).

There's a whole lot of check to ensure there's an image to show but of course it may fail somewhere. I tried all combinations at Detais -> Formatted value for image field settings but still wasn't able to show the error.

For the field appearance issue, try hard reload to get rid of cache.

  • Like 1

Share this post


Link to post
Share on other sites

regarding the error: still there. no time to investigate, i dont need it for now.

regarding field tooltips: they appear as they should now, but a click doesn't do anything?!

Share this post


Link to post
Share on other sites

I guess you haven't updated for v048, see above. I'll try to find out the thumbs issue. Could you post your settings for it (the contents of the textarea)?

Share this post


Link to post
Share on other sites

What a great module!

Small feature wish (if this is possible): Can the url helper also handle URL fields within table fields?

  • Like 1

Share this post


Link to post
Share on other sites

Thanks! You mean the profields table, right?

Just checked it and there's a problem: the markup doesn't tell anything about the field type so IUC doesn't fired. I'll see if I can hook and add a class.

  • Like 1

Share this post


Link to post
Share on other sites

v049 is uploaded, featuring centered login page for RenoTweak and some modal Module edit fixes/improvements.

aos_login.png

  • Like 2

Share this post


Link to post
Share on other sites

do i understand you right that this is only for reno theme? why? :)

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 teppo
      Needed a really simple solution to embed audio files within page content and couldn't find a module for that, so here we go. Textformatter Audio Embed works a bit like Textformatter Video Embed, converting this:
      <p>https://www.domain.tld/path/to/file.mp3</p> Into this:
      <audio controls class="TextformatterAudioEmbed"> <source src="https://www.domain.tld/path/to/file.mp3" type="audio/mpeg"> </audio> The audio element has pretty good browser support, so quite often this should be enough to get things rolling 🙂
      GitHub repository: https://github.com/teppokoivula/TextformatterAudioEmbed Modules directory: https://modules.processwire.com/modules/textformatter-audio-embed/
    • By Richard Jedlička
      Tense    
      Tense (Test ENvironment Setup & Execution) is a command-line tool to easily run tests agains multiple versions of ProcessWire CMF.
      Are you building a module, or a template and you need to make sure it works in all supported ProcessWire versions? Then Tense is exactly what you need. Write the tests in any testing framework, tell Tense which ProcessWire versions you are interested in and it will do the rest for you.

      See example or see usage in a real project.
      How to use?
      1. Install it: 
      composer global require uiii/tense 2. Create tense.yml config:
      tense init 3. Run it:
      tense run  
      For detailed instructions see Github page: https://github.com/uiii/tense
       
      This is made possible thanks to the great wireshell tool by @justb3a, @marcus and others.
       
      What do you think about it? Do you find it useful? Do you have some idea? Did you find some bug? Tell me you opinion. Write it here or in the issue tracker.
    • By Chris Bennett
      Hi all, I am going round and round in circles and would greatly appreciate if anyone can point me in the right direction.
      I am sure I am doing something dumb, or missing something I should know, but don't. Story of my life 😉

      Playing round with a module and my basic problem is I want to upload an image and also use InputfieldMarkup and other Inputfields.
      Going back and forth between trying an api generated page defining Fieldgroup, Template, Fields, Page and the InputfieldWrapper method.

      InputfieldWrapper method works great for all the markup stuff, but I just can't wrap my head around what I need to do to save the image to the database.
      Can generate a Field for it (thanks to the api investigations) but not sure what I need to do to link the Inputfield to that. Tried a lot of stuff from various threads, of varying dates without luck.
      Undoubtedly not helped by me not knowing enough.

      Defining Fieldgroup etc through the api seems nice and clean and works great for the images but I can't wrap my head around how/if I can add/append/hook the InputfieldWrapper/InputfieldMarkup stuff I'd like to include on that template as well. Not even sure if it should be where it is on ___install with the Fieldtype stuff or later on . Not getting Tracy errors, just nothing seems to happen.
      If anyone has any ideas or can point me in the right direction, that would be great because at the moment I am stumbling round in the dark.
       
      public function ___install() { parent::___install(); $page = $this->pages->get('name='.self::PAGE_NAME); if (!$page->id) { // Create fieldgroup, template, fields and page // Create new fieldgroup $fmFieldgroup = new Fieldgroup(); $fmFieldgroup->name = MODULE_NAME.'-fieldgroup'; $fmFieldgroup->add($this->fields->get('title')); // needed title field $fmFieldgroup->save(); // Create new template using the fieldgroup $fmTemplate = new Template(); $fmTemplate->name = MODULE_NAME; $fmTemplate->fieldgroup = $fmFieldgroup; $fmTemplate->noSettings = 1; $fmTemplate->noChildren = 1; $fmTemplate->allowNewPages = 0; $fmTemplate->tabContent = MODULE_NAME; $fmTemplate->noChangeTemplate = 1; $fmTemplate->setIcon(ICON); $fmTemplate->save(); // Favicon source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFavicon'; $fmField->label = 'Favicon'; $fmField->focusMode = 'off'; $fmField->gridMode = 'grid'; $fmField->extensions = 'svg png'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Favicon Silhouette source $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeImage"); $fmField->name = 'fmFaviconSilhouette'; $fmField->label = 'SVG Silhouette'; $fmField->notes = 'When creating a silhouette/mask svg version for Safari Pinned Tabs and Windows Tiles, we recommend setting your viewbox for 0 0 16 16, as this is what Apple requires. In many cases, the easiest way to do this in something like illustrator is a sacrificial rectangle with no fill, and no stroke at 16 x 16. This forces the desired viewbox and can then be discarded easily using something as simple as notepad. Easy is good, especially when you get the result you want without a lot of hassle.'; $fmField->focusMode = 'off'; $fmField->extensions = 'svg'; $fmField->columnWidth = 50; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon(ICON); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($fmField); // Create: Open Settings Tab $tabOpener = new Field(); $tabOpener->type = new FieldtypeFieldsetTabOpen(); $tabOpener->name = 'fmTab1'; $tabOpener->label = "Favicon Settings"; $tabOpener->collapsed = Inputfield::collapsedNever; $tabOpener->addTag(MODULE_NAME); $tabOpener->save(); // Create: Close Settings Tab $tabCloser = new Field(); $tabCloser->type = new FieldtypeFieldsetClose; $tabCloser->name = 'fmTab1' . FieldtypeFieldsetTabOpen::fieldsetCloseIdentifier; $tabCloser->label = "Close open tab"; $tabCloser->addTag(MODULE_NAME); $tabCloser->save(); // Create: Opens wrapper for Favicon Folder Name $filesOpener = new Field(); $filesOpener->type = new FieldtypeFieldsetOpen(); $filesOpener->name = 'fmOpenFolderName'; $filesOpener->label = 'Wrap Folder Name'; $filesOpener->class = 'inline'; $filesOpener->collapsed = Inputfield::collapsedNever; $filesOpener->addTag(MODULE_NAME); $filesOpener->save(); // Create: Close wrapper for Favicon Folder Name $filesCloser = new Field(); $filesCloser->type = new FieldtypeFieldsetClose(); $filesCloser->name = 'fmOpenFolderName' . FieldtypeFieldsetOpen::fieldsetCloseIdentifier; $filesCloser->label = "Close open fieldset"; $filesCloser->addTag(MODULE_NAME); $filesCloser->save(); // Create Favicon Folder Name $fmField = new Field(); $fmField->type = $this->modules->get("FieldtypeText"); $fmField->name = 'folderName'; $fmField->label = 'Favicon Folder:'; $fmField->description = $this->config->urls->files; $fmField->placeholder = 'Destination Folder for your generated favicons, webmanifest and browserconfig'; $fmField->columnWidth = 100; $fmField->collapsed = Inputfield::collapsedNever; $fmField->setIcon('folder'); $fmField->addTag(MODULE_NAME); $fmField->save(); $fmFieldgroup->add($tabOpener); $fmFieldgroup->add($filesOpener); $fmFieldgroup->add($fmField); $fmFieldgroup->add($filesCloser); $fmFieldgroup->add($tabCloser); $fmFieldgroup->save(); /////////////////////////////////////////////////////////////// // Experimental Markup Tests $wrapperFaviconMagic = new InputfieldWrapper(); $wrapperFaviconMagic->attr('id','faviconMagicWrapper'); $wrapperFaviconMagic->attr('title',$this->_('Favicon Magic')); // field show info what $field = $this->modules->get('InputfieldMarkup'); $field->name = 'use'; $field->label = __('How do I use it?'); $field->collapsed = Inputfield::collapsedNever; $field->icon('info'); $field->attr('value', 'Does this even begin to vaguely work?'); $field->columnWidth = 50; $wrapperFaviconMagic->add($field); $fmTemplate->fields->add($wrapperFaviconMagic); $fmTemplate->fields->save(); ///////////////////////////////////////////////////////////// // Create page $page = $this->wire( new Page() ); $page->template = MODULE_NAME; $page->parent = $this->wire('pages')->get('/'); $page->addStatus(Page::statusHidden); $page->title = 'Favicons'; $page->name = self::PAGE_NAME; $page->process = $this; $page->save(); } }  
    • By Sebi
      Since it's featured in ProcessWire Weekly #310, now is the time to make it official:
      Here is Twack!
      I really like the following introduction from ProcessWire Weekly, so I hope it is ok if I use it here, too. Look at the project's README for more details!
      Twack is a new — or rather newish — third party module for ProcessWire that provides support for reusable components in an Angular-inspired way. Twack is implemented as an installable module, and a collection of helper and base classes. Key concepts introduced by this module are:
      Components, which have separate views and controllers. Views are simple PHP files that handle the output for the component, whereas controllers extend the TwackComponent base class and provide additional data handling capabilities. Services, which are singletons that provide a shared service where components can request data. The README for Twack uses a NewsService, which returns data related to news items, as an example of a service. Twack components are designed for reusability and encapsulating a set of features for easy maintainability, can handle hierarchical or recursive use (child components), and are simple to integrate with an existing site — even when said site wasn't originally developed with Twack.
      A very basic Twack component view could look something like this:
      <?php namespace ProcessWire; ?> <h1>Hello World!</h1> And here's how you could render it via the API:
      <?php namespace Processwire; $twack = $modules->get('Twack'); $hello = $twack->getNewComponent('HelloWorld'); ?> <html> <head> <title>Hello World</title> </head> <body> <?= $hello->render() ?> </body> </html> Now, just to add a bit more context, here's a simple component controller:
      <?php namespace ProcessWire; class HelloWorld extends TwackComponent { public function __construct($args) { parent::__construct($args); $this->title = 'Hello World!'; if(isset($args['title'])) { $this->title = $args['title']; } } } As you can see, there's not a whole lot new stuff to learn here if you'd like to give Twack a try in one of your projects. The Twack README provides a really informative and easy to follow introduction to all the key concepts (as well as some additional examples) so be sure to check that out before getting started. 
      Twack is in development for several years and I use it for every new project I build. Also integrated is an easy to handle workflow to make outputs as JSON, so it can be used to build responses for a REST-api as well. I will work that out in one section in the readme as well. 
      If you want to see the module in an actual project, I have published the code of www.musical-fabrik.de in a repository. It runs completely with Twack and has an app-endpoint with ajax-output as well.
      I really look forward to hear, what you think of Twack🥳!
      Features Installation Usage Quickstart: Creating a component Naming conventions & component variants Component Parameters directory page parameters viewname Asset handling Services Named components Global components Ajax-Output Configuration Versioning License Changelog
    • By Robin S
      Page Reference Default Value
      Most ProcessWire core inputfield types that can be used with a Page Reference field support a "Default value" setting. This module extends support for default values to the following core inputfield types:
      Page List Select Page List Select Multiple Page Autocomplete (single and multiple) Seeing as these inputfield types only support the selection of pages a Page List Select / Page List Select Multiple is used for defining the default value instead of the Text / Textarea field used by the core for other inputfield types. This makes defining a default value a bit more user-friendly.
      Note that as per the core "Default value" setting, the Page Reference field must be set to "required" in order for the default value to be used.
      Screenshot

       
      https://github.com/Toutouwai/PageReferenceDefaultValue
      https://modules.processwire.com/modules/page-reference-default-value/
×
×
  • Create New...