Adds the "Mis recursos" feature (personal files per carnet delivered\nthrough \/recursos in private chat). The database is updated automatically\non activation.<\/p>","1.0.0":"
Initial release.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3655070,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3655070,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3655070,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3655070,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3655070,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.0.0","1.1.0"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Settings screen: bot token, webhook configuration, allowed groups,\nadministrators, Ollama integration and group texts.","2":"Validated Users screen: adding members (with their carnet) and a\nlist with search, status (validated\/inactive) and masked access code.","3":"\"Recursos por usuario\" screen: uploading files per carnet and the\nlist of stored files.","4":"Telegram: the \/recursos reply in a private chat, with a button per\nfile and a \"download all\" button."}},"plugin_section":[],"plugin_tags":[2364,2316,1756,226976,9171],"plugin_category":[44],"plugin_contributors":[276543],"plugin_business_model":[],"class_list":["post-354794","plugin","type-plugin","status-publish","hentry","plugin_tags-chatbot","plugin_tags-community","plugin_tags-moderation","plugin_tags-ollama","plugin_tags-telegram","plugin_category-discussion-and-community","plugin_contributors-wvdevel","plugin_committers-wvdevel"],"banners":{"banner":"https:\/\/ps.w.org\/wvdevel-community-assistant-telegram\/assets\/banner-772x250.png?rev=3655070","banner_2x":"https:\/\/ps.w.org\/wvdevel-community-assistant-telegram\/assets\/banner-1544x500.png?rev=3655070","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/wvdevel-community-assistant-telegram\/assets\/icon.svg?rev=3655070","icon":"https:\/\/ps.w.org\/wvdevel-community-assistant-telegram\/assets\/icon.svg?rev=3655070","icon_2x":false,"generated":false},"screenshots":[],"raw_content":"\n
This plugin connects a Telegram bot to your WordPress site to support\nthe community or group you manage:<\/p>\n\n
wp-config.php<\/code>, and is managed from a\nscreen in the WordPress admin, with no loose JSON files.<\/li>\n- If a user is not validated, the bot does not reply at all -except\nfor a single private notice the first time they write- so no\ninformation is exposed and no spam is generated.<\/li>\n
- In a group, the bot only replies if it is mentioned (@bot username,\nreplying to one of its messages, or with a command directed at it).\nIn private chats it always replies, to already validated users.<\/li>\n
- Includes configurable general commands:
\/reglas<\/code>, \/horario<\/code>,\n \/anuncios, \/recursos<\/code>, \/ayuda<\/code>, \/misdatos<\/code> -all editable from\nthe WordPress admin, without touching code.<\/li>\n- Includes moderation commands for administrators, private chat only:\n \/validar,
\/invalidar<\/code>, \/listar<\/code>, \/anunciar<\/code>, \/stats<\/code>.<\/li>\n- \"Mis recursos\": each validated user can have a carnet<\/em> (student\/member\ncode). Files uploaded per carnet from the \"Recursos por usuario\" admin\nscreen are offered to that user -and only that user- when they send\n \/recursos in a private chat: one button per file plus a \"download\nall\" button that sends a ZIP. The files are stored in a private,\nweb-inaccessible folder and are delivered straight to Telegram, never\nthrough a public URL.<\/li>\n
- Integrates an Ollama (conversational AI) client that is already\nbuilt but disabled by default: once your Ollama server is ready,\njust enable the checkbox and set the URL\/model in Settings. Until\nthen the bot replies with a notice instead of failing.<\/li>\n<\/ul>\n\n
Use cases<\/h4>\n\n
Built for any Telegram community that needs to moderate access and\nautomate replies: study groups, communities of practice, work teams,\nclubs or product support.<\/p>\n\n
External services<\/h3>\n\n
This plugin connects to the following external services to work:<\/p>\n\n
\n- Telegram Bot API<\/strong> (
https:\/\/api.telegram.org<\/code>) - required for the\nbot to function. The plugin sends your bot token and the text\nmessages exchanged with Telegram users (inbound and outbound) so it\ncan receive and reply to messages via webhook. Subject to Telegram's\nTerms of Service<\/a> and\nPrivacy Policy<\/a>.<\/li>\n- Ollama<\/strong> (URL you configure, typically your own server) - optional\nand disabled by default. If you enable it, the text of messages from\nvalidated users is sent to the URL you configure to generate an AI\nreply. No information is sent to any third-party server other than\nthe one you specify in Settings.<\/li>\n<\/ul>\n\n
Requirements<\/h4>\n\n\n- WordPress 5.8 or higher.<\/li>\n
- PHP 7.4 or higher, with the
openssl<\/code> extension enabled.<\/li>\n- A site with valid HTTPS (Telegram does not accept webhooks over\n http:\/\/).<\/li>\n
- A bot created with @BotFather on Telegram.<\/li>\n<\/ul>\n\n\n
\n- Upload the full plugin folder to
wp-content\/plugins\/<\/code>, or zip its\ncontents and use Plugins -> Add New -> Upload Plugin<\/strong> from the\nWordPress admin.<\/li>\n- Activate \"WVDevel Community Assistant for Telegram\" in Plugins<\/strong>.\nOn activation, the required database tables and a random webhook\nsecret are created automatically.<\/li>\n
- Go to Bot Telegram -> Ajustes<\/strong> (Settings):\n\n
\n- Paste the bot token (obtained from @BotFather) and save the\nsettings. It is encrypted before being saved.<\/li>\n
- Click \"Configurar Webhook\" to register your site with Telegram.<\/li>\n
- Add the group ID under \"Grupos permitidos\" and your own Telegram\nID under \"IDs de administradores\".<\/li>\n
- Edit the
\/reglas<\/code>, \/horario<\/code>, \/anuncios<\/code> and \/recursos<\/code> texts\nwith your community's actual content.<\/li>\n<\/ol><\/li>\n- Go to Bot Telegram -> Usuarios validados<\/strong> and register each\nmember (Telegram ID, username, name and access code). You can also\ndo this from Telegram with
\/validar [id] [codigo] [usuario]\n[nombre]<\/code> in a private chat with the bot, once your ID is in the\nadministrators list.<\/li>\n- (Optional) \"Mis recursos\" - personal files per member:\n\n
\n- In Bot Telegram -> Ajustes<\/strong>, section \"4. Mis recursos\",\nkeep \"Activar\" checked (it is on by default), optionally edit\nthe intro text and the per-file size limit.<\/li>\n
- In Bot Telegram -> Usuarios validados<\/strong>, fill the Carnet<\/strong>\nfield for each member (their student\/member code). This is the\nkey that links a person to their folder of files.<\/li>\n
- In Bot Telegram -> Recursos por usuario<\/strong>, type a carnet and\nupload one or more files for it. They are stored in a private\nfolder inside
wp-content\/uploads<\/code> that is not reachable from\nthe web.<\/li>\n- The member writes
\/recursos<\/code> in a private<\/strong> chat with the\nbot: after the general text they get a button per file (tap to\ndownload) and, if there are two or more, a \"download all\"\nbutton that sends a ZIP.<\/li>\n<\/ol><\/li>\n- (Optional, later) Enable Ollama in Settings once your server is\nrunning, providing its URL and the model to use.<\/li>\n<\/ol>\n\n\n
\nHow does \"Mis recursos\" (personal files) work?<\/h3><\/dt>\nAssign a carnet<\/em> to a member under \"Usuarios validados\", upload\nfiles for that carnet under \"Recursos por usuario\", and the member\nreceives them by writing \/recursos<\/code> in a private chat with the bot.\nEach file is a button; a \"download all\" button sends a ZIP. It only\nworks in private chats, never in the group.<\/p><\/dd>\nWhere are the personal files stored? Are they public?<\/h3><\/dt>\nThey are saved in wp-content\/uploads\/wvdevel-mis-recursos-<random>\/<\/code>,\nprotected with a \"deny from all\" .htaccess<\/code>\/web.config<\/code> and an\nunguessable random folder name. The plugin never exposes a public URL:\nit uploads each file straight to Telegram, and only to the member\nwhose carnet matches. Deleting the plugin removes the whole folder.<\/p><\/dd>\nA member says \/recursos does not show their files<\/h3><\/dt>\nCheck that: the feature is enabled in Settings; the member has a\nCarnet<\/strong> set that exactly matches the one used when uploading; there\nis at least one file for that carnet; and they are writing \/recursos<\/code>\nin a private<\/strong> chat, not in the group.<\/p><\/dd>\nDo I need Ollama running to use the plugin?<\/h3><\/dt>\nNo. The Ollama client is disabled by default. While it is off, the\nbot still validates users and replies to the configured commands\n(\/reglas<\/code>, \/horario<\/code>, etc.); only free-form natural language\nquestions get a notice that AI is not configured yet.<\/p><\/dd>\nHow do I get the numeric ID of the Telegram group?<\/h3><\/dt>\nForward any message from the group to a bot such as @userinfobot, or\ncheck the first message the group sends to the bot after configuring\nthe webhook (it appears in the WordPress logs if something fails).<\/p><\/dd>\n
Is it safe to store members' access codes in the database?<\/h3><\/dt>\nThe access code and the bot token are encrypted with AES-256-GCM\n(authenticated encryption) using the AUTH_KEY<\/code> \/ SECURE_AUTH_KEY<\/code>\nkeys from your own wp-config.php<\/code> before being saved. They are never\nstored in plain text or in loose files.<\/p><\/dd>\nDoes the bot reply to every message in the group?<\/h3><\/dt>\nNo. In a group it only replies if it is mentioned directly (@bot\nusername, replying to one of its messages, or with a command directed\nat it). Any other message in the group is completely ignored.<\/p><\/dd>\n
Can I have more than one administrator?<\/h3><\/dt>\nYes, add the Telegram IDs separated by commas under \"IDs de\nadministradores\" in Settings.<\/p><\/dd>\n
What happens if I deactivate the plugin?<\/h3><\/dt>\nNothing is deleted: the webhook, the settings and the validated users\nare kept. They are only removed completely if you use\nPlugins -> Delete<\/strong>, which runs the definitive cleanup of tables and\nsettings.<\/p><\/dd>\n\n<\/dl>\n\n\n1.1.0<\/h4>\n\n\n- New \"Mis recursos\" feature: per-carnet personal files. Adds a \"carnet\"\nfield to validated users, a \"Recursos por usuario\" admin screen to\nupload\/delete files per carnet, and extends
\/recursos<\/code> so that in a\nprivate chat the bot also lists the user's files with inline buttons\n(download one by one, or \"download all\" as a ZIP).<\/li>\n- Files are kept in an unguessable folder inside uploads, locked down\nwith a Deny-from-all
.htaccess<\/code>\/web.config<\/code>, and are uploaded to\nTelegram via multipart -no public URL is ever exposed.<\/li>\n- The bot now handles Telegram
callback_query<\/code> updates (inline button\npresses), restricted to private chats and validated users.<\/li>\n- Uninstalling now also drops the
wvdevel_resources<\/code> table and removes\nthe private resources folder.<\/li>\n<\/ul>\n\n1.0.0<\/h4>\n\n\n- Initial release: encrypted user validation (AES-256-GCM), REST\nwebhook protected with a secret_token, configurable general\ncommands, private moderation commands, a message log screen with\nsearch and per-conversation deletion, an administrators screen, a\nbroadcast screen for sending messages\/attachments to validated\nusers and\/or allowed groups, and an Ollama client ready to be\nenabled.<\/li>\n<\/ul>","raw_excerpt":"A configurable Telegram bot for any community or group: validates members, replies only when mentioned, and optionally integrates with Ollama.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/354794","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=354794"}],"author":[{"embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/wvdevel"}],"wp:attachment":[{"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=354794"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=354794"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=354794"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=354794"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=354794"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/pcm.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=354794"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}