Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • How do I check that? I am sadly not that highly experienced with WordPress nor with debugging something :/

    I added the dot to ‘/lang’ to have it read ‘./lang’ and since then I have no further issues and also error_log from Apache2 no longer spits out anything regarding Content Press having an issue with open_basedir.

    I fixed it.

    Change:

    load_plugin_textdomain( ‘content-progress’, false, dirname( plugin_basename( __FILE__ ) . ‘/lang’ ) );

    to

    load_plugin_textdomain( ‘content-progress’, false, dirname( plugin_basename( __FILE__ ) . ‘./lang’ ) );

    The dot is missing before /lang. This results in a directory resolving issue on Linux Machines.

    I add to this issue, since I face it as well.

    My current setup is:

    Latest WordPress Version
    Latest Content Progress Version
    OS: Ubuntu 12.04 LTS
    Plesk 11
    open_basedir on for security reasons

    I have a single WordPress Installation and so far only Timthumb (fixed it) had issues and Content Progress.

    There seems to be an issue with reading the lang files properly, because the path “…/wp-content/plugins/content-progress/content-progress.php/content-progress-de_DE.mo” seems to be invalid. It causes high loading times :/

    I surely am not a PHP Coder, but I think it comes down to this line (and what is attached to it):

    load_plugin_textdomain( ‘content-progress’, false, dirname( plugin_basename( __FILE__ ) . ‘/lang’ ) );

Viewing 4 replies - 1 through 4 (of 4 total)