filesystem path error

Hi, It looks like your style.css is not enqueued properly on your theme.

The path has a double forward slash in the middle: /var/www/dev.mysite.net//wp-content/themes/mts_schema/style.css

Check how your style.css is enqueued on your theme.
You probably need to remove the first forward slash somewhere there.

Thanks. It’s a commercial theme, so I’ll need to ask the developers.

By the way, even adding the file to the exclusion list doesn’t prevent the error. I had to disable CSS processing entirely.

• This reply was modified 8 years ago by cwfaraday.

you have to add the full url (not the file path), is that what you-re doing?

Also, what is the theme you’re using?
Any modifications?

• This reply was modified 8 years ago by Raul P..

I tried adding both URL and file path.

I’m using MyThemeShop Schema.

Hello,

We are using this method to enqueue theme style.css:
wp_enqueue_style( 'schema-stylesheet', get_stylesheet_uri() );

Could you please confirm that you are using latest version of the theme?

Also, If you need any help with our theme, please open new thread in our support forum.

Hope that helps.

Thank you.

I’m using 3.1.3.

Hi Raul,

the same problem happens with any theme. For example, with twentysixteen:
NOT FOUND [/var/www/dev.mysite.net//wp-content/themes/twentysixteen/style.css?ver=1479909172] - Permission denied or the file does not exist

I’m wondering why there is an URL parameter attached to style.css?

• This reply was modified 8 years ago by cwfaraday.

a) On version 1.3.3 I implemented a double check to prevent double slashes in the middle, so your path: .. site.net//wp-content … will not have double slashes anymore. Did you try the latest version?

b) /var/www/dev.mysite.net/ is probably the path to your files, so that’s not an url attached but rather the absolute path to your wordpress installation.

c) From my experience…

1 – you either defined the ABSPATH wrongly on wp-config.php, or

2 – you defined on your wp-config.php:
define(‘WP_HOME’, ‘https://dev.mysite.net/’);
define(‘WP_SITEURL’, ‘https://dev.mysite.net/’);

(the values should be without / at the end)

3 – you have performed some sort of search and replace on the database for the absolute path and added a forward slash in the end.

—

Either way, the latest plugin version tries to bypass this kind of error, so it might work.
Give it another try, update to 1.3.3, remove both cache and intermediate cache from the plugin settings and if it fails again let me know.

[ redacted ]

• This reply was modified 7 years, 8 months ago by Jan Dembowski.

After hours of research, I found out that the culprit is a plugin called “CDN Rewrite.” Damn it.

You can try the CDN enabler from keycdn, it’s better.