tpr

Module
AdminOnSteroids

813 posts in this topic

7 hours ago, tpr said:

I added 1px border to the submenu so it will always have at least 0.5px overlap. I'll add this to the next version of AOS.


#topnav .topnav {
    border-right: 1px solid transparent;
}

 

I don't think that will work. The submenu is positioned using the jQueryUI Position utility. Anything you do in CSS to change the dimensions and/or position of the submenu is accounted for by Position and it will just move the submenu further over as a result.

The admin menus would be so much more manageable if they were just simple nested <ul>s. I don't understand why the admin theme takes the complicated approach it does.

Share this post


Link to post
Share on other sites

You're right it's not working but because the selector should be only '.topnav', these menus are not children of '#topnav'. It seems that jQuery UI doesn't use the border for the calculation. The screencap shows the border increased to 10px:

aos-topnav-overlap.gif

1 person likes this

Share this post


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

It seems that jQuery UI doesn't use the border for the calculation.

Ah, that's great news!

When I was trying to resolve the problem I was focusing trying to adjust the position of the child <ul>s that flyout to the right - it didn't occur to me to try adjusting the parent <ul>. Good stuff!

Share this post


Link to post
Share on other sites

When editing field settings (Setup > Fields > my_field) I'm seeing an error:

PHP Notice: Trying to get property of non-object in ...\modules\AdminOnSteroids\AdminOnSteroids.module:1224

BTW, thanks for making this configurable:

2016-11-28_214808.png

1 person likes this

Share this post


Link to post
Share on other sites

Thanks, that's already corrected here. Actually I removed that part entirely - I added page-template and page-id classes to the body but there were already classes for that (ProcessPageEdit-id-1033 etc).

1 person likes this

Share this post


Link to post
Share on other sites

v106 is up some fixes to the issues mentioned above. I couldn't duplicate adrian's issue not showing the action labels on hover so it's probably not fixed :)

2 people like this

Share this post


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

I couldn't duplicate adrian's issue not showing the action labels on hover so it's probably not fixed

In case it helps, here is the current generated source of one page in the list:

<div class="PageListItem PageListTemplate_course PageListID1018"><a href="#" title="/rock-climbing/basic-rock/" class="PageListPage label"><span data-pid="1018" class="label_title">Basic Rock</span></a><span class="PageListNumChildren detail"></span><ul class="PageListActions actions"><li class="PageListActionEdit"><a href="/admin/page/edit/?id=1018" class="pw-modal pw-modal-large pw-modal-longclick" data-buttons="#ProcessPageEdit > .Inputfields > .InputfieldSubmit .ui-button">Edit</a></li><li class="PageListActionView"><a href="http://sradev.skaharockclimbing.com/rock-climbing/basic-rock/" class="pw-modal pw-modal-large pw-modal-longclick">View</a></li><li class="PageListActionMove"><a href="#">Move</a></li><li class="PageListActionEdit"><a href="http://sradev.skaharockclimbing.com/admin/setup/template/edit?id=44" class="pw-modal pw-modal-large pw-modal-longclick" data-buttons="#ProcessPageEdit > .Inputfields > .InputfieldSubmit .ui-button">course</a></li><li class="PageListActionExtras ui-priority-secondary"><a href="#" class="clickExtras"><i class="fa fa-angle-right"></i></a></li></ul></div>

Any chance it comes back to that span issue that was affecting the page ID being shown? Probably not - thinking a quick guess :)

Share this post


Link to post
Share on other sites

This is trivial, but the template edit link in the Page List hover actions is 1 pixel lower than the other actions. Same in Chrome and Firefox.

2016-11-29_115413.png

Share this post


Link to post
Share on other sites

It's intentional, I wanted it to be smaller. In the Reno theme it looks OK but I agree that it's not that beautiful in the default. I'll remove the styles for the default theme in the next version.

2 people like this

Share this post


Link to post
Share on other sites

v107 is up, containing a new feature for pagelist items: "Use middle mouse click/ctrl+click to View/Edit page".

1 person likes this

Share this post


Link to post
Share on other sites

Just a request for when you're bored. I think it would be nice to have more than one: "aos_column_break" field available. If you are making use of fieldset tabs it would be great to be able to break up the fields on each of the tabs. Maybe if it was just possible to manually create "aos_column_break_1", "aos_column_break_2" etc.

Share this post


Link to post
Share on other sites

There's a way without additional colbreak fields, see the readme. I didn't want to flood the admin with extra fields.

1 person likes this

Share this post


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

There's a way without additional colbreak fields, see the readme. I didn't want to flood the admin with extra fields.

Ah thank you - I didn't see that!

Just an FYI - adding aos_column_break to a tab actually does seem to work - just of course only for that tab :)

Share this post


Link to post
Share on other sites

Great, thanks :) There's a funky calculation going on when setting the columns so I decided not to risk things with multiple aos_column_break fields :)

1 person likes this

Share this post


Link to post
Share on other sites

v108 is up, containing a new feature to add markup to pagelist items:

It uses the [tag.class][/tag] syntax, making it flexible to use. The module also contains default styling for the "em" tag (which is the recommended):

{title} [em.company][b]{company_ref.title}[/b][/em] [em][i]images: {images.count}[/i][/em]

Output in the pagelist:

aos-pagelistmarkup.png

3 people like this

Share this post


Link to post
Share on other sites

Nice feature!! Is there a way to add the label of the field in the tag? Instead of hardcoding "images" in

[em][i]images: {images.count}[/i][/em]

is it possible fe to output the label of the image field like

[em][i]{images.label}: {images.count}[/i][/em]

My site is multilingual and therefore it would be nice if the word "images" could be available in several languages. If not, anyway! ^_^

Best regards

Share this post


Link to post
Share on other sites

Sorry, this tweak is only a regex preg_replace, nothing more.

But this one works - kudos to Tracy Debugger letting me find this out :)

{images.field.label}: {images.count}

 

2 people like this

Share this post


Link to post
Share on other sites

Indeed. Hardcoding the language ID works (images.field.label1017) but the substitution by PW runs before I could replace the ID.

Share this post


Link to post
Share on other sites

Yesterday I was not completely happy with the pagelistmarkup feature because occassionally I need to output dates and as I store them unformatted (unix timestamp) I can't output them formatted in the page list. Now I have added a feature to set the formatting using the following syntax (borrowed from Latte template engine):

({date}|date:%Y. %B %d.)

As you can see it's very flexible, the only issue remained is setting the locale. My idea is to leave this thing to the developer and do not add it here (maybe a hook?). Of course this issue only affects multilanguage sites where you would need to output month names in different languages too, but using only number format is OK.

1 person likes this

Share this post


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

Many Thanks!!!!!!! Unfortunately it only fetches the label in the default language, but anyway.

Got it working by adding a token %LANG_ID% - will be included in the next update.

{images.field.label%LANG_ID%}

 

2 people like this

Share this post


Link to post
Share on other sites

Still wasn't perfect - "images.field.label" worked only for Image fields but not for other.

However I figured out that this one actually works (for a Date field named "date_created"):

{fieldgroup.date_created.label}

It still returns the label int he default language, but with the %lang_id% it's outputted fine:

{fieldgroup.date_created.label%lang_id%}

 

2 people like this

Share this post


Link to post
Share on other sites

Never thought that the "Always show pagelist actions" could be beneficial to me but I was wrong. While setting editor access, it is handy to see whether they are able to add new pages to a page or not, without needing to hover the pagelist item.

Btw, here's a trick I use to simplify setting up roles. I use the same "basic-page" template for several pages, and some of them may have children, some not. But you can't set it page level, only at template level. What I do is create a new template "basic-page-nochildren" and set it's fieldgroup to "basic-page" (need to set $config->advanced to see this feature on the template edit page). Then assign these templates to pages that shouldn't have children, and because of the same fieldgroup, they will also have the same fields as "basic-page".

Update: don't forget to make the template "basic-page-nochildren" viewable by creating a template file for it, or set the "Alternate Template Filename" to "basic-page" on  "basic-page-nochildren" template (Files tab)

3 people like this

Share this post


Link to post
Share on other sites

I noticed that the position:relative rule that AOS adds to h1 makes the select dropdowns in the ProDevTools API Explorer unclickable.

2016-12-14_120455.png

Share this post


Link to post
Share on other sites

I don't know if this have been mentioned earlier in this posts. So many posts to scan and see if it have been mentioned. But... I am encountering a little glitch with AOS using Reno Theme. Everytime I select input, I get kicked out when pressed shift key. This is getting so annoying, wondering if you can look into it? 

 

 

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 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
    • By Steven Veerbeek
      Hi,
      I am trying to create a module for a webshop in which I can predefine a number of thumbnail sizes for my product images. I was thinking of storing each of these image sizes as a child page with 'width' and 'height' fields under the module page , so I can use a PageTable input field in my module to easily manage them.
      I know how to create a Pagetable field and add it to templates so I can use it in regular pages, but because I am planning on implementing some other functionalities that (I think) can't be achieved with a regular page, I need the PageTable field to work within a module.
      So far I have come up with this piece of code by trial and error:
      $page = $this->page; $field_sizes = $this->modules->get("InputfieldPageTable"); $field_sizes->title = "image_sizes"; $field_sizes->label = "Image sizes"; $field_sizes->set('parent_id', $page->id); $template = wire("templates")->get("image_size"); $field_sizes->set('template_id', $template->id); $field_sizes->set('columns', "title\nimage_width\nimage_height"); $wrapper->add($field_sizes); It works in that it does display an empty PageTable in my module. I can also add pages and they will be added as child pages under my module page, but when I do, the way the PageTable is displayed gets all messed up. Instead of showing the newly created page as a row in the PageTable, all the fields on the module page (including the PageTable field itself) are repeated within the PageTable field.
      I hope my explanation makes sense. I am fairly new to Processwire (and module development in particular) so perhaps I am just trying to use PageTable in a way it was not intended to be. Maybe you guys could give me some directions on how to achieve what I am looking for?
      Thanks!