[TYPO3-community] Using external extensions for community extension

[Alexander Heim]

In my eyes, basic settings should be done via Backend and of course,
user generated stuff should be controlled via frontend. Adding a new
forum, setting user-rights for moderation and so on are frontend-tasks.
Deleting a user to. And so on. But the informations, where a plugin is
getting its data and in which sysfolder everything should be written, is
something, which should be set in the backend.

I still think, we should try to use existing extensions as much as
possible. But, most of them will need changes for sure. So it would be
great to integrate the developers of them.

And yeah - a lokal meeting would be quite nice :-)

So where is everybody from? I'm from Berlin and Falk was from Leipzig.

Today i try to complete my extensions wishlist and then i start to think
about the other posts and problems. Last days were just to much stress
at work.


Greetz
Alex


Falk Hermann schrieb:
> Frank Thelemann wrote:
> 
>> go away from thinking to work in the backend at community websites.if
>> you want for example update or delete a forum thread, you browse to the
>> thread on the page in the fe, and if you have the rights
>> (forum-moderator/admin) you update or delete the record. and that should
>> be possible for any kind of content.bye bye backend! optional it would
>> be fine if exist an modul like dam for files, for all community
>> contents, so you can fast browse the forum and find the thread for
>> example. but we talk here about "user generated content";-) so all
>> should be done and possible in the frontend. 
> 
> "user generated content" is OK and also necessary for a community. Bur I
>  don't think, that it's necessary to give each user one PluginSite. The
> most settings should be able to be done with User-Typo-Script. So you
> only have to write a FE-TS-Setting Plugin.
> In my opinion it is a better solution to build up new extensions with
> this FE-Administratives included. Otherwise you have to change nearly
> every community-ext.
> And the basic thoughts to give FE-Users something like BE access...
> well.... NO! Its risky and i also think it would be very difficult to
> make this performant.
> 
>> @falk for an dev server, we should better use typo3 playgrounds on
>> sourceforge,
> 
> Sorry. I don't know very much about the possibilities of sourcforge.
> *shame*
> 
> and to give other users an chance to contribute with us, we
>> should talk in english.
> 
> Of course, for external communication and documentation. But inside the
> (slowly building up) Developer-Team I would prefer to have a German
> language portal.
> 
> but if this project goes on, i preferer an local
>> meeting sometimes!?
> 
> I think so, too.
> 
>> greetings...
> ....back
> FH