Sorry, little from a non-expert, but once again, I start off innocently clicking on the ‘update’ in the UI, then get booted to ‘go do a rebuild from the command line’, and then that fails and I’m pasting bash output into AI for it to tell me what’s wrong.
“The error indicates that the Discourse update failed because the discourse-data-explorer plugin is now bundled with Discourse core and should not be included as a separate plugin in your app.yml configuration file.”
I know that it’s not always possible, but it would be nice to at least have a warning like “get ready, this one is going to hurt”. It could prolong my life expectancy.
It should have printed a warning about exactly that. You could then restart the container with
./launcher start app
And then figured out your next steps more leisurely.
You may still be able to start the container.
But to answer the question in the title, not really. This was a big change and there were notifications here about it. Periodically things need upgrading that are external to the stuff that is just the discourse source code that can be upgraded in the ux.
It’s just that I wasn’t expecting the first rebuild to fail, so that caught me off guard.
The message was there, but I because it was in the wall of log text, I lacked confidence that I would find whatever the problem was. For all I knew it was going to be some obscure exception buried in a call stack. Once AI told me, I saw it was right there near the bottom.
I guess this is what happens when one is a part-part time webmaster
How would a warning someplace else be better than a warning there when both would do the exact same thing and neither have a negative effect outside of reading? The log is always the first place you should look if there’s an error…
The complexity of an update does not depend on the specific update but more on the version your forum is at before the update, and the versions of Postgres, Redis and all the plugins you have.
So it’s basically impossible to tell whether the update is going to “hurt”.
I’ve done updates from 1.8 to 3.5 without issues, and updates from 3.2.1 to 3.2.2 that cost me hours to fix.
from a non-expert, but once again, I start off innocently clicking on the ‘update’ in the UI, then get booted to ‘go do a rebuild from the command line’, and then that fails and I’m pasting bash output into AI for it to tell me what’s wrong.