What should I do if phpcms v9 cannot pass the duplicate name?

What should I do if phpcms v9 cannot pass with the same name?

Scenario: Solution to PHPSSO’s inability to communicate in phpcms v9 (PHPSSO’s inability to communicate indirectly affects phpcms v9 registered members who cannot pass “duplicate names cannot pass”)

Under normal circumstances , most people do this:

Create a virtual environment locally, install the V9 system using 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 would be installed through the domain name, and then the local data would be restored directly to the remote server. In this case, it often happened that SSO and the V9 system could not communicate

Due to the data in the backup The link saved is that the URL is localhost or 127.0.0.1 or the local machine 192.168.xxx.xxx, which is inconsistent with the domain name. For example, SSO corresponds to www.lanrensc.com, and the V9 system after data recovery corresponds to localhost or 127.0.0.1 If the two are inconsistent, of course communication will be impossible. This is one of the most common reasons and can generally be solved according to the official methods.

Of course, if you find that the official method cannot solve the problem, it is estimated that you use local V9 to directly overwrite the remote one according to all the source codes in the directory, including the V9Cache and SSO Cache generated due to installation. You need to know The database information recorded in the cache on the local machine and the server is different, especially in Linux systems with strict permission restrictions, so even if the official method is used, communication is usually still impossible.

Reason 2: V9 of the local machine The Cache of Cache and SSO overwrites the corresponding files of the server. This is the second most common reason for failure to communicate. You can try to modify several files in the cache: system in the \caches\configs\ and \phpsso_server\caches\configs directories. .php and database.php, I won’t go into details about the specific modification method. You can check whether the configuration file datebase.php in the cache is the data you need.

In addition to the above two reasons, there are two possibilities:

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

Second, The two domain names with www and without www point to the same server at the same time. When installing V9, if the top-level domain name without www is installed, but the local machine uses www.lanrensc.com, communication will fail in this case

Especially the second reason, many people may have ignored it! Whether you have WWW or not, SSO thinks they are two different applications. Of course, different applications cannot communicate. . .

To avoid communication problems between 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 there is data on the local machine that needs to be restored to the server, remember not to save tables containing the three prefixes of v9_admin, v9_member and v9_sso when saving local data. When installing V9 remotely, use a new installation. After the installation is completed, only upload the SQL backup and template package

3 in the \caches\bakup\default\ folder. Remember, many times, with www and no With www, SSO considers them two different applications, even if they point to the same server. If you mainly use www, remember to use it to install V9.

4, Linux server, please pay attention to the permissions of the installation directory of V9. Please use binary upload for FTP upload. If the server is an independent host and you have root permissions, it is not recommended to use an account with root permissions to upload. Instead, use Create The associated account at the site uploads the V9 program.

A new way to solve the SSO communication problem is:

Create a data backup of the table that does not contain the three prefixes of v9_admin, v9_member and v9_sso (local or on the server, it doesn’t matter), 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.lock file in the cache) to ensure this The newly installed V9 communication is successful, so just restore the previous backup.

PHP Chinese website, a large number of free PHPCMS tutorials, welcome to learn online!

The above is the detailed content of What should I do if phpcms v9 cannot pass the duplicate name?. For more information, please follow other related articles on the PHP Chinese website!