Cells Installation Fails on Ubuntu 22.04 Server

[bsinou]

@pypypypypypypy

If that’s the case, why not mark the internal strings as “undefined”/“default”/something and place an en-us “translation” on Crowdin?

It could be an idea, indeed. But you have to realize that the code has grown quite big, together with our to-do list…
I’ll have a look in crowdin and put this in our backlog itf it seems do-able: there might be a window for this when we make the last few sprints before the v5 that brings some deep refactoring in the code. But don’t hope too much!

@pypypypypypypy

Or else create a single file/folder in the source code to host all of your internal strings for everything else to pull from?

That would go against our strategy to keep things separated. Typically, each plugin brings its translations and that brings flexibility and modularity. There is little hope we go your way for this.

[pypypypypypypy]

Right, well, if I see an opportunity to contribute, I will.

In the meantime, would you be willing to offer some guidance on using Cells on a subdomain?

[bsinou]

In order to keep things easy for others that might also be looking for some guidance on this, could you rather please open a new thread for the subdomain question.

It would also help if you precise if you mean pydio.example.com as a sub-domain or rather example.com/pydio

See you there !

[bsinou]

@pypypypypypypy

It’s too bad I can’t afford the pricing for my own use case, but it would have been nice to at least be able to change the icon/favicon

And BTW, I just remembered that it is in fact also doable with the home:

Go to Admin Console >> enable advanced params >> Application parameters >> All Plugin >> Client Plugin >> Edit

Et voilà !

[pypypypypypypy]

@bsinou

Go to Admin Console >> enable advanced params >> Application parameters >> All Plugin >> Client Plugin >> Edit

Thank you for pointing that out. I don’t see anywhere to change the favicon, but the options here are still nice.

In order to keep things easy for others that might also be looking for some guidance on this, could you rather please open a new thread for the subdomain question.

I will do that. Thank you for your help.

[bsinou]

@bsinou

@pypypypypypypy

Indeed, the pydio DB user’s password seems to have been the original problem. I reset everything and retried with the original password, and got the same error you originally pointed out, then flushed everything and set it up again with password password and it worked again.

Yep, nailed it. There is indeed an issue with question mark in db password. We’ll fix it. Thanks for the feedback, it really helps.

For the record, we released the v4.4.3 yesterday that adresses this issue:

• in the v4.4 branch: we only prevent MySQL passwords that contain a ?
• we have fixed the issue and support such passwords in the next major version (v5) that is (almost) around the corner.

Thanks again for pointing that out!