Re: [O] Publishing to html With the New Exporter
Hello, I had to update my web site [1] today, a site which is written in org. This was the first attempt at using the new exporter for publishing for a site written with the old exporter in mind. I thought I would summarise the changes I had to make to have them all in one place: 1. change #+SETUPFILE: to #+INCLUDE: and add quotes to the file name. 2. change all configuration lines that I had previously commented out by adding a # (to get "##+") at the start to just "# +" as comment lines now must start with "# ". This is not a change due to the new exporter but one that came in a while ago -- you can tell how often I update my web site! :( 3. add ":publishing-function" to all of my entries in org-publish-project-alist. Before, no such entry was required. The value of this setting is "org-html-publish-to-html" and this entry appears to be required in each element in the alist even for entries that are referred to by other entries. 4. change all #+STYLE: directives to #+HTML_HEAD: After this, everything worked perfectly fine (well, except for some ditaa related export issues which I will address later). I am summarising this here as it took me a while to track down the various bits by trawling the mailing list and Worg. Again, thanks to all involved and Nicolas in particular for the new exporter. eric Footnotes: [1] http://www.homepages.ucl.ac.uk/~ucecesf/ -- Eric S Fraga (GnuPG: 0xC89193D8FFFCF67D)
Re: [O] Publishing to html With the New Exporter
On 18/02/13 17:25, Nicolas Goaziou wrote: Ian Barton writes: A bit more investigating showed that the file causing the problem was a blank .org file with no content at all. Removing this fixed the problem and I can now export! I don't know if not being able to handle files with no content should be considered a bug or not. There was a bug in org-element.el, which returned an error when parsing an empty file. I fixed it a few days ago. Is your Org version recent enough? My org was about a week old. I have just pulled again and the error with the empty file has gone. Best wishes, Ian.
Re: [O] Publishing to html With the New Exporter
Ian Barton writes: > A bit more investigating showed that the file causing the problem was > a blank .org file with no content at all. Removing this fixed the > problem and I can now export! I don't know if not being able to handle > files with no content should be considered a bug or not. There was a bug in org-element.el, which returned an error when parsing an empty file. I fixed it a few days ago. Is your Org version recent enough? Regards, -- Nicolas Goaziou
Re: [O] Publishing to html With the New Exporter
On 18/02/13 13:54, Nicolas Goaziou wrote:
Hello,
Ian Barton writes:
I am trying to change my publishing setup over to use the new exporter.
With the recent merge and change of names from -e-backend to -ox-backend
I am a bit confused as to how I should set up my publishing alist.
I have tried:
#+begin_example
(require 'ox-html)
(require 'ox-publish)
FWIW, (require 'ox-html) also requires 'ox-publish.
;;(require 'org-publish)
(setq org-publish-project-alist
'(
("org-static-ian"
:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
:base-extension
"css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf\\|php"
:publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content"
:recursive t
:publishing-function org-ox-publish-attachment)
This should be `org-html-publish-to-html'.
("org-ianbarton"
:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
:base-extension "org"
:publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content"
:recursive t
:publishing-function org-ox-html-publish-to-html
:headline-levels 4 ; Just the default for this
project.
:auto-preamble t
:auto-index f
:html-extension "yml"
:auto-preamble t
:body-only t
)
("ianbarton" :components ("org-ianbarton" "org-static-ian"))
))
#+end_example
Thanks, I had already tried `org-html-publish-to-html, but got the
following backtrace:
Debugger entered--Lisp error: (wrong-type-argument char-or-string-p nil)
org-export-to-file(html
"/home/ian/Dropbox/web_sites/ianbarton/pelican/blog/content/2012-12-31-test.html"
nil nil t (:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
:base-extension "org" :publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content" :recursive t
:publishing-function org-html-publish-to-html :headline-levels 4
:auto-preamble t :auto-index f :html-extension "yml" :auto-preamble t
:body-only t :filter-parse-tree (org-publish-collect-index)))
org-publish-org-to(html
"/home/ian/Dropbox/web_sites/ianbarton/org/_posts/2012-12-31-test.org"
".html" (:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
:base-extension "org" :publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content" :recursive t
:publishing-function org-html-publish-to-html :headline-levels 4
:auto-preamble t :auto-index f :html-extension "yml" :auto-preamble t
:body-only t) "/home/ian/Dropbox/web_sites/ianbarton/pelican/blog/content/")
org-html-publish-to-html((:base-directory
"~/Dropbox/web_sites/ianbarton/org/_posts" :base-extension "org"
:publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content" :recursive t
:publishing-function org-html-publish-to-html :headline-levels 4
:auto-preamble t :auto-index f :html-extension "yml" :auto-preamble t
:body-only t)
"/home/ian/Dropbox/web_sites/ianbarton/org/_posts/2012-12-31-test.org"
"/home/ian/Dropbox/web_sites/ianbarton/pelican/blog/content/")
org-publish-file("/home/ian/Dropbox/web_sites/ianbarton/org/_posts/2012-12-31-test.org"
("org-ianbarton" :base-directory
"~/Dropbox/web_sites/ianbarton/org/_posts" :base-extension "org"
:publishing-directory
"~/Dropbox/web_sites/ianbarton/pelican/blog/content" :recursive t
:publishing-function org-html-publish-to-html :headline-levels 4
:auto-preamble t :auto-index f :html-extension "yml" :auto-preamble t
:body-only t) t)
#[(project) "\306@!\210A\307 \310\"\307\311\"\307
\312\"\206
A bit more investigating showed that the file causing the problem was a
blank .org file with no content at all. Removing this fixed the problem
and I can now export! I don't know if not being able to handle files
with no content should be considered a bug or not.
Ian.
Re: [O] Publishing to html With the New Exporter
Hello,
Ian Barton writes:
> I am trying to change my publishing setup over to use the new exporter.
> With the recent merge and change of names from -e-backend to -ox-backend
> I am a bit confused as to how I should set up my publishing alist.
>
> I have tried:
>
> #+begin_example
>
> (require 'ox-html)
> (require 'ox-publish)
FWIW, (require 'ox-html) also requires 'ox-publish.
> ;;(require 'org-publish)
> (setq org-publish-project-alist
>'(
>
>
>
>
>("org-static-ian"
>:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
>:base-extension
> "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf\\|php"
>:publishing-directory
> "~/Dropbox/web_sites/ianbarton/pelican/blog/content"
>:recursive t
>:publishing-function org-ox-publish-attachment)
This should be `org-html-publish-to-html'.
>
>
>("org-ianbarton"
>:base-directory "~/Dropbox/web_sites/ianbarton/org/_posts"
>:base-extension "org"
>:publishing-directory
> "~/Dropbox/web_sites/ianbarton/pelican/blog/content"
>:recursive t
>:publishing-function org-ox-html-publish-to-html
>:headline-levels 4 ; Just the default for this
> project.
>:auto-preamble t
>:auto-index f
>:html-extension "yml"
>:auto-preamble t
>:body-only t
> )
>
> ("ianbarton" :components ("org-ianbarton" "org-static-ian"))
>
>
>
>
>))
>
> #+end_example
Regards,
--
Nicolas Goaziou
