PJBlog is a set of open source and free Chinese personal blog system programs developed by Shunzi (Chen Zishun, English name PuterJam, PJblog is named after his English abbreviation, he works in the QZONE development team of Tencent), using asp+Access Technology, PJBlog supports both Simplified and Traditional Chinese, and UTF-8 encoding. Compared with other systems, PJBlog has very high operating efficiency and update rate, and also supports new technologies currently used in blogs.
This version was first completed in October 2008. After a long period of careful research, a lot of bugs were discovered. Because this alias function almost changed all the original PJ files and modified the cache structure. The cache structure written by Shunzi was very good. I have never understood it. Now that I think about it, I have gained a lot from staying in the PJ development team during this period. It also strengthened my confidence in developing PJ. Here, I am also very grateful to the forum administrator Captain for his support and help. I am very grateful to Shunzi for giving me this opportunity. I learned a lot during the exchange with Shunzi, which is precious and worth cherishing. Finally, I hope that PJ will have a stable future. Keep going and develop continuously.
Main updated features of PJBlog3 final version
1. Added alias system to facilitate SEO.
Use a specific category name as the directory name, such as http://www.evio.name/article/web/show.html
The background operation of FSO can accurately move, delete, and update articles. The compatible log encryption function is SEO-friendly, making articles easier to include in this search engine.
2. Fixed the problem that cookies cannot be saved.
3. Fixed the problem that the [mdown] tag fails in static mode.
4. Batch deletion of friendly links.
5. snail.rison has fixed some bugs.
6. Build an Ajax model.
7. Optimize the code.
PJBlog3 upgrade instructions
The upgrade file of the final version of PJBlog3 3.0.6.170 is an upgrade based on the PJBlog3 2.8.5.157 version, so upgrade users are asked to upgrade to version 157 first and then upgrade to the latest version.
Expand
