From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Davison Subject: First line of exported HTML causes error as .php Date: Tue, 26 May 2009 15:20:05 -0400 Message-ID: <8763fnr7ru.fsf@stats.ox.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M92CJ-0007Hs-K8 for emacs-orgmode@gnu.org; Tue, 26 May 2009 15:20:27 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M92CF-00077Y-SD for emacs-orgmode@gnu.org; Tue, 26 May 2009 15:20:27 -0400 Received: from [199.232.76.173] (port=57316 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M92CF-00077G-OQ for emacs-orgmode@gnu.org; Tue, 26 May 2009 15:20:23 -0400 Received: from markov.stats.ox.ac.uk ([163.1.210.1]:61105) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M92CF-0004K6-AS for emacs-orgmode@gnu.org; Tue, 26 May 2009 15:20:23 -0400 Received: from blackcap.stats.ox.ac.uk (blackcap.stats [163.1.210.5]) by markov.stats.ox.ac.uk (8.13.6/8.13.6) with ESMTP id n4QJK7Zn000792 for ; Tue, 26 May 2009 20:20:09 +0100 (BST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs org-mode mailing list I think there's been a change in HTML export which has broken the way in which I was using org to produce PHP files. The HTML exporter now produces the following as the first line (I believe this is new). However, when the file is produced with a .php suffix (setq org-export-html-extension "php") and placed on a PHP-enabled web server, I get this error: Parse error: syntax error, unexpected T_STRING in /net/markov/export/postdocs/davison/pub_html/software/shellfish/shellfish.php on line 1 It seems to work OK if I delete the first line. I know next to nothing about these things and I'd appreciate it if someone could tell me whether this should be viewed as a bug in org, or whether I am just doing things the wrong way. (Is this how others produce PHP files in org?) Thanks, Dan