Forum Replies Created

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter mcataldi

    (@mcataldi)

    Hi! Only one line changes/appears when opening the new site:

    core:crit] [pid 16814] (13)Permission denied: [client] AH00529: sitepath/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable and that 'sitepath' is executable
    

    .htaccess has 0755 and sitepath has 0644.

    Thx a lot.

    Thread Starter mcataldi

    (@mcataldi)

    Thank you so much! Problem solved. Even with that guide I couldn’t get the debug.log file to be created and written, but I checked on the host errors and got an idea.
    I leave what I found and the solution that worked for me in case someone else has the same problem:
    I found this in my error log.

    PHP Warning: require_once(/var/www/html/wp-config.php): failed to open stream: Permission denied in /var/www/html/wp-load.php on line 50
    PHP Fatal error: require_once(): Failed opening required '/var/www/html/wp-config.php' (include_path='.:/opt/remi/php74/root/usr/share/pear:/opt/remi /php74/root/usr/share/php:/usr/share/pear:/usr/share/php') in /var/www/html/wp-load.php on line 50
    PHP Warning: require_once(/var/www/html/wp-config.php): failed to open stream: Permission denied in /var/www/html/wp-load.php on line 50
    PHP Fatal error: require_once(): Failed opening required '/var/www/html/wp-config.php' (include_path='.:/opt/remi/php74/root/usr/share/pear:/opt/remi /php74/root/usr/share/php:/usr/share/pear:/usr/share/php') in /var/www/html/wp-load.php on line 50


    I checked the permissions. Theoretically they were all fine, but I reconfigured them the same way and the issue was fixed. Except for the wp-content folder, which I had to set to 776 for the media library to work properly.
    Clearly the biggest problem was caused by the W3-Total-Cache plugin, which kept throwing errors even after deleting it until I cleaned it entirely with the link I provided above.
    Thank you very much @threadi for your help! I wouldn’t have been able to fix it without your guidance.

    Thread Starter mcataldi

    (@mcataldi)

    I write again with an update.
    Following these instructions (link), I have cleaned up the .htaccess file of the entire plugin. And indeed it has stopped showing the error… however, now it only says error 500.
    I have edited the wp-config file again so that it would show the errors on the screen and not in a .log file, since it wasn’t, but it isn’t. It only shows 500 error. I specifically leave that section of the wp-config here to check:

    /**
     * For developers: WordPress debugging mode.
     *
     * Change this to true to enable the display of notices during development.
     * It is strongly recommended that plugin and theme developers use WP_DEBUG
     * in their development environments.
     *
     * For information on other constants that can be used for debugging,
     * visit the documentation.
     *
     * @link https://www.ads-software.com/support/article/debugging-in-wordpress/
     */
    define( 'WP_DEBUG', true );
    /* Add any custom values between this line and the "stop editing" line. */

    I still don’t know what to do to fix it. I keep all plugins folder as plugins_old so it’s not conflict with some plugin, I think.

    *Since it is no longer the error that I mention in the title, I don’t know if I should keep this topic open, but I haven’t found a solution and I wouldn’t want to open a thousand topics, that’s why I keep it unless they tell me otherwise.

    • This reply was modified 1 year, 2 months ago by mcataldi. Reason: aclaration
    • This reply was modified 1 year, 2 months ago by mcataldi.
    Thread Starter mcataldi

    (@mcataldi)

    Hi. Today, I following that advice:

    Don’t just rename the directory, delete it completely. Then delete the file wp-content/advanced-cache.php – this is also used by the plugin. Then in wp-config.php you have to delete the entry

    define('WP_CACHE', true); // Added by W3 Total Cache

    in wp-config.php. This plugin should be completely out of the picture.

    I did it. And still get the same error message:

    Fatal error: Out of memory (allocated 367001600) (tried to allocate 262144 bytes) in /var/www/html/wp-content/plugins/w3-total-cache/ObjectCache_WpObjectCache.php on line 36

    Fatal error: Out of memory (allocated 367001600) (tried to allocate 262144 bytes) in?/var/www/html/wp-includes/class-wp-fatal-error-handler.php?on line?35

    Help.

    Thread Starter mcataldi

    (@mcataldi)

    Yes. I’m working on the correct server, because it’s the only one I have…
    I am attaching a console image where not only should all the plugins be disabled, but I have also deleted the folder (apart from deleting the other files and the line that you have previously indicated)

    I highlight that the error appears on the screen and not in the error file, because in my wp-config it appears

    define( 'WP_DEBUG', true );
    define( 'WP_DEBUG_LOG', true );
    define ( 'WP_DEBUG_DISPLAY', false );

    and it shouldn’t show up on the screen to begin with.

    Thread Starter mcataldi

    (@mcataldi)

    Hello! Thanks for the help. I just did the steps you told me and it still shows the same error (on the screen. Not in the debug file).

    Thread Starter mcataldi

    (@mcataldi)

    I desactivate a plugin (suggest in other forum) and solved in some pages. I assume, in a few hours will be solved in all.

    Hi. I actually have the same issue. And nothing works

    Thread Starter mcataldi

    (@mcataldi)

    Hi. UPDATE:

    Show this error:
    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 20480 bytes) in?/var/www/html/wp-includes/class-wpdb.php?on line?1793

    So, I did the following:
    I put this line in wp-config: define( ‘WP_MEMORY_LIMIT’, ‘256M’ );
    I modified the php.ini file like this: memory_limit = 256M
    I edited the .htaccess file like this: php_value memory_limit 256M (in the last line before #END WordPress)

    But doesn’t work.

    Thread Starter mcataldi

    (@mcataldi)

    Hi @jawad1234 , thx!

    I already modified the line you asked for. Now when entering the website, the screen goes blank.
    By the way, I checked the use of the server’s resources, in case it was a memory problem or crash, and everything would be working perfectly in that regard.

    Thread Starter mcataldi

    (@mcataldi)

    UPDATE: If I use the browser to upload files, then yes I can upload them to the library with no problem. While this allows me to continue using the page, I’d appreciate any feedback on fixing the error, as we can’t upload more than one file at a time using that method.

    Thread Starter mcataldi

    (@mcataldi)

    Hi. I tried change the tmp folder, but doesn’t work too. Anybody can help me?

    Thread Starter mcataldi

    (@mcataldi)

    I add: I have more than 40 GB free on the server disk and I want to upload a 105 KB image.
    The file upload limits are 128 MB set by WordPress and 500 MB set by server.

    Thread Starter mcataldi

    (@mcataldi)

    Hi George! Thanks very much.

    I was sure that I had done it correctly, and when reviewing to pass the file, I noticed that one of the lines had a typo and one / was missing.
    One final question before closing the topic, as this has also fixed the image issue: when I officially launch the site with the correct domain, an SSL certificate will also be installed. Should I change the urls to https://newdomain.com or leave them as https://newdomain.com?

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