nils-werner / dump_db

A database dumper for Symphony CMS

Dump DB

This extension exports your Symphony database

• Version: 1.12
• Date: 15th October 2014
• Requirements: Symphony 2.4 or above
• Author: Nils Werner, [email protected]
• Constributors: A list of contributors can be found in the commit history
• GitHub Repository: http://github.com/nils-werner/dump_db

Synopsis

This extension will create a downloadable copy of your Symphony CMS database. Please note that it will dump the complete database, not caring about sensitive data whatsoever.

Installation & Updating

Information about installing and updating extensions can be found in the Symphony documentation at http://symphony-cms.com/learn/.

Config

Path lets you define a destination other than /workspace, i.e. outside your publicly accessible directories. Please make sure that destination is writeable by PHP. The path is relative to the constant DOCROOT, it must begin with a slash and must not end with one.

Format lets you define a custom file naming scheme. %1$s is the placeholder for the mode (authors/data). You can use any other PHP function as long as you don't interfere with sprintf's formatting rules (i.e. '%1$s-'.date('Ymd').'.sql' can be used).

The default path is /workspace, the default format is %1$s.sql

For example (this will place the file outside your installation-directory):

	###### DUMP_DB ######
	'dump_db' => array(
		'format' => '%1$s.sql',
		'path' => '/../sql'
	),
	########

These config-parameters enable you to:

• Append a timestamp to your filenames. That way you will be able to go back to older versions of the database.
• Move the file outside your publicly accessible directories.

Any mixture of the options above is possible.

To enable the restore-feature you need to do so manually using the following line in your array:

	'restore' => 'yes'

Database downloads

In some occasions you don't want DumpDB to save your database into the files on your server (i.e. a server that can only pull from your repositories). For these cases you can provide an option like

	'dump' => 'download'

or

	'dump' => 'text'

This will either force your browser to download the dump or display it as text in your browser window without touching the files on your server. An additional help-text will be displayed showing that you're in one of these two modes.

dump_db's Issues

Repo name

The name of this repository is dump-db on GitHub while the extension expects dump_db. (It's about the dashes, in case it isn't obvious.)

Error when attempting a dump with no install directory

I think this is unexpected, but let me know if not.

I'm getting the following error when attempting to save either the authors or the data:

Export Ensemble is not able to create ensembles without a complete install directory. Please refer to the README file for usage instructions.

At first I thought I'd clicked the wrong button, but I'm assuming that this extension must rely on some functionality from the ensemble system - given the error.

But I don't believe this was the case previously… 2.4 thing?

Serious 2.4 and 2.5 issues - extension not functional

I'm hitting a blank white page when attempting to install on a fresh 2.4, nothing in Symphony logs, getting the following in my php log:

[10-Sep-2014 15:44:37] PHP Parse error: syntax error, unexpected T_BOOLEAN_AND in [redacted]/extensions/dump_db/extension.driver.php on line 53

Must be a recent change as I've used the extension a lot with 2.4 already. I'll have a quick look now but am noting the issue in case I don't get anywhere with it.

No assets folder in extension

Hi Nils,

I just noticed that my error log was filled with complaints that the javascript settings file wasn't found; looking at the installed extension there's not even an assets folder. Looking at the repo I can see that there is one there.

Any idea how or why it wouldn't have been there from a standard git install? Does it only populate under certain circumstances? What's it used for?

Cheers,

Nathan

Error on deployment: Symphony Fatal Error: Call to a member function isDeveloper() on a non-object

As mentioned in #13 this error is consistently reproduced when deploying a site to a different location:

Symphony Fatal Error: Call to a member function isDeveloper() on a non-object
An error occurred in [redacted]/extensions/dump_db/extension.driver.php around line 53

I'm assuming something related to moving the files/db - but waiting on confirmation. Either way deploying the site elsewhere after installing the extension in a development environment renders it inoperable - requiring you to turn off the extension manually in the db to regain access to the backend.

Export Ensemble is not able to create ensembles without a complete install directory (??)

Attempting to dump data or authors without an install directory succeeds while displaying the following error message:

Export Ensemble is not able to create ensembles without a complete install directory. Please refer to the README file for usage instructions.

DumpDB v1.10
Symphony v2.3.1

Ability to dismiss message

The message hinting users to import a dump can be annoying if you don't want to import the dump. It should be dismisseable.

Error with `mysql_real_escape_string` on export

Hi,

I get a

Symphony Warning: mysql_real_escape_string(): Access denied for user 'www-data'@'localhost' (using password: NO)

upon clicking either of the two save buttons in the preferences in symphony 2.4 and 2.5. It seems that this line is causing the error and when i remove the mysql_real_escape_string the export works.

Attempting to restore data via preferences results in error

Fatal error: Call to undefined method Administration::saveConfig() in [redacted]/extensions/dump_db/extension.driver.php on line 183

Deploying a site with this extensions results in "Symphony Fatal Error: Call to a member function get() on a non-object"

As mentioned in #13 (along with steps to consistently reproduce) you can't deploy this extension along with a site as-is without receiving the error:

Symphony Fatal Error: Call to a member function get() on a non-object
An error occurred in [site]/extensions/author_roles/extension.driver.php around line 583

This is only an issue when deploying a site that uses this extension. I have a feeling it's due to a change in location/db, but no word from @nils-werner yet.