You can set WP_DEBUG to false in your wp-config.php file. This won’t fix the problem however It will only hide ALL the errors generated by it and any other plugins. The warnings mean the second and third parameters in the ufwp_widget_text() function have no defaults set. If you are using this function in your own … Read more
The “White Screen of Death” (which I assume is your issue, since you provided minimal details) can usually be diagnosed starting with the error.log file for you site. This is available via your hosting Control Panel, File Manager, or via FTP access. The latest error will usually show a folder/file that is causing the problem. … Read more
As the log says, a file is missing. If you FTP in to your site (or use your host’s File Manager, if they offer one) you can change the name of the folder currently called /wp-content/plugins/ – i.e. change it to something like /wp-content/oldplugins/. That should then allow you to log in. Once you log … Read more
Thanks all of you for your response the issue got resolved. The problem was with cached copy of this link https://vreqenz-stream.de/shop/ . I had WP Rocket for caching and apparently it is not doing very good job of purging the cache. I got sure that it is cache issue when I defined the WP_CACHE as … Read more
It is usually caused by a filter or an action not properly declared. Somewhere in your theme or plugins is a line like: add_filter( ‘hook_name’ , array( ‘wphpc_PAnD’, ‘someMethod’ ) ); // or add_action( ‘hook_name’ , array( ‘wphpc_PAnD’, ‘methodName’ ) ); which register class method with hook for a action or filter, but this class … Read more
Removing wp_enqueue_script(‘jquery’); will fix your problem. Put jquery into deps parameter of wp_enqueue_script function.
The headers already sent message means that something — a plugin or a theme, usually — is sending output before it’s meant to. Often this is due to whitespace appearing in a file after the closing ?> tag, which can make it hard to find the culprit. The fact that pluggable.php is mentioned tells me … Read more
The “Comments” column is not a default/core column in the “Posts” page. Perhaps it is being generated by your Disqus Plugin? Try temporarily disabling the Disqus Plugin, and see if the PHP notices go away. EDIT: actually, it is a default column. But I still suspect Disqus is causing the PHP warning.
You have to use just $current_role variable instead of $current_role[0], because call get_user_meta( $author->ID, ‘wp_capabilities’ ); will return you array with roles as keys. <?php add_action( ‘save_post’, ‘update_roles’ ); function update_roles( $post_id ) { if ( defined( ‘DOING_AUTOSAVE’ ) && DOING_AUTOSAVE ) return $post_id; // Get the author $author = wp_get_current_user(); // Set variables for … Read more
I would say if the plugin author hasn’t responded to support in a year that you should dump the plugin causing the issue and find something else. You’re bound to run into more problems in the future. And, yes, s_ha_dum is right that it probably has something to do with the permissions on those files … Read more