Jump to content

Recommended Posts

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

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

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
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
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
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
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
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
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
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
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
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 FireWire
      Hello community!

      I want to share a new module I've been working on that I think could be a big boost for multi-language ProcessWire sites.

      Some background, I was looking for a way for our company website to be efficiently translated as working with human translators was pretty laborious and a lack of updating content created a divergence between languages. I, and several other devs here, have talked about translation integrations and have recognized the power that DeepL has. DeepL is an AI deep learning powered service that delivers translation quality beyond any automated service available. After access to the API was opened up to the US, I built Fluency, a DeepL translation integration for ProcessWire.
      Fluency brings automated translation to every multi-language field in the admin, and also provides a translation tool allowing the user to translate their text to any language without it being inside a template's field. With Fluency you can:
      Translate any plain textarea or text input Translate any CKEditor content (yes, with markup) Translate page names for fully localized URLs on every page Translate your in-template translation function wrapped strings Translate modules Fluency is free, and now so is DeepL
      Since this module was first built DeepL has introduced free Developer accounts that allow anyone to start using Fluency at zero cost and beginning with the version 0.3.0 release Fluency now supports free DeepL accounts. As of June 2021 DeepL supports translation to 26 languages and continues to offer more!
      Installation and usage is completely plug and play. Whether you're building a new multi-language site, need to update a site to multi-language, or simply want to stop manually translating a site and make any language a one-click deal, it could not be easier to do it. Fluency works by having you match the languages configured in ProcessWIre to DeepL's. You can have your site translating to any or all of the languages DeepL translates to in minutes (quite literally).
      Let's break out the screenshots...
      When the default language tab is shown, a message is displayed to let users know that translation is available. Clicking on each tab shows a link that says "Translate from English". Clicking it shows an animated overlay with the word "Translating..." cycling through each language and a light gradient shift. Have a CKEditor field? All good. Fluency will translated it and use DeepL's ability to translate text within HTML tags. CKEditor fields can be translated as easily and accurately as text/textarea fields.

      Repeaters and AJAX created fields also have translation enabled thanks to a JavaScript MutationObserver that searches for multi-language fields and adds translation as they're inserted into the DOM. If there's a multi-language field on the page, it will have translation added.

      Same goes for image description fields. Multi-language SEO friendly images are good to go.

      Creating a new page from one of your templates? Translate your title, and also translate your page name for native language URLs. (Not available for Russian, Chinese, or Japanese languages due to URL limitations). These can be changed in the "Settings" tab for any page as well so whether you're translating new pages or existing pages, you control the URLs everywhere.

      Language configuration pages are no different. Translate the names of your languages and search for both Site Translation Files (including all of your modules)

      Translate all of the static text in your templates as well. Notice that the placeholders are retained. DeepL is pretty good at recognizing and keeping non-translatable strings like that. If it is changed, it's easy to fix manually.

      Fluency adds a "Translate" item to the CMS header. When clicked this opens up a modal with a full translation tool that lets the user translate any language to any language. No need to leave the admin if you need to translate content from a secondary language back to the default ProcessWire language. There is also a button to get the current API usage statistics. DeepL account owners can set billing limitations via character count to control costs. This may help larger sites or sites being retrofitted keep an eye on their usage. Fluency can be used by users having roles given the fluency-translate permission.

      It couldn't be easier to add Fluency to your new or existing website. Simply add your API key and you're shown what languages are currently available for translation from/to as provided by DeepL. This list and all configuration options are taken live from the API so when DeepL releases new languages you can add them to your site without any work. No module updates, just an easy configuration. Just match the language you configured in ProcessWire to the DeepL language you want it to be associated with and you're done. Fluency also allows you to create a list of words/phrases that will not be translated which can prevent items such as brands and company names from being translated when they shouldn't

       
      Limitations:
      No "translate page" - Translating multiple fields can be done by clicking multiple translation links on multiple fields at once but engineering a "one click page translate" is not feasible from a user experience standpoint. The time it takes to translate one field can be a second or two, but cumulatively that may take much longer (CKEditor fields are slower than plain text fields). There may be a workaround in the future but it isn't currently on the roadmap. No "translate site" - Same thing goes for translating an entire website at once. It would be great, but it would be a very intense process and take a very (very) long time. There may be a workaround in the future but it isn't on the roadmap. No current support for Inline CKEditor fields - Handling for CKEditor on-demand hasn't been implemented yet, this is planned for a future release though and can be done. I just forgot about it because I've never really used that feature personally.. Alpha release - This module is in alpha. Releases should be stable and usable, but there may be edge case issues. Test the module thoroughly and please report any bugs via a Github issue on the repository or respond here. Please note that the browser plugin for Grammarly conflicts with Fluency (as it does with many web applications). To address this issue it is recommended that you disable Grammarly when using Fluency, or open the admin to edit pages in a private window where Grammarly may not be loaded. This is an issue that may not have a resolution as creating a workaround may not be possible. If you have insight as to how this may be solved please visit the Github page and file a bugfix ticket.
      Requirements:
      ProcessWire  3.0+ UIKit Admin Theme That's Fluency in a nutshell. A core effort in this module is to create it so that there is nothing DeepL related hard-coded in that would require updating it when DeepL offers new languages. I would like this to be a future-friendly module that doesn't require developer work to keep it up-to-date.
      The Module Is Free
      This is my first real module and I want to give it back to the community as thanks. This is the best CMS I've worked with (thank you Ryan & contributors) and a great community (thank you dear reader).
      DeepL Developer Accounts
      In addition to paid Pro Developer accounts, DeepL now offers no-cost free accounts. Now all ProcessWire developers and users can use Fluency at no cost.
      Learn more about free and paid accounts by visiting the DeepL website. Sign up for a Developer account, get an API key, and start using Fluency today.
      Download & Feedback
      Download the latest version here
      https://github.com/SkyLundy/Fluency-Translation/archive/main.zip
      Github repository:
      https://github.com/SkyLundy/Fluency-Translation
      File issues and feature requests here (your feedback and testing is greatly appreciated):
      https://github.com/SkyLundy/Fluency-Translation/issues
       
      Thank you! ¡Gracias! Ich danke Ihnen! Merci! Obrigado! Grazie! Dank u wel! Dziękuję! Спасибо! ありがとうございます! 谢谢你!

    • By monollonom
      (once again I was surprised to see a work of mine pop up in the newsletter, this time without even listing the module on PW modules website 😅. Thx @teppo !)
      Github: https://github.com/romaincazier/FieldtypeQRCode
      Modules directory: https://processwire.com/modules/fieldtype-qrcode/
      This is a simple module I made so a client could quickly grab a QR Code of the page's url in the admin.
      There's not much to it for now, but if need be you can output anything using a hook:
      $wire->addHookAfter("FieldtypeQRCode::getQRText", function($event) { $event->return = "Your custom text"; }) You can also output the QR code on your front-end by calling the field:
      echo $page->qr_code_field; The module uses the PHP library QR Code Generator by Kazuhiko Arase. When looking for a way to generate a QR Code in PW I came across @ryan's integration in his TFA module. I'm not very familiar with fieldtype/inputfield module development so I blindly followed @bernhard (great) tutorial and his BaseFieldtypeRuntime. At some point I'll take a deeper look to make a module on my own.
      Some ideas for improvements :
      add the ability to choose what to ouput : page's url / editUrl / file(s) / image(s) / ... allow to output multiple QR codes ?
    • By Chris Bennett
      https://github.com/chrisbennett-Bene/AdminThemeTweaker
      Inspired by @bernhard's excellent work on the new customisable LESS CSS getting rolled into the core soon, I thought I would offer up the module for beta testing, if it is of interest to anyone.

      It takes a different approach to admin styling, basically using the Cascade part of CSS to over-ride default UiKit values.
      Values are stored in ModuleConfig Module creates a separate AdminThemeTweaker Folder at root, so it can link to AdminThemeTweaker.php as CSS AdminThemeTweaker.php reads the module values, constructs the CSS variables then includes the CSS framework Can be switched on and off with a click. Uninstall removes everything, thanks to bernhard's wonderful remove dir & contents function.
      It won't touch your core. It won't care if stuff is upgraded. You won't need to compile anything and you don't need to touch CSS unless you want to.

      It won't do much at all apart from read some values from your module config, work out the right CSS variables to use (auto contrast based on selected backgrounds) and throw it on your screen.
      You can configure a lot of stuff, leave it as it comes (dark and curvy), change two main colors (background and content background) or delve deep to configure custom margins, height of mastheads, and all manner of silly stuff I never use.

      Have been developing it for somewhere around 2 years now. It has been (and will continue to be) constantly tweaked over that time, as I click on something and find something else to do.
      That said, it is pretty solid and has been in constant use as my sole Admin styling option for all of those 2 years.

      If nothing else, it would be great if it can provide any assistance to @bernhard or other contributor's who may be looking to solve some of the quirkier UiKit behavior.
      Has (in my opinion) more robust and predictable handling of hidden Inputfields, data-colwidths and showIf wrappers.
      I am very keen to help out with that stuff in any way I can, though LESS (and any css frameworks/tools basically) are not my go.
      I love CSS variables and banging-rocks-together, no-dependency CSS you can write with notepad.



       

    • By opalepatrick
      I see old posts saying that repeaters are not the way to go in Custom Process Modules. If that is the case, when using forms (as I am trying to do) how would one tackle things like repeat contact fields where there can be multiple requirements for contact details with different parameters? (Like point of contact, director, etc) or even telephone numbers that have different uses?
      Just for background I am creating a process module that allows me to create types of financial applications in the admin area (no need to publish any of this, pure admin) that require a lot of personal or company information.
      Maybe I am thinking about this incorrectly?
    • By HMCB
      I ran across a reference to IftRunner module. The post was 6 years ago. I cant find it in available modules. Has it been pulled?
×
×
  • Create New...