When running oik-tip against a theme in a sub-directory install where oik-batch is not available we get a Fatal error.

Fatal error: require_once(): Failed opening required 
'C:\apache\htdocs\hallsgs/wp-content/plugins/oik-batch/oik-login.inc' 
(include_path='.;C:\php\pear') in
C:\apache\htdocs\wordpress\wp-content\plugins\oik-bwtrace\libs\oik_boot.php on line 80 

In another instance it was

Fatal error: Uncaught Error: Call to undefined function oik_batch_load_cli_functions() in C:\apache\htdocs\tags\wp-content\plugins\tags\tags.php:48

Workaround

Create a symlink to oik-batch. The plugin doesn't need to be activated.

Update code to run without problems in PHP 8.1 and 8.2

See bobbingwide/bobbingwide#103

When I changed oik-tip so that it was run under oik-wp I didn't test it to package a theme in a WPMS environment.

Running tip rjdap v0.0.6 produces Warning: Cannot modify header information even when passing the --url=qw/rjduk parameter.

It would have been easier to analyse this problem had Windows not updated itself last night.
I would then have been able to report the other problem with docontinue() being redeclared.
Now I'm going to have to reproduce the problems all over again.
That's wasted nearly an hour!

Fatal error: Cannot redeclare docontinue() (previously declared in C:\apache\htdocs\wordpress\wp-content\plugins\oik-batch\libs\oik-cli.php:305) in C:\apache\htdocs\wor
dpress\wp-content\plugins\oik-tip\oik-tip.php on line 56
C:\apache\htdocs\rjduk\wp-content\themes>

During packaging the readme.txt file is transformed to the markdown file README.md.

GitHub has changed the name of the main branch from master to main.
This needs to be reflected in any URLs which contain the main branch name.
For the theme packaging routine this is the screenshot.png file.

See bobbingwide/txt2md#1
which has already been changed for oik-zip.

The oik base plugin supports the use of a custom.css file which is edited using the theme editor. If we deliver a custom.css file as part of a new version of the theme we can override the custom.css file that's in use. Should the user therefore use a differently named file or what.

Temporary solution

While the jury is out, we'll allow the custom.css file to be zipped if it's present in the theme's directory structure.

Permanent solution

Only include the custom.css file if it's committed as part of the Git repo.

Several improvements have been made or are planned for oik-zip. oik-tip should be similar.

• Correct readme
• Run under oik-wp
• Invoke txt2md using PHP ( co-req change to txt2md )
• README.md should include the theme's screenshot