-
-
Notifications
You must be signed in to change notification settings - Fork 55
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LibreSign Conflicts with Pico CMS #3795
Comments
Hi @smolinde could you check if this PR fix your scenario? You can do this applying the changes of this PR at your environment and checking if when you open LibreSign settings will work fine. |
I have cloned from the fix branch into the apps directory of my NC installation, however I get the following message: |
I handled this issue by simply overwriting MinVersion to 30 in appinfo/info.xml. However, when I now try to activate the app via OCC command, I receive:
|
Don't clone from the fix branch. This branch is made to Nextcloud 31. Only get the changes that I made and apply over your file. This changes: https://github.com/LibreSign/libresign/pull/3808/files You can apply handmade changing the file Pay attention to make a backup of original file before, to be possible do a rollback of this change if you got an strange behavior. |
I tried your suggestion, now the problem is that the Pico CMS webpage responds HTTP error 500. Logs are almost equal to what libresign threw:
Another problem is that when I open the LibreSign app, although CFSSL configured and configuration check shows |
The minimum version of PHP to Nextcloud 31 will be 8.1: The minimum version of Twig without this function is 8.2. I can't remove for now this package from LibreSign side because is used to render the footer template of PDF. Have a possible workaround using the package https://github.com/humbug/php-scoper to implement a scope to Twig project because the function twig_cycle haven't scope but this case together with Pico CMS is a very edge case and will take time from our team now. Another point is that Pico CMS haven't maintainer and isn't officially compatible with newest maintained versions of Nextcloud Server. If you wish to talk more about enterprise support to LibreSign and other Nextcloud apps, we also can pay attention to Pico CMS and work to update this app to newest version of Nextcloud server, you can talk about this with our sales team: [email protected]
I suggest to register this in a new issue specific to this subject. For now I recommend to use OpenSSL to use less binaries dependencies. |
I somehow fiddled around and got CFSSL to work, so no issue necessary. However, in my scenario I cannot get rid of Pico CMS, this is critical. I suggest you to include somewhere in the documentation that the app will not work with Pico CMS installed, and as an alternative people can use Certificate24, which is the exact alternative for LibreSign. Nevertheless, thank you for your time, probably this issue can be closed or marked as |
Certificate24 don't do the same as LibreSign because LibreSign is totally open source. Certificate24 is only a client and need to have a license key to work and send all of your data from signature flow to this address: api.certificate24.com. Look this screenshot of Certificate24 settings: Looking at organization of this app at GitHub, I didn't found the source code of API server side. |
On the other side... By using LibreSign, you ensure that all your data ever will be exclusively on your server, without sharing anything with third parties. We value your privacy and security; your data should always be just yours. Our commitment is to keep LibreSign as open-source software, without blocking any features you may need with license keys. We believe that the freedom to use our software is essential for everyone. I solved the issue with PicoCMS by replacing the Twig template engine with Plates, which is used to customize the footer. All our work is maintained by a team that loves open source softwares. I dedicated over two days to studying and finding a solution to this issue. Every contribution, no matter how small sounds, need time to be implemented. If you wish to contribute with us in the development of LibreSign, consider supporting us through GitHub Sponsors or any other way you prefer. Together, we can continue to build a future where privacy and freedom are priorities. Your participation is very important for us to move forward. Come be a part of this journey with us! |
Describe the bug
When having Pico CMS enabled, opening either LibreSign admin or app page results in a HTTP 500 error.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
LibreSign and Pico CMS should work independently and don't conflict with each other.
Environment information (please complete the following information):
Additional context
I am aware of the fact that Pico CMS is deprecated and is not developed anymore. However, it would be still great if I could use both at the same time. When I try to re-enable Pico CMS, I get:
Error: This app cannot be enabled because it makes the server unstable
The text was updated successfully, but these errors were encountered: