Jump to content
tpr

AdminOnSteroids

Recommended Posts

Hello @tpr

there is a spelling mistake in the new thumbnail feature:

Screenshot_10.jpg

It should be "Pagelist thumbnails" and not "Pagelist thumbmnails" ;)

Best regards

  • Like 1

Share this post


Link to post
Share on other sites

This is where last minute renaming leads :) Thanks, I'll fix it.

  • Like 2

Share this post


Link to post
Share on other sites

I started adding the field (and template?) edit links, similar to Soma's module HelperFieldLinks (but only links, without the all the field/template data).

My first idea is to use ctrl+click (or long click?) on field label go to the edit page (on new tab, or perhaps modal/panel).
I would like to avoid the clutter but let me know if you would prefer icon or other solution instead.

Also, if you have an idea where to put the "Edit template" link, please share. My idea is ctrl+click on page title.

  • Like 1

Share this post


Link to post
Share on other sites

Ok, I made a huge progress after diving into the Inputfield class where I found those hidden features I needed to put the markup just where I needed.  PW is great- it seems that Ryan (and others) have thought about all the things someone needs WAY before :)

I added the field name to show on hover - it's animated from the left, with a small delay because it was frustrating moving the mouse around and they appeared here and there.

I still need to finish a few things before I publish this but I think the majority of the work is done.

aos-editfieldlink.gif

  • Like 3

Share this post


Link to post
Share on other sites

@tpr This is way cool, really! However, why do we need ctrl? I always forget such hidden features. Simple left click? At least optionally?

Share this post


Link to post
Share on other sites

@tpr I have an issue to report. I always enable the System Notifications module by default, I like it a lot better than the "classic" way... AOS always(?) stopped the admin from being able to display the notifications when the option "Compact header" was on (in other words, when I turn this option on, no notifications are seen anywhere), so I dit not turn it on, after all, I can live without it. However, (probably after the last update) the Sticky header "fell apart" too. Please check this out:

AOS Sticky header with System Notifications enabled.png

I cleared the browser's (Chrome) cache to no avail.

Edited by szabesz
Edit: this issue appeared in the 0.3.6 version, probably...

Share this post


Link to post
Share on other sites

That's another z index issue I guess, but I haven't noticed so far. Ctrl+r didn't help?

Left click in label would be frustrating I think. I could imagine longclick or double click could be much better. Or an icon, optionally.

Share this post


Link to post
Share on other sites
1 hour ago, tpr said:

That's another z index issue I guess, but I haven't noticed so far. Ctrl+r didn't help?

I tried Chrome's "Empty Cache and Hard reload", Incognito and another browser too.

1 hour ago, tpr said:

Left click in label would be frustrating I think. I could imagine longclick or double click could be much better. Or an icon, optionally.

Maybe not the best, but with a _blank target it should do. I support the icon idea too, that is something obvious and normally we have enough room for it, I suppose. I just always forget long clicks, modifiers and such. I use so many of them anyway, that I find hard to remember those I do not use often, and this is such a case (at leas for me).

  • Like 1

Share this post


Link to post
Share on other sites

I see your points about clicks/icons etc but I'm still not convinced which would be the best way.

I also see the issue with System Notifications. I'll see what can I do, I hope there will be an easy fix.

  • Like 1

Share this post


Link to post
Share on other sites

As for now I allowed clicking on the fieldname that slides in to edit the field. It opens by default in new tab (configurable to open in panel or modal).

I'll keep the ctrl-click option too.

(AOS's ctrl+s is addictive. I find myself more and more trying to save my comments here that way :))

  • Like 2

Share this post


Link to post
Share on other sites

Interesting module indeed. Can't say I'm one for too much tweaking, but some of the features here are quite helpful. Specifically, I like hotkeys and textarea autosizing. In terms of Reno theming, it's quite interesting, but I can't say I like the sidebar tweaks, specifically the non-linear items (and the flash menus don't work). I have, however, taken a liking to the sticky white compact header. +1 for that.

Just a note: I have tested this in 2.8 (not extensively) and it seems to work fine, as it should. The only differenc between 2.8 and 3.0 is that 2.8 does not have namespaces, but both versions share the same code. As such, and if I were the module author, I would drop the dependency to 2.8.

Oh, and flyout panels (like debug mode tools) needs a higher z-index (testing with sticky header and sidebar on - Reno theme).

Share this post


Link to post
Share on other sites

Thanks! There were many z-index issues so far and one of the latest fix was more subtle, and there are some side effects that needs to be eliminated. Panels are already fixed in the latest version (unreleased yet).

I'll check the flash menus too.

  • Like 3

Share this post


Link to post
Share on other sites

v038 is uploaded with fixes for perhaps all the issues reported above, thanks for all!

This also contains the FieldEditLinks tweak and other fixes.

PW compatibility was set to 2.8, though as I see the modules directory doesn't have this option.

  • Like 1

Share this post


Link to post
Share on other sites

Another version today (039) with a redesigned settings page:

aos_settings.png

  • Like 4

Share this post


Link to post
Share on other sites

v040 brings InputfieldURLChecker to AOS!

This also means that the "standalone" IUC module will be discontinued, only this submodule will be further developed.

All of its features were kept but some were implemented differently (hopefully for the good), so if you encounter an issue please report.

  • Like 2

Share this post


Link to post
Share on other sites

The "panel" mode fails for repeaters but that's I think a PW issue (IUC). The URL is opened in a new tab so it's not a critical issue. I have an idea for a solution but I'm not sure it would work. It was a bad thing to realize that PW panels are not dynamic, meaning they are determined on page load, but I found a workaround that apparently works.

  • Like 2

Share this post


Link to post
Share on other sites

The latest update contains a fix for IUC links inside repeates, though they doesn't work in ajax-loaded fields - PW doesn't add the markup there, no idea why.

There's an "Enable module" toggle too to enable/disable the module without uninstall.

Main changes:

  • workaround to use panel mode for repeaters and other fixes for InputfieldURLChecker

  • added "Enable module" toggle

  • layout improvements for sticky and compact headers (RenoTweaks)

  • miniScrollbar now works with stickyHeader (previously only with compactHeader)

  • more general solution for HoverSaveDropdown

  • Like 2

Share this post


Link to post
Share on other sites

v042:

  • modalModuleEdit option to ModalTweaks: edit modules in a modal dialog. Reloads the Modules page on module uninstall.
  • compactModuleList module names are "full-cell" sized for better clickability

  • breadcrumbs ctrl+click fix for Default admin theme
  • Like 1

Share this post


Link to post
Share on other sites
On 8/8/2016 at 6:28 AM, Mike Rockett said:

I can't say I like the sidebar tweaks, specifically the non-linear items

From v043 that is just uploaded you have the option to disable the inline sidebar items. This feature is now available for all sidebar modes unlike before.

For the modalModuleEdit tweak there are two additions: a secondary "X Submit" button for submit+exit, and ESC also closes the modal dialog.

  • Like 4

Share this post


Link to post
Share on other sites

@tpr I just want to say a big thank you! I'm back from holidays so I could actually update the module and it works fine so far. The new appearance of the normal Sticky Header (not the compact one) with the always show search field is my most favorite setting.The "dropdown" version of System Notifications is great improvement too.

Just one issue I have: with the above mentioned normalSticky Header + always show search field setting I do not have access to the search field in narrow viewport, the search field simply disappears.

All in all, you managed to improve the Reno Theme in such an extent that there is no more reason to prefer the classic admin theme to it.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks! Does it happen under 960px page width? AOS doesn't do anything there it's "desktop-only". Most of the (admin) style tweaks behave this way.

  • 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 eelkenet
      Hi! I've created a small Inputfield module called InputfieldFloatRange which allows you to use an HTML5 <input type="range" ../> slider as an InputField. I needed something like this for a project where the client needs to be able to tweak this value more based on 'a feeling' than just entering a boring old number. Maybe more people can use this so I'm hereby releasing it into the wild.  
       
      What is it?
      The missing range slider Inputfield for Processwire. 
      What does it do?
      This module extends InputfieldFloat and allows you to use HTML5 range sliders for number fields in your templates.
      It includes a visible and editable value field, to override/tweak the value if required.  
      Features
      Min/max values Precision (number of decimals) Steps (Read more) Manual override of the selected value (will still adhere to the rules above) Usage
      Clone / zip repo Install FieldtypeFloatRange, this automatically installs the Inputfield Create new field of type `Float (range)` or convert an existing `Float`, `Integer` or `Text` field. To render the field's value simply echo `$page->field` Demo
      A field with Min=0, Max=1, Step=0.2, Precision=2

      Field with settings Min=0, Max=200, Step=0.25, Precision=2

       
      Todo
      Make the display-field's size configurable (will use the Input Size field setting)  Hopefully become redundant If it's usable for others I'll add it to the Modules list  
      Changelog
      v002
      - Fix issue where setting the step value to an empty value created problem with validation
      - Make the display-field optional 
      v001
      - Initial release
       
      Thanks!
       
       
    • By Robin S
      Another little admin helper module...
      Template Field Widths
      Adds a "Field widths" field to Edit Template that allows you to quickly set the widths of inputfields in the template.

      Why?
      When setting up a new template or trying out different field layouts I find it a bit slow and tedious to have to open each field individually in a modal just to set the width. This module speeds up the process.
      Installation
      Install the Template Field Widths module.
      Config options
      You can set the default presentation of the "Field widths" field to collapsed or open. Field widths entered into the Template Field Widths inputfield are only applied if the Edit Template form is submitted with the Template Field Widths inputfield in an opened state. "Collapsed" is the recommended setting if you think you might also use core inputs for setting field widths in a template context. You can choose Name or Label as the primary identifier shown for the field. The unchosen alternative will become the title attribute shown on hover. You can choose to show the original field width next to the template context field width.  
      https://github.com/Toutouwai/TemplateFieldWidths
      https://modules.processwire.com/modules/template-field-widths/
    • By adrian
      Tracy Debugger for ProcessWire
      The ultimate “swiss army knife” debugging and development tool for the ProcessWire CMF/CMS

       
      Integrates and extends Nette's Tracy debugging tool and adds 35+ custom tools designed for effective ProcessWire debugging and lightning fast development
      The most comprehensive set of instructions and examples is available at: https://adrianbj.github.io/TracyDebugger
      Modules Directory: http://modules.processwire.com/modules/tracy-debugger/
      Github: https://github.com/adrianbj/TracyDebugger
      A big thanks to @tpr for introducing me to Tracy and for the idea for this module and for significant feedback, testing, and feature suggestions.
    • By adrian
      This module allows you to automatically rename file (including image) uploads according to a configurable format
      This module lets you define as many rules as you need to determine how uploaded files will be named and you can have different rules for different pages, templates, fields, and file extensions, or one rule for all uploads. Renaming works for files uploaded via the admin interface and also via the API, including images added from remote URLs.   Github: https://github.com/adrianbj/CustomUploadNames
      Modules Directory: http://modules.processwire.com/modules/process-custom-upload-names/
      Renaming Rules
      The module config allows you to set an unlimited number of Rename Rules. You can define rules to specific fields, templates, pages, and file extensions. If a rule option is left blank, the rule with be applied to all fields/templates/pages/extensions. Leave Filename Format blank to prevent renaming for a specific field/template/page combo, overriding a more general rule. Rules are processed in order, so put more specific rules before more general ones. You can drag to change the order of rules as needed. The following variables can be used in the filename format: $page, $template, $field, and $file. For some of these (eg. $field->description), if they haven't been filled out and saved prior to uploading the image, renaming won't occur on upload, but will happen on page save (could be an issue if image has already been inserted into RTE/HTML field before page save). Some examples: $page->title mysite-{$template->name}-images $field->label $file->description {$page->name}-{$file->filesize}-kb prefix-[Y-m-d_H-i-s]-suffix (anything inside square brackets is is considered to be a PHP date format for the current date/time) randstring[n] (where n is the number of characters you want in the string) ### (custom number mask, eg. 001 if more than one image with same name on a page. This is an enhanced version of the automatic addition of numbers if required) If 'Rename on Save' is checked files will be renamed again each time a page is saved (admin or front-end via API). WARNING: this setting will break any direct links to the old filename, which is particularly relevant for images inserted into RTE/HTML fields. The Filename Format can be defined using plain text and PW $page variable, for example: mysite-{$page->path} You can preserve the uploaded filename for certain rules. This will allow you to set a general renaming rule for your entire site, but then add a rule for a specific page/template/field that does not rename the uploaded file. Just simply build the rule, but leave the Filename Format field empty. You can specify an optional character limit (to nearest whole word) for the length of the filename - useful if you are using $page->path, $path->name etc and have very long page names - eg. news articles, publication titles etc. NOTE - if you are using ProcessWire's webp features, be sure to use the useSrcExt because if you have jpg and png files on the same page and your rename rules result in the same name, you need to maintain the src extension so they are kept as separate files.
      $config->webpOptions = array(     'useSrcExt' => false, // Use source file extension in webp filename? (file.jpg.webp rather than file.webp) ); Acknowledgments
      The module config settings make use of code from Pete's EmailToPage module and the renaming function is based on this code from Ryan: http://processwire.com/talk/topic/3299-ability-to-define-convention-for-image-and-file-upload-names/?p=32623 (also see this post for his thoughts on file renaming and why it is the lazy way out - worth a read before deciding to use this module). 
       
       
      NOTE:
      This should not be needed on most sites, but I work with lots of sites that host PDFs and photos/vectors that are available for download and I have always renamed the files on upload because clients will often upload files with horrible meaningless filenames like:
      Final ReportV6 web version for John Feb 23.PDF

×
×
  • Create New...