Finally, after MONTHS I was able to solve it. Just add $_SERVER[‘REQUEST_SCHEME’] = ‘http’; $_SERVER[‘SERVER_PORT’] = 80; To wp-config.php, preferably before calling wp-settings.php Thanks to Daan Meijer for this. PS: It was a server-side error, probably something to do with PHP process manager such as php-fpm or mod_php. The hosting company solved it without the … Read more
IMHO WP_DEBUG allows to enable display of notices during development. If you look at the core file default-constants.php you see this : if ( !defined(‘WP_DEBUG’) ) define( ‘WP_DEBUG’, false ); So I don’t see why you should set it to false again in wp-config.php. Regarding your issue just delete the line, WP_DEBUG should never be … Read more
Not sure what must be causing this. Try replicating your entire filter hook with function in this format: function filter_handler( $data ) { // do something with the post data return $data; } add_filter( ‘wp_insert_post_data’, ‘filter_handler’, ’10’, 1); Let me know if something happens.
It’s the .MO file compiled saving the .PO file which is used by WordPress. Without .MO no traduction will be available. You can use another plugin to translate your theme : Loco for example ; or a Windows software : Poedit, which will create a .MO file when you’ll save your .PO file with your … Read more
The problem here is a mistake regarding how to schedule a cron event, lets begin with: wp_schedule_event(time(), ‘hourly’, ‘my_schedule_hook’, $args); wp_schedule_event(time(), ‘hourly’, ‘update_user_hours’); Here you are telling WordPress to fire the update_user_hours action/event on an hourly basis. You then hook into this to fire a callback: add_action(‘update_user_hours’, ‘do_this_hourly’); But then, instead of declaring do_this_hourly, for … Read more
Docker events command may help and Docker logs command can fetch logs even after the image failed to start. First start docker events in the background to see whats going on. docker events& Then run your failing docker run … command. Then you should see something like the following on screen: 2015-12-22T15:13:05.503402713+02:00 xxxxxxxacd8ca86df9eac5fd5466884c0b42a06293ccff0b5101b5987f5da07d: (from xxx/xxx:latest) … Read more
It is not necessary to delete it but if you want to save your space then you can delete it. Actually when we turn on the debugger then debug.log file created. It contains the warnings and errors of the code. May be your development team have renamed it with debug.log.old. You can delete it or … Read more
Try something like this in your template tags (or wherever in your theme): function should_display_link() { $post = get_post(); // Something went wrong, bail. (You should always have a post, in theory) if ( ! $post ) { return false; } $current_user = get_current_user_id(); // Assuming only logged-in users can subscribe. if ( ! $current_user … Read more
Okay, here’s what I did. If this happens, hopefully this will work favourably for you. If this is disabled by default, enable wp-debug by changing the value from false to true. Check that you have enabled WP_DEBUG_LOG and WP_LOG_DISPLAY. Try refreshing the page and see what happens. Either using WinSCP or the terminal, go to … Read more
debug.log is exactly what it sounds – it’s just a file that contains log information for debugging purposes. You can easily delete it and without any fear. But… Debugging should not be turned on on production site – it’s a security problem. If your debug.log file is so big, then your site has many problems. … Read more