Unfortunately WordPress does not provide the old value as an additional argument to your sanitize_callback callable. This is supported in general by the option validator hook that WordPress calls when saving the updated setting… return apply_filters( “sanitize_option_{$option}”, $value, $option, $original_value ); …but in practice it is not actually registered with any additional arguments when the … Read more
It happens when the foreach() is fed with an invalid entry, because there is no term returned. To prevent this, wrap your loop inside a conditional: // Get the terms( categories ) for the portfolio item $terms = get_the_terms( $post_item->ID, ‘portfolio_categories’ ); if(is_array($terms) || is_object($terms)){ foreach( $terms as $term ) { // some code here … Read more
That’s simple. You need to upload that file. Wp-includes/template-loader.php That file is missing. So just re upload that there and that should work.
I managed to enter the admin page finally! So I added these two lines to wp_admin.php: define(‘WP_HOME’,’http://example.com’); define(‘WP_SITEURL’,’http://example.com’); afterward deleted the .htaccess file, then deleted browsing history, cleared cache and cookies. After all of this I could enter the admin page. Then I went to options/general and options/permalinks and saved the setting, it generated a … Read more
Via FTP, go into the /wp-content/plugins/ folder and delete the wp-date-remover/ folder. That will disable the plugin on the code level. If you need help with FTP, visit your web host control panel and navigate around, view their docs, andor talk to their support. (A very good reminder to always back up your website!)
I know this thread is a little bit old, but as I spent 3 days installing, “up/down” VPS and searching Google, today I could find an answer to this error. On your WordPress installation root folder, find and open wp-login.php file. Search for the line $user = wp_signon(”, $secure_cookie); and replace the empty string ‘ … Read more
It seems I got some faulty nginx configuration from an article on how to configure WordPress in a subdirectory. Config Before location @wp { rewrite ^/blog(.*) /blog/index.php?q=$1; } location ^~ /blog { root /home/user; index index.php index.html index.htm; try_files $uri $uri/ @wp; location ~ \.php$ { include fastcgi_params; fastcgi_index index.php; fastcgi_intercept_errors on; # Deleted this … Read more
The colour picker is working fine because it’s a separate script being enqueued as a dependency of custom-script-handle. So even if custom-script-handle isn’t loading because the URL is wrong the colour picker script will still load. If you don’t enqueue custom-script-handle then the colour picker won’t work because the script is being enqueued at all. … Read more
That line 123 references the WordPress object cache, see https://github.com/WordPress/wordpress-develop/blob/7c38750b162c784d92f54d9a36044c0f5318fe24/src/wp-includes/cache.php#L123 Sounds like you have an external object cache (Memcached, Redis, etc.) that isn’t set up properly or a plugin that wrongly modifies WordPress’ internal object cache (which is basically a no-op). This could be configured by your host too. Try disabling all plugins to see … Read more
A couple of different hings are going on according to your log: The “deprecated” functions mean that you’re using a theme that calls old functions. You need to update your theme to be compatible with the version of Woocommerce you are running. This doesn’t break your site, but should be addressed. The “warning” and “error” … Read more