tpr

Module
AdminOnSteroids

813 posts in this topic

one thing i'm missing sometimes on the template editor is a shortcut for editing field widths. a slider from 10 - 100% instantly changing the fields width would be a great addition in my opinion :) often changing one field's width makes it necessary to change the other field's width as well (eg adding a field to a row of 4 fields with 25% makes it necessary to change all fields to 20%

it would be great to add the field and drag all field's width from 25 to 20 without the need to open each fields settings, clicking on the display tab, changing value, saving field, closing modal...

all other settings are fine being available behind one click.

1 person likes this

Share this post


Link to post
Share on other sites

Forget the drag and drop idea , a link, fe next to the page title, that opens the template editor in a modal window to show all the fields of the template, would fit the requirements.:)

Screenshot_6.jpg

Share this post


Link to post
Share on other sites

By not reading the manual? :)

Field width changing would be great, provided that a good and simple GUI could be found. My first idea was to change the asm fields width according to the field widths, that would allow instant visual feedback, and allow field width change by dragging their right side. I haven't used such Js library so I don't know how hard that would be to implement.

Share this post


Link to post
Share on other sites

i think the most simple solution would be to make the status text on the right edge of asm select clickable and link directly to the second tab:

<span class="asmListItemStatus">Text 33%</span> --> editurl#inputfieldConfig

would that work? it would save 1 click per field and would still need 1 click to save. maybe 1 inputfield per field directly inside the asm select would be even better? then it would be really easy to change multiple fields in a very short time...

btw: has anyone ever kind of a "newline"-field? for example if you have different number of fields in one line depending on field dependencies. if you have 2 lines with columns < 100% that can lead to wrong field orders. workaround is to put those fields inside a fieldset, but i think there could be a better solution...

Share this post


Link to post
Share on other sites

v117 contains @bernhard's idea (see above). I've also managed to add the "100%" text on full-width fields because this makes percentages align nicer.

asmWidths.gif

3 people like this

Share this post


Link to post
Share on other sites
On ‎27‎/‎12‎/‎2016 at 2:24 PM, bernhard said:

btw: has anyone ever kind of a "newline"-field? for example if you have different number of fields in one line depending on field dependencies. if you have 2 lines with columns < 100% that can lead to wrong field orders. workaround is to put those fields inside a fieldset, but i think there could be a better solution...

I dont think there is such field, I would perhaps add some CSS to fix (clear or before-after pseudos).

1 person likes this

Share this post


Link to post
Share on other sites

thank you tpr for the new update :) also thank you for the css fix. didn't think about that!

what do you think of adding often used widths as a clickable shortcut to the form? clicking it could also save + close the modal :)

2017-01-02 18_52_11-Edit Template_ rockproject • hrd.baumrock.com.png

 

shortcuts could be

  • 20
  • 25
  • 33
  • 34
  • 40
  • 50
  • 60
  • 75
  • 80
  • 100

 

1 person likes this

Share this post


Link to post
Share on other sites

Not sure about this, it wouldn't save too much time imo. Auto save would be also an issue because users could have edited other fields and perhaps they wouldn't like to save.

2 people like this

Share this post


Link to post
Share on other sites

I've added simple svg backgrounds to show values as guidelines. It's not 100% perfect but close :)

aos-columwidth-scale.gif

3 people like this

Share this post


Link to post
Share on other sites
On 12/21/2016 at 3:29 PM, tpr said:

I tried it on two servers (livehost), in a subdir and in the root.

You could try to uncomment the series of bd() calls in line 913 and further down in 961 to see what paths/urls AOS tries to use (requires Tracy Debugger).

You can update the module from the directory as it contains these fixes.

Sorry for delay in respond, Just returned home from out of town during holiday.  Pardon for my ignorance, Tracy Debugger? Is that PW modules? Plugin? I have looked into this https://processwire.com/blog/posts/introducing-tracy-debugger/ and still not yet sure understand how or where I can preform debugging. Can you explain? 

Share this post


Link to post
Share on other sites

Yes, Tracy Debugger is a module which can help you find problems with your code or in others code as in this case too.

Once you install it and see the "Debugger bar" (refer to the introduction post you linked above) then if you uncomment those lines I mentioned you should see the values if you click on the bar. This way you can see why the path/url differs.

1 person likes this

Share this post


Link to post
Share on other sites

Okay, Tracy Debugger module is installed, I 've uncomment  line :913 bd($ckeCSS);  and :961 bd($adminCSS); on AdminOnSteroids.module inside .AdminOnSteroids directory.I have read and followed carefully, I understand am supposed to look for debug bar once debugger is installed. Apparently, its not show any bar. I use chrome browser with firelogger installed. Yes, I've confirmed debugger is enabled, The bar to display at front and back is checked, the uncommented, line 913 and 961 and cleared cache after Tracy debugger module is installed. 

Tracy1.JPG

Tracy2.JPG

Now I am getting confused... what am I missing?

Share this post


Link to post
Share on other sites

@Speed - if this is on a non local server, you will either need to force to "Development" mode (change from Detect), or check the "Force superuser development mode" button.

Tracy must be in development mode to show the debug bar. If it's a remote server, DETECT will determine that it should be in PRODUCTION mode.

1 person likes this

Share this post


Link to post
Share on other sites
9 minutes ago, adrian said:

if this is on a non local server, you will either need to force to "Development" mode (change from Detect), or check the "Force superuser development mode" button.

@adrian - Enabling 'Development' mode got debugger bar to show up. (PW in livehost) Thank you. 

@tpr - let me guess, is that what I should look for??

Tracy3.JPG

 

Share this post


Link to post
Share on other sites
Just now, Speed said:

let me guess, is that what I should look for??

You want to look at the Dumps Recorder panel - the icon looks like a dump truck :)

Share this post


Link to post
Share on other sites

So it contains no dumps? Did you uncomment those bd() calls that @tpr pointed out?

Share this post


Link to post
Share on other sites

yes...Confirmed,  I have commented it out.  (This line was commented out in live server with editor.)

Share this post


Link to post
Share on other sites

v119 comes with a new "Apply to all" button to update all dropdowns with the selected option on the "Add field to templates" page (see the screen capture below), requested by @gmclelland

I've also updated the "Remove all" button on the field deletion confirmation page. Now it reads "Check all" and the default submit button can be used for deletion instead. The same "Check all" button is added to the other field deletion confirmation page (accessed from the Field edit page, Actions tab).

All these are under the "Misc" submodule. Please re-check the checkbox "Add helper buttons to batch field add/remove confirmation pages" because it was renamed.

aos-field-batch-actions.gif

5 people like this

Share this post


Link to post
Share on other sites

Just committed a small update to GitHub which expands the select box if there's only one of it (field add confirmation page):

aos-expand-select.png

2 people like this

Share this post


Link to post
Share on other sites

v123 is up, and here are the latest additions:

1.2.3
- Hotkeys: focus filterbox on alt+s

1.2.2
- title change case button improvements

1.2.1 
- Misc: option to move empty trash confirmation checkbox above trash items

2 people like this

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 cosmicsafari
      Hi All,
      I am working on a module at the moment which in theory will create a few simple fields, templates and pages which will all be linked together.
      All is going well so far, I have it generating said fields, templates and pages, however I would like to also set the pages sort order and icon programmatically at this stage also.
      I have yet to see any documentation or any other threads where this has been brought up, is it even possible programmatically without interacting with the database directly?
      This is the snippet which is generating my pages on the fly at the moment.
      foreach($arrayOfPages as $name => $page) { $p = new Page(); $p->template = 'page'; $p->name = $page['URL']; $p->title = $name; $p->parent = wire('pages')->get('name='.$page['parent']); //is it possible to set the icon and sort order at this point, before saving? $p->save(); }  
    • By Robin S
      I have had this module sitting in a 95% complete state for a while now and have finally made the push to get it out there. Thanks to @teppo for his Hanna Code Helper module which I referred to and borrowed from during development.
      http://modules.processwire.com/modules/hanna-code-dialog/
      https://github.com/Toutouwai/HannaCodeDialog
      HannaCodeDialog
      A module for ProcessWire CMS/CMF. Provides a number of enhancements for working with Hanna Code tags in CKEditor. The main enhancement is that Hanna tags in a CKEditor field may be double-clicked to edit their attributes using core ProcessWire inputfields in a modal dialog.
      Requires the Hanna Code module.
      Installation
      Install the HannaCodeDialog module using any of the normal methods.
      For any CKEditor field where you want the "Insert Hanna tag" dropdown menu to appear in the CKEditor toolbar, visit the field settings and add "HannaDropdown" to the "CKEditor Toolbar" settings field.
      Module configuration
      Visit the module configuration screen to set any of the following:
      Exclude prefix: Hanna tags named with this prefix will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Exclude Hanna tags: Hanna tags selected here will not appear in the CKEditor toolbar dropdown menu for Hanna tag insertion. Background colour of tag widgets: you can customise the background colour used for Hanna tags in CKEditor if you like. Dialog width: in pixels Dialog height: in pixels Features
      Insert tag from toolbar dropdown menu
      Place the cursor in the CKEditor window where you want to insert your Hanna tag, then select the tag from the "Insert Hanna tag" dropdown.

      Advanced: if you want to control which tags appear in the dropdown on particular pages or templates you can hook HannaCodeDialog::getDropdownTags. See the forum support thread for examples .
      Edit tag attributes in modal dialog
      Insert a tag using the dropdown or double-click an existing tag in the CKEditor window to edit the tag attributes in a modal dialog.

      Tags are widgets
      Hanna tags that have been inserted in a CKEditor window are "widgets" - they have a background colour for easy identification, are protected from accidental editing, and can be moved within the text by drag-and-drop.

      Options for tag attributes may be defined
      You can define options for a tag attribute so that editors must choose an option rather than type text. This is useful for when only certain strings are valid for an attribute and also has the benefit of avoiding typos.
      Add a new attribute for the Hanna tag, named the same as the existing attribute you want to add options for, followed by "__options". The options themselves are defined as a string, using a pipe character as a delimiter between options. Example for an existing attribute named "vegetables":
      vegetables__options=Spinach|Pumpkin|Celery|Tomato|Brussels Sprout|Potato You can define a default for an attribute as normal. Use a pipe delimiter if defining multiple options as the default, for example:
      vegetables=Tomato|Potato Dynamic options
      Besides defining static options as above, you can use one Hanna tag to dynamically generate options for another. For instance, you could create a Hanna tag that generates options based on images that have been uploaded to the page, or the titles of children of the page.
      Your Hanna tag that generates the options should echo a string of options delimited by pipe characters (i.e. the same format as a static options string).
      You will probably want to name the Hanna tag that generates the options so that it starts with an underscore (or whatever prefix you have configured as the "exclude" prefix in the module config), to avoid it appearing as an insertable tag in the HannaCodeDialog dropdown menu.
      Example for an existing attribute named "image":
      image__options=[[_images_on_page]] And the code for the _images_on_page tag:
      <?php $image_names = array(); $image_fields = $page->fields->find('type=FieldtypeImage')->explode('name'); foreach($image_fields as $image_field) { $image_names = array_unique( array_merge($image_names, $page->$image_field->explode('name') ) ); } echo implode('|', $image_names); Advanced: define or manipulate options in a hook
      You can hook HannaCodeDialog::prepareOptions to define or manipulate options for a Hanna tag attribute. Your Hanna tag must include a someattribute__options attribute in order for the hook to fire. The prepareOptions method receives the following arguments that can be used in your hook:
      options_string Any existing string of options you have set for the attribute attribute_name The name of the attribute the options are for tag_name The name of the Hanna tag page The page being edited If you hook after HannaCodeDialog::prepareOptions then your hook should set $event->return to an array of option values, or an associative array in the form of $value => $label.
      Choice of inputfield for attribute
      You can choose the inputfield that is used for an attribute in the dialog.
      For text attributes the supported inputfields are text (this is the default inputfield for text attributes so it isn't necessary to specify it if you want it) and textarea. Note: any manual line breaks inside a textarea are removed because these will break the CKEditor tag widget.
      Inputfields that support the selection of a single option are select (this is the default inputfield for attributes with options so it isn't necessary to specify it if you want it) and radios.
      Inputfields that support the selection of multiple options are selectmultiple, asmselect and checkboxes.
      You can also specify a checkbox inputfield - this is not for attributes with defined options but will limit an attribute to an integer value of 1 or 0.
      The names of the inputfield types are case-insensitive.
      Example for an existing attribute named "vegetables":
      vegetables__type=asmselect Descriptions and notes for inputfields
      You can add a description or notes to an attribute and these will be displayed in the dialog.
      Example for an existing attribute named "vegetables":
      vegetables__description=Please select vegetables for your soup. vegetables__notes=Pumpkin and celery is a delicious combination. Notes
      When creating or editing a Hanna tag you can view a basic cheatsheet outlining the HannaCodeDialog features relating to attributes below the "Attributes" config inputfield.
      Troubleshooting
      HannaCodeDialog includes and automatically loads the third-party CKEditor plugins Line Utilities and Widget. If you have added these plugins to your CKEditor field already for some purpose and experience problems with HannaCodeDialog try deactivating those plugins from the CKEditor field settings.
    • By joshuag
      Introducing our newest [commercial] module:
      Recurme
      Processwire Recurring Dates Field & Custom Calendar Module.
      http://www.99lime.com/modules/recurme/
      One Field to Recur them ALL…
      A Recurring Dates InputField for your Processwire templates. The InputField you’ve been waiting for.
      Complex RRule date repeating in a simple and fast user interface.
      Use the super simple, & powerful API to output them into your templates.
      example:
      <? // easy to get recurring events $events = $recurme->find(); // events for this day $events = $recurme->day(); // events for this week $events = $recurme->week(); // events for this month $events = $recurme->month(); ?> <? // Loop through your events foreach($events as $event){ echo $event->title; echo $event->start_date; echo $event->rrule; echo $event->original->url; ... } ?> Unlimited Custom Calendars.
      Imagine you could create any calendar you wanted on your website. Use recurring events with the Recurme field, or use your own Processwire pages and date fields to render calendars… it’s up to you. Fully customizable. Make as many calendars as you like. Get events from anywhere. Recurme does all the hard date work for you.
      Unlimited Custom Admin Calendars too.
      Hope you like it  ,
       Joshua & Eduardo from 99Lime.
       




    • By valan
      At our site we use both email and phone authorizations at frontend. To make life easier, I've developed HelperPhone pack that handles phone numbers. This pack includes following modules for ProcessWire CMS/CMF:
      FieldtypePhoneNumber: module that stores phone numbers InputfieldPhoneNumber: module that renders inputfield for phone numbers HelperPhone: module that loads PhoneNumber and PhoneNumberConst classes, and 'libphonenumber' namespace All these modules require included PW WireData-derived class PhoneNumber and PhoneNumberConst.
      PhoneNumber class is a thin wrapper over giggsey/libphonenumber-for-php, itself is port of Google's libphonenumber. PhoneNumberConst class stores constants, used by PhoneNumber class Usage: PhoneNumber class
      $phone = '8 (916) 318-07-29 ext 1234'; // input string could be in any phone-recognizable format $phoneNumber = new PhoneNumber($phone, 'RU'); // or wire('modules')->get('HelperPhone')->makePhoneNumber($phone, 'RU'); echo ($phoneNumber->isValidNumber() ? 'Yes':'No'); // Yes echo ($phoneNumber->isValidNumberForRegion($regionCode) ? 'Yes':'No'); // Yes echo $phoneNumber->getNumberTypeTitle(); // Mobile echo $phoneNumber->getCountryCode(); // 7 echo $phoneNumber->getRegionCode(); // RU echo $phoneNumber->getNationalNumber(); // 9163180729 echo $phoneNumber->getExtension(); // 1234 echo $phoneNumber->formatForCallingFrom('US') // 011 7 916 318-07-28 echo $phoneNumber->formatForCallingFrom('GE') // 00 7 916 318-07-28
      For more methods and properties please refer to PhoneNumber and PhoneNumberConst source files. Need more? Check giggsey/libphonenumber-for-php and use it by accessing $phoneNumber->phoneNumber property - it is instance of \libphonenumber\PhoneNumber or null (if empty).
      Usage: field
      Note: on field creation, make sure that you've configured field settings
      Default region: assumed region if input phone number string is not in international format (starts with '+', etc)
      Enabled/disabled phone extentions: if disabled, phone extension will be removed on field save.
      Phone field settings in example below: default region code 'RU', phone extensions are enabled
      echo $page->phone; // +79163180729 // Note1: $page->phone stores instance of PhoneNumber and renders to string in E164 format. // Note2: E164 format does not include extension. echo $page->getFormatted('phone'); // +7 916 318-07-29 ext. 1234 echo $page->getUnformatted('phone'); // +79163180729 echo $page->phone->format(PhoneNumberConst::RFC3966); // tel:+7-916-318-07-29;ext=1234 echo $page->phone->getNationalNumber(); // 9163180729 Usage: PW selectors
      FieldtypePhoneNumber is instance of FieldtypeText. It stores phone numbers and extensions as string in E164 format with #extention (if provided by user and enabled in settings) E.g. in db it looks like this: '+79163180729#1234'. This makes it easy to query fields as any text field.
      echo $pages->find([     'template' => 'my_temlate',     'phone^=' => '+79163180729', ]); // will echo page ids where phone starts with '+79163180729' Finally
      I've decided to put it here first and later to Modules directory (based on your feedbacks).
      GitHub: https://github.com/valieand/HelperPhone
      Enjoy
    • By justb3a
      Little admin helper module: Using this module you can view all template cache settings at once. E.g. cache status, cache time (configurable). Furthermore it adds the functionality to clear the entire template cache or just the template cache for a given template. Note that this may cause a temporary delay for one or more requests while pages are re-cached.

       
      GitHub: https://github.com/justb3a/processwire-templatecacheoverview