إضافة ووردبريس · Hamranik TelePress
Hamranik TelePress — Messenger-to-WordPress publishing
Move content and products from everyday messengers into WordPress — with control over which bot may do what.
مقدمة
Why publishing only from wp-admin slows teams down
Content and store teams often work in Telegram/Bale but still re-enter everything in wp-admin. TelePress connects bots, links users, and enables allowed actions for posts and products.
The public demo is display-mode (no live webhook). Real tokens are connected after consultation.
Publishing content is TelePress; order notifications belong to NotifyHub.
المشكلة
Double publishing means more errors
When drafts live in chat and publishing lives in admin, versions drift and bot permissions stay unclear.
Without roles and capabilities, accidental publishes and over-broad access become likely.
- Repeated work across messenger and wp-admin
- No per-action bot controls
- Weak Chat ID ↔ WP user linking
- Messy product gallery/price publishing
- Multiple messengers without one settings model
الحل
How TelePress structures publishing
Connect bots, enable/disable actions, link Chat IDs to WordPress users, and publish within capability boundaries.
Telegram, Bale and Rubika in one plugin.
- Bot and action management
- Chat ID to WP user linking
- Post and product publishing
- Product gallery and price flows
- Multi-messenger settings tabs
القدرات
Hamranik TelePress capabilities
From bot connection to controlled publishing.
Multi-messenger
Telegram, Bale and Rubika in dedicated settings tabs.
Bot action controls
Toggle post, product, gallery, prices and more per bot.
User linking
Map Chat IDs to WordPress users or approve /link requests.
Role-aware menus
Wizard steps respect WP / WooCommerce / Dokan capabilities.
Product gallery
First image featured; remaining images in the Woo gallery.
Dokan-aware
Products can be authored as the linked seller.
Honest demo mode
Public demo is clearly display-only without a live webhook.
Hamranik UI
Aligned with the rest of the plugin family.
كيف يعمل
From bot connection to publish
A practical path for content and store teams.
Connect
Add messenger tokens and settings.
Authorize
Enable allowed actions and link users.
Publish
Send posts or products from the bot.
Review
Check results in WordPress and edit if needed.
مناسب لـ
A good fit for
If messenger publishing is part of daily operations.
- WooCommerce stores with messenger-based content teams
- Dokan marketplaces
- Brands using Iranian messengers
- Teams that need per-action bot control
غير مناسب لـ
Not the right fit for
If you only need order notifications, see NotifyHub.
- A full social media suite replacement
- Order notification hub (NotifyHub)
- Sites not on WordPress
التميّز
Why teams choose it
Messenger publishing for the Iranian market with role control.
Three messengers, one plugin
Telegram + Bale + Rubika.
Action control
Each bot only performs allowed work.
Transparent demo
Display mode without fake live-webhook promises.
Hamranik family
Shared consultation path and UI language.
التسعير
ترخيص سنوي
ترخيص سنوي
$22 / سنة
An annual license covers standard deployment and minor updates. Deep integrations, custom training and bespoke work are scoped separately.
خدمات ذات صلة
عندما تحتاجون تخصيصاً أعمق
من المدونة
اقرأ المزيد عن هذا المجال
الأسئلة الشائعة
FAQ about Hamranik TelePress
Does the demo use a live webhook?
No. The public demo is display-mode so capabilities are visible; real tokens are connected during deployment.
Which messengers are supported?
Telegram, Bale and Rubika via multi-tab settings.
Does it work with Dokan?
Yes — products can be authored as the linked seller.
How is this different from NotifyHub?
TelePress publishes content/products; NotifyHub notifies on store events. An optional bridge is possible, not a hard dependency.
بيئة البرنامج
Hamranik TelePress in practice
سجل الإصدارات
-
الإصدار 0.4.3
- تجهيز الإضافة لـ Plugin Check: تعليقات translators وتعقيم المدخلات وTested up to لووردبريس 7.0
- إعادة صياغة شاشة حول كاعتماد للمؤلف دون ترقية مدفوعة
-
الإصدار 0.4.2
- Admin section headers now show the product name and a short capability list instead of the Hamranik logo
- Dismissible About page keeps the Hamranik credit, logo, and website CTA
-
الإصدار 0.4.1
- Alpine.js unminified source shipped beside alpine.min.js; standard gettext .po/.mo
- Admin Hamranik credit limited to the dismissible About screen
- Removed TelePress Pro upgrade card from the dashboard
-
الإصدار 0.4.0
- No fake Telegram/Bale/Rubika seeding on activate
- Optional Load sample data button; default off
- wordpress.org readme, GPL license, dismissible About credit
-
الإصدار 0.3.4
- Demo messenger inbox with convert-to-draft for posts and products
- Viewer role that can read the inbox but cannot convert
- Clear split from NotifyHub; no live webhook claimed
-
الإصدار 0.3.3
- 12-locale demo sync
- Bot management polish
- Final package prep
-
الإصدار 0.3.0
- Bot actions and Chat ID linking
- Woo product gallery
- Dokan support
-
الإصدار 0.2.0
- Telegram/Bale/Rubika tabs
- Role-aware wizard
-
الإصدار 0.1.0
- Basic post publishing from bot
See the publishing flow in the demo
The demo is display-mode; real bot connection happens after consultation.