+[2017-04-01T23:07:47Z]Scoop7Hey my liquid tags are being processed differently in php files, is there any solutions to avoid this? +[2017-04-01T23:09:13Z]Scoop7<meta property="og:description" content=" Sorry, there where problems with your form: $error Please go back and fix the problems. "; } ..." /> +[2017-04-01T23:09:54Z]Scoop7Where in html files my liquid tags resolve to desired content +[2017-04-01T23:10:52Z]Scoop7<meta name="description" content="{% if page.meta %}{{page.meta}}{% elsif page.content %}{{ page.content | strip_html | strip_newlines | truncate: 160 }}{% else %}{{ site.description }}{% endif %}"> +[2017-04-01T23:12:32Z]Scoop7This is the original liquid code that in php files for some reason returns an error and in html everything is ok, which puzzles me because it's only jekyll processed files with no php parsing by this end... ?
message no. 166961
Posted by judah in #jekyll at 2017-04-01T16:40:08Z
morning
+[2017-04-02T13:30:25Z]osfamerongah, I really do hate all the baseurl wrangling +[2017-04-02T13:30:38Z]osfameronespecially when you also have to do it in non-liquid assets, like CSS +[2017-04-03T03:55:48Z]desnudopenguino[#o KKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKKK ;KJ U5yydPpPPPPPPPPPPPPPPPPPPPPPPPPPP X ,= +[2017-04-03T04:37:56Z]xpmanhi +[2017-04-03T18:47:28Z]howlinbashHi #jekyll, I'm building a simple blog. I was thinking of separating my _posts folder from my website. I use git. Is this common are there any best practices? should i use git submodules or .gitignore strategy? any thoughts? thank you