WordPress.org

Ready to get started?Download WordPress

Forums

Codestyling Localization
[resolved] No detection of language files of plugin Cimy User Extra Fields? (6 posts)

  1. let me see...
    Member
    Posted 3 years ago #

    Hello,

    despite Cimy User Extra Fields having several language files, they are not detected by this otherwise great plugin. Renaming the folder had no effect (from "langs" to "lang").

    What can I do?

  2. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    Could you please describe the problem more specific and also with examples what won't work?
    You didn't name any theme or plugin that will not work. Please provide more info for solving this.

  3. let me see...
    Member
    Posted 3 years ago #

    There is really not much more to say about it - in the list of plugins resp. their language files (menu under "Lokalisierung") it shows 0 language files for the plugin "Cimy User Extra Fields". However, this very plugin has a folder "langs" and 10 language files (po+mo) in it (I checked my server, it is all there). Everything else works (all other plugins & WordPress localisation...), just this one plugin's language files don't show up.

    So, I cannot edit or work with these language files, since I cannot access them via your plugin. I am a bit stuck now, since PoEdit does not work on my PC.

    Do you want a screenshot? I can send one if you want... my theme is "Striking" (from Envato Marketplace), if that is of interest for you.

  4. let me see...
    Member
    Posted 3 years ago #

    BTW, I also tried deactivating and also reinstalling Codystyling Localization, just to be sure; but to no avail. I already customized Fields in Cimy User Extra Fields, but if you say it really is necessary, I could reinstall it, too.

    Maybe you could also install it and tell me if you were able to work on its language files on your installation? Then we would know it's something on my side... Cimy User Extra Fields Plugin

  5. codestyling
    Member
    Plugin Author

    Posted 3 years ago #

    I've tested this plugin locally and the author defined the textdomain in a way not qualified parseable. Nevertheless I wrote additional code for upcomming version 1.99.10 having at least a work arround for this problem. But this also results in a "maybe" classification of this plugin even if it works afterwards.
    Other plugins doing similar unparseable things may not be working, thats why it got this classification too.
    If the author would have been using a constant definition for the textdomain, it would not be a problem. But having this at a variable makes it impossible to find while plugin is not active.
    Please update to the upcomming version if it is available in a few hours.

  6. let me see...
    Member
    Posted 3 years ago #

    Thank you very much! I will notify the author Marco Cimmino, maybe he would like to take a look at this.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic