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

481 posts Keep Walking
  • Has been part of the Envato Community for over 4 years
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $250,000+ on Envato Market
  • Has collected 100+ items on Envato Market
+2 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
  • Has been part of the Envato Community for over 3 years
  • Has referred 1+ members
  • Has sold $1,000+ on Envato Market
  • Has collected 50+ items on Envato Market
+2 more
Ttpmc
says
481 posts Keep Walking
  • Has been part of the Envato Community for over 4 years
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $250,000+ on Envato Market
  • Has collected 100+ items on Envato Market
+2 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
  • Has been part of the Envato Community for over 3 years
  • Has collected 1+ items on Envato Market
  • Sells items exclusively on Envato Market
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 :)

111 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Had an item featured in an Envato Bundle
  • Has been a beta tester for an Envato feature
+4 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!

481 posts Keep Walking
  • Has been part of the Envato Community for over 4 years
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $250,000+ on Envato Market
  • Has collected 100+ items on Envato Market
+2 more
UXbarn
says

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

111 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Had an item featured in an Envato Bundle
  • Has been a beta tester for an Envato feature
+4 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…!

2623 posts Put a Donk On It
  • Elite Author: Sold more than $75,000 on Envato Market
  • Sells items exclusively on Envato Market
  • Made it to the Authors' Hall of Fame
  • Has sold $250,000+ on Envato Market
+10 more
ThemeProvince
says

lol Aptana

1352 posts
  • Has been part of the Envato Community for over 4 years
  • Has sold $40,000+ on Envato Market
  • Has been a beta tester for an Envato feature
  • Has collected 50+ items on Envato Market
+4 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.

111 posts
  • Elite Author: Sold more than $75,000 on Envato Market
  • Has sold $125,000+ on Envato Market
  • Had an item featured in an Envato Bundle
  • Has been a beta tester for an Envato feature
+4 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