Experience joomla2.5, starting with joomla1.5

After more than a year of secondary development of joomla1.5, I have already learned a lot about joomla. joomla1.5 is still good in general, but the system still has many shortcomings. I will list them one by one:

 

1. Document component level

When you create an article, either you do not belong to any category, or you need to select a category, and this category must belong to a unit, that is, the level of the article is: Unit/category, that is, level 2 classification. However, in many cases, only two levels are not enough. More complex content requires three or more levels. Joomla does have many plug-ins, but none of them can directly expand the function of the article component, because this is a system restriction and the article component does not provide many interfaces. Therefore, this problem can be solved only by replacing the default document component with the third-party content management tool. However, this makes the system very strange. Article components are the most important elements in the CMS system, but they must be replaced by a third party. In addition, the article components cannot be deleted, which makes many users feel uncomfortable.

 

2. The document cannot be associated with an image.

This is also a problem with article components. Although the text can be inserted into an image, the text cannot be associated with the image. This is often used in many places. For example, the list of articles displayed on a thumbnail is boring, so the list of articles with images is normal. This allows you to install news show pro gk4 or use a third-party PCP component.

 

3. Fixed user groups

Joomla1.5 has a fixed group, and even the permissions assigned to each group are relatively small, but the permissions that cannot be edited by the group cannot be adjusted. Therefore, many components may directly ignore their permission features and prevent non-administrator users from managing components. This is very limited. For example, if there is more content on the site, it is difficult for the webmaster to ask several entry personnel to manage part of the content.

 

4. sef url: Search for friendly links

No way. joomla's natural URL format is index. php? Option = com_content, while the original address format of Drupal is index. php? /Node/1. It is conceivable that it is difficult to convert a bunch of get parameters into the short address format. The implementation principle of this sef url is that the system first analyzes the short address and obtains the real address through program operations or database comparison and matching. To adjust the short address format, you need to edit router. php to rewrite the matching rules. Most people who use joomla do not write code, so most people choose third-party SEF components, such as sh404sef. The matching principle is database record matching.

 

However, due to the lack of interfaces between joomla1.5 and some changes to the content structure or wrong links, these SEF components may be able to identify errors and generate bad links. This problem is a headache. If you think about it, you just need to change the article from one category to another, and the article will not be accessible. Or if an article has a bad link, the other good links will be broken. Customers can only talk to you every day and think that your system stability is not good.

 

5. Weak APIs

Of course, programmers want to develop more and more system APIs, so they can do a lot less on their own. But joomla has such a bad situation. All the APIS you can see in the built-in components, but what you don't see, don't think it will give you an API, joomla APIs are enough for your own use.

 

For example, the commonly used API of components is the image scaling function, which is not provided by a unified API, so that all image management components can only implement their own image scaling functions, and the management experience is very different. Some of the larger components, such as receivemart, mosets tree, and community builder, have created another framework and framework on the joomla layer! Do you think joomla doesn't need to be lifted like that? However, sometimes the architecture of these large components seems to be better than joomla. Tech experts are brave. Today, you are not famous for joomla. These bosses don't have to send you your secrets. If they are in your house, they still don't accept your rules.

 

But these have all suffered from our programmers. Think about a system and several frameworks. You need to use large components to learn its structure. Its language packs and templates may be stored in different places.

 

6. The joomla1.5 official website will soon stop updating. Currently, 1.5 of new components are rarely considered and fewer components will be generated.

 

Experience joomla2.5

Between 1.5 and 2.5, there have been two versions of 1.6 and 1.7. In fact, both of them are transitional versions, which shows how big the difference between 1.5 and 2.5 is. Almost all components from 1.6 to 2.5 can be installed on 2.5, and 1.5 of the components cannot be installed on 2.5 (however, for powerful teams, the components they make can generally be successfully installed from 1.5 to 2.5, but there are countless compatible layers added in the middle ).

 

Many people think that there is no difference between 2.5 and 1.5, and because the 2.5 component is no more than 1.5, many new people have been persuaded to engage in 1.5. I like new things and place all my bets on 2.5 to understand the differences in this system.

 

The advantages I can understand are as follows:

 

1. Unlimited Classification

If the new version is not infinitely classified, I will give up joomla. This improvement is of course.

 

2. The article component can contain images

The article components are more user-friendly and can be adjusted in many places. You can also upload a list thumbnail and a large text graph. If the template is changed, the news list components do not need to be installed.

 

3. editable user groups

Groups can be edited freely, making it easier to develop websites with deep requirements for permission management. Joomla2.5 provides permission-related APIs. To implement the permission function of components, you only need to add an XML file.

 

4. Rich APIs

To create a background component in 1.5, you really need to copy a lot of code, because even the most basic operation functions of joomla do not encapsulate the code, and many member methods need to be written, however, because there are too many codes, it is easy to copy errors. 2.5 provides several management function encapsulation classes. The traditional management functions only require model and controller to inherit those classes to achieve most of the results. In addition, there is a jimage class that I like very much. The scaling function does not need to include third-party libraries.

 

5. jform

Jform is a new concept. It allows your form to be structured based on an XML file, facilitating the creation of the editing function, and also allows you to expand the field and do anything nice on your own, it can be reused directly in the future, which is very easy to manage.

 

6. The strong team began to abide by the rules.

Virtuemart 1.1.9 is a very stable version, but it can only be installed on 1.5. The new release of receivemart2 can support 2.5. Although there is no difference in usage, the kernel is a repeat change. The second version is completely rewritten using the joomla standard, it seems that the virtuemart team has already become a hero of joomla2.5. This is a good start. It means that the environment provided by joomla2.5 is not weak and you do not have to build a second-layer framework on your own.

 

PS: The above is a summary of my recent research on joomla2.5. It is not too long for me to use joomla2.5.

Http://www.cnblogs.com/catcat811/archive/2012/06/09/2542761.html