For example, using "icons" (patch from bug 137447) lists some but not all icon themes. In particular Yaru is missing for me.
*** Bug 137461 has been marked as a duplicate of this bug. ***
Issue is //FIXME: Temporary URL OString sPrefixURL = "https://yusufketen.com/api/"; accessing hard-coded URL prefix from the wrong site.
Supposed to be solved for 7.1 => high importance
(In reply to Heiko Tietze from comment #3) > Supposed to be solved for 7.1 => high importance the question is, who is going to fix it ? is yusuf still around? if not, anyone from the UX team ?
(In reply to Xisco Faulí from comment #4) > the question is, who is going to fix it ? Muhammet volunteered if Yusuf has no time.
Fine to keep this assigned to me as fail-safe, but yusuf has already prepared a script and reported that it works. It's expected to be deployed later today.
Can't remember what we decided then but it should be dynamic (updated daily) now. So safe to close this?
Created attachment 170457 [details] Scraper script for the current daily-updated pseudo-API
It might be good if infra (cloph?) could adapt this script (see lines 93 and 215 particularly) and place it somewhere under the extensions website, or, even better, inspect this and adapt the API on extensions to fit the needs. Then it would a one-line commit to change the URL to somewhere official/permanent.
(In reply to Muhammet Kara from comment #9) > It might be good if infra (cloph?) could adapt this script (see lines 93 and > 215 particularly) and place it somewhere under the extensions website, or, > even better, inspect this and adapt the API on extensions to fit the needs. > Then it would a one-line commit to change the URL to somewhere > official/permanent. Hi Muhammet, Could you please fill a redmine ticket, so the infra team is aware of it ?
(In reply to Muhammet Kara from comment #9) > […] inspect this and adapt the API on extensions to fit the needs. You have no idea how much this remark triggers me. I repeated countless times that the API (which didn't exist before and was created for this project) and be anything Yusuf needs. I asked him to specify the API. Which he only did half-heartedly. So I filled in missing blanks and created the current api, assuming that he would actually use it to test his implementation against. I only told him repeatedly to add some error handling in case of server not responding, or the server not responding with a json file or the json file having additional tags.
At least, the code still points to Yussuf's address. => back to NEW As Cloph pointed out, there are some missing features. But it's the second-best solution anyway since changes are not immediately available - even when the script would be triggered frequently.
grabbing to change the URL to a non-random-external-site one. Won't fix that it is not using API, and also no commitment to update the json files used for this workaround-like situation in future.
Christian Lohmaier committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/452fcbe0792aa10042bb8cd2cfd6cd29ca754be5 tdf#137470 use a more proper URL for the extensions It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Christian Lohmaier committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/e5b8477a1270a8b572b3815cfb318110eb19d0f2 tdf#137470 use a more proper URL for the extensions It will be available in 7.1.4. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Christian Lohmaier committed a patch related to this issue. It has been pushed to "libreoffice-7-1-3": https://git.libreoffice.org/core/commit/1095de0ae2476a7c3c8d478c360a3d3c7148a245 tdf#137470 use a more proper URL for the extensions It will be available in 7.1.3. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
(In reply to Christian Lohmaier from comment #11) > (In reply to Muhammet Kara from comment #9) > > […] inspect this and adapt the API on extensions to fit the needs. > > You have no idea how much this remark triggers me. I repeated countless > times that the API (which didn't exist before and was created for this > project) and be anything Yusuf needs. I asked him to specify the API. Which > he only did half-heartedly. So I filled in missing blanks and created the > current api, assuming that he would actually use it to test his > implementation against. > > I only told him repeatedly to add some error handling in case of server not > responding, or the server not responding with a json file or the json file > having additional tags. I'm sorry to hear that. If the project didn't end as planned/expected, we all have our parts in it, IMHO. Let's not turn to blaming. The API was not ready until near the end of the GSoC period (July 20th by looking at the redmine ticket), and the project had to move on, that's why Yusuf had to prepare that temp/totally-non-ideal workaround. Though, I wish he updated it to work with the actual API after that, and also did some maintenance to make it shine. On my part, maybe I should had made sure you had room for that task before dumping it on you. I know you have a lot in your plate as the infra team, sorry. I even thought about volunteering to create the API myself, but didn't want to be nosing into your job. (Next time, I'll just offer, and let you decide.) (In reply to Christian Lohmaier from comment #13) > grabbing to change the URL to a non-random-external-site one. > Won't fix that it is not using API, and also no commitment to update the > json files used for this workaround-like situation in future. Thanks a lot for picking this up again! Please feel free to let me know when you are done with this bug report (change of URL to tdf domain), then I'll look into the dialog to see if I can (even if slowly) adapt and make it work with the actual API so that you (along with everyone else) can enjoy seeing the fruit of your hard work in action in the next release. :)
A polite ping to Christian Lohmaier: Is this bug fixed? if so, could you please close it as RESOLVED FIXED ? Otherwise, Could you please explain what's missing? Thanks