Tested v11 tonight

Downloaded composr-v11.zip
unzip composr-v11.zip
cp contents of composr-v11 to public_html
read index.php

——————
Critical error – bailing out
The top-level configuration file (_config.php) is missing. You probably have not yet installed, so run the installer.

Details here are intended only for the website/system-administrator, not for regular website users.
» If you are a regular website user, please let the website staff deal with this problem.

Depending on the error, and only if the website installation finished, you may need to edit the installation options (the _config.php file via the config_editor.php script).

ocProducts maintains full documentation for all procedures and tools (including disaster recovery). These may be found on the Composr website. If you are unable to easily solve this problem, we may be contacted from our website and can help resolve it for you.
——————-
read install.php
white screen
tail  /var/log/httpd/error_log
Nothing found

cat php_errors.log
—————
[13-Aug-2023 03:00:09 UTC] Composr critical error: <div>The top-level configuration file (<kbd>_config.php</kbd>) is missing. You probably have not yet installed, so <a href="install.php">run the installer</a>.</div>
—————
chown –recursive apache:apache *
read install.php
"Composr installer: step 1 of 10"
"There are 94 corrupt Composr files that need to be uploaded: "
"Your PHP upload_max_filesize setting is very low (2M, which parses as 2,097,152 bytes). "
"You appear to be installing via the official GitLab repository. This is not intended for end-users and will lead to a bloated insecure site. You should use an official package from the Composr download page." – that's okay, I'm a loner, Dottie, a rebel.

Proceed

Composr installer: step 2 of 10: I agree
Composr installer: step 3 of 10:  Advanced database / site-network configurations Expand (cause I'm thinking php 8 is better than php 5)
    Composr's own forum (Conversr, recommended)
    MySQL 5.5.3+ selected, but I don't think I have 5.5.3. I have 8-something. But 8 isn't listed.
    Proceed
Composr installer: step 4 of 10: Install Composr
"Could not connect to database-server (when authenticating) (Access denied for user 'root'@'localhost' (using password: YES))"
Hmm… no mysql password: grep 'temporary' /var/log/mysqld.log
2023-08-09T07:41:32.291228Z 6 [Note] [MY-010454] [Server] A temporary password is generated for root@localhost: *************
mysql -u root -p
mysql> ALTER USER 'root'@'localhost' IDENTIFIED BY '************';
mysql> flush privileges;
mysql> exit;
—————
03:28] [server1.witches.community public_html] # tail  /var/log/httpd/error_log
[Sun Aug 13 03:11:01.513826 2023] [lbmethod_heartbeat:notice] [pid 915] AH02282: No slotmem from mod_heartmonitor
[Sun Aug 13 03:11:01.566452 2023] [mpm_prefork:notice] [pid 915] AH00163: Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/8.1.22 configured – resuming normal operations
[Sun Aug 13 03:11:01.566478 2023] [core:notice] [pid 915] AH00094: Command line: '/usr/sbin/httpd -D FOREGROUND'
[03:29] [server1.witches.community public_html] #
—————-
Back to install.php, Composr installer: step 4 of 10: Install Composr
"An error has occurred" - "For your security, please use a database user other than root."

Composr installer: step 4 of 10

mysql> create user 'composr'@'localhost' identified by '**********';
mysql> flush privileges;
Install Composr
"Could not connect to database (Access denied for user 'composr'@'localhost' to database 'cms')"

mysql> create user 'composr@localhost' identified by '*****';
mysql> flush privileges;
Install Composr
Could not connect to database (Access denied for user 'composr'@'localhost' to database 'cms')

Ohh!!!!
mysql> GRANT ALL PRIVILEGES ON cms.* TO 'composr'@'localhost';
mysql> flush privileges;
Install Composr

all sorts of things happened on the screen…
Composr installer: step 10 of 10

Congratulations! Composr is now successfully installed!

Configure my Composr first (Recommended)
Go to my new website now!

What the hell! This looks way different!
Setup Wizard

Start
Community: Proceed
Filled out the page, then Proceed
Setup Wizard, step 4 of 10

Multi-moderations for the Conversr forum. Huh? What's that mean?
composr_homesite: Simple addon to include Composer (the standardised PHP package manager) autoload support… What?!?! Let's just leave it alone.
There's a lot of things that have insufficient explanations. Leaving them unchecked.
Setup Wizard: Step 5 of 10
Setup Wizard: Step 6 of 10
Setup Wizard: Step 7 of 10
Setup Wizard: Step 8 of 10
Whoooo!!!! Way better site/theme color selection layout!
Selecting Preview doesn't do much. Colors of the icons don't change. No matter the color I select for the theme, nothing really changes here. (but I suspect it will change on the site)
Proceed
Setup Wizard: Step 9 of 10
Proceed
48 seconds later (not too bad!)
Setup Wizard: Congratulations, the Setup Wizard has now completed! You may now continue to work on your website.
Go To Homepage
Homepage is here, but we've got an error:  An error has occurred: PHP WARNING [2] Undefined variable $avatar_url in sources/cns_members2.php on line 64 (version: 11 alpha1, PHP version: 8.1.22, URL: https://witches.community/index.php?page=home)

OMG! An Error lol (not bad at all for an alpha or beta code!
on about line 33 of sources/cns_members2.php, let's do this:

function cns_choose_default_avatar(string $email_address = '', string $algorithm = 'avoid_conflict') : string
{
    $avatar_url = null;
    …
    
Reload the page….
Ah ha! No errors!

I'll stop here and look around all night. I used a green color for the theme. It's absolutely awesome. The css on this absolutely rocks! Composr has come of age. So, of course, I'm going to ignore all the good advice about not putting development sofrware into production…and I'll put it into production. I know, I'm bad.

Please add $avatar_url = null; at about line 33 of function cns_choose_default_avatar ( sources/cns_members2.php )
After a fresh install, index.php should point to install.php if there's no config data.
Some kind of explanation about mysql prohibiting the installation of the software is probably helpful. In shared environments, things like Wordpress never ask for database credentials. It just installs stuff. On a VPS, it should give some kind of reason why the install can't proceed.
"You probably have not yet installed, so run the installer." should have a hyperlink to install.php
It might also help to check that chmod is fair and chown is reasonable…somehow. ( chown –recursive apache:apache * )

Anyway, I'm very excited about v11. It's really a serious step!

EDIT: it's the next day, and I want to add a few more things.
I think v11 is a big deal. To that, at the bottom of the v11 page (da footer) has "Chat with other Composr users" which on click yields "Error Connecting (Error: xhr poll error)" - this might be a me thing or a Composr thing. However, on Compo.sr > Community > Chat > Start yields a hanging "connecting…" message. The following is a temporary workaround to get to the Composr group chat…

https://kiwiirc.com/nextclient/#irc://irc.compo.sr:+6697/#ComposrCMS?nick=ComposrMember

And I found that some Admin Zone configurations require Scheduling to be activated. But clicking on the link Set up system scheduler sends you to a 404, but it should go to something like Composr tutorial: Basic configuration and getting started. The v11 tut files aren't done yet, so this is a super low priority.

 

@Malatesa This is going to be a short reply. I'll reply more in-depth when I have the time to more deeply analyze your test. I appreciate the feedback!

chown –recursive apache:apache *

Looks like you were having issues with the install not being owned by the webserver user. Good to see you were able to resolve that.

There are 94 corrupt Composr files that need to be uploaded:

You can ignore this for now; as GitLab is not a proper build, the SHA hash integrity checks fall out of date since they are only re-generated when a build is made.

Your PHP upload_max_filesize setting is very low (2M, which parses as 2,097,152 bytes).

I would recommend at least 8 MB, maybe even 16 MB.

MySQL 5.5.3+ selected, but I don't think I have 5.5.3. I have 8-something. But 8 isn't listed.

It is… there is a + after 5.5.3 indicating "and up". I've been running v11 on MariaDB 10.6 just fine.

"Could not connect to database-server (when authenticating) (Access denied for user 'root'@'localhost' (using password: YES))"

Hmm… I will make a note to throw an error when trying to use a root user before actually trying to connect as root. This caused you unnecessary extra work with MySQL.

GRANT ALL PRIVILEGES ON cms.* TO 'composr'@'localhost';

Haha, oops. I've forgotten to do that before too.

What the hell! This looks way different!

Yes, v11 has a brand new, more modern theme!

Multi-moderations for the Conversr forum. Huh? What's that mean?

If I recall correctly, this is a workflow system. You can specify custom forum actions that your forum mods can use to quickly perform multiple actions on a topic at the same time, such as locking it, moving it, deleting it, and/or posting a template message as well. E.g. I could create an action such as "Spamming" and define that it will both lock the topic and post a message saying "the topic has been locked by staff for spamming."

composr_homesite: Simple addon to include Composer (the standardised PHP package manager) autoload support… What?!?!

For the general public, you don't need this. Composer is a PHP package manager. Composr CMS uses third-party libraries which can easily be updated / managed through Composer (PHP). The names are confusing; just remember -er is PHP, -r is our CMS.

There's a lot of things that have insufficient explanations. Leaving them unchecked.

Please elaborate and I'll be sure to include better explanations in the future.

Colors of the icons don't change.

There is a setting in Theme Options regarding using SVG sprites or something… I can't remember it off the top of my head. That needs checked for the icons to match the color of the theme. I think it's unchecked by default. Maybe we should have it checked by default?

Setup Wizard: Congratulations, the Setup Wizard has now completed! You may now continue to work on your website.

Interesting… you were able to make it through. I get an error after step 4 when it tries to download stuff for the weather addon. Did you de-select the weather addon in the wizard?

PHP WARNING [2] Undefined variable $avatar_url in sources/cns_members2.php on line 64

Sounds like $avatar_url is being requested in a code block where it is not being set, and thus maybe $avatar_url needs to go further up the code chain / stack. We generally don't initialize variables at the top of functions but instead at the top-most code block where they are used.

The css on this absolutely rocks!

I'm glad you enjoy it! Chris had a former developer make the new theme. And I perfected the colorization that takes place via the theme wizard (there were many problems with color contrasting and WCAG compliance; it's not perfect and never will be, but I think v11 has made a huge improvement. We even have dark mode working quite well, now.)

So, of course, I'm going to ignore all the good advice about not putting development sofrware into production…and I'll put it into production. I know, I'm bad.

It's your choice, but be aware of the following (considering I have a site running v11 as we speak… https://wallden.pdstig.me , so these are a few things I've had to be careful):

• The upgrader in v11 does not work yet. So as we make changes in v11, you'll need to pull them yourself manually from GitLab and take care in any customizations you made.
• Make backups frequently
• There are quite a few things under the hood still broken. Please do post an issue on the tracker at https://compo.sr/tracker in the Alpha Testing project when you find anything broken.

Please add $avatar_url = null; at about line 33 of function cns_choose_default_avatar ( sources/cns_members2.php )

There is probably a better solution than that specifically. So I will take a look at the file and make the appropriate fix. Please add to the tracker (link above) so Chris and I don't forget. I would greatly appreciate that!

After a fresh install, index.php should point to install.php if there's no config data.

Perhaps. I will talk it over with Chris. He designed that error message, so I'm assuming he has a reason for not redirecting to install.php. My guess is install.php is meant to be deleted after use, so you can't guarantee it exists.

In shared environments, things like Wordpress never ask for database credentials. It just installs stuff.

Many shared hosting sites use control panels, such as Softaculous, which streamline the installation (such as creating the database and user automatically and then installing your CMS). That's something they do and not something we can do for Composr CMS (except via those control panels).

at the bottom of the v11 page (da footer) has "Chat with other Composr users" which on click yields "Error Connecting (Error: xhr poll error)"

I'll bring this up with Chris. We've commonly had issues with IIRC providers.

But clicking on the link Set up system scheduler sends you to a 404

Correct. v11 docs are not live on the Composr site yet. However, they do exist inside the GitLab Composr in the docs folder, if you wish to look at them. They might not be 100% up to date yet. Please let us know if you find any errors in the tutorials via the above tracker.