Jump to content


tiagoroldao

Member Since 28 Dec 2011
Offline Last Active May 22 2013 11:22 AM
-----

Posts I've Made

In Topic: LanguageLocalizedURL

23 December 2012 - 01:57 PM

Well, this stopped for me when using tinyMCE, it happened only when using plain text, with no formatting... Sorry for the delay responding, I came across this issue during a project, one that ended up being a pain in the arse... And one that yielded nothing - clients from hell :P
Clarifying - this is a problem specific to a plain (no formatting) body (the "original") textarealanguage field. any other textarealanguage (not the Body) works ok.

Anyhow, a different issue made me think of a possible feature - control over the field lang substitution behaviour.
When a field is called via the selectors, it is automatically translated to the other available languages, if it is empty.(right?) This may not be the desired behaviour (as when doing something like the echo (headline || title) behaviour ) is there a way to control this?

In Topic: LanguageLocalizedURL

17 December 2012 - 08:14 PM

Hey Soma, great module! I'm trying to use it, but get the same problem nikola did: Unknown Selector operator: '' -- was your selector value properly escaped?
It happens only on the root page.. I've reproduced it sucessfully on a clean install - it occurs to me when using a textAreaLanguage - whenever I change the default language's text, it throws an error! If I leave the default language blank, it saves just fine.

Update:

Okaaaaaayyy weird things are happening... So I've been experimenting, and the module tries to do some url rewriting, mapping a /page toa /lang/page, depending on which the textAreaLanguage's languages we are writing. On the standard Body (made to be a textAreaLAnguage) a "<a href='/templates/'>" maps to a "<a href='/pt/templates/'>", but a "<a href='./templates/'>" (notice the extra dot) throws the infamous error. Weirder still, a new "new_body" field (plain textArea field, no formatting) accepts no url format at all, not /pt/templates, nor /templates, neither ./templates....

In Topic: PageAutoComplete fieldtype and hidden pages bug

13 July 2012 - 03:59 PM

Like a charm, and like you said exactly! Thanks!

In Topic: PageAutoComplete fieldtype and hidden pages bug

13 July 2012 - 11:07 AM

Thanks for the reply! Just tested it, using a superuser login as well as a regular editor one, and both don't work, with either include=hidden or include all, for both hidden and unpublished pages..

In Topic: jQuery UI Range Slider Fieldtype

09 July 2012 - 03:36 PM

Thanks a lot Soma! I detected a bug in this last iteration, while trying to use it, on line 81 of InputfieldRangeSlider.module:

   $display = "$( '#RangeSlider_{$this->name}_display1' ).text( '$this->prefix' + ui.value + '$this->suffix');";
  
   $constrain = "$( '#Inputfield_{$this->name}1' ).val( ui.value );"	   // !!! there is a semicolon missing here
   // for change event checks
   $constrain .= "$( '#Inputfield_{$this->name}1' ).trigger( 'change' );";

When I added the semicolon, everything started working again!

PS: I'm fairly new to web coding and communities, is there a place where I could have posted this bug? (in the Git, or something like that?)

Cheers :)