The Imperial CMS7.2 Edition multi-terminal access feature uses graphic tutorials
With the continuous integration of PC Internet and mobile Internet, as well as the increase of various mobile access terminals, the website mobile interconnection is becoming more and more important, so the Empire CMS7.2 version in the original versionMulti-access terminal featuresBased on, make more improvements, make the site a variety of mobile access to create more convenient. Let's talk about the CMS7.2 version of the Empire "multi-terminal access feature" using:
New Site access steps:
One, set all access to the unified access address;
Second, the new Access end used template group;
Third, create a new access directory, and copy an Imperial CMS program file in;
Iv. binding a two-level domain name to the new access-side directory;
Five, to the main access terminal backstage added "website Access";
Vi. Modify the configuration file parameters to the new access-side directory;
Seven, complete.
The following is a detailed procedure:
One, set all access to the unified access address
Background > System > System parameter settings:
website Address: This address must not add domain name, such as set to:/(the default is not added after the installation of domain name, if modified by itself, please remove the domain name.) ）
Attachment Address: This address must be added to the domain name, such as: http://www.xx.com/d/file/or to the attachment directory/d/file/binding a two-level domain name, and then set to bind the two-level domain name address, such as: http://file.xx.com/
This way, all the access addresses on all sides are unified.
Note: If you change the website address, remember to the back office > System > Data Update > Update information page address: Re-update the content page address. No modifications are not done.
second, the new Access end used template group
(a), the new access to use the template group
1. Export the default template group
Background > Templates > Template Group Management > Import/Export template groups: Export the default Template group template group and save the exported template group *.temp file.
2. Add template groups for access by importing default template groups
Background > Templates > Template Group Management > Import/Export template groups: Import the template group *.temp file that you just exported.
overriding template groups: Be sure to select "New New Template group".
3. After the import is complete, return to the Administrative Templates Group page and modify the imported template group name:
4, the new access end of the template group was added to complete.
(ii), follow-up access to Template group template modification method
1, Mode one: background template management directly modify
Background > Templates: The Default Template group drop-down box at the top of the left menu allows you to select the template under which template group you want to modify, and then you can modify the template for that access end.
2, Mode two: can be locally installed Empire CMS templates for managing and debugging this access-side template group
(1), after the local installation of the Empire, the new access to the template group export, and then import the template group into the local Empire CMS background, so that the local can modify the template.
(2), after modifying the template under the new Access End template group, export the template group, then import the template group in the background of the site, butoverriding template groups: To select the template group for this access side to reach the overlay template effect.
Third, create a new access directory, and copy an Imperial CMS program file in
(i), new access-side directory: can be created in any directory. (Note: Do not build subdirectories in the main-side directory, you should be aware of setting directory permissions.) )
It is generally possible to build subdirectories on the main access side. For example: In the Empire CMS root directory Built "phone" directory to do Mobile Access directory.
(b), copy the primary access directory to the new access-side directory. For example: Copy to the "phone" directory I built above.
Select directories and files, and copy:
Paste the directories and files into your phone's access "Phone" directory:
Related instructions:
1, copy the directory, remember to set up this access to the directory permissions, you need to set the directory permissions list can see the Imperial CMS installation instructions, as well as the site's column directory permissions.
2, you can also copy a new Empire CMS program to the new Access directory, but after copying remember to delete the E/install installation directory, as well as replicate the primary access to the e/config/config.php configuration file in the past. Then set the directory permissions.
Iv. Binding a two-level domain name to the new access-side directory
For example: Bind the m.xx.com to the new access-side phone directory above. (Local tests can modify the hosts file to implement binding domain name effects.) )
Related instructions: The general steps of domain name binding are as follows
1, the Domain name Control Panel set resolution to the server IP
2, the server set the binding domain name to the directory (Apache/iis set)
3. Restart Apache or IIS after Setup.
Domain binding operations need to operate on the server or space, not in the Imperial CMS operating range, detailed operation steps we can Baidu search for a bit.
Five, to the main access side background added "website Access"
(a), main access backend > System > Website multi-access > Manage website access, click on "Add Access":
access-side name: For example, fill in the "Mobile phone access terminal";
access-side address: Fill in the binding level two domain name address, for example: http://m.xx.com/
access-side directory: Fill in the absolute path of the new access-side directory above, for example: d:/empireserver/web/empirecms72/phone/
Communication Key: Fill in any character within 100 characters.
working with template groups: Select the new access-side template group above.
Page Mode：
Select "Force dynamic page Mode": The access side is dynamic display, do not need to refresh the page update;
Select "Same as primary": If the main side is in static page mode, it needs to refresh the page in the background of this access to display synchronously.
Close the access side: Not selected.
Close Submissions: Select Close if this access does not use contributions.
After setting the "Submit" button, add back "Manage Web site access" to see the site Access ID, write down.
(b), return to "manage website access", click "Update all Access side cache and dynamic page", Direct click "Submit" button to update the cache.
six, to the new access-side directory, modify the configuration file parameters
Modify the/e/config/config.php configuration file under the new Access directory (such as the phone directory above), set the following two parameters: (UTF-8 version must not be modified with Notepad, otherwise the contents of the file will be converted to GBK, it is recommended to modify with Dreamweaver.) ）
$ecms _config[' sets ' [' Deftempid ']=0; Default Template group ID
$ecms _config[' sets ' [' Selfmoreportid ']=0; Current site access End id,0 Primary access |
Fill in separatelytemplate group ID used on this access sideAndAccess ID of this website。 For example, instead:
$ecms _config[' sets ' [' Deftempid ']=2; Default Template group ID
$ecms _config[' sets ' [' Selfmoreportid ']=2; Current site access End id,0 Primary access |
Save the file after you modify it.
Seven, to this point, the new access end has been added, you can access the new End address view effect. The rest of the story is to modify the access-side template.
Related instructions:
1, it is recommended that the main access template after the completion of the production, and then increase the other site access.
2, after the main access end to modify the site access configuration parameters, to update the next all the access to the database cache, before it can take effect.
3, after the main access end of the backend, the access side of the foreground all dynamic pages will not be used, but the static page is not affected by the access.
4, multi-access end of the dynamic template are independent, if the dynamic page also to be different, login to the backend to modify the dynamic page template, in order to achieve a comprehensive personalization.
The Empire CMS7.2 version of the mobile end of the two scenarios differences:
1. Multi-terminal access function:
Support for n access-side production, the need to copy multiple empires, and then make each end of the independent access-side template, and each end of the page is independent, support browsing and dynamic interaction, comprehensive high.
2, WAP Mobile Access function:
If the mobile side only provides browsing information function, with WAP more convenient point, do not need to copy multiple empires, create a WAP template.
RELATED LINKS
The Empire CMS7.2 version of WAP system features updated to better suit smartphones
WAP Management Using Tutorials
Empire CMS5.1 Open Source version of the first to Know (a): New WAP Mobile browsing function |
|
