[Feature] Save CustomCSS settings to user data

[hkcomori]

Is your feature request related to a problem? Please describe.

I faced the issue of not being able to write CustomCSS settings and solved it in #182. However, if the extentsions directory has user data, it becomes more complicated to manage. Because the extensions directory is managed outside of the application, but the user data is variable data that the application writes.

Describe the solution you’d like

I think CustomCSS settings should be stored in the database or in each user's data directory, because they are user data.

For example, Readable stores settings in data/users/<username>/config.php. If it needs to be saved in an independent file, data/users/<username>/custom.css would be better.

Is it a technical difficulty to store CSS in the same way as general user data because it is a file delivered over HTTP?

Describe alternatives you’ve considered

Additional context

[Alkarex]

Indeed, that would be very welcome.

I suggest the following:

1. Promote CustomCSS and CustomJS to core extensions (i.e. move the code from the Extensions repo to the core FreshRSS repo)
2. For system extensions (not relevant for CustomCSS), save extension data in data/extensions-data/{extension-name}/ (some initial work was done in https://github.com/FreshRSS/FreshRSS/pull/1547)
3. For user extensions (relevant for CustomCSS), save extension data in data/users/{user-name}/{extension-name}/

Would you feel like sending a PR? (maybe @Frenzie could help?)

[Frenzie]

I'm not really sure what that would entail without investigating, but happy to answer some questions if asked.

[hkcomori]

Thanks for the reply. It will take me a long time because I'm a PHP beginner, but I will try it. I will decide which approach to adopt after a better understanding of the code.

BTW, any approach would lose compatibility with existing configurations, is that a problem?

[Alkarex]

A few points:

• If we promote CustomCSS and CustomJS to core extensions, they will get a slightly different name, and both the old and new extensions can co-exist for some time, without breaking anything

• In any case, we could consider copying automatically from the old location to the new

• https://github.com/FreshRSS/FreshRSS/blob/edge/p/ext.php might have to be adapted a bit

[hkcomori]

OK, then I'll avoid duplicate names so that they can be used at the same time.

[hkcomori]

I submitted a pull request FreshRSS/FreshRSS#6267. Please review.