pling-store-development issueshttps://www.opencode.net/dfn2/pling-store-development/-/issues2024-03-22T16:35:10Zhttps://www.opencode.net/dfn2/pling-store-development/-/issues/28It is not necessary to use n2024-03-22T16:35:10ZblacklightpyIt is not necessary to use nI'm running Void Linux with musl libc, and the Node runtime provided by n is built for GNU libc.
Also, same goes for the AppImage release, which also doesn't support musl libc.
And theres also the thing about libraries in musl being un...I'm running Void Linux with musl libc, and the Node runtime provided by n is built for GNU libc.
Also, same goes for the AppImage release, which also doesn't support musl libc.
And theres also the thing about libraries in musl being under `/usr/lib` and not `/usr/lib/x86_64-linux-gnu`.https://www.opencode.net/dfn2/pling-store-development/-/issues/27darktheme or plasma integration for pling?2023-07-11T03:20:09Zjhortondarktheme or plasma integration for pling?i don't found dark theme or plasma integrationi don't found dark theme or plasma integrationhttps://www.opencode.net/dfn2/pling-store-development/-/issues/26"SSL handshake failed" error2023-02-19T02:32:51Zsilopolis"SSL handshake failed" errorHi,
Just installed Pling-Store on my oldish Debian Buster and installations fail with a "SSL handshake failed".
Edit: output in terminal shows
```
{ Error: certificate has expired
at TLSSocket.onConnectSecure (_tls_wrap.js:1049:34...Hi,
Just installed Pling-Store on my oldish Debian Buster and installations fail with a "SSL handshake failed".
Edit: output in terminal shows
```
{ Error: certificate has expired
at TLSSocket.onConnectSecure (_tls_wrap.js:1049:34)
at TLSSocket.emit (events.js:182:13)
at TLSSocket._finishInit (_tls_wrap.js:631:8) code: 'CERT_HAS_EXPIRED' }
```https://www.opencode.net/dfn2/pling-store-development/-/issues/25Cannot install externally hosted AppImage2021-04-28T13:13:49ZjuliangroCannot install externally hosted AppImageWhen clicking to install an AppImage that is hosted externally, nothing happens.
An example is Vircadia: https://www.appimagehub.com/p/1505432When clicking to install an AppImage that is hosted externally, nothing happens.
An example is Vircadia: https://www.appimagehub.com/p/1505432https://www.opencode.net/dfn2/pling-store-development/-/issues/24Can't install on Raspiberry Pi 4 armf2020-11-24T00:05:59Zchest070Can't install on Raspiberry Pi 4 armfHello,
Is there any chance that you are making this to work and install on a Raspberry Pi 4 based system. The app-image stuff works but I can't use this though and I would love to be able to use it. Thanks for the help.Hello,
Is there any chance that you are making this to work and install on a Raspberry Pi 4 based system. The app-image stuff works but I can't use this though and I would love to be able to use it. Thanks for the help.https://www.opencode.net/dfn2/pling-store-development/-/issues/22Pling-Store armhf appimage for the Pinebook Pro2020-02-19T20:38:51ZpinebookfanPling-Store armhf appimage for the Pinebook ProHello,
Assassine from AppImageLauncher made a xenial armhf deb.
So you can run AppImageLauncher.
But the Pling-Store is only for x86 and x64.
So please make armhf appimage for the pinebook pro and should work on raspberry pi so too.
Pine...Hello,
Assassine from AppImageLauncher made a xenial armhf deb.
So you can run AppImageLauncher.
But the Pling-Store is only for x86 and x64.
So please make armhf appimage for the pinebook pro and should work on raspberry pi so too.
Pinebook is using debian 9 stretch 32bit armhf architecture.
Best regards and Thanx!https://www.opencode.net/dfn2/pling-store-development/-/issues/21Fail to connect with a squid proxy2020-02-11T14:54:11ZreinaldoplacetasFail to connect with a squid proxyWhen I try to use the program its fails because it ignore the proxy environment variables.When I try to use the program its fails because it ignore the proxy environment variables.https://www.opencode.net/dfn2/pling-store-development/-/issues/20Product Updates2019-11-04T19:59:23Zazubietacontact@azubieta.netProduct UpdatesSome users have requested support for updates on different types of "items" such as:
icon themes, applications, fonts, add-ons and others.
The ocs-store already stores a "version" attribute for each file but there is now way (at least n...Some users have requested support for updates on different types of "items" such as:
icon themes, applications, fonts, add-ons and others.
The ocs-store already stores a "version" attribute for each file but there is now way (at least not known to me) of relating a file with it's next version.
The file name could be used if no versioning is used on it, i.e.: `appimage-cli-tool-1.9-x86_64.AppImage` will have to be renamed to `appimage-cli-tool-x86_64.AppImage` and the file versioning will be shown in the "version" attribute. Yet the downloaded file must preserve the original name for debugging purposes.
This approach has the inconvenient that files cannot be renamed after they are uploaded and they will have to be uploaded without versioning information in its name. So users will not be able to rely on the file name to know the version of a downloaded product.
In resume, file names without version information altogether with the "version" attribute can be used to identify the right file to download when a new release of a given product is made. Yet it requires allowing renaming the files on the pling-store after they are uploaded.
Alternative solution: add an "update-id" attribute to relate files that represent successive releases of a given product. Client apps will search for the product files with the same "update-id" and select the one with the greatest "version". Once the file is identified they can proceed do the update.
The update process in the clients systems will vary depending on the type of product and the format. But basically it should contain the following steps:
- downloading the new file
- installing the file as usual
- uninstalling the old one, but keeping the file to allow rollbacks
In some scenarios (icons, wallpapers or themes) will be possible to perform and additional "apply" step as part of the update process.
The only modification required in the client side will be adding an "update lookup" method the already existent install/uninstall methods can be reused.https://www.opencode.net/dfn2/pling-store-development/-/issues/17Download progress not being reported on downloads2019-10-24T17:43:28Zazubietacontact@azubieta.netDownload progress not being reported on downloadsWhen a download is performed using the "download" button no progress report is shown. Yet when an install is performed the downloads progress is visible.
This is a legacy issue from the old ocs-store app.When a download is performed using the "download" button no progress report is shown. Yet when an install is performed the downloads progress is visible.
This is a legacy issue from the old ocs-store app.https://www.opencode.net/dfn2/pling-store-development/-/issues/13add "Login" Button to toolbar left of the ..." dropdown, simply link to login...2019-09-12T11:01:52Zopendesktopadd "Login" Button to toolbar left of the ..." dropdown, simply link to login page: pling.com/login![Screenshot_20190911_191251](/uploads/02b18b3761b827bcbb28fc4ec88c4668/Screenshot_20190911_191251.png)![Screenshot_20190911_191251](/uploads/02b18b3761b827bcbb28fc4ec88c4668/Screenshot_20190911_191251.png)https://www.opencode.net/dfn2/pling-store-development/-/issues/115.1: add entry in right side dropdown to manually invoke update checking popup2019-09-12T11:02:58Zopendesktop5.1: add entry in right side dropdown to manually invoke update checking popupput underneath "Report a bug":
![Screenshot_20190907_110856](/uploads/bf2464863d8370eb58acf9483b9effef/Screenshot_20190907_110856.png)put underneath "Report a bug":
![Screenshot_20190907_110856](/uploads/bf2464863d8370eb58acf9483b9effef/Screenshot_20190907_110856.png)https://www.opencode.net/dfn2/pling-store-development/-/issues/9[Feature Restore] Pick content to restore/install from Favorites on a new ins...2019-08-31T02:14:05Zazubietacontact@azubieta.net[Feature Restore] Pick content to restore/install from Favorites on a new installed systemTrack keeping of downloaded content is done already on the server side whenever a user is logged in.
Allow to re-install them on new system installations going by the "heart"=Favorites feature.
Restore Dialog:
Contents should be group b...Track keeping of downloaded content is done already on the server side whenever a user is logged in.
Allow to re-install them on new system installations going by the "heart"=Favorites feature.
Restore Dialog:
Contents should be group by categories like in the following picture:
![image](/uploads/3b97ef2eb432541aa5706680e5ff6924/image.png)
It should be possible to either select ALL or single items from that view which then gets restored.
Already restored items can be shown as done and not be allowed to be selected again, neither single nor by the "ALL" selector.https://www.opencode.net/dfn2/pling-store-development/-/issues/2download progress bar: check to fill up the URL field in toolbar either compl...2019-08-27T12:22:20Zopendesktopdownload progress bar: check to fill up the URL field in toolbar either complete or a thin line while downloading or installing an itemmake it look similar in the URL field how it looks when you click on the Items section:
![Screenshot_20190827_124009](/uploads/e403d2fa6170451aa92053efd15408b0/Screenshot_20190827_124009.png)make it look similar in the URL field how it looks when you click on the Items section:
![Screenshot_20190827_124009](/uploads/e403d2fa6170451aa92053efd15408b0/Screenshot_20190827_124009.png)