Categories
CWT Community Typo3

What’s new in Community v1.1.x

Since CWT Community 1.1.x has been released a few days ago, I would like to give you some impressions on the new features.

The new version features a new view, that enables you users to send private messages to multiple recipients or to all of their buddies.

2009-08-02_1549_messaging

The private message will show up in the recipients inbox as before:

2009-08-02_1551_messaging_list

Another nice function is the newly created sorting function on the userlist page. Now, one may sort the Community users by any column ascending or descending. Of course, this function may also be used for your custom columns (see CUSTOM MARKER chapter in the official documentation).

2009-08-02_1552_userlist

Finally I’d like to highlight the enhanced privacy functions for your Community’s users. Each FE user is now able to control who may see their whole profile page. Additionally each FE user may hide itself from the userlist page.

2009-08-02_1555_privacy

I hope you enjoy the new version of CWT Community as much as I do. 🙂

Regards,

Sebastian

By Sebastian Faulhaber

Sebastian has spent over 8 years at IBM working as a technical consultant focusing on Business Integration and Business Process Management (BPM).
In 2013 Sebastian joined Red Hat as a Solution Architect; In this role, he used his extensive field experience to support customers with their digital transformation using open source & cloud technology. In 2019 Sebastian took over the leadership for a team of IT architects dealing with middleware, container technology and cloud at Red Hat Germany.

21 replies on “What’s new in Community v1.1.x”

Hi Sebastian,

your Typo3 extension looks really interesting !
I am working on personal project for people who speak french and I want to provides them a space to publish their profiles.

I downloaded your extension(cwt_community) and tried to test it on EasyPHP (ver2.01), however I can not see any user in the Sysfolder(I previously created them)

The error message is :
Warning: mysql_fetch_assoc(): supplied argument is not a valid MySQL result resource in C:\Program Files\EasyPHP 2.0b1\www\relais\t3lib\class.t3lib_db.php on line 809

I still continue to work on it but if you have few minutes to help me, I will appreciate it.

Regards.
william

arrrrggg .. ok ok ! It was a small dependency problem…
xD
Sorry for that : I installed CWT Frontend Edit + CWT Community Users and it is working now.
I continue to evaluate your extension.

Hi, I installed : cwt_feedit(V1.1.1), cwt_community (V1.1.1), cwt_community_user (V0.3.0).
Userlist mode does not work. When I call the page, I got these error reports:

t3lib_DB::sql
Unknown column ‘u.tx_cwtcommunityuser_userlist_visibility’ in ‘where clause’
SELECT * FROM fe_users AS u WHERE NOT u.deleted=1 AND NOT u.disable=1 AND u.pid IN (85) AND ( (u.tx_cwtcommunityuser_userlist_visibility = 2) OR (u.tx_cwtcommunityuser_userlist_visibility = 1 AND u.uid IN (SELECT fe_users_uid FROM tx_cwtcommunity_buddylist AS b WHERE b.buddy_uid = 31)) ) ORDER BY ‘username’ asc
require#76 // tslib_fe->INTincScript#461 // tslib_fe->INTincScript_process#3012 // tslib_cObj->USER#3086 // tslib_cObj->callUserFunction#724 // call_user_func_array#5866 // tx_cwtcommunity_pi1->main# // tx_cwtcommunity_pi1->doGetUserlist#499 // tx_cwtcommunity_lib_common->doDatabaseQuery#1790 // t3lib_DB->sql#406 // t3lib_DB->debug#757

How to fix it. I have seen that the field tx_cwtcommunityuser_userlist_visibility is not in the fe_user table and it will be not created during installation.

Thank you very much for the support and also for this great plugin.

Best regards
Carsten

Hi Carsten,

the column mentioned is part of the cwt_community_user. Please make sure that the extension is installed correctly. Maybe you should to try to uninstall and install it again. Check if the columns are added to the fe_user table during installation.

Regards,
Sebastian

Hi Sebastian,
thanks for the extension and your recent update.
I’ve got on question: how do I navigate to the guestbook of other users? I don’t see any options.

One tip: perhaps you can set the dependencies for your other extensions so during install we get notified (I also struggled with the problem Carsten had)

Thanks,
Pascal

@Pascal
Hi Pascal,
as the guestbook is a seperate plugin you can for example add it to the page containing the profile plugin. If the user enables his guestbook other user can see it when they view his profile.

The next community version will have the dependency settings.

Regards,
Sebastian

Hallo Sebastian, ich bin zwar kein Profi, habe aber schon einige Typo3 Installationen laufen und komme soweit meist alleine klar (Bsp http://www.ecologic-architecture.org/main, http://www.dasinternet.biz,etc.) Jetzt bin ich dabei eine neue Seite zu machen (http://ecological-investment.com/) und habe deine extension CWT Community installiert. Zuerst cwt_community_user, dann cwt_feedit und zum Schluss cwt_community_1.1.1, hab das Plugin auf der Welcome Seite installiert und bekommen jetzt folgende Fehlermeldungen:
Warning: Call-time pass-by-reference has been deprecated in /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php on line 392

Warning: Call-time pass-by-reference has been deprecated in /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php on line 548

Warning: Call-time pass-by-reference has been deprecated in /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php on line 1440

Warning: Call-time pass-by-reference has been deprecated in /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php on line 1440

Warning: Cannot modify header information – headers already sent by (output started at /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php:392) in /home/content/55/4928155/html/ecoinvestcom/typo3/sysext/cms/tslib/class.tslib_fe.php on line 3229

Warning: Cannot modify header information – headers already sent by (output started at /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php:392) in /home/content/55/4928155/html/ecoinvestcom/typo3/sysext/cms/tslib/class.tslib_fe.php on line 3358

Warning: Cannot modify header information – headers already sent by (output started at /home/content/55/4928155/html/ecoinvestcom/typo3conf/ext/cwt_feedit/pi1/class.tx_cwtfeedit_pi1.php:392) in /home/content/55/4928155/html/ecoinvestcom/typo3/sysext/cms/tslib/class.tslib_fe.php on line 3242

Alles andere funktioniert prima, sieht aber halt nicht gut aus, solche Fehlermeldungen über der Seite zu haben. Hast Du eine Idee?

Liebe Grüsse Karl-Heinz

Hi,

wenn man sich dir privaten Messages anschauen will kommt nur eine leere Seite.

Aufgerufene URL: index.php?id=151&action=getviewmessagessingle&msg_uid=2

Ansonsten funktioniert alles Board, Benachrichtigung über den Erhalt neuer Messages.

Jemand eine Idee woran dies liegen könnte ??

Thx in advance TSE

@Sebastian Faulhaber

Also ich will ja nichts sagen, aber wenn der Server eine Fehlermeldung zurückgibt, dann hat das seinen Grund. Nämlich dass es in der PHP-Codierung einen Fehler gibt. Zu empfehlen, diese Fehlermeldung einfach nur zu unterdrücken, womit das eigentliche Problem ja nicht gelöst ist, finde ich etwas mager, und das vom Entwickler der Extension selbst…

Ich hab nämlich das selbe Problem mit den Warnings an genannter Stelle…

@stanley
Hallo Stanley,

es handelt sich hierbei um Warnings, die die Funktion der Extension sehr wahrscheinlich nicht beeinflussen. Aus diesem Grund halte ich es für durchaus valide und kostengünstig, diese auszublenden.

Viele Grüße,
Sebastian

Ich hatte dasselbe Problem mit den Warnmeldungen auch. Habe es inzwischen wie hier beschriebeb unterdrückt und – außer das es die Errordatei zumüllt – gibt es keine direkten Probleme.

Allerdings wird dadurch das Errorlog auch unbrauchbar, weil man kaum richtige Fehler findet, wenn ständig die CWT-Fehlermeldungen dazwischen auftauchen. Das kann eigentlich nicht Sinn der Sache sein?

Gibt es denn keinen Weg, um die Fehlermeldungen durch ein Update der Extension ganz zu unterdrücken, um damit das Errorlog wieder für wirkliche Fehlersuche gebrauchen zu können?

Moinmoin,

da der Autor keinen Wert auf eine Umstellung gelegt hat hab ich mich selber auf die Suche gemacht, Zeitaufwand ca 25min zur Lösungsfindung. Umsetzung 5min… wie dem auch sei, wen die Lösung interessiert kann sich gern bei mir melden. Natürlich auch der Autor der Extension 🙂

Gruß Tino

Hi,

ich bekomme auch die gleich Meldung und deine Lösung Tino würde mich sehr interessieren. Könntest du mir die Lösung verraten?

Gruß

Baris

@Tino
Hallo Tino,
auch wenn Dein Post schon lange her ist – verrätst Du die Lösung?
Denn das Phänomen taucht noch immer auf …
Danke und einen fröhlichen Abend!
Tscherming

Leave a Reply

Your email address will not be published. Required fields are marked *

close

Subscribe to our newsletter.

Please select all the ways you would like to hear from Open Sourcerers:

You can unsubscribe at any time by clicking the link in the footer of our emails. For information about our privacy practices, please visit our website.

We use Mailchimp as our newsletter platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices here.