2 new errors since update to 2.1.0

  • HeliR

    (@helir)


    14 years, 10 months ago

    updated today to new plugin-version, since then 2 Error-Msg that have not been there before

    1) BackWPup: – WP-Cron arbeitet nicht, bitte überprüfen Sie die Funktion!

    in Settings I have not checked “dont use WP-Cron” (have checked / unchecked to put maybe newly added settings into settings-file)

    2) following Error-Msg I get throughout the entire Plugin and in Dashboard

    Warning: is_writable() [function.is-writable]: open_basedir restriction in effect. File(/tmp) is not within the allowed path(s): (/home/.sites/444/site630/web:/home/.sites/444/site630/tmp:/usr/share/pear) in /home/.sites/444/site630/web/zoo/wp-content/plugins/backwpup/backwpup-functions.php on line 184

    ————————————————–

    now, this plugin is simply great and this 2 errors remind me that I have to donate urgently, because you did a great job and do a super support job!

    if you want to look directly into my installation please tell me, I mail you the datas, tx a lot, best health & wishes !

    Heli

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter HeliR

    (@helir)

    14 years, 10 months ago

    SOLVED the error with is_writeable with following solution found in wordpress.org

    To solve that do following:
    add following line in wp-config.php

    <strong>define('WP_TEMP_DIR', ini_get('upload_tmp_dir'));</strong>

    Daniel told us on his homepage (http://backwpup.com/blog/) that he is now using
    * Uses now ‘WP_TEMP_DIR’ for getting temp folder

    in above blog-entry we see that WP_TEMP_DIR is basically undefined in WordPress, so we have to set it, so Daniel, you better use the above solution to save you from such reports.

    The CRON Error is still present in DASHBOARD

    tx, Heli

    Plugin Contributor Daniel Hüsken

    (@danielhuesken)

    14 years, 10 months ago

    ok, i have both in next version

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

The topic ‘2 new errors since update to 2.1.0’ is closed to new replies.