-
Notifications
You must be signed in to change notification settings - Fork 14
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Patching some bugfixes back to version 9.0:
- We are no longer allowing .html files to be uploaded into the CMS. - You can no longer upload and attach SVGs to forum posts and replies. - Visitors can no longer upload SVGs to use as user avatars. - Added sanitisation for all SVGs that are uploaded, to protect against attackers embedding XSS attacks inside them. - The admin toolbar will now once again remember the tab you last clicked on if you reload the page. - Some tweaks and improvements to CRM integration in user forms. - Some tweaks and improvements to Mailchimp integration in user forms. - Added a warning on the diagnostics screen if the layouts cache directory is not writable. We'll now also send an email to the support address when a page cannot be displayed when this is missed. - Fixed a bug on the diagnostics screen, where the "directories" section was sometimes flagged with a warning, even when there was no warning. - Fixed a database error that could happen when trying to install Zenario using the installer. - Fixed a JavaScript error when trying to click on a translation in the "Translations of" panel in Organizer. - Fixed some bugs with tracking link click-throughs in newsletters. - Removed the "fullscreen: none" rule from our suggested .htaccess rules, as it was stopping the fullscreen plugin from working. - Fixed a bug where there was missed escaping when sending an etag from the server to the client. - Fixed a bug when using page caching, where the browser body class variable could be wrong when a page was served from the cache. - Fixed a bug where the preview in the skin editor would not update after making a change. - Fixed a bug with admin permissions, where dependant admin permissions could be granted without also giving the permissions they depended on. - Fixed a bug where administrators with the "View user" permission could not see the Users panel in Organizer if they didn't also have the "View administrator" permission. - Fixed a bug where an administrator could change the extension of a document by manipulating the inputs sent when editing its properties. - Fixed a bug where newer versions of the MySQL/Ubuntu command line tools would not work with the backup tool in Zenario.
- Loading branch information
1 parent
b4f56ad
commit 4566d8a
Showing
80 changed files
with
794 additions
and
558 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,99 +1,5 @@ | ||
Installing Zenario CMS | ||
====================== | ||
|
||
System Requirements | ||
------------------- | ||
Please see [https://zenar.io/how-to-install-zenario](https://zenar.io/how-to-install-zenario). | ||
|
||
To run Zenario you will need a web server/hosted account with the following: | ||
|
||
* Apache Server version 2.4.7 or later | ||
* PHP version 7.2 or later (PHP 7.4 preferred) | ||
* MySQL version 5.7 or later | ||
* The GD, libCurl, libJPEG and libPNG libraries, and multibyte support in PHP | ||
* Apache mod_rewrite support for .htaccess files (optional but highly recommended) | ||
* Linux server (ideally, but may also work on Windows). | ||
|
||
Zenario sites will work with all modern, standards-compliant web browsers, however this is | ||
dependent on how a designer writes CSS and frameworks for the site. If compatibility with | ||
yet older browsers is required, this should be possible with careful design. | ||
|
||
|
||
In administration mode, Zenario will run on at least the following browsers: | ||
|
||
* Windows with Chrome (stable channel) or equivalent | ||
* Windows with Firefox (release channel) | ||
* Windows with Microsoft Edge (latest version) | ||
* Mac OSX with Chrome (stable channel) or equivalent | ||
* Mac OSX with Firefox (release update channel) | ||
* Mac OSX with Safari (latest version) | ||
|
||
We test on all of the above platforms. Administration mode may be usable on other | ||
operating systems and browsers, but this is not tested. | ||
|
||
|
||
Place the files on your server | ||
------------------------------ | ||
|
||
You should download the `.zip` file, unzip it on your local machine, and then use a FTP | ||
program to upload the files to your server. | ||
|
||
Alternatively, if you have ssh access it's faster to download the `.tar.gz` file, | ||
upload it to your server and then unpack it by running: | ||
|
||
tar xfz zenario-probusiness-9.0.54149.tar.gz | ||
|
||
|
||
If you want to run Zenario in the root of a domain (e.g. http://example.com/), you | ||
should place the files into your server's web directory (sometimes called the public HTML | ||
directory or the document root) . | ||
|
||
If you want to run Zenario from a subdirectory (e.g. http://example.com/cms/), you should | ||
create a subdirectory with the correct name inside your server's web directory and place | ||
the files in there. | ||
|
||
|
||
Create directories and set permissions | ||
-------------------------------------- | ||
|
||
You will need to create two directories: | ||
|
||
* A backup/ directory | ||
* A docstore/ directory | ||
|
||
These should not be publicly accessible, so you should create them outside of your web | ||
directory. Zenario will need to write files and folders to these directories, so you need | ||
to make them writable, e.g. on a UNIX/Linux server: | ||
|
||
chmod 777 backup/ | ||
chmod 777 docstore/ | ||
|
||
|
||
There are three directories in the CMS that you need to make writable: | ||
|
||
* The cache/ directory | ||
* The private/ directory | ||
* The public/ directory | ||
|
||
E.g. on a UNIX/Linux server: | ||
|
||
chmod 777 cache/ | ||
chmod 777 private/ | ||
chmod 777 public/ | ||
|
||
|
||
You can optionally make the `zenario_siteconfig.php` file writable for a smoother install | ||
process. | ||
|
||
|
||
Run the installer | ||
----------------- | ||
|
||
To run the installer you need to visit your site using a browser - e.g. by going to | ||
http://example.com, or http://example.com/cms/ if you are running from a subdirectory. | ||
|
||
The installer will then take you through the installation process, during which you will | ||
need to enter: | ||
|
||
* A name, username and password to connect to a database | ||
* A name and an email address to create your first administrator account. | ||
* An initial language for your site (you can add more languages later). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -25,5 +25,5 @@ | |
"vimeo-upload": "*", | ||
"wowjs": "*" | ||
}, | ||
"version": "9.0.54156" | ||
"version": "9.0.55141" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.