Jump to content
adamspruijt

LanguageFieldTabs

Recommended Posts

Can we please remove this module from directory already? Every other installs this instead of the core one and runs into problems!

Share this post


Link to post
Share on other sites

First time using this module (the core version). I have the module installed, and 4 LanguageText fields. How do I make them into tabs? I assumed there would be a new field type that I wrap them in, but nothing is showing.

Running the latest dev

Share this post


Link to post
Share on other sites

Hey Antti,

I do have language packs installed. Turns out there was some other weird stuff with the install as well.

Just setup a fresh test environment, and everything is working as expected. Sorry for the false alarm.

Share this post


Link to post
Share on other sites

Hi there, i ve just installed PW 2.5.2 in Multilanguage basic mode and am missing the Language Tabs Core Module, which should be available in core modules since PW 2.4. Am i doing something wrong?

Cheers Chris

Share this post


Link to post
Share on other sites

Hi Soma, yes physicaly its stored in wire/modules/ folder but doesn´t shows up in modules core nor install area. Is there a way to install it manually?

Share this post


Link to post
Share on other sites

Have refreshed the modules cache? It may has to do with folder/file dates, as there was something added by Ryan which caused problems fro others, but can't remember and never had an issue.

Share this post


Link to post
Share on other sites

Ok, there is something definitely going wrong. Once again i installed a new blank PW 2.5.2. Starting with no language support activated, but 4 language modules listed under core modules

Languages Support
Languages Support - Fields
Languages Support - Page Names

Languages Support - Tabs.

Installing one by one everything is fine until Tabs. I got an error message about an missing ID (Sorry i ve been to fast and closed message without copying).

Afterwards listing core modules the Languages Support - Tabs module wasnt listed anymore...

So... any ideas anybody? :)

Share this post


Link to post
Share on other sites

I have the same issues.
In Debug Mode i get a error:

 Modules: Module 'LanguageTabs' dependecy not fulfilled for: LanguageSupportFields

I also tried it with 2.5.4 dev

Share this post


Link to post
Share on other sites

Any ideas regarding the LanguageTabs issue? I've the same one, but only with the version which is online. On my local dev server everything is working. 

PW-Version is 2.5.3

Share this post


Link to post
Share on other sites

I just ran into some issues as well with several javascript errors like "setupLanguageTabs is not defined".

Looks like I had an old "templates-admin" folder in my /site/ folder. Deleting this fixed my issues.

  • Like 1

Share this post


Link to post
Share on other sites

Having the same problem here, I investigated a little and found a bug and a workaround.

First, there is a bug in LanguageTabs.module, lines 83 and 84. This prevents the JS and CSS file from being found.

Wrong:

$this->config->scripts->add($this->config->urls->LanguageTabs . "LanguageTabs.js");
$this->config->styles->add($this->config->urls->LanguageTabs . "LanguageTabs.css");

Right:

$this->config->scripts->add($this->config->urls->LanguageSupport . "LanguageTabs.js");
$this->config->styles->add($this->config->urls->LanguageSupport . "LanguageTabs.css");
But this doesn’t solve the bug that the module doesn’t show up in the Core section of the module list. The quick and dirty workaround to fix this: Move the file LanguageTabs.module from directory /wire/modules/LanguageSupport to /wire/modules 
 
Unfortunately I have no idea why this fixes the problem. I have not found any hint in any file which would indicate that ProcessWire doesn’t like the file LanguageTabs.module in the subdirectory /wire/modules/LanguageSupport

Share this post


Link to post
Share on other sites

This is probably a future topic:

I'm wondering, if it's possible to divide the page content into tabs for each language? (in order to avoid having tabs for every textfield)

Let's say there would be just one tab per language next or below to the page content-tab. (e.g. could be called LanguagePageTabs) Wouldn't this be nice and resulting in a cleaner interface while editing? 

Especially with a couple of different languages and a few more content-fields I would find it easier to keep track of the content. 

Then of course the question is how to handle Non-MultiLanguageFields, which will have to be not editable and grayed out for example.

I guess such a different approach is a bit out of range for this great module. 

But anyway, I just want to share my thought.

P.s.

Because I only have a dozen pages with slightly a different structure and different images, I'm considering to build separate trees without using the multi-language modules. I stumbled upon the PageReferencesTab Module and my idea is to use it for referencing the different page-languages with the default one. 

This way the editor can jump from a page with the default language to a referenced different one. This is the idea so far  ;)

Share this post


Link to post
Share on other sites

I'm wondering, if it's possible to divide the page content into tabs for each language? (in order to avoid having tabs for every textfield)

Let's say there would be just one tab per language next or below to the page content-tab. (e.g. could be called LanguagePageTabs) Wouldn't this be nice and resulting in a cleaner interface while editing? 

Especially with a couple of different languages and a few more content-fields I would find it easier to keep track of the content.

You could build this by yourself with language alternate fields and fieldset tab: http://processwire.com/api/multi-language-support/multi-language-fields/#language-alternate-field-values. It's a lot more clicking to get this does, but it does work.

I think a automatic way wouldn't work as easily, as you can't depend on users having only a single tab with fields and duplicating 3 or 4 (or even more) tabs for each language will quite fastly lead to something, that's less clear than the current way. Maybe a "global" switch to change all fieldtabs of a page to the selected language would have the same effect, while keeping the current structure.

  • Like 1

Share this post


Link to post
Share on other sites

Thanks Lostkobrakai, for your input and reminding me of the precious and easy to use fieldset tabs. 

I'm still overlooking these gems.

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