Popular Content

Showing most liked content since 03/28/2017 in all areas

  1. 1 like
    hello, I've responded to this inquiry over on the IPS thread "Babble: Real Time Chat".
  2. 1 like
    Hi, I have several questions and suggestions to the latest/new Babble version. Questions: 1. I understood: "There must be 2 default rooms, babble and the widget room." This formulation is a little bit misunderstanding: It’s ok for me to have these 2 must-have rooms, but I require to rename ALL ROOMS / at least the “babble” room into anything else. Possible? Or is it a “MUST” to have it named babble? 2. Is it possible to deactivate whispers or at least reserve this feature for premium groups? 3. Are chats and whispers logged to file, f.e. 30 days, so my moderators can follow up ALL of the conversations? Are logs searchable? 4. Is it possible to give premium members the permission, to start or close public or private rooms by themselves? I mean for additional rooms, not for the default ones. Or are rooms only configured via the ACP with predefined settings? 5. What about copyright removal? Suggestions: 1. Monitoring of bad words or phrases. There should be an auto-reporting feature to staff groups, if users chat about forbidden stuff, other company names or links. And a warning should be presented to the user, that he is reported for indicated bad words. Maybe this function could use the IPS native functions profanity filter/allowed-forbidden links… 2. Who is chatting widget (online chat users) like in IPS chat Thanks.
  3. 1 like
    it will display that, if it detects the conf_global.php setting "sql_utf8mb4" isn't set to true, this is a good sign the charset of the database isn't set to utf8mb4_unicode_ci, and you pass it a utf8 unicode symbol of some kind.
  4. 1 like
    This guide is for sites trying to run Babble over SSL, this is required for babble to be able to function correctly. location /socket.io { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_pass http://localhost:3000; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection 'upgrade'; proxy_set_header Host $host; proxy_cache_bypass $http_upgrade; proxy_set_header X-NginX-Proxy true; proxy_redirect off; } Add this to your nginx config for your server. replace "http://localhost:3000" with the URL/Port to babble.js (if it is on the same server as your IPS community, you can use localhost here). Save the config and restart nginx. Now go to your ACP->babble->configuration->general->node settings tab. Once there go to "Node Url", for the "Node Url", enter in your sites URL without a port, example: save. now start/restart babble.js in node. Babble should now work as intended.
  5. 1 like
    and the new settings panel as the menu was annoying me