Chris Everson

I think you’re correct in assuming that the issue is with the actual server as my issues are the same without having any CDN functionality ever implemented on the site.

I’m having this same (or similar) issue.

I’ve also completed all steps above, but it is still caching (stylesheet) at the browser level and calling the minified stylesheet.

Anyone have any luck with this yet?

I’ll let you know if I figure it out.

Do you (or your host) have this set to auto-update? I’ve run into that issue before with auto-updating installations.

Should be “%postname%”.

I didn’t test this code, but maybe try naming it something different? Sidebar seems like a name that might conflict with defaults.

The validator that I linked to will run your CSS to make sure it’s valid. This ensures that it is cross-browser compatible and that everything will work as expected.

If something is wrong and needs to be changed, the Validator will let you know.

Maybe I’m not understanding this correctly, but it sounds like the best option is to use the built in password protection.

See the Content Visibility page in the Codex.

You might want to check the CSS Validator and see if there’s an error as suggested above.

https://jigsaw.w3.org/css-validator/

As far as I know, the only way to accomplish this is to edit the ‘wp_options’ table in your database.

If I remember correctly there are two values to change. The option_name fields will read ‘siteurl’ & ‘home’

SOLUTION:

in tubepress.php add the following after $tubepress_base_url = get_option('siteurl') . "/wp-content/plugins/$baseName";

// Modification to Allow SSL by Chris Everson (https://chriseverson.net)
    if($_SERVER['HTTPS']) {
    	$tubepress_base_url = str_replace("http:","https:",$tubepress_base_url);
    }

For myself, it was caused by changing the permalink structure. This resulted in a modification of, or in my case, the generation of a .htaccess file including rules for mod_rewrite.

Make sure in your host configuration file that AllowOverride is set to All to allow mod_rewrite to work its magic. I’m not sure how I overlooked that for a half hour.

I was running it on a test server of mine, and it ended up being the specific vhost. So be sure to check outside of your global Apache configuration file if you’ve got virtual hosts set-up.

There are advanced ways of configuring the processing rules for mod_rewrite and configuring AllowOverride, so if you want to enable without AllowOverride All, just google and learn. If you don’t know what you’re doing though, I’d suggest reading about mod_rewrite and AllowOverride from the get-go for a better understanding of what’s going on with mod_rewrite and how it’s used / permalinks.