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

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • 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-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 Process refunds and send customer notifications 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 (alpha version only available via GitHub) 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 ----
       
    • By d'Hinnisdaël
      Happy new year, everybody 🥬
      I've been sitting on this Dashboard module I made for a client and finally came around to cleaning it up and releasing it to the wider public. This is how it looks.
      ProcessWire Dashboard

      If anyone is interested in trying this out, please go ahead! I'd love to get some feedback on it. If this proves useful and survives some real-world testing, I'll add this to the module directory.
      Download
      You can find the latest release on Github.
      Documentation
      Check out the documentation to get started. This is where you'll find information about included panel types and configuration options.
      Custom Panels
      My goal was to make it really simple to create custom panels. The easiest way to do that is to use the panel type template and have it render a file in your templates folder. This might be enough for 80% of all use cases. For anything more complex (FormBuilder submissions? Comments? Live chat?), you can add new panel types by creating modules that extend the DashboardPanel base class. Check out the documentation on custom panels or take a look at the HelloWorld panel to get started. I'm happy to merge any user-created modules into the main repo if they might be useful to more than a few people.
       Disclaimer
      This is a pre-release version. Please treat it as such — don't install it on production sites. Just making sure 🍇
      Roadmap
      These are the things I'm looking to implement myself at some point. The wishlist is a lot longer, but those are the 80/20 items that I probably won't regret spending time on.
      Improve documentation & add examples ⚙️ Panel types Google Analytics ⚙️ Add new page  🔥 Drafts 🔥 At a glance / Page counter 404s  Layout options Render multiple tabs per panel panel groups with heading and spacing between ✅ panel wrappers as grid item (e.g. stacked notices) ✅ Admin themes support AdminThemeReno and AdminThemeDefault ✅ Shortcuts panel add a table layout with icon, title & summary ✅ Chart panel add default styles for common chart types ✅ load chart data from JS file (currently passed as PHP array) Collection panel support image columns ✅ add buttons: view all & add new ✅
    • By Robin S
      This module is inspired by and similar to the Template Stubs module. The author of that module has not been active in the PW community for several years now and parts of the code for that module didn't make sense to me, so I decided to create my own module. Auto Template Stubs has only been tested with PhpStorm because that is the IDE that I use.
      Auto Template Stubs
      Automatically creates stub files for templates when fields or fieldgroups are saved.
      Stub files are useful if you are using an IDE (e.g. PhpStorm) that provides code assistance - the stub files let the IDE know what fields exist in each template and what data type each field returns. Depending on your IDE's features you get benefits such as code completion for field names as you type, type inference, inspection, documentation, etc.
      Installation
      Install the Auto Template Stubs module.
      Configuration
      You can change the class name prefix setting in the module config if you like. It's good to use a class name prefix because it reduces the chance that the class name will clash with an existing class name.
      The directory path used to store the stub files is configurable.
      There is a checkbox to manually trigger the regeneration of all stub files if needed.
      Usage
      Add a line near the top of each of your template files to tell your IDE what stub class name to associate with the $page variable within the template file. For example, with the default class name prefix you would add the following line at the top of the home.php template file:
      /** @var tpl_home $page */ Now enjoy code completion, etc, in your IDE.

      Adding data types for non-core Fieldtype modules
      The module includes the data types returned by all the core Fieldtype modules. If you want to add data types returned by one or more non-core Fieldtype modules then you can hook the AutoTemplateStubs::getReturnTypes() method. For example, in /site/ready.php:
      // Add data types for some non-core Fieldtype modules $wire->addHookAfter('AutoTemplateStubs::getReturnTypes', function(HookEvent $event) { $extra_types = [ 'FieldtypeDecimal' => 'string', 'FieldtypeLeafletMapMarker' => 'LeafletMapMarker', 'FieldtypeRepeaterMatrix' => 'RepeaterMatrixPageArray', 'FieldtypeTable' => 'TableRows', ]; $event->return = $event->return + $extra_types; }); Credits
      Inspired by and much credit to the Template Stubs module by mindplay.dk.
       
      https://github.com/Toutouwai/AutoTemplateStubs
      https://modules.processwire.com/modules/auto-template-stubs/
    • By Mike Rockett
      Jumplinks for ProcessWire
      Release: 1.5.60
      Composer: rockett/jumplinks
      ⚠️ NOTICE: 1.5.60 is an important security patch-release for an XSS vulnerability discovered by @phlp. It's HIGHLY RECOMMENDED that all Jumplinks users update to the latest version as soon as possible.
      Jumplinks is an enhanced version of the original ProcessRedirects by Antti Peisa.
      The Process module manages your permanent and temporary redirects (we'll call these "jumplinks" from now on, unless in reference to redirects from another module), useful for when you're migrating over to ProcessWire from another system/platform. Each jumplink supports wildcards, shortening the time needed to create them.
      Unlike similar modules for other platforms, wildcards in Jumplinks are much easier to work with, as Regular Expressions are not fully exposed. Instead, parameters wrapped in curly braces are used - these are described in the documentation.
      Under Development: 2.0, to be powered by FastRoute
      As of version 1.5.0, Jumplinks requires at least ProcessWire 2.6.1 to run.
      View on GitLab
      Download via the Modules Directory
      Read the docs
      Features
      The most prominent features include:
      Basic jumplinks (from one fixed route to another) Parameter-based wildcards with "Smart" equivalents Mapping Collections (for converting ID-based routes to their named-equivalents without the need to create multiple jumplinks) Destination Selectors (for finding and redirecting to pages containing legacy location information) Timed Activation (activate and/or deactivate jumplinks at specific times) 404-Monitor (for creating jumplinks based on 404 hits) Additionally, the following features may come in handy:
      Stale jumplink management Legacy domain support for slow migrations An importer (from CSV or ProcessRedirects) Feedback & Feature Requests
      I’d love to know what you think of this module. Please provide some feedback on the module as a whole, or even regarding smaller things that make it whole. Also, please feel free to submit feature requests and their use-cases.
      Note: Features requested so far have been added to the to-do list, and will be added to 2.0, and not the current dev/master branches.
      Open Source

      Jumplinks is an open-source project, and is free to use. In fact, Jumplinks will always be open-source, and will always remain free to use. Forever. If you would like to support the development of Jumplinks, please consider making a small donation via PayPal.
      Enjoy! 🙂
    • By Robin S
      Add Image URLs
      Allows images/files to be added to Image/File fields by pasting URLs.

      Usage
      Install the Add Image URLs module.
      A "Paste URLs" button will be added to all image and file fields. Use the button to show a textarea where URLs may be pasted, one per line. Images/files are added when the page is saved.
       
      https://github.com/Toutouwai/AddImageUrls
      https://modules.processwire.com/modules/add-image-urls/
×
×
  • Create New...