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

403 posts Keep Walking
  • Has been a member for 3-4 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
  • Exclusive Author
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
  • Bought between 10 and 49 items
  • Europe
  • Exclusive Author
  • Has been a member for 2-3 years
  • Referred between 1 and 9 users
  • Sold between 1 000 and 5 000 dollars
Ttpmc says
403 posts Keep Walking
  • Has been a member for 3-4 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
  • Exclusive Author
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 > ..”

:)

1 post
  • Bought between 1 and 9 items
  • Has been a member for 2-3 years
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 :)

75 posts
  • Elite Author
  • Author had a File in an Envato Bundle
  • Sold between 50 000 and 100 000 dollars
  • Referred between 10 and 49 users
  • Bought between 50 and 99 items
  • Envato Studio (Microlancer) Beta Tester
  • Exclusive Author
  • Has been a member for 2-3 years
  • Europe
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!

403 posts Keep Walking
  • Has been a member for 3-4 years
  • Elite Author
  • Sold between 100 000 and 250 000 dollars
  • Bought between 100 and 499 items
  • Referred between 100 and 199 users
  • Exclusive Author
UXbarn says

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

75 posts
  • Elite Author
  • Author had a File in an Envato Bundle
  • Sold between 50 000 and 100 000 dollars
  • Referred between 10 and 49 users
  • Bought between 50 and 99 items
  • Envato Studio (Microlancer) Beta Tester
  • Exclusive Author
  • Has been a member for 2-3 years
  • Europe
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…!

2566 posts Put a Donk On It
  • Elite Author
  • Sold between 250 000 and 1 000 000 dollars
  • United Kingdom
  • Exclusive Author
  • Attended a Community Meetup
  • Repeatedly Helped protect Envato Marketplaces against copyright violations
  • Referred between 200 and 499 users
+5 more
ThemeProvince says

lol Aptana

1075 posts
  • Forum Superstar
  • Most Wanted Bounty Winner
  • Envato Studio (Microlancer) Beta Tester
  • Author had a Free File of the Month
  • Bought between 50 and 99 items
  • Referred between 50 and 99 users
  • Europe
  • Has been a member for 3-4 years
  • Exclusive Author
+1 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.

75 posts
  • Elite Author
  • Author had a File in an Envato Bundle
  • Sold between 50 000 and 100 000 dollars
  • Referred between 10 and 49 users
  • Bought between 50 and 99 items
  • Envato Studio (Microlancer) Beta Tester
  • Exclusive Author
  • Has been a member for 2-3 years
  • Europe
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