WordPress.org

1. AnonymButFamous
   Member
   Posted 2 years ago #

   When I try to "rescan" in my admin-panel (Tools -> Localization) I get some problems. Please see this picture: http://i48.tinypic.com/152jdpw.jpg

   Or see the following text (myUSERnameX has replaced my actual username, which nearly have the same name as my website - I don't want to tell which site I'm working on, however if it's very important I will of course tell):

   Warning: scandir(/home/myUSERnameX/public_html/wp-content/themes/default/) [function.scandir]: failed to open dir: No such file or directory in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php  on line 238
   
   Warning: scandir() [function.scandir]: (errno 2): No such file or directory in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php on line 238
   
   Warning: array_diff() [function.array-diff]: Argument #1 is not an array in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php on line 238
   
   Warning: Invalid argument supplied for foreach() in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php on line 239
   
   Warning: scandir(/home/myUSERnameX/public_html/wp-content/themes/classic/) [function.scandir]: failed to open dir: No such file or directory in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php on line 238
   
   Warning: scandir() [function.scandir]: (errno 2): No such file or directory in /home/myUSERnameX/public_html/wp-content/plugins/codestyling-localization/codestyling-localization.php on line 238

   What should I do?

2. AnonymButFamous
   Member
   Posted 2 years ago #

   No one?

3. AnonymButFamous
   Member
   Posted 2 years ago #

   This problem comes up sometimes when I try to rescan in the Localization-menu. I've reinstalled WordPress around 35 times now. The problem is over (well, atleast for now) now, however, I'm sure the same problem will come up again (as it have done plenty of times now) so I hope the plugin creator will fix this in a later plugin-version.

Topic Closed

This topic has been closed to new replies.