Jump to content
adamspruijt

LanguageFieldTabs

Recommended Posts

-------------------------------------------------------------------

LanguageFieldTabs is now included in ProcessWire by default (version 2.4). Unless you are using version 2.3 DO NOT install this module, instead navigate to Modules and then core and you will find the module in the Language section

-------------------------------------------------------------------

LanguageFieldTabs 

Beautify and organize you Field Languages into tabs!

DOWNLOAD  - Github

DEFAULT UI

post-778-0-32333900-1372433237.png

UI IN "UNIFY" ADMIN THEME

post-778-0-97857000-1371961376.png

Sorry for the lack luster write up, will add to Modules Directory later, late, long day tomorrow. Enjoy! (very much beta maybe alpha, minimal testing, just quick evening idea at this point).

Changelog

v1.0.2

  • Improved styling capabilities (added surrounding class "LangTabsContainer" )
  • Added admin wide support
  • Fixed description text order (was being pushed to bottom)

v1.0.3

  • Added support for toggling tabs display and faded labels to represent empty fields

v1.0.4

  • Fixed tabs destroy error
  • Moved toggle into Inputfield ui-widget-header

post-778-0-97857000-1371961376_thumb.png

post-778-0-32333900-1372433237_thumb.png

  • Like 19

Share this post


Link to post
Share on other sites

Really nice UI solution when working with more than 2 languages. Most often the simplest solutions are the most difficult to think of.

  • Like 1

Share this post


Link to post
Share on other sites

There's a little glitch in this module. It tries to create tabs in fieldsets.

Though not ideal, the code below will remove the unused div with uncomplete ul.

	$(".ui-tabs-nav").each(function(){
		if($(this).find('li').length == 0) {
			$(this).parent('.langTabs').remove();
		}
	});
  • Like 1

Share this post


Link to post
Share on other sites

I'm really liking this module. Thanks for making this! I used it yesterday, all day on a multi-language site that I'm developing with 5 different languages. It has really made the interface a lot nicer to look at and use.  It makes me think we should have this in the core. There are two things I think I'd personally add to it though:

  • I'd make the tabs that have un-populated text a little different, perhaps a little faded or lighter text or something to indicate the empty state. Either that, or the populated tabs bold.
  • I'd add an option to to switch between tabbed view and regular stacked view. The reason is that I anticipate clients have cases where they are translating and want to see the text in multiple languages at the same time. But overall tabbed view seems like a much better default than what we've got now. 

Has anyone tried this with Teppo's text version control module? I'm wondering if it would break that... will probably find out later today.

  • Like 4

Share this post


Link to post
Share on other sites

I'm really liking this module. Thanks for making this! I used it yesterday, all day on a multi-language site that I'm developing with 5 different languages. It has really made the interface a lot nicer to look at and use.  It makes me think we should have this in the core. There are two things I think I'd personally add to it though:

  • I'd make the tabs that have un-populated text a little different, perhaps a little faded or lighter text or something to indicate the empty state. Either that, or the populated tabs bold.
  • I'd add an option to to switch between tabbed view and regular stacked view. The reason is that I anticipate clients have cases where they are translating and want to see the text in multiple languages at the same time. But overall tabbed view seems like a much better default than what we've got now. 

Has anyone tried this with Teppo's text version control module? I'm wondering if it would break that... will probably find out later today.

I hadn't thought of a toggle, but had planned to add an indicator for empty fields, maybe a strike-trough? I will see to adding both, thanks!

Share this post


Link to post
Share on other sites

There's a little glitch in this module. It tries to create tabs in fieldsets.

Though not ideal, the code below will remove the unused div with uncomplete ul.

	$(".ui-tabs-nav").each(function(){
		if($(this).find('li').length == 0) {
			$(this).parent('.langTabs').remove();
		}
	});

Is it possible I already fixed this? I have pushed a few minor tweaks as the module was a touch rough when I first made the thread. Anyway, I'm not seeing this happen maybe I'm just misunderstanding.

Share this post


Link to post
Share on other sites

I hadn't thought of a toggle, but had planned to add an indicator for empty fields, maybe a strike-trough? I will see to adding both, thanks!

I prefer the faded style suggested by Ryan rather than a strike-through...

  • Like 1

Share this post


Link to post
Share on other sites

Added support for toggling tabs display and faded labels to represent empty fields. Rough for now but useful for feedback I'm sure. Thanks guys.

  • Like 4

Share this post


Link to post
Share on other sites

Wow that was quick – Thanks, great update! It seems to work well, but two issues I'm running into, at least on the default admin theme:

  • Clicking the toggle button for the first time works, but throws a JS error. Clicking it a second time does not work. So you can switch to expanded view, but not switch back to tabs. The JS error is: "Uncaught Error: cannot call methods on tabs prior to initialization; attempted to call method 'destroy'." I did try to debug it a bit, but wasn't sure how to fix it. 
  • Not a bug per se, but the position of the toggle icon seems a little unusual at least in the default profile (see screenshot). Maybe there is something that works better across themes, not sure? Though let me know if you think there is an issue in the default admin theme CSS that needs tweaking.   

Thanks for your great work on this module. It's already one of my favorites. 

post-2-0-13403500-1372413876_thumb.png

Share this post


Link to post
Share on other sites

Yep, the toggle button issue is an odd one, if you keep click on it the fields will collapse eventually and after that should go back and fourth fine. I will tweak the styling for sure, the problem isn't so much with the default admin theme as it is just a limitation of the markup. I will focus on getting to look good with the default admin before I worry about it on any of my themes.

EDIT:

Might be an easy fix, it seems the number of repeat clicks is proportional to the number of Language Fields on the page, something bad in my loop.

Share this post


Link to post
Share on other sites

This looks amazing! Thanks very much :)

Share this post


Link to post
Share on other sites

Wow that was quick – Thanks, great update! It seems to work well, but two issues I'm running into, at least on the default admin theme:

  • Clicking the toggle button for the first time works, but throws a JS error. Clicking it a second time does not work. So you can switch to expanded view, but not switch back to tabs. The JS error is: "Uncaught Error: cannot call methods on tabs prior to initialization; attempted to call method 'destroy'." I did try to debug it a bit, but wasn't sure how to fix it. 
  • Not a bug per se, but the position of the toggle icon seems a little unusual at least in the default profile (see screenshot). Maybe there is something that works better across themes, not sure? Though let me know if you think there is an issue in the default admin theme CSS that needs tweaking.   

Thanks for your great work on this module. It's already one of my favorites. 

attachicon.gifScreen shot 2013-06-28 at 5.51.57 AM.png

V1.0.4 pushed, should fix both issues, a bit more cleanup and optimization needed but I'm pretty happy with this where it is, just wondering how I can make the title text translatable if it's inserted using JS? Maybe I missed that in the docs.

  • Like 1

Share this post


Link to post
Share on other sites
V1.0.4 pushed, should fix both issues, a bit more cleanup and optimization needed but I'm pretty happy with this where it is, just wondering how I can make the title text translatable if it's inserted using JS? Maybe I missed that in the docs.

Thanks for the update–It works perfectly here!

I will submit a pull request to you that makes the title attribute translatable. I also moved the hook-attach logic to a ready() method (rather than init), and made it attach the hooks only if the page template is 'admin'. 

  • Like 2

Share this post


Link to post
Share on other sites

Thanks for the update–It works perfectly here!

I will submit a pull request to you that makes the title attribute translatable. I also moved the hook-attach logic to a ready() method (rather than init), and made it attach the hooks only if the page template is 'admin'. 

Thanks for the quick addition Ryan, nice to see how the JS translatable string is handled, noted for next time.

Submitted to Module Directory :)

Edited by adamspruijt

Share this post


Link to post
Share on other sites

This looks great! Can't wait to try it! Congratulations Adam!

Share this post


Link to post
Share on other sites

Also wanted to chime in and say wow! It could be almost coming from me ;)

Joke aside, I really thought about that the day Ryan implemented this, but never bothered as I'm not currently needing it. Really cool here's how it looks on my Teflon dev theme.

post-100-0-50761800-1372447949_thumb.png

  • Like 1

Share this post


Link to post
Share on other sites
/*
not looka.so nice on pages name.setting tab i changes js.file from this
*/

var $langField = $(".Inputfield").has(".LanguageSupport");

/*
to this.
*/

var $langField = $(".Inputfield:not(.InputfieldPageName)").has(".LanguageSupport");
 

uses daveleper.branch i do

Share this post


Link to post
Share on other sites
/*
not looka.so nice on pages name.setting tab i changes js.file from this
*/

var $langField = $(".Inputfield").has(".LanguageSupport");

/*
to this.
*/

var $langField = $(".Inputfield:not(.InputfieldPageName)").has(".LanguageSupport");
 

uses daveleper.branch i do

Are you using a specific admin theme? I just checked in a few and they all looked perfectly fine.

Share this post


Link to post
Share on other sites

I think he's talking about the page name field on the settings tab. It says "Active" after each language name, like "English Active", "Spanish Active", etc. It looks like it's picking up the LanguageSupportPageNames checkbox label in the tab. As far as I can tell, WillyC's solution above was to prevent it from making tabs out of the page name field. Tested here and seems to work. 

Share this post


Link to post
Share on other sites

I think he's talking about the page name field on the settings tab. It says "Active" after each language name, like "English Active", "Spanish Active", etc. It looks like it's picking up the LanguageSupportPageNames checkbox label in the tab. As far as I can tell, WillyC's solution above was to prevent it from making tabs out of the page name field. Tested here and seems to work. 

Ok, gotcha. All fixed, my selector finding the label value wasn't specific enough. Pushed the changes.

  • Like 2

Share this post


Link to post
Share on other sites

One idea came up, and was just curious about the feasibility of it: What if the "active" tab was based on the current user's language? So if I had my language set as Spanish, I'd see the Spanish tabs active (rather than default language tab) when editing a page? 

  • Like 3

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 MoritzLost
      This is a new module that provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Beta release
      Note that I consider this a Beta release. Since the module is relatively aggressive in deleting some caches, I would advise you to install in on a test environment before using it on a live site.
      Let me know if you're getting any errors, have trouble using the module or if you have suggestions for improvement!
      In particular, can someone let me know if this module causes any problems with the ProCache module? I don't own or use it, so I can't check. As far as I can tell, ProCache uses a folder inside the cache directory to cache static pages, so my module should be able to clear the ProCache site cache as well, I'd appreciate it if someone can test that for me.
      Future plans
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory

    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="optin" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="optin" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="optin" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: https://github.com/blaueQuelle/privacywire/tree/master
      Download: https://github.com/blaueQuelle/privacywire/archive/master.zip
      I would love to hear your feedback 🙂
      Edit: Updated URLs to master tree of git repo
       
    • By David Karich
      Admin Page Tree Multiple Sorting
      ClassName: ProcessPageListMultipleSorting
      Extend the ordinary sort of children of a template in the admin page tree with multiple properties. For each template, you can define your own rule. Write each template (template-name) in a row, followed by a colon and then the additional field names for sorting.
      Example: All children of the template "blog" to be sorted in descending order according to the date of creation, then descending by modification date, and then by title. Type:
      blog: -created, -modified, title  Installation
      Copy the files for this module to /site/modules/ProcessPageListMultipleSorting/ In admin: Modules > Check for new modules. Install Module "Admin Page Tree Multible Sorting". Alternative in ProcessWire 2.4+
      Login to ProcessWire backend and go to Modules Click tab "New" and enter Module Class Name: "ProcessPageListMultipleSorting" Click "Download and Install"   Compatibility   I have currently tested the module only under PW 2.6+, but think that it works on older versions too. Maybe someone can give a feedback.     Download   PW-Repo: http://modules.processwire.com/modules/process-page-list-multiple-sorting/ GitHub: https://github.com/FlipZoomMedia/Processwire-ProcessPageListMultipleSorting     I hope someone can use the module. Have fun and best regards, David
    • By dimitrios
      Hello,
      this module can publish content of a Processwire page on a Facebook page, triggered by saving the Processwire page.
      To set it up, configure the module with a Facebook app ID, secret and a Page ID. Following is additional configuration on Facebook for developers:
      Minimum Required Facebook App configuration:
      on Settings -> Basics, provide the App Domains, provide the Site URL, on Settings -> Advanced, set the API version (has been tested up to v3.3), add Product: Facebook Login, on Facebook Login -> Settings, set Client OAuth Login: Yes, set Web OAuth Login: Yes, set Enforce HTTPS: Yes, add "https://www.example.com/processwire/page/" to field Valid OAuth Redirect URIs. This module is configurable as follows:
      Templates: posts can take place only for pages with the defined templates. On/Off switch: specify a checkbox field that will not allow the post if checked. Specify a message and/or an image for the post.
      Usage
      edit the desired PW page and save; it will post right after the initial Facebook log in and permission granting. After that, an access token is kept.
       
      Download
      PW module directory: http://modules.processwire.com/modules/auto-fb-post/ Github: https://github.com/kastrind/AutoFbPost   Note: Facebook SDK for PHP is utilized.


×
×
  • Create New...