Custom Pico theme selection does not list themes after upgrade to NC26 (and hacky workaround)

[StuartJMackintosh]

Context

• Nextcloud 26 (upgraded from many previous versions)
• cms_pico installed_version 1.0.21
• database: Postgres
• Nextcloud as docker container running inside virtual machine
• external nginx reverse proxy
• mixture of sites with their own domain names, and sites hosted in subfolders on the main domain
• variety of themes

Background

Pico is listed as an untested app in NC26.

I did share this issue on IRC with @PhrozenByte who was kind enough to chat through, and plans testing of Pico & NC26 at some future point.

This issue may also relate to/duplicate #236 although I don't have enough specifics to confirm this.

The efforts with bringing Pico and themes to Nextcloud is very much appreciated!

Problem

After upgrading to NC26, the custom theme interface doesn't list installed themes, therefore these cannot be made available to users.
Specifically, the 'Reload theme' button on the right has no effect, and the dropdown of themes does not list any custom themes.

Looking at the code (I am not a coder), the function will read the folder listed above the box and offer these themes to be added to the installed themes. Behind the scenes, this runs basic validation of the themes, and copies them to an internal folder, for users to select.

Hacky workaround

WARNING: this is not recommended and could easily destroy all of your data

To get past my today problem, I identified the internal themes folder, manually copied the appropriate theme folders, then added the list to the config array.

As soon as this is applied, the themes are available in the personal settings dropdown

Internal themes folder

docker:~/var_www_html/apps/cms_pico/appdata_public/themes/SoWN6rCUlu$ ls
axcorapico  clean-blog  default  dimension  freelancer-pico-main  just-pico-master  picobook  piconic  story  story-custom

SQL config

update oc_appconfig set configvalue = '
{
    "story":{"name":"story","type":2,"compat":true},
    "clean-blog":{"name":"clean-blog","type":2,"compat":true},
    "dimension":{"name":"dimension","type":2,"compat":true},
    "just-pico-master":{"name":"just-pico-master","type":2,"compat":true},
    "freelancer-pico-main":{"name":"freelancer-pico-main","type":2,"compat":true},
    "picobook":{"name":"picobook","type":2,"compat":true},
    "piconic":{"name":"piconic","type":2,"compat":true},
    "story-custom":{"name":"story-custom","type":2,"compat":true},
    "axcorapico":{"name":"axcorapico","type":2,"compat":true}
}
' where appid = 'cms_pico' and configkey = 'custom_themes';

Don't forget, never run code pasted from websites, if you have not fully verified it and know exactly what it does

Hypothesis

I speculate that the issue relates to the theme copy function, theme validation or simply source file location.
However having no PHP / nextcloud app dev experience, don't have the debug tools to be able to narrow this down further without lots of guesswork. If someone can tell me how to print to the log file, I may be able to add more info.

[jochenwierum]

I found one (the?) culprit:

the file admin.js calls $icon.tooltip(…) in Line 204. This function does not seem to be available anymore. When I commented out the lines 204-207, I got a list of themes to install.

[StuartJMackintosh]

Thank you @jochenwierum - after removing those lines , the themes are listed (cms_pico-1.0 branch).
I will report back when I have fully tested this.

From what I can understand by the commit message from @PhrozenByte, these lines were added to enable a future theming API 4 years ago (see c82fd8d).

As this refers to a function that is no longer available and doesn't seem to affect functionality, will it be safe to issue a PR for the removal of those lines? Do you feel there is risk or other impact to consider?

[GVLLIFESTYLE]

Issue still persisting after upgrate to NC 27.0.0

[harlows]

I had the same issue with NC26 running in a docker container. I inadvertently managed to fix it when I set up cron.php to run to fetch NC News feeds.

[GVLLIFESTYLE]

so what exactly did you setup in the cron.php?
Does anyone know if this will be fixed some day in gerneal at the app?

[harlows]

I simply used my local server's cron to run Docker's cron.php using:
*/15 * * * * docker exec -u www-data [container_name] php cron.php
Then change Ajax to Cron in Settings > Basic settings.
(All credit to Seismologo on Redit)

[GVLLIFESTYLE]

Hm.. This I have already but still it does not work in my case. Am 20. Juni 2023, 21:52, um 21:52, Stephen Harlow ***@***.***> schrieb:

…

I simply used my local server's cron to run Docker's cron.php using: `*/15 * * * * docker exec -u www-data [container_name] php cron.php` Then change Ajax to Cron in Settings > Basic settings. (All [credit to Seismologo on Redit)](https://www.reddit.com/r/NextCloud/comments/hat70n/comment/fv5lkr3/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button) -- Reply to this email directly or view it on GitHub: #237 (comment) You are receiving this because you commented. Message ID: ***@***.***>

[StuartJMackintosh]

Not sure how the cron comment relates to this issue.

It is not resolved in later versions, my solution is to deploy a NC25 and create some shares between them for now.

[rcjcarr]

Same issue here. Cannot install themes.

• Commenting lines 204 to 207 did not resolve the issue.
• Copied 'themes' file to pubic folder similar to above, and this did not resolve the issue.
• I'm wondering where the config array is... I did not update that as I don't know where the file is.

Using Nextcloud 27.0.1 (under Docker)
Pico 2.1.4

[jkraffthha]

Any news on future compatibility updates.
Suggested workaround didn't work.
I'm currently editing themes in the public folder for now but its clearly not a sustainable way of doing things.
Any other ideas ?

[escribana]

Same here! Still no progress??

I tried with NC26.0.7 to no avail!

[stullekovski]

Is there any chance for an update to NC 26/27?
Because it was a perfect tool for our collective (yes, "collectives" app could be an alternative) . :(

Thanks a lot!