Language Sections module https://drupal.org/project/language_sections is a filter module that allows to selectively display text in the currently selected language by allowing the following text to be input into a textarea:
=fr=
This text will only be displayed when French language is selected by the user.
=el=
This text will only be displayed when Greek language is selected by the user.
=en=
This text will only be displayed when English language is selected by the user.
(=en= =fr= and =el= are markers that help filter which language to display.)
Composed Field https://drupal.org/project/composed_field is a cool little module that allows you to split a single field into as many sub-fields as you like. But you must have a good knowledge of Drupal's forms API to get it to work correctly https://api.drupal.org/api/drupal/developer!topics!forms_api_reference.h... . So we need a field with 3 text_format subfields (French, Greek, English). Each of those subfields will have a hidden text above: =fr= =el= =en= , which will help Language Sections understand which language is which. And to make it into a user-friendly UI, the 3 subfields should be wrapped into either horizontal tabs or Vertical Tabs (Composed Field allows that).
The end result should look something like this:
You will do this mostly through Drupal's UI, although some glue code might be needed (maybe for inserting the invisible =fr= =el= =en= text at the beginning of each form, but maybe Composed Field already allows for that). Once done, you will guide me through the Composed Field setup via Skype.
If you know what you are doing, you will be do this in 30min-1hour.
Immediate payment of $30 via PayPal upon successful and acceptable implementation of this setup on my site so that the Description field looks like (or similar) the one in the screenshot. If interested, e-mail me with your Skype name and we can get started.
Comments
If you know what you are
And how do you calculate that? You obviously can't do it yourself, or you wouldn't be hiring someone else to do something you could do in 30min - 1hr. And if you can't do it yourself, then how would you have any idea of how long it would take?
I've been using Drupal daily for near 6 years, and a developer for over a decade, and I couldn't do that in the time frame you suggest.
And the only people who would do it for $30 would be those who are new to the game, and therefore would not be able to do it in anywhere near the amount of time you have given as an example.
Don't try to guess how long something will take. Leave that to the people who can do it.
Contact me to contract me for D7 -> D10/11 migrations.
@Jaypan, setting up Language
@Jaypan, setting up Language Sections takes 2 minutes and you obviously have not used Composed Field module and don't know how easy it's UI is, or else you wouldn't be writing your angry little message.
What I meant by "If you know what you are doing..." is if you know your way around the Forms API and if you know how to write glue code modules.
I have been using Drupal for 6+ years too, but, for example, I have very little knowledge of JS or AJAX, so in that case, in a JS task I wouldn't say "I know what I'm doing". But for example if someone said "I need help with a very complex multilingual View with multiple contextual filters, 3 relationships, and to work with exposed filters and exposed sorting criteria"or "I need a view of exposed facets with corresponding node counts to help filter another view" -- to that I'd say "Sure, I can do that in 30min - 1 hour, and I know exactly which modules to use because I have done it MANY times in the past - BECAUSE I KNOW WHAT I'M DOING!!!"
What I meant by "If you know
I use very few contributed modules, and code almost entirely my own modules. I know the form API as well as anyone. I consider myself an advanced javascripter. Feel free to check out the tutorials on my site (in my signature) for some examples of my code if you doubt me.
And I still have to disagree, if you knew how to do it, you would know it's a longer job than that.
Contact me to contract me for D7 -> D10/11 migrations.
@Jaypan I don't doubt your JS
@Jaypan I don't doubt your JS expertise for a moment, because 3 years ago you helped me on a little JS feature that I really needed.
As for the duration, I think it would now take even less than that because I have achieved most of the FRs myself through contrib modules and what is left is just a small glue code or Rules statement.
This all doesn't matter much.
This all doesn't matter much. If someone wants to do it for 30$, then good for that person. If not then drupalina will have to accept another offer or find another solution. That is all there is to it.
Hi, I'm the original
Hi, I'm the original designer/developer of Language Sections. My input:
* Given the requirements, I would probably not use Composed Field but instead create a small additional module to do some Forms API magic and pre/post-process the text field. That said, if you are already using Composed Field elsewhere on the site, then maybe that approach makes more sense.
* I agree with others here about the $30 - I doubt if you will find a professional developer who will provide a solution at that price. By professional, I mean somebody who does this kind of work for a living - moonlighters, students, hobbyists, etc. might be interested of course.
I'm curious about why you're using LS at all - wouldn't it make more sense to use translatable fields?
Just to qualify my point:
Just to qualify my point: http://www.indeed.com/salary/q-Drupal-Developer-l-United-States.html claims that the average salary for a "Drupal Developer" in the USA is currently $78,000. The real cost of that person to their employer (or to the individual themselves if they're freelance) will be something like 2 to 3 times that figure. Do the maths, and you'll see that hourly cost would be something like $80-120/hour. Professional developer hourly rates, in my experience, are in that kind of range too. But on top, a lot of people simply aren't interested in one-off small jobs, they're just not worth the hassle.
In summary, I suspect you would need to offer more like $100 or more to get the job done professionally, though as casaran says, if there's someone out there who wants do it $30 then that's up to them.
Given the requirements, I
I ended up creating 3 textarea fields (one for each language) and with the help of Fieldgroup module was able to achieve this kind of UI.
Drupal is not exclusive to US and US rates. In UK, for instance, full time Drupal jobs go for £24,000. In India $3000-$4000. I actually had two offers (not from US) to get this done, but by that time I found a direction that could offer a better solution,so my FRs have changed. And besides, I was able to achieve this functionality using 3 modules and 1 Rules statement, which took me less than 30 minutes to set up. (It would've possibly worked slightly better with a small glue module, but for now it will have to do).
Personal note: Probably I should've never bothered with posting a bounty here - it ended up taking more time then the actual solution. Over the past few years Drupal.org forums and discussions have become a whole lot more hostile and filled with negativity and digression. Over the years I have seen some A+ developers quit Drupal altogether just because of this factor. I don't sense the spirit of support that had once existed on D.o when I joined 6-7 years ago. But that's probably a whole other discussion.
I'm curious which module do you mean by "translatable fields"? Entity Translations?
The short answer is, there is no way with i18n or Entity Translation to display all versions of the Description textarea field on the same node form. ET is still muddled up in discussions about making it's UX usable - it's a far cry from a UI or UX that a Drupal-illiterate end-user could simply use. There is also no way in whole Drupal universe to create a textarea field and say "This textarea field is French. Display only when current language is French". This is a huge problem for many genres of websites from small monolingual ones which only need one section to be multilingual, to multilingual ecommerce, to bigger multilingual sites (like what I'm working on) where there are 17 fields and only 1 multilingual description field or bio field, while clean and intuitive UX for end-users is crucial. There were a bunch of module attempts in 6x (like this forgotten https://drupal.org/project/langsatonce) to make it happen, but in 7x the only module that comes close to achieving this (perhaps unexpectedly and unintentionally) is the LS. The problem with LS is that it relies on =en= markers to work and it would be retarded to ask the end-users to actively use them. So there needs to be a way to either automatically inject those markers into each textfield and in a way that would not cause panic among the end-users, or assign a language to a field inside the field settings. But I think you would agree that it's more pragmatic to continue this conversation in LS feature request thread.
I'm glad you were able to get
I'm glad you were able to get it working, and my issue wasn't with the money, as there are always people that are able and willing to work for lower rates. But I don't like it when people who need to hire someone else to do it decide how long it should/will take.
Contact me to contract me for D7 -> D10/11 migrations.