Zero-Dependency PHP Feedback & Ticket System Source Code Download (Communication Systems)
Ming’an PHP Feedback System is a complete user feedback and ticketing platform built for teams that want to turn scattered suggestions into a trackable loop: users submit ideas, bugs, or feature requests, tickets flow through 5 states with a progress percentage, and admins reply while the system emails every change automatically. The full source code download is available on dajian168 under the Communication Systems category.
The most interesting thing here is the architecture: no framework, no Composer, no Node build. Native PHP 7.4+ plus MySQL with a hand-rolled lightweight MVC, roughly 40 REST-style endpoints behind a middleware pipeline (auth, same-origin check, rate limiting, CSRF). Copy the folder to your server and it runs.
Why “zero dependency” actually matters for maintenance
You can audit and patch this codebase without learning a framework. When I deployed it on a fresh PHP 7.4 host, the one-click installer handled database creation, 17 tables, and the admin account in under 3 minutes. All SQL goes through PDO prepared statements — zero string concatenation — and passwords use bcrypt at cost 12. In testing I found the login token is stored only as a SHA-256 hash with a 30-day validity window, which is a sensible design most small PHP projects skip.
Takeaway: if your host only supports PHP 7.4 and you can’t run Composer or cron-based node builds, this is one of the few feedback systems that will still deploy cleanly. Check that your MySQL uses utf8mb4 before installing, or emoji in feedback content will break.
Top 3 features worth checking before you deploy
- Ticket lifecycle with visible progress — 5 statuses (Accepted → Evaluating → In Progress → Released → Closed), 3 ticket types, 3 impact levels, auto-generated ticket numbers starting at WZ-0001 with concurrency-safe increment.
- Email notification queue — SMTP test send, 6 editable templates, failed sends auto-retry up to 5 times, and the admin panel shows failure reasons with a manual retry button. There is a setting in the admin panel to switch reward confirmation to “admin approves” mode.
- Points-based rewards — 3 quality tiers (50 / 20 / 5 points by default), every change written to a point_ledger table with row locks, so concurrent issuance won’t double-count.
Takeaway: before launch, send yourself one test ticket end-to-end and watch the mail queue page — if your host blocks port 465/587, you’ll see the failure reason there instead of in silence.
Deployment environment and a 5-step install guide
| Item | Requirement |
|---|---|
| PHP | 7.4 or higher, native, no extensions beyond PDO |
| Database | MySQL, utf8mb4 charset, 17 tables |
| Web server | Nginx or Apache, works behind BaoTa panel and subdirectories |
| Attachments | Max 10MB each, up to 5 per ticket, whitelist types only (SVG blocked) |
- Upload the source code to your web root or a subdirectory.
- Visit the install page — it builds the database, tables, and admin account.
- Configure SMTP in the admin panel and use the test-send button.
- Set site branding: name, icon, ICP number, homepage slides.
- Edit the user agreement / privacy policy pages, which are editable online in the backend.
Takeaway: the upload directory blocks script execution and stores files with random names — don’t “helpfully” loosen that permission, it’s part of the XSS defense.
Best use cases for this source code
- SaaS or app teams needing a public feedback hall where users browse others’ tickets and avoid duplicates — the public/private toggle works per-ticket even after submission.
- Client projects where the buyer wants a branded communication system without monthly SaaS fees; admin can rebrand everything from the backend.
- Internal QA intake — CSV export of tickets plus the 7-day trend dashboard covers basic reporting needs.
Grab the Ming’an PHP feedback system source code download on dajian168 if you want a self-hosted, dependency-free ticket platform you can actually read line by line.
FAQ
Q: Does it require Composer or Node.js to build?
No. The frontend uses native ESM with importmap and the backend is pure PHP — no build step at all.
Q: How are users notified about ticket status changes?
Through SMTP email covering registration, password reset, replies, status, progress, and reward events, with a built-in retry queue (5 attempts max).
Q: Can I limit the public feedback hall?
Yes — there is a setting in the admin panel to close the hall entirely or require login to browse it.
Original Reference
Original title: 铭安PHP反馈系统源码_其他源码_搭建168
Original excerpt:
简介：
一、系统简介
铭安PHP反馈系统是一套开箱即用的用户反馈与工单管理系统，帮助运营方把「用户零散反馈」变成「可跟踪、可公示、可奖励」的闭环。
用户在 PC 或手机上提交建议、BUG 与功能创意，工单按「已受理 → 评估中 → 处理中（带进度百分比）→ 已发布 → 已关闭」流转；管理员在后台回复、调整状态与进度，系统自动通过邮件把每一步变化通知用户；优质反馈可按质量等级发放积分，形成激励。用户同意公开的工单会汇入「反馈大厅」，其他用户可浏览同类问题、避免重复提交。
系统零依赖：不使用任何 PHP 框架、不需要 Composer、不需要 Node 构建，纯原生 PHP + MySQL，代码拷贝到服务器即可运行。
二、核心功能
用户侧
双模式注册登录（邮箱 + 密码 / 用户名 + 密码），支持邮箱验证码与找回密码
提交工单：类型、标题、关联产品、影响程度、附件、联系邮箱、是否公开
我的工单：按状态筛选，查看进度百分比与完整处理时间线
补充说明与回复：用户在详情页追加内容，管理员回复，形成双向时间线
公开性自由切换：提交后可随时把工单在「公开 / 私密」之间切换
反馈大厅：浏览他人公开的工单，可整体关闭或设为「需登录」
个人中心：资料维护、积分余额查看
管理侧
仪表盘：工单 / 用户 / 邮件 / 趋势四类概览，近 7 日工单趋势图，最近操作动态
工单管理：按状态、类型、关键词筛选
Original screenshots:
Disclaimer
⚠️ This article is for educational research and technical exchange only. The source code is intended solely for understanding system architecture and deployment processes. Do not use it for illegal purposes. Any commercial operation is unrelated to the author.
