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
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module 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) Clear the ProCache page render cache (if your site is using ProCache) 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.
      Plans for improvements
      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 CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...