3.1 Version does not work anymore

  • Florian_discus

    (@florian_discus)


    12 years, 3 months ago

    I just upgraded to 3.1 of xcloner and since then it does not work anymore…

    Xlconer does not work anymore since updateing to 3.1

    To run this script you need to create a custom config file inside XCloner Config, and call the script using php cli command like this:

    doing manually:

    Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in

    Details: parsererror — SyntaxError: JSON.parse: unexpected character

    JSON url: admin-ajax.php?action=json_return&task=recurse_database&nohtml=1&dbbackup_comp=&dbbackup_drop=

    https://ww.wp.xz.cn/plugins/xcloner-backup-and-restore/

Viewing 15 replies - 16 through 30 (of 31 total)
1 2 3
  • Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    Thank you very much. For now I will stick to this version then…

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    I have one more question.

    When restoring I get an error with:

    : a foreign key constraint fails

    the db doesnt work.
    Do I have to make some special settings?

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    And for the xcloner standalone version 3.5 (latest)

    for manual update i get:

    Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /data01/virt30509XCloner/classes/mysqlBackup.class.php on line 108
    Initializing backup…

    also this error

    XCloner

    (@xcloner)

    12 years, 3 months ago

    Disable deprecated errors in your php.ini config, error_reporting parameter…

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    First of all thanks for your really fast and good support.
    Sorry to annoy you further 😉

    ; Error Reporting
    error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT
    display_errors = On
    display_startup_errors = Off
    log_errors = On
    log_errors_max_len = 1024
    ignore_repeated_errors = Off
    ignore_repeated_source = Off
    report_memleaks = Off
    track_errors = Off

    THats only what i can change in the php.ini at least those are the ones named there

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    Could you maybe before importing the database make the settings:

    “SET foreign_key_checks = 0”

    I get always errors like that:

    ###MYSQL error
    Cannot add foreign key constraint
    ###On Query:

    while importing the database.

    XCloner

    (@xcloner)

    12 years, 3 months ago

    The “SET foreign_key_checks = 0” is already added in the latest version of XCloner.php restore script, if that doesn’t work, the issue might be different.

    Regarding php.ini , that is good, simply change error_reporting line to

    error_reporting = E_ALL & ~E_NOTICE & ~E_STRICT & ~E_DEPRECATED

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    I cannot change the phpini webftp, will have to try at home.
    But thanks for the line.

    Regarding the latest restor script:
    What is the latest one?
    3.0.1 ?
    Thats at least the one I have for tar.php and xcloner.php.

    But unfortunately I always receive this foreign key error.

    XCloner

    (@xcloner)

    12 years, 3 months ago

    Latest version of XCloner.php is 3.1.0 , you can download it directly from the latest package and use it when restoring!

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    It seems there is still a bug.
    When i download the lastest standalone package:

    $_CONFIG[‘my_version’] = “3.0.1”;
    $_CONFIG[‘script_name’] = “XCloner.php”;
    $_CONFIG[‘sql_usefile’] = “”;
    $_CONFIG[‘filesLimit’] = 100;
    $_CONFIG[‘seek’] = 0;

    Is within the xcloner.php

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    Ok just saw within the wordpress version it tis 3.1.0
    Maybe you can update the standalone version as well.
    Thanks!
    will give it a try in a bit (maybe tomorrow)

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    It works almost perfectly.
    but i guess I have to check this now again 😉
    it always includes for whatever reason a wp-config.php in that archive 😛

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 3 months ago

    — OUTPUT (166 B) –>
    Could not open input file: /data01/virt30509/domeenid/www.domain.com/htdocs/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php?config=specialcron.php

    How do I call it ? I do have in the corntab like this:
    [[$PHP]] [[$D2ND_A]]/htdocs/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php?config=specialcron.php

    XCloner

    (@xcloner)

    12 years, 2 months ago

    Cron command should be

    [[$PHP]] [[$D2ND_A]]/htdocs/wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php specialcron.php

    Thread Starter Florian_discus

    (@florian_discus)

    12 years, 2 months ago

    I talked to my support and they told me mysqli is available.

    Their answer:
    “Hello

    For Cronjob you have to load PHP modules manually or add -C and the location of PHP.INI fail in the cron it self.”

    What does it mean? How can I fix it? If I can fix it at all?

Viewing 15 replies - 16 through 30 (of 31 total)
1 2 3

The topic ‘3.1 Version does not work anymore’ is closed to new replies.