Once again, I'm looking for import / export functionality, but I don't see anything about it in the documentation.

There's a nifty magic URL to download the latest version of a GitHub release asset:

https://github.com/user/repo/releases/latest/download/asset-name.zip

However, the asset-name.zip for toolset-cli includes the version number in it:

toolset-cli-refs.tags.1.1.zip

The unfortunate consequence of this is that one must know the version number to take advantage of the magic URL.

Could the version number be removed? The end result would be something like this:

https://github.com/OnTheGoSystems/toolset-cli/releases/latest/download/toolset-cli.zip

If removal isn't an option, I certainly understand why it would be desirable to keep the version number in the filename. (Another option might be to create two assets, one with the version number and one without it. But this redundancy seems a bit much.)

I have a couple custom post types (chapter and member) and a one-to-many relationship defined for those types. From the Web UI I can go to a "chapter" and see the list of "members" associated with it via that relationship. I would really love a way to do that same thing from toolset-cli, so I can grab a list of all of the members associated with a chapter and then can script doing operations on them. Does such a thing exist already in here and I haven't figured it out via the documentation, or would this be new code?

Thanks for any assistance!

Use this in case we need to implement a more complex command.

https://symfony.com/doc/current/components/options_resolver.html

The web interface can import and export XML (*.xml) and zipped XML (*.zip) files. Currently, the CLI interface only supports XML.

I've been in touch with @decodekult about adding import and export commands for Layouts. Via email he mentioned, "Layouts is probably more complex, as there is no initial CLI implementation for it, and it is considered a legacy plugin just in maintenance." With some guidance from Toolset staff, I'd like to add support for these commands, and this issue can be assigned to me.

Is there any scope to support caching google map coordinates?

The plugin cannot be built against the latest version of Composer, 2.x. It only builds against 1.x.

When I have a couple minutes, I'll try to provide more details about the error I encountered when I attempted to build the plugin against 2.x.

@zaantar Layout import and export commands aren't working. The culprit seems to be that my patch for layouts/inc/theme/wpddl.theme-support.class.php wasn't implemented, nor was my slight alteration to layouts/classes-auto/wpddl-options.class.php.

Do you know when these changes can be incorporated into the Layouts plugin? I've just written a great shell script to export types, views, and layouts, copy them to a remote server via scp, and then import them—but it doesn't handle the layouts! :-)

The plugin needs to be built with composer install, the result should be a ZIP package that is ready to be downloaded and directly used as a WordPress plugin.

Hey @zaantar, I forgot to mention this sooner: the first time I tried to build the plugin, it didn't work. The reason it failed was that I was using the latest version of composer, 2.x, and the plugin needs to be built with the older 1.x version. The README.md file, however, doesn't mention a version. Should I submit a PR with an update to README.md that explicitly states the version number?

It would be nice to be able to update the plugin automatically via the WP dashboard when a new version is released, as many other plugins can be (including the Toolset suite).

• Set up PHPUnit (without the usual OTGS dependencies)
• Begin covering the newer classes.

I tried to download the latest version of the plugin's ZIP file from the releases page, and when I attempted to activate the plugin, a PHP fatal error occurred.

I think it's an issue with composer. It's trying to automatically load dependencies from a subfolder named vendor, which only gets created when composer dependencies are installed. I thought the new action @zaantar created obviated the need for composer. Is that understanding correct?

Or, put another way, will it ever be possible to just install the plugin without having to issue composer commands? What brought all of this on was an attempt to install the plugin via the command line like so:

$ wp plugin install https://github.co
m/OnTheGoSystems/toolset-cli/archive/refs/tags/1.1.zip --activate

The initial implementation of the layouts import command only supports .zip files. To peer with the web interface, it should also support .ddl, .json, and .css files.

This task can be assigned to me.