What else ? Probably everything else which isn't in a Block (Login, User Menu, Main Menu etc.) - without understanding how feasible this is ! Some things are already configurable as you point out, and pulled by the theme, Sitename, Banners also - but part of the problem, as a new user, is that you aren't aware of this or understand the system conventions. So it's sort of 'all or nothing'.

Perhaps the difficulty with this is that it would need to be Theme specific, so an admin UI would be on a per theme basis - although not obligatory and perhaps only done for one. Initially I'd probably just do an admin panel for Xswatch4 and make this the default theme. So a new Xoops user would see this first and could be directed to the Theme Admin UI, immediately change the theme interactively, and be up and running within a few minutes.

Theme Administration UI

I float this as an idea having found the need to hack template code even to make simple changes very frustrating - which possibly puts off new xoops users altogether. One of the first things you do is pick a Theme for your site (xSwatch4 in my case). These are invariably Responsive 3 panel, 2 header, 2 footer designs because this meets most needs - you only need one or two. A Theme Administration UI, enabling editing of site name, logo, colour scheme etc. would get people up and running very quickly and encourage further use methinks.

Thanks, this hinted at a Permissions problem and once I had mastered PHP Error Logging the fix was straightforward.

The PHP Error :
Warning: fopen(/var/local/lib/xoops/data/protector/configcachea07794): Failed to open stream: Permission denied in file /var/local/lib/xoops/lib/modules/protector/class/protector.php line 184
Error: TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in file /var/local/lib/xoops/lib/modules/protector/class/protector.php line 185

Fix:
Change directory/file Ownership to root:www-data and Permissions to 0775/0664

I have a clean install of Turnkey Linux XOOPS 18.0 appliance running in VirtualBox 7.1.6 (no Guest Additions). This installs without error and initially XOOPS runs without error : the only modules present are System, Private Messaging, User Profile and Protector. However when I amend Protector Preferences there is a fatal error (even when nothing is actually amended but Go is pressed) :

Error : TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given

The same is true after applying Updates to all four modules, which are error-free in themselves.

My debugging skills have reached there limit and I could do with some support. Any ideas?
Thanks.

XOOPS 2.5.11 Stable
Protector 3.6.2_Stable
PHP 8.2.26
MySql 10.11.6-MariaDB-0+deb12u1
Apache 2.4.6.2

@liomj

Thanks, this worked for me, problem solved !

Thanks for the tip - wggallery is very impressive.
However, I picked myAlbum-P because it allows any MIME type/file extension to be specified, such as .pdf .docx .wav. It is also cloneable.
As well as image files, I want to create a clone in order to upload audio files (.ogg .mp3).
Do you know of any other module that can do this ? (I think it is why myAlbum-P remains such a popular module).

UPDATE

Even on a clean build with no other Modules added and no Updates to the core modules, the install still fails with:

Failed to execute xoops_module_install_myalbum

Debug:

When following the normal System Admin > Modules install procedure I’m getting an Install error towards the end of the install log:

‘Failed to execute xoops_module_install_myalbum’
(curiously followed by ‘myAlbum installed successfully’ at the very end).

Subsequent attempts to access any of the myalbum menu functions results in ‘Page isn’t Working HTTP Error 500’

I think I’ve installed the downloaded module directories correctly? :
/xoops/modules/myalbum (code base)
/xoops/modules/sitemap
/xoops/modules/tag
/xoops/includes/ myalbum (containing /photos & /watermarks)

I’ve given everything the widest set of permissions (0777);
/xoops/includes owner:group is set to www-data:ww-data for everything
/xoops/modules owner:group is set to root:root for everything

Module access rights have been granted for Admin User under Groups.

I have also installed xLanguage, Publisher and QRcode which work fine.

I get the same error with myAlbum-P (3.07 RC 2).

What have I got wrong – has anyone else got this problem or is it just me ?!


XOOPS version is 2.5.10
PHP version is 7.4.30
MYSQL version is 5.5.5-10.5.15-MariaDB-0+deb11u1
ModuleAdmin version is 1.2
Running Turnkeylinux XOOPS appliance (17.1) - Debian/Linux 10 - inside VirtualBox VM.


DEBUG MESSAGES