通常这是由于修订历史页上过时的链接到已经被删除的页面所导致的。 <p>如果情况不是这样，您可能找到了软件内的一个臭虫。请记录下URL地址，并向管理员报告。

1.5版本:
以下等式右侧的值决定各组成员的权限。左侧第一方括号内的'*'代表包括匿名用户在内的所有成员。登录用户控制存放在'user'组，这些将综合决定user_groups数据表中的成员权限。
这些设置取代了以前的wgWhitelistAccount和wgWhitelistEdit。
 #$wgGroupPermissions = array();
 $wgGroupPermissions['*']['createaccount']   = false;
 $wgGroupPermissions['*']['read']            = true;
 $wgGroupPermissions['*']['edit']            = false;
以上例子中禁止了匿名用户的自行创建账户和进行编辑。（“编辑”标签仍会显示，但匿名用户点击时会被提示要求进行登录。

 ===开放图形上传功能===
  + 系统安装完成后，有个新生成的LocalSettings.php文件，请到里面搜索upload字串。找到下列内容，并取消第三行之后的注释；然后将网站的images目录权限设为允许写入即可。（针对版本1.4.X）
  + ## To enable image uploads, make sure the 'images' directory
  + ## is writable, then uncomment this:
  + # $wgDisableUploads = false;
  + $wgUseImageResize = true;
  + # $wgUseImageMagick = true;
  + # $wgImageMagickConvertCommand = "/usr/bin/convert";

===管理员权限设定===
  + 以下修改中，很多过程需要管理员的权限。因此请以管理员帐号登录。如需他人帮忙，则要将其也提升为管理员：
  + *以站长或行政管理员(bureaucrat)身份进入'''[[Special:Makesysop]]'''页面（在[[Special:Specialpages|特殊页面]]最下方），输入用户名并按下方按钮即可。
  + *该页面上有行政管理员的选项，请慎重考虑而不要随意勾选（因为无法删除，程序bug）

How do I change a user's password?
Assuming that $wgPasswordSalt is set to true (the default), you can use the following SQL query:

UPDATE user SET user_password = MD5(CONCAT(user_id, '-',
  MD5('somepass'))) WHERE user_name = 'someuser';
Where obviously "somepass" is changed to the password you want to set and "someuser" is changed to the user name as it is listed in the table "user".

之后发出SQL命令，给已经存在的指定用户设定sysop权限：

mysql> UPDATE user SET user_rights='sysop' WHERE user_name='指定用户名';
域user_rights可以采用逗号分隔的列表，目前软件支持三个数值：

update WK_user_rights set ur_rights='bureaucrat,sysop' where ur_user='name';

phpMyAdmin的某个Database的管理界面中的SQL可以输入SQL语句。Export可以输出数据库，除了“Export Type”和“Save as file”设置外，其他都可以用默认值。“Operation”重新命名和拷贝数据库。
phpMyAdmin的某个Table的管理界面中的Browse可以编辑和删除某一行。此处可以修改用户名，但wiki的帐号在数据库里要求大写，所以要大写。也可以用命令来修改用户名和密码（Wiki要求大写）：
UPDATE `revitapi_user` SET  `user_name` = 'Username', `user_password` = MD5(CONCAT(user_id, '-', MD5('password'))) WHERE  `user_id` = 1;
删除某一行也可以用命令：DELETE FROM `revitapi_user` WHERE `user_id` =2 LIMIT 1 ;

里面的Operations中表中属性名的前缀名。移动和拷贝表到另一个数据库。

可用.net开发环境替换字符。

复制数据库后，可能首页是空的，这时候可以复制原来的wiki的首页内容到新的wiki上，问题就解决了。（为什么呀？）

如何增加沙盒功能？
再编辑的页面中加{{sandbox}}，则此页面就是沙盒页面了。

Mediawiki 访问权限设置管理:
http://blog.handsbrain.com/youzheng/entry/6746 

Amoskeag coding rules

1. Follow existing code structure and conventions as much as possible.  We have to maintain existing development style to have our code accepted.

1. When adding new files: maintain project structure (determine appropriate project and project folder); maintain folder structure; start file name with "Aecb" prefix, continue with "Ui", "UiCmd", "UiDlg" as appropriate, then follow with object/function name.  For database object and their implementations continue with "Col", "DbCol" or "ImpCol" as appropriate, then object name.  Extension should be ".cpp".
   
2. Header files should have the same names as source files, extension replaced with ".h". Header files have their own structure: headers local to project go to the project's own "Inc" folder; inter-project headers go to "Source\Inc" or "Source\Inci" folders - as determined by Autodesk reviewer.
3. Deleting or moving of existing files is not allowed unless authorized by Autodesk reviewer.
4. Every source or header file should have the standard Autodesk header.  See existing code.
   

1. Resources and export definitions should be added to the appropriate existing files.
2. All strings visible to users have to be entered as resources.  Strings that are not visible to users but required for certain API have to use _DNT macro.
3. Use AecRmCString and AecRmCStringArray classes for resource strings; use appropriate macros to convert to AecRmCString. No MFC string classes allowed.
4. When passing strings as function parameters, use const-reference for input and or reference for output strings.
5. Messages can be displayed with AfxMessageBox or Ac print function. Prompts should use appropriate Aec utilities with monitors.
   

1. Use MFC for all UI tasks, use MFC types when appropriate except strings.
2. Allocate twice as much space as required for English strings for static strings in dialogs.
3. Try to match existing dialogs in terms of fonts and layouts.
   
4. Dialogs should be based on Aec UIDlg base classes.
   

1. Class names obey the same convention as file names.  No additional prefixes or suffixes. Class name should be the same as file name.
2. Hungarian variable naming convention is strictly enforced, including using "m_" for member variable names.  The convention is extended to use some Aecb-specific object prefixes, such as "id" for object ids or "cs" for strings.  Again, follow existing code as much as possible.
3. Class and type names should start from capital letters; function names start from small letters. No underscores should be used in any names (except for member variable prefix); new words in names start with capital letters.

1. Multiple class definitions in the same file are not allowed, except nested (classes within classes or functions) classes.
2. Global functions or variables are not allowed, except when required by APIs.
3. Use AEC_ASSERT macro to check developer error conditions, such as function parameters and important intermediate check-points.  Try to fail graciously (prevent crashes) in case of an assertion. Standard assertions or console print-outs should not be used.
4. Use try-catch clauses only for specific exceptions that represent expected failures.  Never catch all exceptions: catch(...).
5. Check returned error codes from the utility functions and add appropriate logic to handle error conditions.
   
6. All local variables have to be initialized when defined, all member variables have to be initialized in the appropriate constructors.  Exception: variables with appropriate default constructors.  Limited scope variables are encouraged.
7. Use MFC or STL for algorithmic utilities (vectors, maps), but try to minimize type conversions.  Use Aec/Aecb algorithmic utilities when possible.
   
8. Use enumerations for all logical state flags as appropriate.  Do not hard-code numbers when coding logical statements.
9. Use const statements as appropriate for accessors or non-modifying functions in data classes.  Use const references / pointers for object-type parameters not modified by functions.
10. Do not use any technologies that are not used by the existing code; we cannot introduce new dependencies unless specially permitted.

1. Indent code with tab of size 4 (set tab and indent size as 4 and use "keep tabs" option).
2. { and } symbols and return statements must appear on their own lines.
3. Use empty lines to denote logical code blocks.
   

1. Fixed format comments are required for every function in source files and every class in header files.  See existing code.  No standard comments required for functions in header files, but section comments encouraged.  Member variables should have comments on the same line after their definition.
2. Source code comments are very important and should follow standard commenting rules.

1. Every code submission must represent a reasonably completed feature or a defect fix.  Review your changes carefully before submission.  Make sure words are spelled correctly.  Cosmetic changes or changes not related to the implemented feature or defect fix will not be accepted.
   
2. Every submission must be accompanied by the description created with Subdoc tool.  See tool documentation and project specific instructions about the submission information to enter.
   
3. All compiler warnings have to be resolved before submission.

2)  [
   ClassInterfaceAttribute(ClassInterfaceType::AutoDual)
   ,GuidAttribute("D66B262E-CFF3-4d26-9FE3-4A3DF3EDFEF3")
  ]
  public ref class B: public A
{}

3)extern "C"

4)MFC133:
其?的 AFX_PMSG 定義為函式指標：
typedef void (CCmdTarget::*AFX_PMSG)(void);

(AFX_MSGMAP_ENTRY*) &(theClass::_messageEntries)

5)在MFC中为什么函数可以光声明，不定义

6)MFC141:为什么不和其他的宏放一块。
#0082 typedef void (CCmdTarget::*AFX_PMSG)(void);
#0083
#0084 struct AFX_MSGMAP_ENTRY // MFC 4.0
#0085 {
#0086 UINT nMessage; // windows message
#0087 UINT nCode; // control code or WM_NOTIFY code
#0088 UINT nID; // control ID (or 0 for windows messages)
#0089 UINT nLastID; // used for entries specifying a range of control id's
#0090 UINT nSig; // signature type (action) or pointer to message #
#0091 AFX_PMSG pfn; // routine to call (or special value)
#0092 };

7)MFC142:有什么用
#0143 typedef void (CWnd::*AFX_PMSGW)(void);
#0144 // like 'AFX_PMSG' but for CWnd derived classes only

8)MFC149:有什么用
BOOL CFrameWnd::OnCommand(WPARAM wParam, LPARAM lParam)
{
cout << "CFrameWnd::OnCommand()" << endl;
// ...
// route as normal command
return CWnd::OnCommand(wParam, lParam); 
}
BOOL CWnd::OnCommand(WPARAM wParam, LPARAM lParam)
{
cout << "CWnd::OnCommand()" << endl;
// ...
return OnCmdMsg(0, 0); 
}