General discussion

how to allow users create blog category, but not others? thanks

Here is my problem: I want to use TinyMCE with very limited features (that's not the point) but I don't want to give my users Full HTML access so they can't do anything they want in HTML if they disable TinyMCE. The problem is that with Filtered HTML (the default settings) TinyMCE's code does not get parsed properly, if at all. When it is set to Filtered HTML, and the user submits any content outputed by TinyMCE, the content comes out but the style doesn't not appear. Does anyone know how to remedy this without giving my users full out HTML access?

Does anyone experience the following problem? Basically, 4.6.3 locale module does not work on my system.

Project: Drupal
Version: 4.6.3
Component: locale.module
Category: bug
Priority: critical
Assigned: Unassigned
Status: active

Description

The locale module failed to import Chinese and Spanish language localization translations. The rows are inserted into the database. However, the translation are lost. The blog fields are all empty.

I am new in Drupal world, and I have one question/suggestion.

I was looking up and down through Drupal.org web site in a hope to find some dummy data (or example web site) to initialize core Drupal installation, something similar that Mambo/Joomla has.
I think that would be useful for new users, like me, to understand how to organize web site in Drupal.

If somebody could point me where to find such example (mysql dump) I would be thankful.

Greetings from Germany

Hi,

I'm about to start development on a new site, and I would -love- to start work using HEAD; particularly to take advantage of the changes at http://drupal.org/CHANGELOG.txt

Today is 15th September, could you please indicate to us when HEAD will be frozen. I suspect working on the site will also result in (hopefully) significant usability and stability information, and we could all contibute to rewriting the documentation.

Question: Xtemplate is totally removed?

Regards,
Alex

It may be of some interest to the Drupal community to know about recent events in the Mambo community. It seems that less than a month ago the majority of the core development team left Mambo to form Joomla, in a response to some events regarding control of the development path/Mambo community etc. As it may be known to some of you, Mambo is "hosted"/sponsored - and now probably controlled - by a company called Miro. I don't know the details, but some of it can be found here:
http://forum.joomla.org/index.php/topic,72.0.html

This is not the first time I've seen forks happen. Some of you may remember the Php-Nuke to PostNuke split, and the subsequent PostNuke to Xaraya split/fork (and some other PostNuke to something forks that I don't recall now....). It is not often that such forks have good endings, Xaraya is an exeption I think.

In my opinion forks often happen when the leading developers get tired of people fighting for power and influence - and decide to take the code and walk away (in good compliance with the ideas that Richard Stallman preaches..). This is what it means when we say that "software wants to be free".
It happens when a project grows and becomes so succesfull that the community cannot stay one. When forces driving people away from each other, overpowers the opposite forces.

What can we learn from these events? Drupal has not yet experienced the pains related to such a fork. But that does not mean it will not happen. Can the Drupal community prepare itself for this?