Bysoft China's Blog > Your Resource To Keep Up With the Web!

With Asia-Pacific emerging as a global growth driver, there is a stronger need to professionalise information technology (IT) infrastructure. eZ Systems is determined to fill this gap with what could be the next-generation content management platform in the region: the Enterprise edition , eZ Publish.

World leading in the publishing industry with its open, reliable and adaptable content platform, eZ Systems’ solution can extend to any industry. Its client roster includes The Wall Street Journal, Financial Times, Canal Plus Group, government space and defence agencies, and industry leaders in automotive, banking, telecommunications and fashion.

Build on the open source business model paradigm, the multichannel content management platform ez Publish has an installed base of 200,000 users spread across 160 countries. Highly scalable and easy to use, it is versatile to the highly evolving gadget marketplace. eZ Systems’ portal has a marketplace that allows clients to create new business opportunities with each other. These evoke eZ System’s cutting-edge stature with IT innovations that are one to two years ahead of the curve.

“Through the openness, we attract people to help us innovate, and this is with customers, business partners and the community,” says Gabriele Viebach, eZ Systems CEO.

Its newly launched Enterprise edition can transform websites into revenue-earning portals through affiliate marketing. With an analytics tool, it follows and extends its clients customise business processes on their websites.

“We are not just a publishing company but a business enabler to our customers,” Viebach says.

eZ Systems is looking to double its business in Asia-Pacific with BySoftChina, the mainland’s largest independent web solution architect. To scale up in Asia, eZ Systems will open an office in Singapore in September. It is keen on working with media agencies, enterprise system integrators, application service providers, telecommunication companies and hosting companies in the region. It will meet with these prospects at its London conference on June 16th and 17th.

Firstly, please check the technical manual if you are not familiar with the configuration concept in eZ Publish.

In this article I will provide a short article about reading order of configuration file. I assume that you have already used eZ Publish in real projects and have idea about configuration (ini) in eZ Publish.

What is configuration’s order? When a siteaccess is used, eZ Publish reads the configuration files using the following sequence:

0 Default configuration settings – /settings/*.ini?

1 Active extension siteaccesses – /extension/my_extension/settings/siteaccess/my_site/*.ini.append.php

2 Siteaccesses                             - /settings/siteaccess/my_site/*.ini.append.php?

3 Active extensions                    – /extension/my_extension/settings/*.ini[.append.php]?

4 Global overrides                     – /settings/override/*.ini.append.php

In other words, eZ Publish will first read the default configuration settings. Secondly, it will read my_site/*.ini.append.php to find the siteaccesses for the active extensions during the installation. Then, it will determine which siteaccess to use according to the rules defined in the global override for “site.ini” (“/settings/override/site.ini.append.php”). When it knows which siteaccess to use, it will go into the directory of that siteaccess and read the configuration files belonging to that siteaccess. Lastly, it will go into the configuration file for the active extensions and read the configuration files for the active extensions. The settings of the siteaccess will override the default configuration settings.

But, if we have many extensions providing similar configuration information, which one we should use? That’s the issue about configuration override among extensions.

For example:

`– extension

|– ini_1

|   `– settings

|       `– test.ini.append.php

`– ini_2

`– settings

`– test.ini.append.php

And content of test.ini.append.php in ini_1 extension is:

[IniOrderTest]

CurrrentActiveName=ini_1

As you may guess, content of test.ini.append.php in ini_2 will be:

[IniOrderTest]

CurrrentActiveName=ini_2

So, if we want to read content of ‘CurrentActiveName’ in block ‘IniOrderTest’, which value should it be? The truth is: it depends on the load order of extensions.

For eZ Publish version less than 4.3, the load order is defined in ‘ActiveExtensions[]‘ under ‘ExtensionSettings’ block. For example:

[ExtensionSettings]

ActiveExtensions[]

ActiveExtensions[]=ini_1

ActiveExtensions[]=ini_2

Then the value for ‘CurrentActiveName’ in block ‘IniOrderTest’ should be ‘ini_1′, because eZ Publish uses prepending order to register extensions into configuration list during the activation of extensions. That means eZ Publish firstly activates extension ‘ini_1′ and register this extension into the list, then activates extension ‘ini_2′ and prepends ‘ini_2′ into the list. So, at the moment of reading configuration value, the order will firstly be ‘ini_2′, then ‘ini_1′.

The situation has changed since eZ Publish 4.4. This version introduces a new concept about extension dependency called ‘topology’. You can have a look at ‘extension.xml’ file in ezOE extension, which required ‘ezjscore’ extension as defined.

Let’s see how ‘extension.xml’ affects the result of configuration. We define dependency in ini_2 as following:

<dependencies>

<uses>

<extension name=”ini_1″ />

</uses>

</dependencies>

The word ‘extends’ define the ‘before’ relation, and words ‘required’ or ‘uses’ define the ‘after’ relation. The above example means that extension ‘ini_2’ uses extension ‘ini_1′, so the extension ‘ini_1’ should be firstly activated. Actually, this relation can be represented as:

[ExtensionSettings]

ActiveExtensions[]

ActiveExtensions[]=ini_1

ActiveExtensions[]=ini_2

As you know, configuration system will prepend ini_2 before ini_1. So, ini_1 configuration value can override the value from ini_2. When you want to read ‘CurrentActiveName’ in block ‘IniOrderTest’, you will get ‘ini_1′.

In conclusion, eZ Publish 4.4 has improved loading order of extension by introducing the ‘topology’. Keep in mind, the extension order is the reverse of the order of configuration list, since it uses prepending method when activates extensions.

The tags in Magento  is basically a description of the keyword. They can be assigned to the product through the login customer. Tags help clients to organize and remember the products that they have viewed , provide fast navigation options in your shop and optimize search engine optimization process.

The front product page of each product has an ‘Add Your Tags’ button.

When customers enter a word and click Add Tags, the tag will be sent to the Pending Tags queue (if they have not logged in, they will first login or create an account before they can submit tag). If they add many words, each word will be used as a single tag into the queue. Unless the words are included in single quotation marks, in this case, they would be classified as a tag. If you prefer, you can enable customers to get new tags reminder through RSS.

To access the Pending Tags queue, browse Catalog> Tags> Pending Tags, you can click on Edit in the Action column to edit. Select Approved to remove the Tag in this list and displayed in the foreground. Select Not Approved to remove the Tag in this list and will not appear in the foreground. You can also edit the tag’s name. Click Save Tag to Save when you finish.

If you do not need to change the tag’s name, you can batch updates to the audit Tag in order to save time. In the Tag list, select the comments you want to update. In the top of the list, you can select all tags or select all visible tags (tags in current page list). Or you can simply select the check box for each Tag option. You can see the number of options above the list, and to keep it updated. When you choose all tags that you want to modify, you may select your preferred action in the Action drop-down menu.
• Delete – This will delete all the selected Tag.
• Change Status – Select this option, the Status drop-down menu will appear on the right and you can choose Approved, Pending, or Disable. Click the Submit button and the status will be updated.

In Pending Tags queue, you can view all the products lists that the tag was applied to them, find the tag in the list, and select View Products in the Action column. For each product, you can see the frequency of the tag that applies to the product. By clicking the product you will be redirected to the product background page of this product. In Pending Tags queue, you can also view the customer list of the tag that applied to the product to find your needed tag, and select View Customers of Action column. For each customer, you can see customers using this Tag’s Store View and the products, and product SKU. Click customers, and you will redirect yourself to the customer’s background account page.

Once the mark has been approved, it will be displayed in the foreground. When adding to a new product or other customers, it no longer needs to be reviewed. It will automatically appear in the foreground, above the Add Your Tags area, and show the number of times this tag is applied to the product in parentheses.

Click the tag, you will see all products with this tag. In addition, hot tags will appear in the site’s left column, which lists the most common tag cloud.

Although Approved and Disabled Tags are not showed in the Pending Tags queue, they can still be edited. Simply go to Catalog> Tags> All Tags, you can modify them as the same in Pending Tags queue.

From 100magento

• 1. Do not install the Joomla sample database

Do not install the sample database when you install Joomla, because these examples usually are not related to the theme of your website. If you have installed it, we suggest you to delete it and empty the recycle bin; otherwise it will contain duplicated data that is largely used by other sites, and this is not conductive to SEO.

• 2. Your site name should be your domain

Some people like to fill in the Site Name with many keywords. In fact, this would not help you much. When users register on your site, they will receive an email saying” welcome to software   download database web source” which seems not very clear and also it is not your wish.

• 3 Disable PDF links

The rank value of PDF files is usually higher than that of the average webpage. Because Google considers that the PDF files are filtered, collated and the content value is higher than ordinary webpage. However there is no menu in the PDF links page generated by Joomla. When users access to this page through search engine, they are unable to visit others pages of the website. Therefore you should disable this feature.

• 4. Do not put too many social bookmarking links on the page

Users like the clean pages and so does search engine. Therefore we suggest you to put social bookmarking links in the valuable content pages, rather than leave around everywhere.

• 5. Redirect www and non www domain name to the same page

It is very simple. Add the following code to .htaccess file and pay attention to replace MyDomain.com with your own domain name

## Can be commented out if causes errors.
Options FollowSymLinks
# mod_rewrite in use

RewriteEngine On
RewriteCond %{HTTP_HOST} ^MyDomain.com$ [NC]
RewriteRule ^(.*)$ http://www.MyDomain.com/$1 [R=301,L]
RewriteCond %{HTTP_HOST} !^.*MyDomain.com [NC]
RewriteRule (.*) http://www.MyDomain.com/$1 [R=301,L]

• 6. Open the website cache

Search engines like to visit the fast speed website, open this option, and make your site the better performance.

• 7.Fill in the complete description for each section and category.

It can help to improve the site’s page rank and optimize search engine visit.

• 8. Simple is beautiful

Thousands of pages indexed by Google is not a good thing, especially some of  the pages have little value content .Google usually does not like it. Some of Joomla’s components will generate a lot of pages and some of them are useless for the website. You should enter site:mydomain.com in Google for checking. If the indexed pages contain no significant value, you can remove them from Joomla.

• 9. Fill in metadata in Joomla’s Global Settings page

Complete the installation of Joomla, the default metadata is “Joomla! – The dynamic portal engine and content management system”. If you do not want it as the description of your site, change it.

• 10.Confidence

Joomla designer takes into account the SEO problems. It is a great CMS and you should learn how Joomla works. You’ll find your site have a higher search rankings soon.

One of many key features of eZ publish is flexibility. You can customize almost anything from content structure to output presentation. In this short tutorial I will show how to specify a custom default root node class.
By default, eZ publish uses a root node ID 2 in content structure (“Content structure” tab) tree based on the folder class, and in many cases that is sufficient. However, sometimes we want to use our own custom class as the site’s front page. A custom class allows us to build a complex front page that uses a different layout than the rest of the site. Rather than extending the default folder class with attributes that are only used on the front page, creating a custom class gives us the flexibility to build a custom front page without impacting the rest of the site.
First we need to create new content class. You can define your new content class in the Administration Interface. Click the Setup tab, then select the Classes option from the left menu. I will not describe this process as it is very well explained in the eZ publish technical manual.
Note that your custom class must be marked as a ?container? in order to display content from within the content structure tree.
Once the content class is ready to use, create a new content object as an instance of your new class somewhere under the root node. Now we can swap the eZ publish root node with the newly created object. Click the left mouse button on the folder icon beside the root node folder name and select “Advanced->Swap with another node” from the context menu.

In browse mode choose the newly created object and click the “Select” button.

Done. Now you can edit your root node and populate the attributes of your custom class with content.
Next we need to configure the content structure tree.
Edit the file “settings/siteaccess/(your_admin_siteaccess)/contentstructuremenu.ini.append.php” and add your class to the list. Your configuration file should contain the following data:
[TreeMenu]
ShowClasses[]
ShowClasses[]=folder
ShowClasses[]=user_group
ShowClasses[]=custom_class
*/ ?>
Save your settings and clear the cache. After the page reloads, you should see your custom front page in the content structure, similar to the picture below:

Now you can assign a template to your custom class or make a node override for node ID 2 and make nice front page for your site.

Tianfu subsite1, or Human Resourcs Solution Center has been developped and released online. It is a standard content management system(CMS) solution. Clean design with slideshow feature on home page presents quick information to users.

tianfusoftware-humanresourcesolutioncenter

More info? Please see at http://www.tianfusoftwarepark.com/hrsc/index.php