Blank page after upgrade and javascript error

Hello. Latest build (commit 0adaa7c) brings it back after some years :wink:

It comes right after the discourse-presence plugin is integrated and enabled by default. Should I remove it from the list? I have renamed it so it looks like

I thought it failed because I changed the container configuration without running ./launcher rebuild app but then I ran it and:

I, [2017-09-07T12:41:47.226058 #14]  INFO -- : > cd /var/www/discourse/plugins && git clone
fatal: destination path 'discourse-presence' already exists and is not an empty directory.
I, [2017-09-07T12:41:47.232919 #14]  INFO -- :

Pups::ExecError: cd /var/www/discourse/plugins && git clone failed with return #<Process::Status: pid 159 exit 128>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn'
exec failed with the params {"cd"=>"$home/plugins", "cmd"=>["mkdir -p plugins", "git clone", "git clone", "git clone", "git clone", "git clone", "git clone", "git clone"]}
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

On the server-side nothing’s wrong. The /logs/report_js_error contains only OK which gives a syntax error. See screenshot below.

fatal: destination path 'discourse-presence' already exists and is not an empty directory.

So I guess I have to remove mention of this plugin…

Yes, discourse-presence is now part of core, so you need to remove the line from your app.yml file


Indeed, while you replied I went:

cd /var/discourse
./launcher start web
./launcher enter web
cd plugins
mv discourse-presence/ discourse-presence-legacy
./launcher rebuild web

The rebuild continued, but the error was still there. Having the legacy code in the way caused problem.

So I removed the line entirely as you suggested, and it’s rebuilding now…

1 Like

No luck… It looks like a bug…

What is the purpose of this file? Does this syntax error come before or after another error?

rebuild from master: works.

Still have an error though in the console:


You need to remove it from app.yml.

Is this the console on the /admin/upgrade page? If so you may have hit this issue:

No it’s the console on any page, running the master branch at (the one after your fix to that bug you mention.) still mentions the build failing… I’m going to wait until test-passed includes your fix to revert to that branch.

1 Like

If the Discourse.markdown error is on every page then maybe it’s not the same issue. What plugins do you have installed?

OK, thanks for your interest @david, but I guess it’s a different topic. I resolved the blank page issue by switching to the master branch that includes your reverts. Now, on the master branch, there’s still this Markdown issue that doesn’t seem to affect much of the site use.

Since you asked, here’s my list of plugins:

    - exec:
        cd: $home/plugins
          - mkdir -p plugins
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone
          - git clone

I suppose the last one is the culprit since the others are official.


That is a good supposition.

Latest commit ca8318b on Mar 14, 2015

Much has changed since then.



Today I switched back to tests-passed from master and all is working again. I suspect the patch @david was mentioning in response #8 was causing the blank page. All izz well now.


The same happens because of a issue in discourse-encrypt (debounce). See
I guess you need to pick an older version of discourse-encrypt in 2.6

1 Like