Could not find module `discourse-common/lib/icon-library`


(sepideh Javdani) #1

Hi,
Any idea How we can solve below error?
uncaught Error: Could not find module discourse-common/lib/icon-library imported from `discourse/plugins/discourse-solved/discourse/initializers/extend-for-solved-button
[v1.9.0.beta1]


(Penar Musaraj) #2

I think you are trying to use the current solved plugin with an older version of Discourse core. You should upgrade core to latest, it should fix the issue.


(sepideh Javdani) #3

we are not able to upgrade discourse, how we can use older version of solved?


(Penar Musaraj) #4

That is unsupported, but if you absolutely can’t update Discourse, then you could checkout a commit prior to the commit that adds the icon-library import.


(Jeff Atwood) #5

It does not matter, 1.9 has security exploits and is unsupported. At minimum you should be on 2.1, and 2.2 is about to be released…


(sepideh Javdani) #6

So if we use old version of solved, it means we don’t have icon-library but we have an issue with solved button is not appearing.


(sepideh Javdani) #7

I am not sure but I think we have an issue with database, we can not upgrade now. Do you have any other workaround?


(Jay Pfaffman) #8

Is there some reason that you cannot upgrade to latest?


(sepideh Javdani) #9

Hi,

I am trying to follow

But I am getting error any idea?

I, [2019-01-31T17:08:39.945102 #15]  INFO -- : > cd /var/www/discourse/plugins && mkdir -p plugins
I, [2019-01-31T17:08:39.950402 #15]  INFO -- :
I, [2019-01-31T17:08:39.950737 #15]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2019-01-31T17:08:41.890949 #15]  INFO -- :
I, [2019-01-31T17:08:41.891630 #15]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-solved.git
Cloning into 'discourse-solved'...
I, [2019-01-31T17:08:43.344731 #15]  INFO -- :
I, [2019-01-31T17:08:43.345246 #15]  INFO -- : > cd /var/www/discourse/plugins && cd discourse-solved
I, [2019-01-31T17:08:43.349650 #15]  INFO -- :
I, [2019-01-31T17:08:43.350051 #15]  INFO -- : > cd /var/www/discourse/plugins && get reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd
sh: 1: get: not found
I, [2019-01-31T17:08:43.354172 #15]  INFO -- :
I, [2019-01-31T17:08:43.354702 #15]  INFO -- : Terminating async processes
I, [2019-01-31T17:08:43.354881 #15]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 70
I, [2019-01-31T17:08:43.355271 #15]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 186
2019-01-31 17:08:43.355 UTC [70] LOG:  received fast shutdown request
186:signal-handler (1548954523) Received SIGTERM scheduling shutdown...

(Penar Musaraj) #10

that should be a git reset, not get


(sepideh Javdani) #11

yes i found that but still have issue.

I, [2019-01-31T17:31:46.695638 #15]  INFO -- : > cd /var/www/discourse/plugins && cd discourse-solved
I, [2019-01-31T17:31:46.699054 #15]  INFO -- :
I, [2019-01-31T17:31:46.699228 #15]  INFO -- : > cd /var/www/discourse/plugins && git reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd
fatal: Could not parse object '7745adb6eb0c1d1b2a37c9441c3877b7eec087cd'.
I, [2019-01-31T17:31:46.728342 #15]  INFO -- :
I, [2019-01-31T17:31:46.728832 #15]  INFO -- : Terminating async processes
I, [2019-01-31T17:31:46.728916 #15]  INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/10/bin/postmaster -D /etc/postgresql/10/main pid: 70

(Penar Musaraj) #12

that’s the wrong folder, you’ll want to do the git reset in the discourse-solved folder.


(sepideh Javdani) #13

yes, I know. how i can go to correct one.


(Penar Musaraj) #15

try

cd /var/www/discourse/plugins/discourse-solved && git reset --hard 7745adb6eb0c1d1b2a37c9441c3877b7eec087cd

(sepideh Javdani) #16

thanks. It is worked in staging but I can not test to see if problem with solved button is ok or not.
staging and production are in different version, I need to ask for downtime for production. please keep ticket open. thanks.


(sepideh Javdani) #17

Thank you Thank you sooooo much, It solved lots of issues. :smiley::smiley::smiley::smiley:


(Penar Musaraj) closed #18