Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I created drupal multiligual site using i18n + i18n_menu modules.
Everything works fine.
I have two languages on my web site.
I've created custom menus and menu items and linked them with appropriate categories (taxonomy terms)
When I created the taxonomy terms I set their language to be English. Next thing was translating them.
I went to admin -> category -> translation and clicked on "new translation". In the next window I got
two EMPTY comboboxes, one for each language.
I use drupal 4.6.4,site use UTF-8, When create new user, a mail will send to. The mail use UTF-8. Our user donot how tu view with UTF-8. We have many user. So we must send GB2312 mail to them. My question is:
How to send GB2312 mail. Please hep me
I am using the sfnet_mailer scripts from http://jason.sim8.com/drupal_sourceforge to send e-mails from my drupal site at sourceforge. The configuration has been modified for the change of sourceforge to MySQL 4 and seems ok, and attempts are being made to send mail. However, when sending mails, an error message like the following is given:
I finished reading all the comments on this post and I'm looking for some sort of resolution.
My business is really considering using Drupal for a proprietary Realtor Agent CMS we're building but the GPL licensing confusion is causing us to have second thoughts.
So first, is it my understanding that any code on our servers is ours? Meaning we can have contracts with businesses and they wouldn't be allowed to take our custom modules and freely distribute them? Is that much clear-because I haven't gotten that clear in my own mind yet. It seems to me that yes, as long as its on our servers they can't distribute our custom modules or themes and say they're GPL.
The 2nd question is this: if we sold modules in the public domain that didn't contain any Drupal code and marketed them as Drupal-compatible, could we license those modules as whatever we want? Basically I would create an API for the module that I would include in the installation for the customer. Then the API script that plugs it into Drupal could be GPL for all I care but the custom module itself could still have restrictions. Is that a correct assumption? Is it clear cut wrong/right or is that debatable?
I don't see why a piece of code with no Drupal syntax could be infected by the GPL license. I imagine I would make the module an object with function calls and the API interface would call those functions thus allowing me to "own" my custom module.