revixi5

You can not solve this problem using the WordPress dashboard. You have to edit the files located in your server. Do you have access to the file manager of your server (in your hosting control panel)? Or do you use a FTP software?

It is the same problem as everybody else, nothing different. Your hosting company simply changed something in their server adress (what we call “absolute path”). The plugin is using that “adress”. That is why, now it can’t reach one file, and is showing a warning message.

The warning message is giving you the right “path” : /home/yngvilvg/public_html/wp-content/advanced-cache.php

You will need to correct that “path” by hand. I suggest you find someone able to do it for you, or simply disable the plugin (if you are able to reach it). It is a really simple job, but if you know nothing about those things, it can be hard to understand. Also, your username and password are needed to reach that file (by the server control panel or by FTP).

Never heard of a problem that serious with that plugin… Probably in conflict with another plugin. You will have to remove it manually by FTP, or by your host file manager.

UPDATE :
I found an important detail. The file “advanced-cache.php” that is located OUTSIDE the PLUGINS folder, that is to say in the WP-CONTENT folder is not updated when updating the plugin. So if you are using this plugin for a long time, it is possible that the code in this file differs from the current version (v1.2).

In older versions (for example v0.8.9.1), the absolute path is written in it directly.

<?php
# WP SUPER CACHE 0.8.9.1
function wpcache_broken_message() {
	if ( false == strpos( $_SERVER[ 'REQUEST_URI' ], 'wp-admin' ) )
		echo "<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->";
}

if ( !include_once( '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' . 'wp-cache-phase1.php' ) ) {
	if ( !@is_file( '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' . 'wp-cache-phase1.php' ) ) {
		define( 'ADVANCEDCACHEPROBLEM', 1 );
		register_shutdown_function( 'wpcache_broken_message' );
	}
}
?>

In the new version (v1.2), that file only contains a link to the WordPress “wp-config.php”. So it would be better to update the contents of the “advanced-cache.php” found in WP-CONTENT folder with the following:

<?php
# WP SUPER CACHE 1.2
function wpcache_broken_message() {
	if ( false == strpos( $_SERVER[ 'REQUEST_URI' ], 'wp-admin' ) )
		echo "<!-- WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory. -->";
}

if ( false == defined( 'WPCACHEHOME' ) ) {
	define( 'ADVANCEDCACHEPROBLEM', 1 );
} elseif ( !include_once( WPCACHEHOME . 'wp-cache-phase1.php' ) ) {
	if ( !@is_file( WPCACHEHOME . 'wp-cache-phase1.php' ) ) {
		define( 'ADVANCEDCACHEPROBLEM', 1 );
	}
}
if ( defined( 'ADVANCEDCACHEPROBLEM' ) )
	register_shutdown_function( 'wpcache_broken_message' );
?>

And then you can check your “wp-config.php” file (at the root of WordPress) if it contains the absolute path of your server (the warning message usually contain the old and the new absolute path of your server). The line should be like this (with your absolute path):

define('WPCACHEHOME', '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager

Hope this help.

UPDATE :
I found an important detail. The file “advanced-cache.php” that is located OUTSIDE the PLUGINS folder, that is to say in the WP-CONTENT folder is not updated when updating the plugin. So if you are using this plugin for a long time, it is possible that the code in this file differs from the current version (v1.2).

In older versions (for example v0.8.9.1), the absolute path is written in it directly.

<?php
# WP SUPER CACHE 0.8.9.1
function wpcache_broken_message() {
	if ( false == strpos( $_SERVER[ 'REQUEST_URI' ], 'wp-admin' ) )
		echo "<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->";
}

if ( !include_once( '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' . 'wp-cache-phase1.php' ) ) {
	if ( !@is_file( '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' . 'wp-cache-phase1.php' ) ) {
		define( 'ADVANCEDCACHEPROBLEM', 1 );
		register_shutdown_function( 'wpcache_broken_message' );
	}
}
?>

In the new version (v1.2), that file only contains a link to the WordPress “wp-config.php”. So it would be better to update the contents of the “advanced-cache.php” found in WP-CONTENT folder with the following:

<?php
# WP SUPER CACHE 1.2
function wpcache_broken_message() {
	if ( false == strpos( $_SERVER[ 'REQUEST_URI' ], 'wp-admin' ) )
		echo "<!-- WP Super Cache is installed but broken. The constant WPCACHEHOME must be set in the file wp-config.php and point at the WP Super Cache plugin directory. -->";
}

if ( false == defined( 'WPCACHEHOME' ) ) {
	define( 'ADVANCEDCACHEPROBLEM', 1 );
} elseif ( !include_once( WPCACHEHOME . 'wp-cache-phase1.php' ) ) {
	if ( !@is_file( WPCACHEHOME . 'wp-cache-phase1.php' ) ) {
		define( 'ADVANCEDCACHEPROBLEM', 1 );
	}
}
if ( defined( 'ADVANCEDCACHEPROBLEM' ) )
	register_shutdown_function( 'wpcache_broken_message' );
?>

And then you can check your “wp-config.php” file (at the root of WordPress) if it contains the absolute path of your server (the warning message usually contain the old and the new absolute path of your server). The line should be like this (with your absolute path):

define('WPCACHEHOME', '/YOUR ABSOLUTE PATH/wp-content/plugins/wp-super-cache/' ); //Added by WP-Cache Manager

Hope this help.

To me, the problem is cause by a change (by the hosting company) in the absolute path of the server. By following the instruction in the warning, I solve the problem. No need to touch the wp-config.php file.

Open the file : /wp-content/advanced-cache.php
Compare the absolute path written in that file with the one include in the warning message (in WordPress dashboard). The warning message is giving you the new path, use it to fix the one in the advanced-cache.php file.

To me, the problem is cause by a change (by the hosting company) in the absolute path of the server. By following the instruction in the warning, I solve the problem. No need to touch the wp-config.php file.

Open the file : /wp-content/advanced-cache.php
Compare the absolute path written in that file with the one include in the warning message (in WordPress dashboard). The warning message is giving you the new path, use it to fix the one in the advanced-cache.php file.

Thanks! Another nice update would be a widget that allow to show the top downloads in a sidebar. I’ll wait for your next version.

It looks like the perfect plugin, nice structure and options, but… in my case all my files are already in my server, classified in specific folders. Do you plan to add the option of “entering the URL manually” when you create a new Download item?
Probably as many others, i am not interested in re-uploading all my stuff, and in a default area of the server.
Thanks a lot for your great plugin and help.

This is the comment i was looking for… i will give it a try. I was using ShareThis plugin and it was slowing everything… so i deactivated it.

Small detail… the special class for blocking fancybox was not added to the proper line. Instead of line 81, it should be on line 83.

return '<a href="'.$url.'" target="_blank" class="nofancybox">'.$img.'</a>';

Thanks again.

Your plugin is sooooooooo useful, and look so nice in my website. I would recommend to anyone. Thanks again for your great work.

Ok, I found that I can use class=”nofancybox” in order to stop the FancyBox… so for all those who are using Easy FancyBox plugin : at line 72 of the file ultimate-follow-me.php
return '<a href="'.$url.'" target="_blank" class="nofancybox">'.$img.'</a>';

By the way, in order to modify the language of the widget title : at line 232
echo $args['before_title'] . 'Suivez-moi sur le web!' . $args['after_title'];

Thanks for this very nice plugin!

I am not a pro, but my theme also do that… i think it is only relate with the use of custom field and thumbnails. WordPress create a Cache folder in the theme folder, and put in it a copy of the thumbnails… that’s all. I hope I am right… I am saying that because when i test my theme on a local computer with PHP enabled (not on internet), wordpress is creating the same folder on the fly, with the thumbnails in it (with long numbers for file names)… it does what it says… it’s a cache folder.