on install step 7 the install wizard errors out when creating the cache table.

/install.php?step=7

Unfortunately a query has failed [CREATE TABLE cmpsr_cache ( id integer unsigned auto_increment NOT NULL, cached_for varchar(80) NOT NULL, identifier varchar(40) NOT NULL, the_theme varchar(40) NOT NULL, staff_status tinyint(1) NULL, the_member integer NULL, groups varchar(255) NOT NULL, is_bot tinyint(1) NULL, timezone varchar(40) NOT NULL, lang varchar(5) NOT NULL, the_value longtext NOT NULL, dependencies longtext NOT NULL, date_and_time integer unsigned NOT NULL, PRIMARY KEY (id) ) CHARACTER SET=utf8mb4 engine=MyISAM] [You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'groups varchar(255) NOT NULL, is_bot tinyint(1) NULL, timezone varchar(4' at line 8]

I am using windows 2012, IIS and mysql 8 

I logged this in a ticket at https://compo.sr/tracker/view.php?id=3778

Hello,

This appears to be an incompatibility with MySQL 8. While this has been out for about 10 months, Linux users and hosting users tend to be on much older versions so nobody spotted it yet.
I'll take a closer look very soon.

Thanks for the help.  I looked at the install faq and I didn't see any versions of mysql specified, so I just used the latest.

Right. There's a minimum specified in the web hosting tutorial, but generally we expect Composr to run on any new version of MySQL.

In this case they introduced a new keyword conflicting with one of our field names, which is unusual.

I'll do some kind of workaround when I can, hopefully today. It is important we support the latest version.

I was going to reply to this last night. So I updated my MySQL on my dev machine to v8. MySQL then didn't upgrade my databases properly, so currently I am dealing with repairing them. When I have I'll post my Composr fix!

Thanks for the update.  I appreciate the help.

I've fixed the issue with a workaround. You'll need to use the manual installer (i.e. not quick installer), and get these 2 updated files before installing:

1. database/mysqli.php
2. sources/database/shared/mysql.php

For reference, issue is discussed in detail here:
0003782: Clean MySQL 8 support - Composr CMS feature tracker

I replaced the files from git and the site installed properly.

Running through the site wizard, I get to step 10 and I am getting an error:

Cannot write to sources/hooks/systems/addon_registry/aggregate_types.php. File permissions for it (or the directory it is in) have not been set correctly.

Then errors appear on the dashboard about missing images:

The admin dashboard is showing errors for missing files of 48x48 and 24/24 aggregate_types  
icons/24x24/menu/adminzone/structure/aggregate_types.
icons/48x48/menu/adminzone/structure/aggregate_types.


I put the files back in but the set up wizard removes them each time it runs.


When I do the /upgrader.php all permissions are correct.  File integrity scan is clear as well.

I have the site application pool identity set up to be a active directory user with full persimmons on the folder and files.

If I restore all the files and do not run the set up wizard, the site functions normally.  I just configure it manually.

Hi,

This one will be an issue on your end. From Admin Zone > Tools > PHP-Info you should be able to see the user PHP is running as.

Double check that the permissions for this user are applied recursively (OTTOMH Windows calls it something like 'replace child object permissions' or something similar).

Make sure read-only is off recursively too.

The Setup Wizard will change a lot of files as a part of configuring what addons to keep.

Thanks for all the help. I worked through all the permissions issues and got it configured.

I was wanting compsr to be used as an image gallery for over 900gb worth of images mounted on our network media share.    is it possible to have composr gallery access and process those images?  

Wow, that's a lot of data.

There is the capability to mass-import images, but nothing on that kind of scale, and not from a folder structure.

It could be implemented, I've added a tracker issue:
0003783: Import from filesystem - Composr CMS feature tracker

Depending on the nature of the images, it might require some reconfiguration of PHP or other server settings. For example, if you have 10000x10000 image (100 megapixels), that's going to require at least 400MB of RAM to load to generate a thumbnail - and will typically bust default limits. Very doable though, as long as it is done in a background task rather than within a web request.

Thanks for all of the help on this.  

It is the catalog images and and raw images that we want to share with our distribution partners for use on their web platforms.      The server created for composr is just for it.   the average image dimenstions are 2048x1436.  There are not a lot of gallery software that support network shares.

I was trying to find a gallery software to view these through but I may just end up just creating SFTP folders for access.

It is looking a bit more complex than I first thought.

I was assuming the network share would be mounted as a web server directory.

I was also assuming that the media wouldn't be managed direct from filesystem after import, but my guess is you'd want to continue to rearrange it on there rather than via the Composr UI.

So what you'd need is either:

1. a system that doesn't use any Composr database tables to store the gallery structure, but rather directly maps to the current disk directory structure. Probably best.
2. a system that regularly reimports (e.g. nightly) to the Composr gallery structure.

And in both cases you'd need it to have some proxying script to be able to make media on the network share available by URL.

Still possible with custom coding.