Got warnings from Theme-Check plugin about "Both DOS and UNIX style line endings". What does it mean!?

500 posts Keep Walking
  • Trendsetter
  • 4 Years of Membership
  • Elite Author
  • Author Level 9
+5 more
UXbarn
says

Hi guys,

While I’m testing my theme with Theme-Check plugin, I got some warning:

WARNING : Both DOS and UNIX style line endings were found in the file theme-options.php. This causes a problem with SVN repositories and must be corrected before the theme can be accepted. Please change the file to use only one style of line endings.

There are 2 files that raise this warning, theme-options.php and style.css.

What does it mean exactly about this kind of warning and how to solve it? :|

Thanks in advanced for your advices. :)

72 posts
  • 3 Years of Membership
  • Affiliate Level 1
  • Author Level 3
  • Collector Level 3
+2 more
Ttpmc
says
500 posts Keep Walking
  • Trendsetter
  • 4 Years of Membership
  • Elite Author
  • Author Level 9
+5 more
UXbarn
says

Thanks DimiR! That really helps! :D

In case of anyone who uses Aptana Studio and face this warning, go to “File > Convert Line Delimeters To > ..”

:)

2 posts
  • 3 Years of Membership
  • Collector Level 1
  • Exclusive Author
Raaaa
says

Thanks DimiR! That really helps! :D

In case of anyone who uses Aptana Studio and face this warning, go to “File > Convert Line Delimeters To > ..”

:)

Thanks, Aptana solved issue :)

113 posts
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
  • Bundle Boss
+5 more
djwd
says

Bumping this up…

How about a css file that is generated from a less file and compiled through less.inc.php?

Themecheck + Themeforest Check throws out this warning but I’m not sure how to fix this, If I open and re-save the generated file with some text editor the error obviously disappear, but as soon as it regenerates same error shows up again.

Will this actually be critical in the review process?

Thanks!

500 posts Keep Walking
  • Trendsetter
  • 4 Years of Membership
  • Elite Author
  • Author Level 9
+5 more
UXbarn
says

Yes, it is critical and still required to fix the error. :)

113 posts
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
  • Bundle Boss
+5 more
djwd
says

Thanks for your answer even though that’s not exactly what I wanted to hear :)

Does anybody have any suggestion on how to fix this? That’s what the PHP less compiler throws out I have no idea how to affect the output in order to fix this warning…!

2627 posts Put a Donk On It
  • Weekly Top Seller
  • Elite Author
  • Exclusive Author
  • Featured Author
+11 more
ThemeProvince
says

lol Aptana

1368 posts
  • Weekly Top Seller
  • 5 Years of Membership
  • Author Level 6
  • Beta Tester
+5 more
Smartik
says

Thanks for your answer even though that’s not exactly what I wanted to hear :) Does anybody have any suggestion on how to fix this? That’s what the PHP less compiler throws out I have no idea how to affect the output in order to fix this warning…!

Why ThemeCheck detects it? Do you save the CSS directly in theme? If so, then you don’t do it right because you must save any custom generated CSS in wp-uploads directory.

113 posts
  • Weekly Top Seller
  • Elite Author
  • Author Level 8
  • Bundle Boss
+5 more
djwd
says

Why ThemeCheck detects it? Do you save the CSS directly in theme? If so, then you don’t do it right because you must save any custom generated CSS in wp-uploads directory.

That’s the main CSS file for the theme, why should I put it outside theme folder?

by
by
by
by
by
by