symphonycms/export_ensemble

Export Ensemble for Symphony CMS

Symphony CMS

• Version: 3.0.0
• Date: 27th March 2020
• Release notes
• Changelog
• Github repository
• MIT Licence

Contents

• Overview
• Server requirements
• Responsible Security Disclosure

Quick links

• Installing
• Updating from LTS
• Contributing
• Documentation TOC

Overview

Symphony is a PHP & MySQL based CMS that utilises XML and XSLT as its core technologies. This repository represents version 3.0.0 and is considered stable.

Useful places:

• The Symphony website
• The Symphony forum
• Symphony Extensions
• DEV chat room
• HELP chat room

Server requirements

• PHP 5.6 or 7.0-7.3
• PHP’s LibXML module, with the XSLT extension enabled (--with-xsl)
• MySQL 5.7 or above is recommended
• A webserver (known to be used with Apache, Litespeed, Nginx and Hiawatha)
• Apache’s mod_rewrite module or equivalent
• PHP’s built in json functions, which are enabled by default in PHP 5.2 and above; if they are missing, ensure PHP wasn’t compiled with --disable-json
• PHP’s zlib module
• PHP’s pdo_mysql module

Responsible Security Disclosure

Please follow the guideline for security bug disclosure.

export_ensemble's Issues

Save Install files not overwriting install.sql when exporting .Zip

Minor issue on 2.3.3 when saving install files all is well, but when exporting a zip of the complete ensemble, there is a duplicate install.sql file saved in the workspace folder.

Is it supposed to overwrite the install.sql here?

Current Master-Release (2.1.2) not compatible with Symphony 2.6.X

The current master release 2.1.2 (that is officially bundled with Symphony) does not include/support the vendor-folder that has been introduced in Symphony 2.6.0.

The integration branch of this extension includes a** PR** that fixes this problem, but hasn't found its way to an official release - so Symphony (Bundle) 2.6.0 up to 2.6.4 are shipping an incompatible version of this extension.

Would be awesome if this could be fixed for the upcoming Symphony 2.6.5 is release.

Maybe a version 2.1.3 that is marked as only compatible up to Symphony 2.5.X and another (2.2.0 ?) release that is marked as compatible with 2.6.X and upwards would be a good solution?

@brendo @nitriques - could you have a look? Thanks alot!

Export ensemble auto enabling extensions

I noticed latest Export Ensemble runs the enable/install functions for extensions drivers. Is this the default and intended behavior?

From my part this is undesired because the order of extension enabling matters (I posted a few issues regarding this topic) and I would like to enable them myself, as needed.

I'm asking because I didn't notice this behavior in pre Symphony 2.3 versions.

Not to mention I want some extensions to be disabled, other uninstalled, for various reasons.

Return key in System > Preferences executes export

Because this extension adds two button elements without type attributes, the browser treats them as submit buttons. This means that hitting the return key (think you will submit the preferences page form) will actually trigger the first Export Ensemble button instead. Giving the buttons an explicit type attribute (of button) will prevent this. But will require JavaScript event handlers to replace the existing functionality (to submit the form with the appropriate action[...]).

db connection error on sym 2.4

symphony version: 2.4
export ensemble version: 2.0.3

i get this error when i'm trying to export ensemble

Export doesn't include email settings

When exporting an ensemble the email-settings from the configuration aren't included. Would be cool if this could be changed.

Further the latest version of this extension (2.2.1) is marked as incompatible with Symphony 2.7.x:

<release version="2.2.1" date="2016-10-06" min="2.6.0" max="2.6.x">

As this is a core extension it could need an update I guess…

Fatal error when installing from ensemble

I just tried to install from ensemble and I get this error.

It goes like this: Export ensemble tries to enable Page LHandles:

Extension_page_lhandles->enable( )

This extension tries to get a list of existing datasources:

DatasourceManager::listAll( )

In this method from DatasourceManager, on line 123 it dies trying to get an instance of ExtensionManager:

$extensions = Symphony::ExtensionManager()->listInstalledHandles();

Any thoughts?