Shulou(Shulou.com)06/02 Report--

Editor to share with you phpcms v9 double name can not pass the solution, I hope you will learn a lot after reading this article, let's discuss it together!

What if the phpcms v9 duplicate name fails?

Scenario: PHPSSO can not communicate solution in phpcms v9 (PHPSSO's inability to communicate indirectly affects phpcms v9 registered members unable to pass "duplicate name cannot be passed")

In general, most people do this:

Make a virtual environment locally, install V9 system with localhost or 127.0.0.1, there is no problem with local communication, so make a local data backup. At that time, the remote installation will be installed through the domain name, and then the local data will be directly restored to the remote server. This often happens that SSO and V9 systems can not communicate.

Since the data link in the backup saves the URL localhost or 127.0.0.1 or native 192.168.xxx.xxx, which is inconsistent with the domain name, for example, SSO corresponds to www.lanrensc.com, while the V9 system after data recovery corresponds to localhost or 127.0.0.1, of course, you cannot communicate if the two are inconsistent. This is one of the most common reasons, which can be solved according to official methods.

Of course, if you find that the official method cannot be solved, it is estimated that you use local V9 to directly overwrite the remote end according to all the source code under the directory, including the Cache of V9Cache and SSO generated by installation. You should know that the database information recorded in cache on this machine and on the server is different, especially the Linux system with strict permission restrictions, so it is usually impossible to communicate even according to the official method.

Reason 2: local V9 Cache and SSO Cache overwrite the corresponding files of the server, which is the second most common reason for being unable to communicate. You can try to modify several files in cache:\ caches\ configs\ and\ phpsso_server\ caches\ configs directory system.php and database.php. You can check whether the configuration file datebase.php in caches is the data you need.

Apart from the above two reasons, there are two possibilities:

First, if it is a linux server, the permissions of the website directory are set incorrectly, which may lead to inability to communicate.

Second, the two domain names with www and without www point to the same server at the same time. If you install V9 with a top-level domain name that is not included, but the local machine uses www.lanrensc.com, the communication will also fail.

Especially for the second reason, many people may ignore it! With or without WWW,sso that is considered to be two different applications, different applications are of course unable to communicate.

To avoid uncommunicable problems with V9 and SSO, it is recommended to do this:

1. If your local data does not need to be restored to the server, just upload the template file directly. Do not overwrite the remote cache folder.

2. If the local machine has data to recover to the server, remember not to save the table with the prefixes v9_admin, v9_member and v9_sso when saving the local data. Install V9 remotely with a new installation, and only upload the SQL backup and template package in the\ caches\ bakup\ default\ folder after installation.

3. Remember, a lot of times, there are two different applications with and without www,SSO, even if both point to the same server. If you mainly use www, remember to use it to install V9.

4Jing FTP server, please pay attention to the permission to install the V9 directory. Please upload it in binary if the server is an independent host. If the server is an independent host, you are not recommended to use the account with root permission to upload the V9 program, but to use the associated account when you set up the site.

To provide a new solution to the SSO communication problem is:

Create a data backup of a table that does not contain the prefixes v9_admin, v9_member and v9_sso (it doesn't matter locally or on the server), then install a brand new V9 on the server (overwrite the folder with the same name on the server with the install, cache and phpssoserver directories in the latest V9, and delete the install.lock file in cache) to ensure that the newly installed V9 communication is successful, so that the previous backup can be restored.

After reading this article, I believe you have a certain understanding of the solution of phpcms v9 double name can not pass, want to know more related knowledge, welcome to follow the industry information channel, thank you for reading!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.