Of course. Let's break down the DedeCMS configuration variable cfg_mb_editday.

This is a very specific and important setting for member-based websites.
What is cfg_mb_editday?
In simple terms, cfg_mb_editday is a configuration setting in DedeCMS that defines the number of days a member has to edit their own submitted content.
cfg: Stands for "ConFiGuration".mb: Stands for "MemBer".editday: Stands for "EDIT DAY", meaning the edit window in days.
What is its Purpose and Functionality?
This setting controls a core workflow for member submissions. When a member (e.g., a user in a forum, an article author, a blogger) submits content (like an article, a post, a photo, etc.), DedeCMS can be configured to allow that member to edit their submission for a limited time only.
The cfg_mb_editday variable sets that time limit.

How it works:
- A member submits a new piece of content.
- DedeCMS records the submission time.
- If the member tries to edit that content later, DedeCMS checks the current time against the submission time.
- If the number of days that have passed is less than the value of
cfg_mb_editday, the edit is allowed. - If the number of days that have passed is equal to or greater than the value of
cfg_mb_editday, the edit is blocked.
Where is it Found and Set?
This variable is typically defined in the main DedeCMS configuration file.
- File:
/data/config.cache.inc.phpor/include/config.inc.php - Look for a line similar to:
$cfg_mb_editday = 7;
You can edit this value directly in the file, but it's better to use the DedeCMS backend if possible to avoid manual errors.
How to set it in the DedeCMS Backend:

- Log in to your DedeCMS admin panel.
- Navigate to [System] -> [Basic Parameter Settings] (系统 -> 基本参数设置).
- Find the category or section related to members or content. It's often under "Site Settings" (站点设置) or a dedicated "Member Settings" (会员设置) section.
- Look for an option named something like "Member Content Editable Days" (会员内容可编辑天数) or "Member Article Edit Limit (Days)" (会员文章修改时限(天)).
- Enter the desired number of days into the input field and save the settings. This will automatically update the
config.cache.inc.phpfile.
Practical Examples
Let's say you set $cfg_mb_editday = 3;.
-
Scenario 1: Edit within the limit
- A member submits an article on Monday.
- They try to edit it on Wednesday.
- Result: Allowed. (2 days have passed, which is less than 3).
-
Scenario 2: Edit after the limit
- A member submits an article on Monday.
- They try to edit it on Friday.
- Result: Blocked. (4 days have passed, which is more than 3). The system will likely show an error message like "The editing time for this content has expired."
Why is this Setting Important?
- Content Stability: It prevents old articles from being constantly changed, which helps maintain the integrity and accuracy of your website's content archive.
- Encourages Quality Submissions: Members know they have a limited time to perfect their work, which can encourage them to proofread and write more carefully before submitting.
- Preventing Abuse: It stops members from going back and changing the meaning or context of an old post to stir up controversy or mislead readers later on.
- Workflow Management: For sites that require editorial review, this limit ensures that the author finalizes their version before an editor begins their work.
Common Values and Their Implications
-
$cfg_mb_editday = 0;- Meaning: Members can never edit their content after submission.
- Use Case: Good for news sites, official announcements, or any content where historical accuracy is paramount and changes should not be allowed.
-
$cfg_mb_editday = 1;- Meaning: Members have 24 hours to edit their content.
- Use Case: A strict but reasonable window for fixing typos or minor errors.
-
$cfg_mb_editday = 7;(Default/Recommended)- Meaning: Members have one week to edit their content.
- Use Case: A balanced approach. It gives users enough time to revisit their work, correct mistakes, or add missing information without being too permissive.
-
$cfg_mb_editday = -1;- Meaning: Members can always edit their content, with no time limit.
- Use Case: Community forums, personal blogs, or collaborative platforms where content is expected to evolve over time.
Summary
| Feature | Description |
|---|---|
| Name | cfg_mb_editday |
| Full Name | Member Content Edit Day Limit |
| Type | Integer (number of days) |
| Location | /data/config.cache.inc.php |
| Function | Sets a time limit for members to edit their own submissions. |
| Default | Often 7 days. |
| Purpose | To ensure content stability, encourage quality, and prevent abuse. |
