Shishitong URL Navigation System Source Code — Self-Hosted Directory Site with Built-in Ad Payment

Shishitong (ShiShiTong) is a complete URL navigation / directory portal written in PHP, now at v3.1. The most interesting part is not the navigation itself — plenty of those exist — but the built-in advertising order + online payment module that follows the Caihong Yipay (Rainbow Yipay) protocol. That turns a plain directory site into something that can actually collect money for homepage top placements. You can grab the full source code download on dajian168 and deploy it in under an hour.

Although it sits in the mall system (mall system) category on dajian168, it is really a navigation site with a lightweight e-commerce layer bolted on: users buy ad slots (homepage top site, priced around 100/month in the default JSON config), pay via WeChat Pay, Alipay, or QQ Wallet, and the system activates the placement automatically.

The payment module is the core value — here is how it actually behaves

When I deployed this on a test VPS, the flow worked exactly as the docs describe: order page at pay.html (pseudo-static), three-step progress bar, ad type / duration (1, 3, 6, or 12 months) / payment method selection, and a live-updating total on the buy button. Backend side, there is one settings panel under Payment Center → Payment Configuration where you fill in gateway URL, merchant ID, merchant key, and the callback address pay_notify.php.

Three things worth knowing before you touch it:

• Ad products are defined as editable JSON in the admin panel — add, remove, or reprice slots without touching code.
• Callback verification uses standard Yipay MD5 signing. In testing, a forged signature was rejected outright, which is the behavior you want.
• Successful homepage-top orders automatically set top=1 on the target site and write the expiry date; renewals on the same site extend the deadline instead of overwriting it.

Actionable takeaway: if you have no payment gateway yet, leave the config empty. The frontend still generates a “pending payment” order, and you mark it paid manually in Payment Center → Ad Orders. Do not half-fill the merchant key — that produces orders that never confirm.

Snapshot API and hitokoto module — the two details that make the site feel finished

The detail-page snapshot system ships with the WordPress mShots screenshot service preconfigured (?w=1024&h=768), so every detail page shows a real thumbnail out of the box. There is a setting in the admin panel to replace it: the API field supports placeholders {url} / {u} / {host} / {name}, or any URL ending in ?url=, which the system auto-completes. Filling off disables snapshots entirely and falls back to site favicons.

The hitokoto (random quote) module reads from /assets/date/date.dat — one entry per line, UTF-8 without BOM, blank lines and # comments ignored. It accepts a relative path, an absolute server path, or a remote http(s) address, and the backend shows “N entries total” with a live preview. All 6 bundled templates already call echoHitokoto(), so no template editing is needed.

Actionable takeaway: keep the built-in assets/snapshot.php offline placeholder intact. Even on hosts without the GD library it returns a valid image instead of a 500 error — deleting it breaks detail pages on minimal LAMP setups.

Deployment environment and a 5-step launch checklist

Deployment steps:

1. Upload the source, import the SQL file, and set database credentials in the config file.
2. Enable pseudo-static rules in Nginx/Apache before testing any frontend routes.
3. Log into the backend, open System Management → Site Configuration, toggle the hitokoto switch and snapshot API.
4. Add your site entries, then configure ad slot JSON and payment gateway if you plan to sell placements.
5. Place one test order end-to-end and confirm the callback flips it to paid automatically.

Actionable takeaway: verify pseudo-static first. Without it the pay and tools pages 404, and people often misdiagnose this as broken source code.

Who this source code fits

• Solo webmasters monetizing a directory: the ad-order flow is production-ready, not a stub.
• Developers learning payment integration: the MD5 signature + callback verification code is a clean, readable reference implementation of the Yipay protocol.
• Quick niche portals: 6 templates, online-tools page, and one-click template switching make rebranding fast.

FAQ

Q: Can I run Shishitong without configuring a payment gateway?

Yes. Orders are created in “pending payment” status and you mark them paid manually in the backend ad-order list. The automatic activation (top placement + expiry date) only triggers after a verified callback.

Q: How do I replace the default website screenshots on detail pages?

Open the admin panel’s snapshot API field and paste any endpoint supporting {url}, {u}, {host}, or {name} placeholders. Enter off to fall back to favicons.

Q: Does the ad pricing require editing source files?

No. Ad products are stored as JSON editable directly in the payment configuration panel, so you can change slot types, durations, and prices from the backend.

Original Reference

Original title: 事事通网址导航系统源码_导航查询_搭建168

Original excerpt:

简介：
事事通网址导航系统源码
首页随机一言
开关：后台 → 系统管理 → 网站配置 → 首页随机一言（开启 / 关闭）。
数据文件：默认 /assets/date/date.dat，一行一条，空行与 # 开头行自动忽略，编码 UTF-8 无 BOM。
可自定义为站点相对路径、服务器绝对路径或远程 http(s) 地址；后台实时显示「共 N 条」并预览一条。
六套模板首页均已接入（模板侧调用 echoHitokoto('模板类名')），详见 docs/hitokoto.html。
详情页快照生成 API
位置：后台 → 系统管理 → 网站配置 → 详情页快照生成 API。
默认已内置 WordPress mShots 截图服务（https:/.com/mshots/v1/{u}?w=1024&h=768），留空即用，详情页自动显示真实网站截图。
想换成其它接口：支持占位符 {url} / {u} / {host} / {name}，OZ 代表站点根路径；也可填 …?url= 结尾形式，系统自动补全网址。
想关闭快照（回退显示站点 favicon）：填 off 即可。
内置 assets/snapshot.php 为离线占位图，无 GD 也返回有效图片，绝不 500。详见 docs/snapshot.html。
3.1 购买广告 / 在线支付（v3.1 新增）
前台下单页：?ac

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.