Front End PM vs NS Chat

Front End PM is a Private Messaging system to your WordPress site.This is full functioning messaging system from front end. The messaging is done entirely through the front-end of your site rather than the Dashboard. This is very helpful if you want to keep your users out of the Dashboard area. Some Front End PM PRO Features Multiple Recipients Only admin Group message Email Piping Read Receipt Email template Announcement Email queue Role to Role Block View Details Some Useful Link Basic Admin Settings Basic Walkthrough Remove minlength Remove menu button If you want paid support you can contact with me through Front End PM paid support Features Works through a Page rather than the dashboard. This is very helpful if you want to keep your users out of the Dashboard area! Users can privately message one another Threaded messages/Individual message Ability to embed things into messages like YouTube, Photobucket, Flickr, WordPress TV, more. Notification sound. Desktop notification. Admins can send a public announcement for all users to see or to perticular role(s). Admins can set the max amount of messages a user can keep in his/her box per role basis. This is helpful for keeping Database sizes down. Admins can set how many messages to show per page in the message box. Admins can set how many user to show per page in front end directory. Admins can set will email be sent to all users when a new announcement is published or not. Admins can set “to” field of announcement email. Admins can set Directory will be shown to all or not. Admins can block any user to send private message. Admins can set time delay between two messages send by a user. Admins can see all other’s private message. Admins can block all users to send new message but they can send reply of their messages. Admins can hide autosuggestion for users. There are three types of sidebar widget. Users can select whether or not they want to receive messages Users can select whether or not they want to be notified by email when they receive a new message. Users can select whether or not they want to be notified by email when a new announcement is published. Users can block other users. Translation please use wordpress translation. Github https://github.com/shamim2883/front-end-pm/

NS Chat Plugin enables real-time communication between WordPress users using WebSocket technology, powered by the Workerman library. Key Features: * Real-time private chat between users * Visual unread message indicators * Persistent chat history stored in the database * Lightweight modular JS + PHP architecture * Automatic migration and sync of WP users to chat system * Linux daemon service with SSL support for secure connections * Future-ready integration with NFS or AWS S3 for file upload/download Planned Features: * Message editing and deletion * Read receipt indicators (message seen) * File attachments with optional NFS or AWS S3 integration Ideal for community websites, intranets, or any platform requiring internal messaging without third-party services. For integration help or consulting on adapting the plugin to your project, contact the developer at: [email protected] WebSocket Server Setup (Linux with SSL) Create a systemd service file: bash sudo vim /etc/systemd/system/websocket_server.service Paste the following content: bash [Unit] Description=WebSocket Server for NS Chat (SSL) After=network.target [Service] ExecStart=/usr/bin/php /file/to/path/yourdomain/wp-content/plugins/ns-chat/server.php start Restart=always RestartSec=25 User=www-data Group=www-data StandardOutput=file:/var/log/websocket_server.out.log StandardError=file:/var/log/websocket_server.err.log [Install] WantedBy=multi-user.target Add SSL context in server.php: php $context = [ 'ssl' => [ 'local_cert' => '/path/to/file.crt', 'local_pk' => '/path/to/file.key', 'verify_peer' => false, ] ]; Set permissions for plugin folder: bash sudo chown -R www-data:www-data /path/to/ns-chat/ sudo chmod -R 775 /path/to/ns-chat/ Reload and start the daemon: bash sudo systemctl daemon-reload sudo systemctl enable websocket_server --now sudo systemctl restart websocket_server sudo systemctl status websocket_server Check logs if needed: bash /var/log/websocket_server.out.log /var/log/websocket_server.err.log Custom Port Configuration By default, the WebSocket server listens on port 2346. To use a different port: Change the port in server.php: php $wsWorker = new Worker('websocket://0.0.0.0:2346', $context); Change the port in ns-chat.php: php $ws_port = 2346; You can check and change the port in chat-ui.js: js const port = nschat_data.wsPort || 2346; If the port is closed, then open a new port on your server’s firewall: bash sudo ufw allow /tcp sudo firewall-cmd --permanent --add-port= /tcp sudo firewall-cmd --reload sudo iptables -A INPUT -p tcp --dport -j ACCEPT sudo iptables-save > /etc/iptables/rules.v4 Database Tables The plugin creates and uses the following tables: wp_ns_chat_dialogues wp_ns_chat_messages wp_ns_chat_users Tables are created and populated automatically on plugin activation. User Synchronization Initial migration of all users from wp_users to wp_ns_chat_users on plugin activation. New registrations are handled by: php add_action('user_register', 'ns_chat_add_user_on_registration'); Profile updates are synced via: php add_action('profile_update', 'ns_chat_update_user_data'); You may bind these functions to custom hooks based on your app’s logic. License GPLv2 or later