Jump to content
tpr

AdminOnSteroids

Recommended Posts

ok thank you.

what do you think of also adding the preview links also to parent items in the breadcrumb nav?

2016-07-22 10_47_14-Edit Page_ News 2 • mustangs2016.dev.png

  • Like 1

Share this post


Link to post
Share on other sites

As I see there's no way to get the actual link of those links. Maybe hooking to breadcrumbs and set the links to data attribute could work though.

Share this post


Link to post
Share on other sites

you have the actual link of the current page:

/path/to/your/page

i think it should be possible to just remove the last part of the url for every parent?

/path/to/your
/path/to
/path

Share this post


Link to post
Share on other sites

Good idea. I can't think of any drawbacks that could happen, but maybe I'm wrong.

To avoid the clutter, I would do it on ctrl+click instead any visual icon or something. What do you think about it?

Plus alt+click for edit for example, that's something I have already planned.

  • Like 1

Share this post


Link to post
Share on other sites

my vote goes for

view: icon
edit: ctrl+click

:)

only drawback of my method would be if somebody is rewriting urls somehow... maybe also on multisite environments? but at least they have the option to switch it OFF ;)

  • Like 1

Share this post


Link to post
Share on other sites

My vote is: 

  • long click for view
  • ctrl+click to edit

or reversed :) Icons would make too much mess.

Btw, I most of the time can't get the long-click work in Chrome 51 (the built-in Edit/View feature). I works 1 times out of 10 or 20. In Firefox seems to work fine.

Share this post


Link to post
Share on other sites

Update: looks like it's SlimJet browser only, in Chrome longclicks seem OK.

I got the longclick to work, now I need a similar bright idea how to get the edit link ("/edit/?id=XXX"). Perhaps I need to add all the parents' IDs to an inline JS and get it from there.

  • Like 1

Share this post


Link to post
Share on other sites

v035 adds the abovementioned breadcrumb tweaks:

  • long-click on breadcrumb item to view page in frontend
  • ctrl+click to edit breadcrumb page

It's relatively buried under the "Hotkeys" submodule but I think it fits there. 

I'm open to ideas on different implementation of this feature but I woud like to keep the current "minimal" style (eg. better not using icons or hover menu).

  • Like 1

Share this post


Link to post
Share on other sites

I'll see, thanks. I think a confirm (yes-no) dialog would be of more help here. Strictly forbidding to save the page may result in data lost if the upload never finishes (so you can't save the page itself at all).

  • Like 2

Share this post


Link to post
Share on other sites

definitely true. but no message at all is a no-go in my opinion :)

Share this post


Link to post
Share on other sites

I would have been probably use the Raptorize plugin to make it really clear but this will also do :)

  • Like 2

Share this post


Link to post
Share on other sites

@tpr Good evening :)  While tinkering with the settings it occurred to me that it would be nice to be able to adjust the height of the rows of the Pages tree. The Reno theme uses this:

.content .PageList .PageListItem {
    border-bottom: 1px solid #e6ebf1;
    padding-top: 0.6 em;
    padding-bottom: 0.6 em;
    line-height: 1.3em;
}

Top/bottom padding with 0.3 em is quite usable too. Something like the "LongClickDuraton" inputbox would be nice to have to adjust this one too.

What do you think?

Share this post


Link to post
Share on other sites

I have tried to improve the page list but I have to admit it's close to perfect as it is (at least for me). I see that this tweak could save some space but I'll wait until other page list related needs arise.

  • Like 2

Share this post


Link to post
Share on other sites

The Page tree is a strange beast :) It works and it's usable but still... Anyway, thanks for putting my feature request on your todo list. I just want to save some scrolling. The Page tree of the Default Theme is more compact and I like it that way.

Share this post


Link to post
Share on other sites

@szabesz

I use Soma's Page List Image Label module often and I think it would be nice having this feature inside AOS. While at it, I'll implement your request, it'll be named as "Compact page list" or similar. I think there's no need to make it customizable.

  • Like 1

Share this post


Link to post
Share on other sites

Thanx in advance! Are you planning to make it adjustable on the fly? I mean not just in the module's settings (preferred default), but right on the page of the page list too. If we can stick to one setting only, then it is not so versatile.

Share this post


Link to post
Share on other sites

You mean the page thumbs? There will be one global default (image field name), or template-field pairs for those who need more. Plus a setting for square thumbs, and that's all.

I think these settings are easier to use because you can set everything at one place (module settings).

Share this post


Link to post
Share on other sites

I think I'll go with this syntax for the page thumbs:

{
	"featured_image": "template=wine|basic-page, children.count=0, parent!=1",
	"bg_image": ""
}

The idea is to use different fields (eg. "featured_image") and filter them with selectors. The first matching selector will be used. In this example featured_image is used on matching pages, and bg_image elsewhere.

I may modify the syntax to something that is easier to use. If only a string is entered, it will be treated as a global field to use on all pages.

  • Like 2

Share this post


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

You mean the page thumbs?

Sorry, I was on mobile, and could not spend too much time on my reply. Actually, I was talking about the thumbnail list vs the simple but compact list I requested. If I understand you correctly, we are talking about two different representation of the same list (tree). One with image thumbs, the other one is without the thumbs. Of course, you can use small top/bottom padding regardless of the presence of the thumbnail images, making the list compact no matther what. It just won't be too "compact" with the otherwise optional thumbnails, right?

Share this post


Link to post
Share on other sites

I'm afraid I'm lost somewhere in between :) I was talking about the existing page list but prepending a small thumbnails to the items, not a thumbnail-only page list (there's a module for that as I know). I don't plan to add the latter because that would require much modifications and it's not the purpose of AOS.

To make this pagelist compact with the thumbnails, I will see how usable it is with smaller thumbs but I'm not sure that would make much sense (thumbs were too small).

  • Like 2

Share this post


Link to post
Share on other sites

I have discovered an z-index issue with the Leaflet module. It concerns the breadcrumbs and headline div.

Screenshot_1.jpg

As you can see the magnifying glass on the right and and the size changer on the left side overlap.

Adding the following z-index to the breadcrumbs and headline div solves the problem:

#breadcrumbs {z-index:11}
#headline {z-index:11}

A lower index than 11 will not work.

Best regards

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @Juergen (or z-index-man :)) Version 0.3.6 is uploaded which should fix it. The problem is that the leaflet field sets a z-index of 1000 so I decided to use much larger values.

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

This update contains the "Pagelist thumbnails" feature. I'm sure this will have some iterations but I really like the "fieldname: selector" syntax to add thumbs, it's really flexible.

  • Like 3

Share this post


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

@szabesz is also covered with the new "Set narrow pagelist items" to reduce row height for the main pagelist. It's Reno theme only so it can be found under the RenoTweaks submodule.

Thank you very much, Sir! Double like :)

Have a good night!

  • Like 1

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...