Cloudron Forum

Also the bot randomly mentioning it's for pro only is it making things up... Change password would never be a pro feature
Please don't take dosu bot messages as law, they are great for quick things but info like this is often wrong sadly

Hey creator of Stirling PDF here
We didn't drop it on purpose
We just missed change user password in the migration to V2
The 'missed' feature discussed before was changing another users password that isn't your own
We are adding both in upcoming update

Also we should have roll called as admin and the can manage settings etc as description, on my screen it shows as such, could be a UI bug related to your browser or something else
Are you able to provide a screenshot and extra info for that?

If the account is outside of stirling-pdf it doesn't count, so if its a cloudron account, this doesn't count (it doesn't actually make an account in stirling as far as I am aware?)

Grandfathering will allow existing accounts but wont allow you to add new ones even if you were at 500 and remove 100, you cant add any since you are past the 5 limit. Yes we do have a admin dashboard etc but since most don't actually use login via stirling many don't even know!.

Also something extra to note
From our opt in analytics
Most of our users don't have login enabled so have never seen seen this and wont be impacted
And out of that subset 98-99% of users fall under the 5 user limit.

Hi all!
This will be with our V2 release in month or two and is only for named login accounts. Any third party Auth like cloudron etc completely fine! And any general usage is also fine.
The aim is to price business features like SSO etc but allow general users and small businesses use still (hence only more than 5 users) businesses using any other login system also fine

Grandfathering will be in as well somewhat, a 500 user system won't crash or deny users or anything if it already has those users, it just won't allow new ones. But those 500 will function same as normal

This should already be covered by the changes discussed in
https://forum.cloudron.io/topic/13343/bad-paths-for-weasyprint-unoconv

Provided you inputted unoconvert for the path etc

FYI to Cloudron guys, Users that have reported this issue often say its some permission issue
https://github.com/Stirling-Tools/Stirling-PDF/issues/2928

We also now start
/opt/venv/bin/unoserver --port 2003 --interface 0.0.0.0
alongside stirling app.jar

The reason is unoconv which we use for file to PDF now is a server and unoconv is depreciated

For Cloudron they might need to do the following changes
https://github.com/Stirling-Tools/Stirling-PDF/commit/d34c44ed7bbf60d85f96744f99cd38a38911daa3
adding
PYTHONPATH=/usr/lib/libreoffice/program:/opt/venv/lib/python3.12/site-packages
UNO_PATH=/usr/lib/libreoffice/program
URE_BOOTSTRAP=file:///usr/lib/libreoffice/program/fundamentalrc

and pip install unoserver
along with
ln -s /usr/lib/libreoffice/program/uno.py /opt/venv/lib/python3.12/site-packages/ &&
ln -s /usr/lib/libreoffice/program/unohelper.py /opt/venv/lib/python3.12/site-packages/ &&
ln -s /usr/lib/libreoffice/program /opt/venv/lib/python3.12/site-packages/LibreOffice && \

(or whatever the python install path is that aligns with unoserver etc)

@necrevistonnezr correct

A few weeks ago we removed ghostscript and Ocrmypdf (since it uses ghost script) due to licensing issues

For Ocrmypdf we are using tesseract directly so no additional dependencies
For compression we now use the dependency qpdf
(Works better on some PDFs and worse on others, we are trying to improve this)

One functionality that was completely removed with this is pdf/a, we are readding this soon natively

Also any feature that are disabled due to something missing should show in console logs if you check

So the way it works on stirling side is we just grab whatever files are in static if their naming and path is the same on stirling pdf side
In this case any files you place will override any files placed in here
https://github.com/Stirling-Tools/Stirling-PDF/tree/main/src/main/resources/static

since you want to override the favicon itself then you would nee dto change favicon.svg for the homepage icons and favicon-16x16.png etc for the favicon itself (smaller sizes for better loading on SSO side)

That change is to remove the config to change the path as it never actually worked
It is instead hard coded to .\customFiles\static
I can still customise this on latest version with a favicon.svg file placed in that folder

Not sure what is happening here, i can still change the icon in the base package, we have not made any updates to this functionality in a long time

Stirling founder here, it means nothing other than more money to support the free version
Our goal is to only target enterprise users that need advanced audit logs or SAML SSO etc
Outside of that we want to try make all features and improvements for all users
I think so far it's going well

I hope you have all had a chance to fill out our survey which showed up in our latest update

https://stirlingpdf.info/s/clwzgtfw7000gltkmwz1n212m

Hoping to get more information from our user base with focus on businesses and larger operations to hopefully become a funded OSS via company paid support etc
Please let me know anything you think might be interesting for me to know

@dev-cb Let me know if you would rather me do a PR

@dev-cb I love all these changes! Please consider raising this as a PR so I can give proper credit

In original post I mentioned
"Please let me know what you think, there is a new on hover Tools navbar" refering to this

@necrevistonnezr no it's been that way ever since the demo etc I showed earlier

And OAuth was also the other big feature introduced this patch