tpr

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

Looks like a great module, however, I got an error on a multilanguage install " Missing required GET param pages_id ". Using PW 3.029.

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.

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.

Is there a way to specify array in field name? I have this in getDefaultData: static public function getDefaultData() { return array( 'InputfieldURLChecker' => array( 'IUC_mode' => array( 'button' ), 'IUC_button_position' => 'button-left', 'IUC_target' => 'new-window', 'IUC_force_http' => 1, 'IUC_enabled_templates' => array(), 'IUC_enabled_fields' => array() ) ) } Now if I make a field and set its name to 'IUC_mode' and save the module, the $data in getModuleConfigInputfields($data) will NOT have 'IUC_mode' under 'InputfieldURLChecker' (but a flat array). I have tried this, but no joy: $f = wire('modules')->get('InputfieldCheckboxes'); $f->name = 'InputfieldURLChecker["IUC_mode"]'; ...

Offtopic: no offense, but this is one reason why I stopped using bootstrap, uikit, foundation et al. Looks tempting at first but maintenance becomes a nightmare later.

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

Forked here to add support for editing module files from /site/modules, plus on PW3 namespaced textarea inputs are also detected: https://github.com/rolandtoth/ProcessTemplateEditor

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.

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.

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 :))

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.

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.

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.

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.

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

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.

Definitely better!

No idea then. If you can't see the add new field with admin rights then it's surely not a permission issue. Have you tried uninstalling the inputfiedchosen module to see it helps? (or any other module you installed to make this work)

Are you sure all permissions are set up correctly? Have you restricted template relationships (in the Family tab of Category and Categories template settings)? Also try setting other than PageListSelectMultiple, the notes say it's incompatible (see the second to last setting in your screenshot). I suppose it works with Home by accident only.

No idea, but it's shorter so leaves more space in my head for others

Checking for wire('languages') wouldn't work? I use this and seem to do the trick.

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

I haven't tried that but as they filter only loaded items with jQuery, they won't work as expected. Making it fully functional would need another approach (Ajax). I'll see how to fix this when paginated fields become more widespread. Multilanguage sites have a built-in live search available for translations but I think neither that has support pagination.

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.