I have seen this before. There was an update to Freeway to address the way that it was writing out the CSS. Whatever version of Freeway you have, update to the latest minor version and force the entire site to republish. Then upload again. The issue is that the CSS is being written in a manner that looks almost exactly like a Server Side Includes directive, and this causes your server to try to interpret it as an SSI, which fails.
Another thing to try is to ensure that Freeway is set to output its code in More Readable format. That forces the comments to a different line, which keeps them from looking so much like an SSI.
On Jan 20, 2015, at 9:03 AM, Thomas Kimmich email@hidden wrote:
All I can see is a message that is entirely new to me:
[an error occurred while processing this directive]
in the head part of your page. Try to publish again and observe if there is something obscure happening. If - I’d say tower’s support would be the better address.
When Freeway writes CSS, it follows the HTML4 rules for escaping the contents of tags with comments. Unfortunately, the way that it writes these comments looks awfully similar to the way that a Server Side Include comment is written (the difference between what works and does not is a single space character). Some servers have SSI turned on by default, many/most do not (it’s mostly been superseded by PHP or other server-side languages any more). If you happen to be on such a server, and don’t know how to turn it off, then you will hit this bug. I know that there was an update to Freeway to fix this, but it appears as though it may have regressed in the current version of Freeway. I believe the fix was in the Action itself, not the core of Freeway, but since these Actions are included in Freeway (and not available separately) they fix has to ship within Freeway proper.