Thank you for the quick reply, I’m using Discourse 2.3.2 which looks quite old. On the settings, they are still on defaults. I don’t believe there are any plugins, this was the first component I installed.
Ugh. I missed this warning. I’m running Discourse 2.6.3. I’m assuming that came out before March 17, since I lost my custom images. Is there any way for me to downgrade this component?
Edit:@jtbayly it should work now if you update the component. Sorry for the trouble! I’ll try to be more careful about backwards compatibility going forward.
We seem to be getting more 429 errors these days due to this add-on (I can’t put my finger on when that started, but I’d say in the last 2-3 months). Are there still plans to reduce the number of requests?
Unfortunately, it doesn’t seem that time has permitted yet for the core changes that would be required. The priority is probably going to be even lower now that there is a plugin that handles it in a more graceful manner:
If the component is becoming an issue for your community, I would highly recommend switching over the the plugin if possible.
I took a look, but the functionality is different from the TC: in the plugin, users can set which badges to show. In the TC, the site admin decides. I’ll see if I can fork it to make it do what I need.
_application-fe5f714a0b25da04a163bd904e96336e.js:6171
Ocurrió un error en el tema/componente \"Post Badges\": TypeError: Cannot read properties of undefined (reading 'currentProp')
at 6dd3e4df7d5d30781da2109aaad4015405b3f832.js?__ws=discourse.myforum.tld:108
at e.withPluginApi (_application-fe5f714a0b25da04a163bd904e96336e.js:4070)
at Object.initialize (6dd3e4df7d5d30781da2109aaad4015405b3f832.js?__ws=discourse.myforum.tld:107)
at Object.s.initialize (_application-fe5f714a0b25da04a163bd904e96336e.js:60)
at _vendor-89acebf53895afcc5339ec7eda71567e.js:2730
at e.each (_vendor-89acebf53895afcc5339ec7eda71567e.js:4074)
at e.walk (_vendor-89acebf53895afcc5339ec7eda71567e.js:4064)
at e.each (_vendor-89acebf53895afcc5339ec7eda71567e.js:4056)
at e.topsort (_vendor-89acebf53895afcc5339ec7eda71567e.js:4056)
at n._runInitializer (_vendor-89acebf53895afcc5339ec7eda71567e.js:2733)
(anonymous) @ _application-fe5f714a0b25da04a163bd904e96336e.js:6171
_application-fe5f714a0b25da04a163bd904e96336e.js:4072
Para evitar errores, agrega una clave `pluginId` a tus cambios al llamar a `modifyClass`
ie @ _application-fe5f714a0b25da04a163bd904e96336e.js:4072
_application-fe5f714a0b25da04a163bd904e96336e.js:4072
Hola, ¡gran trabajo en este componente de tema! También creo que debería ser parte del núcleo.
Tengo curiosidad, ya que no ha habido mucha actividad aquí en un tiempo, ¿aún recomendarías usar el plugin en lugar del componente de tema? ¿Es el plugin oficial / está bien mantenido?
¿Alguna idea de si esto se convertirá en una característica principal?
¿El plugin que creó @angus está funcionando para alguien? No parece funcionar para mí, y sigue siendo la forma recomendada de usar esto. Sería muy bueno ver esto respaldado por el equipo en forma de plugin. ¡Gracias!