Failing to publish: buffer *temp* modified; kill anyway?

[Trevoke]

Here's the relevant log from *Messages*:

Publish all org files? (y or n) y Publish to a directory? (to original repo if not) (y or n) n Auto commit to repo? (y or n) y Auto push to remote repo? (y or n) y Mark set (:title Why Elixir is the next Great Tech :date 2016-03-31 :mod-date 2016-04-18 :thumb nil :tags (elixir) :category blog :uri /blog/2016/03/31/why-elixir-is-the-next-great-tech :pub-dir /home/trevoke/.op-tmp/blog/2016/03/31/why-elixir-is-the-next-great-tech/) Read post.mustache from file Buffer temp modified; kill anyway? (y or n) y byte-code: Wrong type argument: listp, #("2016-03-31 Thu" 0 14 (:parent (#0)))

This is a file I've previously published - in case it makes a difference.

My org-page config looks like this:

  (use-package org-page
    :config
    (setq op/repository-directory "~/src/projects/trevoke.github.io")
    (setq op/personal-github-link "https://github.com/trevoke")
    (setq op/site-domain "http://blog.trevoke.net/")
    (setq op/site-main-title "Seven Steps")
    (setq op/site-sub-title "Words... words, they're all we have to go on! — Rosencrantz and Guildenstern are dead"))

[Trevoke]

I toyed with org-page a little. I have the impression it's trying to be clever by determining what work needs to be done. It looks like if something goes weird, it's very hard to recover.

For instance, if you go to the homepage: https://blog.trevoke.net/ -- you'll see a link for "benefits of a rapid test suite". That link was generated, but the HTML wasn't. And now I have no idea how to get it to generate the HTML.

[ghost]

@kelvinh +1 I

[ghost]

@Trevoke Have you found another way to publish avoid this problem？

[ghost]

@Trevoke @kelvinh This seems some bug with org-*, after update all elpa, this bug is missing.

[WangLeshan]

@Trevoke I met the same problem since I did not use git and op correctly. Yesterday buffer temp modified message came again since I had set

op/personal-github-link to be nil. No bug, but abuse.

I followed @ruanxiang's, step by step tutorial (in Chinese) to avoid the message.

Since I publish my blog in local computer, I borrow the following comments from Xiang Ruan's blog.

更新博客流程

这部分可能很多人觉得莫名其妙，怎么搞得这么复杂? 不是一个 op/do-publication 就搞定了吗？是的，supposed to be, 但是很多问题搞不定，具体参考“残留问题”章节。所以如果你没有遇到我遇到的问题，那就忽略这步吧

确认当前repository在source branch下，if not, git checkout source open emacs, M-x op/new-post write your blog and save it git add new blog (under source branch) and commit it ( in emacs, you can use magit, it would be much easier to do the process) git push source， push source到center branch。这个不是必须的，因为博客本身只需要html文件，也就是master的文件。但是既然有了center server，何不把source备份呢 M-x op/do-publication, 第一个问题选择y，第二个问题选择no，因为不用发布到其他文件夹，第三第四个问题选择y

Translate them to English, where the italic texts are my comments.

Update you blog, step by step

1. make sure that the current branch is on source. If not, git checkout source
2. add a new post, open emacs, M-x op/new-post, write your blog and save it
3. git add new blog (under source branch) and commit it ( in emacs, you can use magit, it would be much easier to do the process)
4. git push source， push source to center branch, which is not need for me.
5. M-x op/do-publication, than choose y,n,y,y Since I publish my blog in local computer I choose y,n,y,n or use M-x op/do-publication-and-preview-site instead
6. git checkout master to see the blog for using M-x op/do-publication

[matrikslee]

@zwb-ict sorry, I have reinstall all my packages in emacs(because of this problem), however, this bug still exists. so, what should I do to resolve this problem..

[matrikslee]

In my emacs, the error messages are these:

Buffer temp modified; kill anyway? (y or n) y org-export-get-footnote-definition: Definition not found for footnote 5

&&

Buffer temp modified; kill anyway? (y or n) n org-export-get-footnote-definition: Definition not found for footnote 5

[ghost]

@lechain Do you use spacemacs? I found after clean upgrade elpa. This issue is still there. But cd elpa and delete org-, then restart spacemacs, after autoinstall org-. restart again. This bug is gone. It's amazing!

[matrikslee]

thank you, i use spacemacs, i have solve it by reinstall spacemacs..

On Sun, Jun 26, 2016, 07:28 Altaїr notifications@github.com wrote:

@lechain https://github.com/lechain Do you use spacemacs? I found after clean upgrade elpa. This issue is still there. But cd elpa and delete org-, then restart spacemacs, after autoinstall org-. restart again. This bug is gone. It's amazing!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/kelvinh/org-page/issues/184#issuecomment-228575671, or mute the thread https://github.com/notifications/unsubscribe/AL-gq5PADsIXCNgqqfDwT33LZIisq08oks5qPbmPgaJpZM4IJwyE .

[sillykelvin]

@zwb-ict is right, only delete the org-* packages in elpa, and then it will be alright.

[rolandoam]

I'm still having the same issue. Running emacs 25.2 and orgmode 9.0.8 (org-20170606 from melpa). This is trying to build your (@kelvinh) blog, error:

apply: Wrong type argument: listp, #("2012-11-27 Tue" 0 14 (:parent (#0)))

I removed all the org-* packages and reinstalled them. still same error.

[sillykelvin]

@rolandoam Please paste your call stack here.

[rolandoam]

I removed all elpa packages and installed again fresh: it is working now :) thanks!

[sillykelvin]

Glad it works finally :-p