Comet Cache Upgrade Crashes

@sanyadolpins Nothing changed in the most recent version (v160521) that would have any affect on the path. Comet Cache has always used, and still does, the WP_CONTENT_DIR path from WordPress to build the full path to things. So if you’re seeing the wrong first part of the path, it sounds to me like something, somehow, changed with your WP_CONTENT_DIR setting.

When you say “If I revert back to an older version it works fine.”, which version specifically are you reverting to that is working fine?

My wp-content-dir has been the same for the last 3 years. Yes, I have the changed wp-content to foo-foo content. But, it has “NOT” been a problem in the past with previous upgrades. Nor, is it a problem with any other plugin. So, seems to me that it’s very clear your new upgrade is “NOT” picking up the change and converting the path to the “ABSOLUTE” path rather then the correct path which should be the “RELATIVE” path. Why don’t you look into it, rather than assuming I’ve done something wrong, which I have not. I have upgraded to v160521 “FIVE” times now. And, each time it is picking up the “WRONG” path. And, if I revert back to v160417 it works just fine. STRANGE you don’t find that STRANGE and look into it more, rather than assuming it’s MY problem.

@sanyadolpins Where are you seeing this changed path?

It is showing in the CometCache Admin Panel as you can clearly see from the following image. https://screencast.com/t/g3zrWxPR8u

Here is the same website, running v160417, works just fine, when I reinstall a lower version. https://screencast.com/t/NwBJGWSi

@sanyadolpins We’ve had more than 4,000 people upgrade to Comet Cache v160521 and yours is the first report of an issue.

I’m not seeing anything in your screenshots that shows where you’re seeing the incorrect path. Is Comet Cache being installed into the wrong path?

I am not able to reproduce the problem in a clean installation of WordPress, which tells me your problem is related to one of these things:

• If it’s only the CSS styles in the Dashboard that you’re having a problem with, then your browser cache is becoming corrupt—I suggest clearing your browser cache.
• I know you said you tried disabling other plugins, but since I can’t reproduce this issue on ANY of my sites (and nobody else has had any problems), we have to look at the differences between your site and everybody else’s site: that would be your installed plugins, your theme, and your hosting environment.

See also this article.

How many of those 4,000 customers are redirecting wp-content in the wp-config.php file, according to the “define” statements in WordPress codex?

It’s simple to see the problem. All I (you) need to do is open one of the BROKEN Icons on the CometCache Admin page and you will see the WRONG path, and therefore the broken Icons.

Simply by changing the path manually in the broken Url, the Icon shows. So, again, this is a problem that occurs during the upgrade. To say, you have 4,000 upgrades and mine is the first, well so be it. It’s a problem, whether or not, it’s the first time you have seen it.

It seems that the new version upgrade is NOT recognizing the config.php define statements:

define( ‘WP_CONTENT_URL’, ‘https://domain.com/foo-foo’ );
define( ‘WP_CONTENT_DIR’, ‘/var/www/html/foo-foo’ );

However, the older version correctly recognizes it.

Everyone of my other 20 plugins work just fine. And, upgrade without error or problem. I figure that there are over 1,000,000 users in total using the other plugins. Again, this currently is ONLY a CometCache problem.

You say you cannot reproduce the issue. Did you try re-defining your WP_CONTENT_DIR in your wp-config.php file. I bet not.

BTW, I brought my BEEF to the public forum, because I got NO (VERY SLOW AND PURELY CANNED) support from my PAID CometCache subscription and submitting my original problem through the proper Support Ticket channel.

You say you cannot reproduce the issue. Did you try re-defining your WP_CONTENT_DIR in your wp-config.php file. I bet not.

Until now, you haven’t told me that’s what you were doing, so how could I test it? Now that you’ve told me exactly what you’re doing differently, I can run some more tests. I’ll report back shortly.

I got NO (VERY SLOW AND PURELY CANNED) support from my PAID CometCache subscription

I apologize for that. What is your support ticket number? I will look into why that happened.

YES I DID. YOU JUST DIDN’T READ IT!

Posted 2 hours ago #

My wp-content-dir has been the same for the last 3 years. Yes, I have the changed wp-content to foo-foo content. But, it has “NOT” been a problem in the past with previous upgrades. Nor, is it a problem with any other plugin.

I added the following custom settings to my wp-config.php:

define( 'WP_CONTENT_URL', 'https://local.wordpress.dev/foobar-content' );
define( 'WP_CONTENT_DIR', '/srv/www/wordpress/foobar-content' );

I then renamed my wp-content directory to foobar-content and refreshed my WordPress Dashboard and I was able to confirm that Comet Cache v160521 is still working as expected—all of the images and icons appear correctly, and the paths are correct. See screenshot: https://cloudup.com/cXwuPZHBipz

I noticed that your WP_CONTENT_URL example above contains “https://”; are you sure that the broken images aren’t the result of misconfigured SSL? What happens if you use “https://”?

I have been running a Symantec EV SSL for over a year, it has had no effect on any other part of the website. And, as I have previously stated all other plugins run just fine with the re-define in wp-config.php.

And, as I continue to say, that CometCache v160417 works just fine. The problem is consistent and only with upgrading to CometCache v160521.

I have “no” other plugin upgrade problems, nor do I have any PHP Errors running WordPress debug.

@sanyadolpins As I demonstrated above, I haven’t been able to reproduce any problem with custom WP_CONTENT_URL or WP_CONTENT_DIR settings, and there were no changes in the update to v160521 that would have any effect on either of those custom settings.

The next step would be to look at your web server log files to see if they give any clues as to what is going wrong on your site when you activate v160521.

Agreed. I sent my logs to support yesterday. I got NO reply. I’ll send them here again, in a few minutes.

I got NO Support Ticket number, only an email from ZenDesk that says to reply to the same email. There is NO Support Ticket number inlcuded in that email.

Here is the Support Ticket email. You can also see the Log Files I sent yesterday there.

[WebSharks? Support Center] Re: [Comet Cache] Cannot Activate (enable) Comet Cache, Or It Becomes A Mess