PHPSSO cannot communicate in phpcmsv9 (PHPSSO cannot communicate, which indirectly affects the failure of phpcmsv9 registered members to pass "duplicate names cannot pass ")

PHPSSO cannot communicate in phpcmsv9 (PHPSSO cannot communicate indirectly affects phpcmsv9 registrants cannot pass "duplicate names cannot pass"). In general, most people do this: make a local virtual environment and use localhost or 127.0.0.1 to install the V9 system. there is no problem with local communication, so we will make a local data backup, at that time, during remote installation, domain names are used for installation, then, you can directly restore the local data to the solution that PHPSSO cannot communicate in phpcms v9 (PHPSSO cannot communicate, which indirectly affects the failure of phpcms v9 registered members to pass "duplicate names cannot pass ")

Generally, most people do this:

Make a local virtual environment and use localhost or 127.0.0.1 to install the V9 system. there is no problem with local communication, so we will make a local data backup, at the time of remote installation, domain names are used for installation, and local data is directly restored to the remote server. in this case, SSO and V9 systems are often unable to communicate.

The data link in the backup stores the website address localhost, 127.0.0.1, or 192.168.xxx.xxx, which is inconsistent with the domain name. for example, SSO corresponds to www.lanrensc.com, after the data is restored, the V9 system corresponds to localhost or 127.0.0.1. communication fails if the two are inconsistent. this is one of the most common reasons. generally, it can be solved according to the official method.

Of course, if you find that the methods provided by the official website cannot be solved, it is estimated that you use local V9 to directly overwrite the remote network based on all the source code in the directory, including the V9Cache and SSO Cache generated by the installation, you must know that the database information recorded in the cache on the local machine and server is different, especially for Linux systems with strict permission restrictions, therefore, even though the official method is provided, communication is still unavailable.

Cause 2: V9 Cache and SSO Cache on the local machine overwrite the corresponding files on the server. this is the second common cause of communication failure. you can try to modify several files in the cache: \ caches \ configs \ and system under the \ phpsso_server \ caches \ configs directory. php and database. php. you can view the configuration file datebase in caches. whether php is the data you need.

There are two possible causes except the preceding two:
First, if the website directory permission is set incorrectly on a linux server, communication may fail.
Second, the two domain names with and without www point to a server at the same time. when V9 is installed, if the top-level domain name is not installed, but the local machine uses www.lanrensc.com, communication will also fail.

In particular, the second reason may be ignored by many people! If there is no WWW, sso is considered to be two different applications. of course, different applications cannot communicate...

Avoid communication failures between V9 and SSO. we recommend that you do this:
1. if your local data does not need to be restored to the server, you can directly upload the template file without overwriting the remote cache folder.
2. if the local machine has data to be restored to the server, remember not to save the tables with the v9_admin, v9_member, and v9_sso prefixes when saving the local data, install V9 remotely. after the installation is complete, only the SQL backup and template packages in the \ caches \ bakup \ default \ folder are uploaded.
3. Remember, in many cases, SSO is considered to be two different applications with or without www, even if the two point to the same server. If you are using www, remember to use it to install V9.
4. for Linux server, please pay attention to the permission to install the V9 Directory. for FTP upload, please use binary Upload. if the server is an independent host, you are not recommended to use the root account for upload if you have the root permission, instead, upload the V9 program with the associated account when the site is created.

To solve the SSO communication problem, provide the following methods:
Create a data backup for a table that does not contain the v9_admin, v9_member, and v9_sso prefixes (it does not matter on the local machine or server ), then install a brand new V9 on the server (use the install, cache, and phpssoserver directories in the latest V9 to overwrite the folder with the same name on the server, and delete the install in the cache. to ensure that the newly installed V9 communication is successful, so that the previous backup can be restored.