WordPress.org

Ready to get started?Download WordPress

Forums

Codestyling Localization
[resolved] Codestyling Localization (13 posts)

  1. kopgamer
    Member
    Posted 3 years ago #

    I love to use this plugin, and I'm using for years..
    But at my last site, rescan option isn't working. I had to delete the language files and make a fresh new one to start translation.

    How can I fix this?

  2. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    Could you please describe the problem more specific?
    What happens and what went wrong doing so?
    Rescan may only fail, of the files at the server have the wrong user rights and the script is not allowed to access them.

  3. kopgamer
    Member
    Posted 3 years ago #

    Which files?? I did some chmod to some of them to 777 but didn't make any difference?

    The problem is this:

    When I install a new plugin with a language file I need to edit, it gives this error:
    Your translation file doesn't support the multiple textdomains in one translation file extension.
    Please re-scan the related source files at the overview page to enable this feature.

    So when I go back and try to rescan, it doesn't rescan anything. Not the new installed one, nor the other installed plugin files. I just had to delete it & make a new language file in order to translate.

  4. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    Do you need FTP credential for automatic updates at this install? If yes, than this server may be not suitable for this plugin. Currently it can't deal with servers, where the files can't be changed because of ownership is different to running script. This is subject of future change.
    If you switch the ownership of existing files to those the plugin creates, than it should work. Please check this.

  5. kopgamer
    Member
    Posted 3 years ago #

    I don't think it needed FTP credential for a update. It got updated a day ago via WordPress automatic updating process. I didn't do anything.

    Also I'm using Godaddy hosting which isn't the best I know...

  6. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    Question: Are the permission buttons for po and mo files green or red colored? In case of showing in red, it can't be scanned, please press the red buttons to get the correct file permissions. I have no other idea, it seems to be related to the file permissions at the hoster.

  7. kopgamer
    Member
    Posted 3 years ago #

    If you mean the small boxes that says ".po & .mo" they are green, I never seen them red.

  8. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    GoDaddy seems to have problems with file access permissions. The *.po and *.mo files need to have permission 666 or 664 or 644 to be readable/writable. (from highest needed down to lowest, also known as [rw-|rw-|rw-] or [rw-|rw-|r--] or [rw-|r--|r--]).
    Could you please check at a file not scannable or editible what permissions it has?

  9. kopgamer
    Member
    Posted 3 years ago #

    The pot files have permissions of 644[rw-|r--|r--].

    I changed them to 777, but still no luck. I just updated Codestyling to newest version also. If you like I can manage you a back-pass.

  10. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    The permission 777 (includes execute) is not necessary, 666 is enough in highest case. It would be a good idea to have a look at the affected WordPress install to understand the issue. Unfortunately I'm off until Monday. Would you please so kind and provide an appropriated access for testing purpose and send me a mail about, so I can help you starting Monday 20.06. earliest.

  11. kopgamer
    Member
    Posted 3 years ago #

    Ok, I'll assign you a membership on weekend but I don't know your email. Can I use your paypal address?

  12. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    You can also use my address from imprint page.

  13. codestyling
    Member
    Plugin Author

    Posted 2 years ago #

    closed because of no further response from intial topic opener.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic