5

There are a few gotchas that you'll have to get around. The first is that Transcribe creates translations of entries by creating an additional entry for the translated content and then relates it to the original entry. So if you use Transcribe on the channel you use for products in Store, you will have duplicate products (one for each language). As you can ...


3

You can fix this if you limit the entries outputted to those in the language you are in. You can do this by adding the 'entry_id' parameter and using a Transcribe tag to output all the entry ids The refined channel tags is: {exp:channel:entries channel="blog" dynamic="yes" paginate="bottom" limit="3" entry_id='{exp:transcribe:entry_ids channel="blog"}' ...


3

it should work according to the docs. have a look here: http://eeharbor.com/transcribe/faq Does Transcribe work with the next_prev tag? Yes, Transcribe does work with the next_entry and prev_entry tags in ExpressionEngine, please note, it requires you to use the parse="inward" parameter, Here is an example of how it works - {exp:channel:entries channel="...


3

Tom from EE Harbor helped me out, here's his answer: {exp:channel:entries channel="name" ....} {exp:transcribe:language_links has_entry="yes" entry_id="{entry_id}" parse="inward"} <select name="lang"> {languages} <option value="{abbreviation}"{if current} selected="selected"{/if}>{name}</...


2

Repeated use of an identical single tag (as would be generated by the looping of the Playa tag pair) will cause EE to cache the value of the first instance. That means subsequent tag instances would be replaced with a marker such as M00093... which are then replaced with the value of the first instance later in the parse order. I'm not sure why these ...


2

If you have a lot of if segment == or just a lot of ifs in general, depending on what is within your ifs this can slow your site down. If you have a lot of channel:entries calls within each if, for example. EE actually parses all the info within the ifs regardless of whether they are valid or not. This can mean your entire page is parsing. So if it's long ...


2

I think I got it to work: With the add-on language prefix option turned on, the add-on prefixes urls with “index.php/es” like this http://domain-name.com/index.php/es, http://domain-name.com/index.php/es/page-name, etc. I created a new template group called “es” and it seems the existing htaccess code that removes “index.php” from templates groups has dealt ...


2

As long as the template translations are all in place in the module, the default behavior of the segment_x variables should be to default back to their native ExpressionEngine template group / template names as defined in the template manager. In the next version of Transcribe we're also introducing several additional early parse order variables such as {...


2

Since you're evaluating a string, the arguments should be enclosed in quotes ("). {if "{month}" == "{segment_4}"}class="current"{/if} You may need to add a OR operator for a second condition to check. Update Just realized I misunderstood your question. I found this Multi Language Module that allows you to define phrases ...


2

The loop occurs because you're testing again and again and again... Try this: {exp:browser_sniff available_languages="en|zh"} {if browser_sniff_negotiated_language == "zh"} {if browser_sniff_negotiated_language != "{segment_1}"} {redirect="zh/{uri_string}"} {/if} {/if} {/exp:browser_sniff} update Since Transcribe ...


2

Adding to this, I had to put transcribe=“disable” inside of the Playa tag (not the ece loop) to get it to output. Credit goes to EE Harbor.


2

You could try and use the playa:children tag instead of the Parse tag: {exp:playa:children var="lv_book_slider_en"} {title} {/exp:playa:children}


2

Just emailed a fix over to you!


2

I got this just now with a combo of Transcribe and Freeform. I think Transcribe messes with the fetch_site_index function of EE. In any case the POST action in my form was: example.com/////?ACT=86 I fixed this by modifying line 3473 in third_party/freeform/addon_builder/addon_builder.php to just use site_index instead of the native fetch_site_index ...


2

This Solspace thread describes probable causes for that error: http://www.solspace.com/forums/viewthread/16547 If you’re having issues with the params_id error, I would look at whether EE and your server can read ACT URLs correctly (eg. http://mysite.com/index.php_ACT=123). Also, make sure the form isn’t being cached: that’s a common cause for the error Had ...


2

Turns out this was due to Transcribe, we needed to use {exp:transcribe:uri path="/"} paths!


2

Unfortunately the long random string is the result of a run time pseudo caching that the template system in ExpressionEngine uses. (If you google that string M40o93H7pQ09L8X1t49cHY01Z5j4TT91fGfr you will find loads of live EE sites where this issue is present). That being said, the fix is very easy! This happens when the same tag is present on a given ...


2

You can simply make entries for the return pages, and have transcribe handle it for you. What i do is to embed the form: {embed="_inc/.contact_form" thepath="{exp:transcribe:uri path='/contact/thank-you/'}"} {exp:forms_js_validation:init lang="{transcribe:language_abbreviation}"} {exp:forms_js_validation:add selector="form" require_class="...


2

We ran into the same issue with Transcribe and Playa fields. We had a 'staff' channel (amongst many others) so we had lots of identically named entries for each person in each language (4 x John Smiths, etc), so it was tricky trying to pick the correct language 'John Smith' in a Playa field. First of all, the ideal solution would be if there was a ...


2

You could have pasted your complete tag as an example :), however I guess you're doing sometihng like this (from the docs) : {exp:transcribe:language_links} {languages} <a href="{link}"{if current} class="active"{/if}>{name}</a> {/languages} {/exp:transcribe:language_links} Right? I'm not sure if this is the desired beghaviour (...


2

Thanks to Tom at EEHarbour, my problem has been solved. I didn't realize that there was any difference at all between the two tags {exp:transcribe:language_abbreviation} and {transcribe:language_abbreviation} and it seems like using the second is the way to go in this case.


2

This is as designed. Low Seg2Cat creates its own instance of EE's URI class, because add-ons like Transcribe (and specifically Structure) tend to rewrite the original URI instance, which rewrites the segment array into something else, which can lead to other unexpected results. Low Seg2Cat therefore uses the URI as is, including "prefixes". You'll need {...


2

You can export the data from the EE MySQL database if you have access to a MySQL utility such as Sequel Pro or Navicat. You'll need to enter some SQL to isolate the data you want, something like this: SELECT t_variable.id AS entry_id, t_variable.name AS entry_name, t_translation.content AS entry_content FROM exp_transcribe_variables t_variable ...


1

I figured out what's happening here. I'm also using transcribe on this site and it somewhat hijacks the channel entries output. The entry ID needs to be in the exp_transcribe_entries_languages table to be output on the frontend. All of the members that weren't outputting were added through a front end Zoo Visitor registration form but this wouldn't take ...


1

An {if:else} conditional won't work here (or with any other tag to try to change a parameter) because it's parsed after {exp:...} tags. This is often called an advanced conditional. You can see this by turning on Template Debugging: the parameters should look unparsed or partially parsed for the tag. I don't have experience with Transcribe, Structure and ...


1

You can use the parameter transcribe="disable" in the channel entries tag


1

It's ok, I was passing the url title in as a parameter, I've changed that to be the full url and it is working perfectly. Thanks. Stephen.


1

At its core, Transcribe provides three main functions for translating websites: It lets you set up languages and will detect from the URL which of those languages the user wants. It allows you to have different language versions of the same channel entry (e.g. About Us and Over ons) and (using step 1) gives you the correct language version in your {exp:...


1

The biggest issue you're going to run into is that Simple Commerce doesn't have any tags for displaying purchase information, so you'll have no way to verify if the user has purchased the content, thus allowing them to download the product. If you have any knowledge of SQL queries, you could possibly use the Active Record module to directly grab purchase ...


1

Low Yearly Archives isn't specifically compatible with Transcribe. But if the languages can be differentiated by, for example, status, then you can use that parameter to filter the entries. Otherwise, some sort of hack would be required.


Only top voted, non community-wiki answers of a minimum length are eligible