Joke Collection Website - Blessing messages - I cannot log in to the Dreamweaver backend, and it prompts that the verification code is incorrect. How to solve the problem?

I cannot log in to the Dreamweaver backend, and it prompts that the verification code is incorrect. How to solve the problem?

When I cannot log in to the DreamWeaver backend, it prompts that the verification code is incorrect\x0d\1. The password is obviously correct, but I cannot log in to the backend management\x0d\Answer:\x0d\In addition, whether you are a newbie or phper, It should be noted that the username and password can only be composed of [a-z A-Z - _ @ .] and cannot be Chinese or other symbols. \x0d\2. The verification code is obviously correct, but it prompts that the verification code is incorrect and cannot log in to the backend. \x0d\Answer: I just cleared the cookies and IE temporary folder, and it worked. If not, see below. \x0d\Enter the root directory through FTP\x0d\Modify inc_safe_config.php under /data/safe\x0d\Remove the 6 in the $safe_gdopen value and the verification code will not appear when logging in to the background\x0d\For example: $safe_gdopen = '1, 2, 3, 4, 5, 7';\x0d\\x0d\If it still doesn't work, you can't enter the background~ Although there is no verification code, it prompts that the password is wrong. . No matter how I enter it, it always prompts that the password is wrong\x0d\Other people say that there is no write permission\x0d\The answer is to identify the password without write permission\x0d\Therefore, it is indeed your password that is wrong\x0d\\x0d\The latest discovery can solve DEDE How to solve the problem of "incorrect verification code" when logging into the backend of a template website \x0d\ Today, a dreamweaver CMS website I built for a client showed up again when logging into the DED backend, prompting: The verification code is incorrect. \x0d\ I tried many solutions but couldn't solve it. Finally, I used the following method to finally solve it.

\x0d\The solution is given below:\x0d\\x0d\First, enter the data/session directory and delete all other session files in this directory except index.htm. Then clear the cache of the local IE browser. \x0d\Finally, it was normal to re-enter the backend homepage of the DreamWeaver website. This is the quickest solution for me to solve the problem of incorrect verification code when the background login prompt of the Dedecms template website is incorrect. \x0d\ The more common problem is the permission setting of the directory, which leads to the problem of background file permissions. For details, please refer to the "DEDE Dream Weaver Directory Permission Security Setting Instructions Document Important\x0d\ dede5.7 verification code is incorrect solution, provide me with a solution In the situation encountered, /data/sessions does not have write permissions, just give sufficient permissions. \x0d\ \x0d\[Other issues] Summary of solutions to various dede backend login verification codes that are incorrect or not displayed: \x0d\ \x0d\ Summary of various dede backend login verification codes that are incorrect or not displayed! What is common is that the verification code is clearly entered correctly but the prompt is incorrect, or it is not displayed at all. Let’s talk about several reasons for encountering this situation:\x0d\①The dede version program upgrade operation is incorrect and the verification code prompt is incorrect\x0d\②Better Space New Space There is a problem with the gd library configuration in pho.ini in the new space\x0d\ ③The website space is full\x0d\④Specially caused by the transfer of the data directory in version 5.7 (please see: How to correctly migrate the dede dreamweaver data directory and the solutions to the problems caused)\x0d\⑤In-program /data/session Directory permission setting problem\x0d\⑥Clear the cookies of the browser and restart the browser;\x0d\⑦The network speed is not good, change the time and try again when the network speed is faster!\x0d\⑧The website program has an error, re-upload and install;\ x0d\Okay, the reason why dede backend login verification code is incorrect or not displayed has been found, so now let’s summarize the solution. \x0d\1. If it is caused by the transferred data directory of version 5.7.

\x0d\Please change the file /include/vdimgck.php. This file also calls the file in DATA. You can also change the path. Change the /../data with this to your current\x0d\\x0d\ path. \x0d\2. After consulting the information, I learned that the session has not been cleared. Just go to the data/session directory and delete all files except index.html. \x0d\3. If it still doesn't work, check whether the session has write permissions. If not, add write permissions to the "internet guest account". For Linux, set the directory permissions \x0d\\x0d\ to "777". 4. Set the server's php.ini: Open the php.ini file and find it; session.save_path = "/tmp" and rewrite it as session.cookie_path = /\x0d\extension=php_gd2.dll; remove the semicolon in front of it. \x0d\5. Check whether your space is full. The test method is that you can upload a file in the FTP space at will. There will be a prompt and you can contact the space service provider. \x0d\6. Remove the verification code directly: open login.php and find: \x0d\if($validate=='' || $validate != $svali)\x0d\Replace with: \x0d\if( false )\ x0d\Then, remove the specific HTML code of the following verification code in the template dede/templets/login.htm: \x0d\Verification code: \x0d\ \x0d\\x0d\ Or: in [Verification Code Security Settings], It is said that the modified save actually modified the data\safe\inc_safe_config.php file, which is a configuration\x0d\\x0d\ file. \x0d\For example: $safe_gdopen = '1, 2, 3, 5, 6'; This is where the verification code is enabled in the system. There is a one-to-one relationship with the [Verification Code Security Settings] interface. \x0d\So, if we want to turn off the verification code in the management background (if the verification code cannot be entered correctly and the GB library is not supported), we only need to open data\safe\x0d\\x0d\\inc_safe_config.php and set $safe_gdopen = '1, 2, 3, 5, 6'; just delete the 6 in it. No need to go through tedious settings. \x0d\As shown in \x0d\7, modify the vdimgck.php file in the include folder and modify the following paragraphs, \x0d\//Session save path\x0d\$sessSavePath = dirname(__FILE__)."/../data/ sessions/";\x0d\Modify it to //$sessSavePath = dirname(__FILE__)."/../data/sessions/";\x0d\After the modification, it sometimes works and sometimes doesn't work, and the same situation happens when you change it back. If you change the DEDE background path to the default DEDE folder, there will be no verification code errors\x0d\\x0d\. Finally, if none of the above methods apply, then reinstall the corresponding version of the program, and then transfer your css and image files, template files, and upload file \x0d\ folder. Finally restore the database.