Posted by admin on Nov 30, 2008 in
Uncategorized 我们更看重数据的可管理能力，最终给出的国内免费php类cms的数据负载排名如下（排名仅供参考）：
编辑选择奖：supesite
特别推荐奖：phpcms
总结评语
经过几轮的测试，SupeSite和PhpCms通过其优异的表现赢得了测评小组的青睐，通过三项得分数据看出他们在数据的管理能力上相比其他的 cms更胜一筹。supesite取胜之道在于高效的后台管理和取巧的数据生成方法，优秀的品质使其成为最佳数据负载内容管理系统的不二人选，遗憾的是程序不开源；phpcms则各方面更加平均，尤其是数据生成能力非常优秀，加上程序完全开源，因此有很多的追随者，值得我们大力的推荐，但这套cms近来由于收购的原因，似乎停止了开发的脚步，不免让人担心其未来的发展；HBcms的表现完全出乎意料，在数据管理维护和生成方面有着非常明显的特点，效率也很高，但后台管理界面凌乱，希望能做进一步的改进；php168系统是一个中规中矩的内容管理系统，没有明显的弱项，也没有明显的强项，如果前台模板的效率能提高的话，会更有前途；verycms专注于文章管理领域，后台管理简洁，明快，效率也较高，但文章静态化的速度实在不该恭维，使用这个系统应尽可能减少批量生成文章的操作；帝国cms一直是受到个人站长追捧的一套内容管理系统，但是其在较大数据管理方面的表现差强人意，勉强及格；dedecms也是受到众多个人站长关注的网站内容系统，同时也因为其源代码开放而有相当多的研究者，但是其对较大数据的管理能力确实非常的差，数据量较大的网站不推荐使用。
助易网CMS评测小组
http://www.cmshelp.com.cn
Tags: cms
Posted by admin on Nov 29, 2008 in
promote To be accepted into ReviewMe, a blog must meet a minimum number of citations, subscribers, and traffic. If your blog is rejected, you may want to return in a few months’ time and submit your blog again.
I setup my blog in a few days. but rejected by review me,so I have to regist in a few weeks later
Tags: promote
Posted by admin on Nov 28, 2008 in
Uncategorized Phpcms 是一个基于PHP+Mysql架构的网站内容管理系统，同时也是一个开放的PHP开发平台。Phpcms 采用模块化方式开发，功能强大灵活易于扩展，并且完全开放源代码，面向大中型站点提供重量级网站建设解决方案。3年来，凭借 Phpcms 团队长期积累的丰富的Web开发及数据库经验和勇于创新追求完美的设计理念，使得 Phpcms 得到了近10万网站的认可，并且越来越多地被应用到大中型商业网站。
主要特性：
1、功能强大，内置近20个功能模块
Phpcms2008 由内容模型、会员模型、问吧、专题、全站搜索、个人空间、广告、订单、财务、投票调查、短消息、邮件订阅、Digg、心情指数、评论、友情链接、公告、留言板等近20多个功能模块组成。
2、模块化，开源，可扩展
Phpcms 采用模块化方式开发，提供统一的模块开发接口和底层平台支持，并且完全开源，便于二次开发。
Phpcms 2008 采用面向对象方式开发，代码更易于阅读和维护，代码质量大幅提升。
3、负载能力强，支持千万级数据
Phpcms团队基于3年的开发经验和不断总结，从缓存技术、数据库设计、代码优化等多个角度入手进行优化，内容可文本存储，让信息和会员数据量支持达到了千万级。
4、权限控制更完美
Phpcms 2008 后台通过角色进行权限控制，可按模块、栏目、菜单、字段、推荐位、碎片、自由调用、审核流程等设置角色权限，并支持同一个管理员继承多个角色的权限，这让多人维护的站点权限控制变得轻松自如。支持自定义稿件状态和工作流，可自由定义多级稿件审核机制，更适合大中型网站或者单位内网协同工作。
5、模板制作方便，支持中文标签、万能自由标签和碎片功能
Phpcms 2008 采用MVC设计模式实现了程序与模板分离，不仅继续支持 {tag_焦点新闻} 格式的中文标签，还支持万能自由标签，轻松调用 Phpcms 之外的数据库信息，比如论坛、博客、商城。碎片功能融合了2007版里的自由调用和自定义标签功能，并且可以有效地和首页、栏目、专题等进行结合，支持后台可视化编辑和预览。
6、前后台模板设计精美，用户体验好
Phpcms 2008 前台、后台、会员中心界面全新设计，模板采用 DIV+CSS，引入jquery框架，广泛应用AJAX无刷新技术，并且兼容 IE 和 Firefox 浏览器，访问速度快。新的后台界面非常漂亮，支持自定义无限极树形菜单，并且采用AJAX加载。
7、支持推荐位功能，内容推送更方便
大中型站点的网站首页、频道首页、专题页的内容都是编辑精心挑选推荐的，可见内容的精确定位推送非常重要。Phpcms 的推荐位功能则可以让指定的编辑把信息精确推送到多个指定的位置，也可以随时撤下来。
8、支持生成Html和PHP动态访问，支持内容访问权限控制和收费
可按内容模型自由设置是否生成html，如果不生成html，就可以自由设置内容访问权限和收费，配合强大的财务功能，提供了高效的商业收费网站解决方案。
9、支持自定义内容模型
Phpcms 2008 支持自定义内容模型，按内容模型自定义字段，并且按字段自定义标签调用条件和信息搜索条件，按栏目绑定内容模型。
Phpcms 2008 内置了文章、图片、下载、信息四个常用内容模型，并且用户可以根据自身需求自定义内容模型。
10、支持自定义会员模型
Phpcms 2008 支持自定义会员模型，按会员模型自定义字段，并且按字段自定义标签调用条件和会员搜索条件。
phpcms2008（11月27日8时发布）新增：
1、加强易用性和用户体验
2、增加批量导入图片
3、整合ucenter头像和积分
4、专题可以加文章了
5、增加会员付费自助升级，类似QQ会员功能，超级亮点
会员完全自助付费升级至某个级别的会员组，但是有期限限制，过期后自动从VIP组退出，但是可以续费
这个完全和QQ的会员制类似，所有操作都是会员自助完成，并且可以通过收会员费来帮助网站实现盈利
6、碎片和中文标签可视化编辑和预览，而且网站首页、栏目页、专题页全部都整合了碎片功能，此次完善后的碎片功能已经很好用了，和门户用的差不多了。
Posted by admin on Nov 28, 2008 in
joomla Given enough time, that "ahha" moment eventually comes. The penny drops. The jigsaw puzzle starts to take shape. I clearly remember when I "got" MVC (Model View Controller) theory and realised my folly at being staunchly opposed to it.
The same can be said for documentation and, in particular, developer documentation. It’s a daunting task to work out how to organise hundreds of pages of information just about how you write code to work in Joomla!. We have five types of extensions, three types of applications, all sitting on top of a multi-layer framework involving hundreds of PHP classes and supported by over a dozen third party libraries. Making sense has been a significant challenge that has taken some lateral thinking to solve.
Enter the Wiki - some refuse to use them while others stare in wonder at the organised chaos as if looking at a representation of the Lorenz butterfly. This is one of the tools we are now using to address the enormous task of documenting all aspect of Joomla!. In this article, I want to spend some time going over how we have been structuring our sites to help developers find the information they need.
Posted by admin on Nov 27, 2008 in
joomla
By default, Joomla! allows access to your site using the built in username and password systems. For the most part this is fine. But, if you aren’t using this fea
ture, it’s good to disable it and remove any possibility of brute force attacks on your site. In addition, it is good to protect your site from others getting into the Administrator. Depending on the site you’re trying to run you might have disabled the front end Login Module and links, but you can’t disable access to your Administrator Login Form. Bummer! So we’ll work through this and give some options on how you can secure your Administrator to make it a little bit harder for the bad people to get in, but to begin with we are going to really fully disable front end logins.
Before we get started, I advise using a testing or development environment, maybe only on your own desktop, to test some of this out. As with everything, do not experiment with your production site.
1. Fully disable front end Logins
You might have disabled the Login module and removed all links to the Login Form but if you don’t want anyone to log into your front end you can take one more step to ensure that no one can login to the front end with the default install.
In the Administrator, navigate to Extensions -> Install/Uninstall, then select Components and disable the User Component. In my system, this option is towards the bottom of the list and it is also protected so that you can’t uninstall it. However, you can disable this Component which will prevent users from logging into the front end of the site and it will completely disable Registration. If you decide to use front end Logins later, simply re-enable this Component.
Following this process prevents users from getting directly to the front end Login Form via a link similar to index.php?option=com_user&view=login or index.php?option=com_login, if Legacy Mode is enabled.
2. Utilize Web Server Access Control
A great way to help secure your site is to implement another layer of security clearance before anyone can get to the Joomla! Login Form. This doesn’t need to be anything fancy or special, it’s just a simple level of protection. It is aimed at an attempt to slow down people who don’t know the password. It is a simple protection against direct file attacks in your Administrator.
What I’ll be covering is securing your site with Apache using .htaccess files primarily, so you must enable .htaccess for your site or set things up in the main Apache configuration. For flexibility, it is easier to enable .htaccess files for your Joomla! directory.
To secure your Administrator site you will need to create a password file. You can do this on most Linux or Mac OS X machines with the htpasswd command, and if you don’t have access to this then there are many generators online. Since this is a password file, you don’t want to place it in your web accessible directory, you will want to put it in a subdirectory.
You may also wish to apply access restrictions to the following front end directories as well: cache, tmp, modules, libraries, languages, and logs. You can do this simply by putting in a .htaccess file in each of these directories (or symlinked back to a common file, such as htaccess-deny in your site directory):.
Deny From All
This will prevent any access from the Web server to these directories. Some of these folders and files should not be accessed directly anyway, so, this extra bit of protection ensures that the folders and files are not accessed by anything other than Joomla!. Unlike the earlier setting, there is no username or password to get access to them either.
You may also wish to apply this to your plugins and includes directory as well, however this will cause issues with JavaScript and WYSIWYG editors. But, even this challenge can be resolved by individually unprotecting specific directories, such as the editors directory in plugins and the js folder in includes. The following line in a .htaccess file, or symlinked from a common file such as htaccess-allow, will allow access to those directories:
Allow From All
The Allow From and Deny From directives also accept IP addresses that you can then use to allow access or deny access to specific IP addresses, hostnames and wildcards. For more information on how to use these features, check out the Apache manual. So, if you’ve got Apache, you can do IP-based access control as well.
For more information, see Apache Access Control Restrictions.
3. Ban IP Address or Range
But, what if you can’t enable .htaccess or aren’t using Apache? In response to a posting on the Joomla! forum, a while back I wrote a plugin called Ban IP Address/Range for 1.5 that allows you to do the above, except from the Joomla! interface. The plugin doesn’t accept hostnames, however it does accept IP addresses and optionally ranges.
This System Plugin that can be configured to whitelist certain IP addresses (other addresses are blocked) or blacklist certain IP addresses or ranges from visiting your Administrator or your site. If you are deploying your site in an environment where access is restricted to a certain range of IP addresses, then you can use this method to limit access to your Administrator for only those IP addresses that fall within that range. You may also use this approach to limit access to your front end, as well, if required.
4. Implement jSecure
This is another approach one can use if Apache or .htaccess is not available, or to simply add another layer of security protecting the Administrator. jSecure is an interesting project that requires a user to enter a key before the Administrator Login Form appears. If the value is not entered, then a 404 page appears, instead.
jSecure is available for 1.0 or for 1.5 and is configured with a key to enable logins. This may be used as an alternative protection if you cannot enable .htaccess files. The extensions supports 1.0 via an Administrator module with a slight alteration to your Administrator template (if you are using the default, I suggest you make a copy of it and change the copy and then use the copy as the default template) or as a System Plugin for 1.5 installations.
5. Follow the recommendations on the Joomla! Administrator Security Checklist
The simplest is last, which is to work through the Joomla! Administrator Security Checklist to ensure that you’ve got your site running on the most secure settings available. The list might look long but it is well worth working through and trying to get things to work.
Also, remember that your site is only as secure as the Extensions that you install. Keep in mind that your hosting environment contributes to your security, as well. So whilst a lot of this can help your site, there are a lot of things that Joomla! can’t control that can cause your site to be vulnerable. Simply using good hosting will go along ways to protecting your Web site.
Tags: security
Posted by admin on Nov 26, 2008 in
joomla How to easily add additional data elements for Users
Written by Kevin Devine
The Usermeta plugin makes use of hooks in the JUser library to extend the properties of the user object. This would allow a developer to customize a user registration form to include information not available in the standard form. There are two different methods for extending the user object. The first is by adding to the user parameters which are stored in the params field of the jos_users table. The second method is by creating a database table joined to jos_users by a foreign key.
User parameters are defined in XML setup files which by default are stored in administrator/components/com_user/models. The UserMeta plugin provides an example custom XML setup file located in plugins/system/usermeta. A developer can use this file to define custom parameters for the user object then enable the UserMeta plugin to make them available through the hooks provided in JUser.
In the method JUser::getParameters() it is possible to define the directory path to XML setup files to be used for all user parameters.
JUser::getParameters( [ $loadsetupfile = false[, $path = null ] ] )
The second parameter of the getParameters() method is $path and by defining that parameter when statically calling the method the $parampath will then be defined as a static local variable in the getParameters() method. During subsequent calls to getParameters(), if the $path parameter is left undefined, the previous value will be used.
By taking advantage of the plugin trigger onAfterInitialise(), it is then possible, using a system plugin, to define a directory path to custom XML setup files where user parameters have been defined.
/**
* Define parampath as a directory path to custom XML setup files
*
* @return void
* @access public
*/
function onAfterInitialise()
{
// Enable the custom xml setup file to extend the user parameters
JUser::getParameters(false, ‘path/to/files’);
}
Once this plugin is executed the custom parameters are immediately part of the user object. If you choose to edit a user in the User Manager of the administrator you will see the custom parameters in the parameters box ready to be edited.
The one drawback of using this method to extend user parameters is that all of the custom parameters are stored in one database field. This makes it difficult to retrieve the data for other uses. The UserMeta plugin offers the option to extend the user object by using this parameter method or by using another database table joined by a foreign key.
Similar to the getParameters() method there is a getTable() method available to developers.
JUser::getTable()( [ $type = null[, $prefix = ‘JTable’ ] ] )
The method makes use of a static local variable to define which table class the application will use in building the user object. First the table class needs to be added to the JTable include path and then defined as the class to use in JUser. Again, this is possible by using a system plugin and the onAferInitialize() plugin trigger.
/**
* Define the table name of the user table
*
* @return void
* @access public
*/
function onAfterInitialise()
{
// Add the tables path to the JTable library
JTable::addIncludePath(‘path/to/table/class’);
// Set the custom table object as the user table
JUser::getTable('NameOfTableClass');
}
Obviously when using this method it is necessary to develop a custom table class capable of joining two tables. This is not possible using the current Joomla! framework but a custom class is provided in the UserMeta plugin which joins the jos_users table with a custom table named jos_usermeta. The fields of the jos_usermeta table can be defined by the developer installing the plugin. The plugin then dynamically reads the table information from the database and builds the user object.
It is possible to add these custom parameters and properties to both the user manager in the administrator and the registration form on the frontend. There are full instructions for using the plugin in a README file provided with the plugin.
Tags: joomla code
Posted by admin on Nov 26, 2008 in
blog,
source How can I get a head image in blog comment ?
can register in http://www.gravatar.com with your email.when you submit your comment will display your head images (when submit your email address same with gravatar register email).
Tags: gravatar
Posted by admin on Nov 25, 2008 in
blog,
source Write Blog With Live writer Smoothly
Fist You need config blog account . open your site support xml-rpc .configure your live writer blog account .
Weblog Dashboard can manage your site (will open your blog online no login) ;-)).really good
Secondly write your blog , title and body and addtions.
give proper categories . slug means your title combine with - , replace white space with -. can set publish date , if you sometime won’t update your blog. It’s friendly to search engine.Every time robot can get new food .
Tags: write blog
Posted by admin on Nov 25, 2008 in
joomla Joom!FreeMind 2.1.1 is a Joomla! 1.5.x native component. This extension generates an appealing visual mindmap observing your menus,categories and sections. It makes use of FreeMind - a premier mind-mapping software written in Java and displays the published site structure by connecting the component to a menu, a menu item or to a simple hyperlink placed inside your articles. The name of the component is the same as the one we have chosen for the stand-alone tool (you might want to check this one as well, especially if you are using Joomla 1.0) but note that the previous versions (1.8.x) do not provide complete Joomla! integration. Version 2.0.4 made corrections to the wrong categories and sections links. Several display options and color variation schemes were added in the backend, and Joom!FreeMind 2.1.1 kept the two different ways of rendering maps by either using the sections-categories structure or the published menus. It also brings the option of rendering maps through an alternative flash based viewer if you do not want to use the java viewer on your site.
http://www.xinet.ro/en/current-projects/joomfreemind.html
