05-Oct-2015

Updated WordPress
Tonight I updated both blogs to WordPress 4.3.1, and consequently Aksimet to the latest version (3.1.3 comes with WordPress 4.3.1 but a new version has been released as well).
No problems whatsoever.
Next, I installed Jetpack – latest version as well – but this cannot be activated: it runs into an error:
Fatal error: Cannot find a library with slug admin-pages/class.jetpack-landing-page. in /sysblog/wp-content/plugins/jetpack/require-lib.php on line 35
The reason is that this plugin seems to require a directorypath [.INC.LIB]. That is: this does exists in the root of this plugin, and accessing it deeper into the structure, the required file does exist:
$ set def wp431:[wp-content.plugins]
$ dir

Directory WP431:[WP-CONTENT.PLUGINS]

AKISMET.DIR;1       hello.php;1         index.php;1         JETPACK.DIR;1

Total of 4 files.
$ set def [.jetpack]
$ dir .dir

Directory WP431:[WP-CONTENT.PLUGINS.JETPACK]

^.INC.DIR;1         3RD-PARTY.DIR;1     CSS.DIR;1           IMAGES.DIR;1
JSON-ENDPOINTS.DIR;1                    LANGUAGES.DIR;1     MODULES.DIR;1
SCSS.DIR;1          VIEWS.DIR;1

Total of 9 files.
$ dir [.^.INC]

Directory WP431:[WP-CONTENT.PLUGINS.JETPACK.^.INC]

FONTS.DIR;1         footer.php;1        gallery-settings.js;1
GENERICONS.DIR;1    genericons.php;1    header.php;1        IMAGES.DIR;1
IMG.DIR;1           jetpack-admin.js;1  JETPACK-ICONS.DIR;1 jetpack-jitm.js;1
jetpack-modules.js;1                    jetpack-modules^.models.js;1
jetpack-modules^.views.js;1             jetpack.js;1        jp-my-jetpack.js;1
jp.js;1             jquery^.inview.js;1 jquery^.jetpack-resize.js;1
jquery^.jetpack-sync.js;1               jquery^.spin.js;1   LIB.DIR;1
postmessage.js;1    SCSS.DIR;1          spin.js;1

Total of 25 files.
$ dir [.^.INC.lib]

Directory WP431:[WP-CONTENT.PLUGINS.JETPACK.^.INC.LIB]

ADMIN-PAGES.DIR;1   class^.color.php;1  MARKDOWN.DIR;1      tonesque.php;1

Total of 4 files.

but for some reason, this file is not reachable. It’s not a matter of protection since all directories are W:RE and files W:R so that should not be a problem..
There must be something within the plugin code that needs to be adapted before this can be used on VMS. The code where the error is generated uses a variable lib_dir , set to WP_CONTENT_DIR and additions:


if ( defined( 'ABSPATH' ) && ! defined( 'WP_CONTENT_DIR' ) ) {
define( 'WP_CONTENT_DIR', ABSPATH . 'wp-content' ); // no trailing slash, full paths only - WP_CONTENT_URL is defined further down
}

$lib_dir = WP_CONTENT_DIR . '/lib';

and somewhat further down:

$lib_dir = apply_filters( 'jetpack_require_lib_dir', $lib_dir );
$choices = array(
"$lib_dir/$slug.php",
"$lib_dir/$slug/0-load.php",
"$lib_dir/$slug/$basename.php",
);

so probably there is something wrong here that needs to be addressed. to have it working on VMS.
For the time being, I can live without this plugin but it would be nice to have it working as well.