[CWB] CQPweb version 3.3.0

[Hardie, Andrew]

Hi everyone,

The big CQPweb changeover to version 3.3 is now "complete".

By putting "complete" in quotes I mean that all the new and revised features and architectural changes are finished - but it's anticipated that there are still lots of bugs that I've failed to spot. Also, the documentation has not yet been fully updated, though parts have (below is the current version of the new manual section discussing the upgrade, itself not wholly complete).

If you are an adventurous sort who does not mind working with the bugs (or, even better, reporting them here or on sourceforge.net) then you can now switch over from the 3.2 branch to the trunk.

Most users should probably stick to v3.2.42 for a while yet though, till v3.3.1 or v3.3.2 ...

Note that this new version requires:

  *   PHP 7.3+
  *   CWB 3.4.21 (i.e. the very latest and greatest)

Over the next two to three weeks I intend to (a) upgrade the Lancaster server in the hope that having a big live server using v3.3 will shake out bugs as quickly as possible; (b) fix all now-obsolete passages in the manual. Later goals include (c) updating the now out-of-date YouTube tutorials, (d) get a CQPwebInABox virtual machine image ready and released.

Thank you all for bearing with me.

best

Andrew.



================================

15.11 Updating to version 3.3.0

Various major changes were made in the move from 3.2 to 3.3.

Extra code files (CSS and JavaScript): these were previously to be placed in the css and jsc folders within the main CQPweb directory. From v3.3.0 onwards, they should instead be placed in the extra subdirectories (that is: css/extra and jsc/extra). See 10.4.6<node93.html#sec:visualise:xml:extra-code>

Plugins: PHP files for plugins are no longer directly contained in lib/plugins. Instead, that folder contains a folder tree called builtin, which has one folder per type of plugin; e.g. lib/plugins/builtin/CorpusInstaller.

Plugins do still need to be in lib/plugins to be used; the principle is that you should create a symlink to just those builtin plugins that you wish to use, as follows:

cqpweb/lib/plugins > ln -s builtin/CorpusInstaller/BasicVrtInstaller.php

This system was added because, as the number of builtin plugins increased, the plugins folder became harder to manage.

A local folder, with the same subdirectories as builtin, is provided for convenience; it is for you to place your own plugins into. However, you can symlink (or copy) your plugins from anywhere. You do not have to use lib/plugins/local.

See 12<node104.html#sec:plugins>.

The database upgrade procedure for 3.3.0 involves major architectural changes. It may take a long time to run. So, it is recommended to run the process with your CQPweb server offline (see 2.3.10<node20.html#sec:config-file:variables-optional:misc> on the $cqpweb_switched_off setting).

Because this is a major upgrade, it is possible to generate the SQL commands that will run during upgrade without running them, by adding the --rehearse flag to the call to the upgrade-database script. A second flag, --stepwise, allows you to run the upgrade a chunk at a time (you must keep running the script repeatedly until all chunks are complete). Note that --rehearse implies --stepwise, i.e. you can't rehearse the second phase until you have run the first stage for real (and so on).


================================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://liste.sslmit.unibo.it/pipermail/cwb/attachments/20200312/88adfec3/attachment-0001.html>