Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • Thread Starter avtop

    (@avtop)

    Hi!
    Are there any chances for this issue to be resolved?

    Thread Starter avtop

    (@avtop)

    Well… I’ll probably take a pause with this issue and reopen the topic after research. Thanks a lot for the reply.

    Thread Starter avtop

    (@avtop)

    Sorry for the silence, I missed notification of your reply in this topic.
    I had problem with one of plugins that could not be updated because of cURL being not enabled. That issue was resolved by installing another plugin. And when I started discovering the issue about Google reCAPTHA I found many cases of using Google reCAPTHA with cURL. Thus I started to suspect cURL to be the reason of the problem

    avtop

    (@avtop)

    The issue was resolved for me by adding
    define( 'ALTERNATE_WP_CRON', true );
    to wp-config.php

    avtop

    (@avtop)

    …and yes, folders: uploads/, backwpup-e51577-temp/, backwpup-e51577-logs/ are writable

    avtop

    (@avtop)

    And I get the same error with 3.4.4.

    WordPress version	4.9.2
    BackWPup version	3.4.4 Get pro.
    PHP version	7.1.13 (64bit)
    MySQL version	5.5.56-MariaDB
    cURL version	7.29.0
    cURL SSL version	NSS/3.28.4
    WP-Cron url	https://HIDDEN/wp-cron.php
    Server self connect	Not expected HTTP response:
    Status-Code: 200
    Cache-control: private
    Content-type: text/html; charset=utf-8
    Content-encoding: gzip
    Vary: Accept-Encoding
    Server: Microsoft-IIS/7.5
    X-powered-by: ASP.NET
    Date: Wed, 07 Feb 2018 14:11:45 GMT
    Content-length: 4831
    Content: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "https://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="https://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head><title> ...
    ........
    </body> </html>
    Document root	/HIDDEN
    Temp folder	/HIDDEN/wp-content/uploads/backwpup-e51577-temp/
    Log folder	/HIDDEN/wp-content/uploads/backwpup-e51577-logs/
    Server	Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips
    Operating System	Linux
    PHP SAPI	apache2handler
    Current PHP user	apache
    Maximum execution time	30 seconds
    Alternative WP Cron	Off
    Disabled WP Cron	Off
    CHMOD Dir	493
    Server Time	15:55
    Blog Time	15:55
    Blog Timezone	
    Blog Time offset	0 hours
    Blog language	en-US
    MySQL Client encoding	utf8
    PHP Memory limit	256M
    WP memory limit	64M
    WP maximum memory limit	256M
    Memory in use	12.00 MB
    Loaded PHP Extensions:	Core, PDO, Phar, Reflection, SPL, SimpleXML, Zend OPcache, apache2handler, bcmath, bz2, calendar, ctype, curl, date, dom, exif, fileinfo, filter, ftp, gd, gettext, gmp, hash, iconv, json, libxml, mbstring, mysqli, mysqlnd, openssl, pcre, pdo_mysql, pdo_sqlite, posix, session, shmop, sockets, sqlite3, standard, sysvmsg, sysvsem, sysvshm, tidy, tokenizer, wddx, xml, xmlreader, xmlwriter, xsl, zip, zlib
    • This reply was modified 7 years ago by avtop.
    Thread Starter avtop

    (@avtop)

    Sorry for my request, I understand now it was not clear. Forget about GIT, the point is:
    Imagine you are going to update WP core. You uploaded (via FTP for example) new core release (without wp-content folder) to the server. From that point and until the next core update can WP by itself or some plugin in any circumstances change files in wp-admin or wp-includes folders? Or they (wp-admin and wp-includes folders and their content) stay the same until next core update?

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