New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow skipping LESS parser for individual files #2254
Comments
I am having a similar issue with Alternatively, there is oyejorge/less.php which appears to be much more actively maintained, and has a drop-in replacement shim for |
@Celti, my workaround is to include the Bulma CSS from a link element in the top of my template main.php, rather than letting DokuWiki handle it. |
@Celti In the master branch, we are actually using a fork of |
I think what might help is to separate less and css styles in css.php. AFAIK it currently puts both, .css and .less files together and then runs the lessphp functions over it. It would be better to handle less and css separately and merge them after processing has finished. |
A trick to insert (nearly) every unparsed code in LESSPHP
compiles to this "CSS-code":
Manual reference: http://leafo.net/lessphp/docs/#string_unquoting Online-compiling for testing: http://leafo.net/lessphp/editor.html DokuWiki Manual: LESS CSS Support Michael Sy. Edit (only 2 years later...): A method with milder means, but not quite as extensive possibilities:
compiles to this CSS-code:
Application see: DokuWiki Forum |
~"screen CSS code from LESS parser" |
Is there a way to do string unquoting for a string that takes up multiple lines? Example CSS
|
See the solution here, at the position "Edit II". - Michael Sy. |
See also: #3735 (comment) - Michael Sy. |
I'm using the Bulma CSS framework, which uses CSS calc() functions for various values, but when these are parsed through LESSPHP, it incorrectly parses these and runs the calculation before the browser has a chance to, so the values are wrong in the finished page.
leafo/lessphp#326
While LESSPHP fixes the issue, is there a way to indicate to DokuWiki that it shouldn't parse a particular file, but just add it to the CSS output as-is?
The text was updated successfully, but these errors were encountered: