WP toolkit can't scan for exiting site
Hello everyone,
WP Toolkit generally works well for me, but on 1 account, it just won't detect an exisitng Wordpress installation.
Any pointers?
Thanks everyone
-
Whats the error you get when running the command? 0 -
Whats the error you get when running the command?
This is what I got after running the command:Warning: Current locale is unusable. Using 'C' instead. WordPress installation was added to WordPress Toolkit.
I checked WPtoolkit on both Cpanel + WHM, still not added :-?0 -
This is what I got after running the command:
Warning: Current locale is unusable. Using 'C' instead. WordPress installation was added to WordPress Toolkit.
I checked WPtoolkit on both Cpanel + WHM, still not added :-?
@PeterN123 what did you get when runlocale
UPDATE: This is what I get on my server with AlmaLinux 8.5.0[root@server1 ~]# locale LANG=en_US.UTF-8 LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL=
andlocale -a
what operating system are you using ?0 -
You can find global locale settings in the following files: - /etc/default/locale " on Ubuntu/Debian
- /etc/locale.conf " on CentOS/RHEL
0 -
You can find global locale settings in the following files:
- /etc/default/locale " on Ubuntu/Debian
- /etc/locale.conf " on CentOS/RHEL
0 -
Thanks so much, it is currently running: LANG="en_US.UTF-8" Do you think I should change to LANG=en_IN.UTF-8?
I change it to US sorry I write down IN by mistake the correct one should be en_US.UTF-80 -
Thanks so much, it is currently running: LANG="en_US.UTF-8" Do you think I should change to LANG=en_IN.UTF-8?
I change it to US sorry I write down IN by mistake the correct one should be en_US.UTFThanks so much, it is currently running: LANG="en_US.UTF-8" Do you think I should change to LANG=en_IN.UTF-8?
run this command cat /etc/locale.conf0 -
I change it to US sorry I write down IN by mistake the correct one should be en_US.UTF run this command cat /etc/locale.conf
Sure, this is what i got:LANG="en_US.UTF-8"
Please note, It didn't make any changes.0 -
Sure, this is what i got:
LANG="en_US.UTF-8"
Please note, It didn't make any changes.
yes no just getting information what system are you using ? Almalinux ? centOS 7 ? Ubuntu ?0 -
yes no just getting information what system are you using ? Almalinux ? centOS 7 ? Ubuntu ?
Yes, I am running CentOS 7, just weird that all others WP working fine just except this site. The language of the site is Vietnamese by the way.0 -
Yes, I am running CentOS 7, just weird that all others WP working fine just except this site. The language of the site is Vietnamese by the way.
is that the only one that is Vietnamese ?0 -
is that the only one that is Vietnamese ?
Ah no, not at all. There are a few sites in there that is vietnamese as well. 1 thing I want to note is that, the site was detected properly. 2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-? Just odd.0 -
Ah no, not at all. There are a few sites in there that is vietnamese as well. 1 thing I want to note is that, the site was detected properly. 2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-? Just odd.
when going to the website it is working yes ? or completely down0 -
Ah no, not at all. There are a few sites in there that is vietnamese as well. 1 thing I want to note is that, the site was detected properly. 2 weeks ago, the site went down due to updates, I then recovered the site from Jetbackup 5, I am unsure if was able to be detected at that time, I just recently try again and it can't be found by WPtoolkit anymore. :-? Just odd.
@PeterN123 ok just found something interesting.. maybe you can try this go to that users home directory and see if this file is there .wp-toolkit-ignore check home/ and home/public_html if found rename that file DO NOT delete it just rename to .wp-toolkit-ignore.bkp so after we try to scan and find it - if it still does not we can rename back to the original name just rename for a moment then try again to scan and see if it finds it this time I found this on Plesk which is how we got the Wordpress toolkit from. Cause Starting from WordPress Toolkit 5.9.2 detached WordPress instances are no longer re-added through the Scan procedure, making their detachment permanent. Resolution If the website should be added to WordPress Toolkit back for some reason, perform the following:- Log into Plesk.
- Go to Domains > example.com > File Manager.
- Find and remove the .wp-toolkit-ignore file in the domain's document root.
- As soon as the file is removed, go to the WordPress menu and re-scan instances.
0 -
@PeterN123 ok just found something interesting.. maybe you can try this go to that users home directory and see if this file is there .wp-toolkit-ignore check home/ and home/public_html if found rename that file DO NOT delete it just rename to .wp-toolkit-ignore.bkp so after we try to scan and find it - if it still does not we can rename back to the original name just rename for a moment then try again to scan and see if it finds it this time I found this on Plesk which is how we got the Wordpress toolkit from. Cause Starting from WordPress Toolkit 5.9.2 detached WordPress instances are no longer re-added through the Scan procedure, making their detachment permanent. Resolution If the website should be added to WordPress Toolkit back for some reason, perform the following:
- Log into Plesk.
- Go to Domains > example.com > File Manager.
- Find and remove the .wp-toolkit-ignore file in the domain's document root.
- As soon as the file is removed, go to the WordPress menu and re-scan instances.
Hey I actually did that before but couldn't find the wp-toolkit-ignore file. BUt, I just tried changing site PHP to 7.3 and it is now detected :| Super weird. I then revert it back to 7.4, it is detectable now, any idea how this happen?0 -
Hey I actually did that before but couldn't find the wp-toolkit-ignore file. BUt, I just tried changing site PHP to 7.3 and it is now detected :| Super weird. I then revert it back to 7.4, it is detectable now, any idea how this happen?
I will have to defer that question to someone else @cPRex when or someone whom might have that answer. The good thing is it worked :) maybe php.ini was 7.3 prior to transfer and update from jet 5 when you recovered the site ? I am not 100% sure. At least there was some workaround that worked. Im glad it works :)0 -
Good job here guys! 0 -
I'm not 100% sure either, but the most likely explanation would be some type of .htaccess weirdness that got fixed when the site's PHP version was adjusted, as that gets written to the local .htaccess file. 0
Please sign in to leave a comment.
Comments
20 comments