generation hangs at wp-config.php with no method match

[mastef]

when generating wordpress:app it gets to the wp-config.php it hangs with no method .match available for ( already replaced ) wp-config.php content

( on windows )

c:\dev\wp\node_modules\generator-wordpress\util\wordpress.js:81
                db.name   = contents.match(/define\(["']DB_NAME["'],[\s]*["'](.*)["']\)/)[1]
                                     ^
TypeError: Object <?php
/**
 * The base configurations of the WordPress.
 *
 * This file has the following configurations: MySQL settings, Table Prefix,
 * Secret Keys, WordPress Language, and ABSPATH. You can find more information
 * by visiting {@link http://codex.wordpress.org/Editing_wp-config.php Editing
 * wp-config.php} Codex page. You can get the MySQL settings from your web host.

 *
 * This file is used by the wp-config.php creation script during the
 * installation. You don't have to use the web site, you can just copy this file

 * to "wp-config.php" and fill in the values.
 *
 * @package WordPress
 */

// ** MySQL settings - You can get this info from your web host ** //
/** The name of the database for WordPress */
define('DB_NAME', 'wp');

/** MySQL database username */
define('DB_USER', 'test');

/** MySQL database password */
define('DB_PASSWORD', 'testie');

/** MySQL hostname */
define('DB_HOST', 'localhost');

/** Database Charset to use in creating database tables. */
define('DB_CHARSET', 'utf8');

/** The Database Collate type. Don't change this if in doubt. */
define('DB_COLLATE', '');

/**#@+
 * Authentication Unique Keys and Salts.
 *
 * Change these to different unique phrases!
 * You can generate these using the {@link https://api.wordpress.org/secret-key/
1.1/salt/ WordPress.org secret-key service}
 * You can change these at any point in time to invalidate all existing cookies.
 This will force all users to have to log in again.
 *
 * @since 2.6.0
 */
define('AUTH_KEY',         'a');
define('SECURE_AUTH_KEY',  'b');
define('LOGGED_IN_KEY',    'c');
define('NONCE_KEY',        'd');
define('AUTH_SALT',        'e');
define('SECURE_AUTH_SALT', 'f');
define('LOGGED_IN_SALT',   'g');
define('NONCE_SALT',       'h');

/**#@-*/

/**
 * WordPress Database Table prefix.
 *
 * You can have multiple installations in one database if you give each a unique

 * prefix. Only numbers, letters, and underscores please!
 */
$table_prefix  = 'test_';

/**
 * WordPress Localized Language, defaults to English.
 *
 * Change this to localize WordPress. A corresponding MO file for the chosen
 * language must be installed to wp-content/languages. For example, install
 * de_DE.mo to wp-content/languages and set WPLANG to 'de_DE' to enable German
 * language support.
 */
define('WPLANG', '');

/**
 * Set custom paths
 *
 * These are required because wordpress is installed in a subdirectory.
 */
define('WP_SITEURL', 'http://' . $_SERVER['SERVER_NAME'] . '/cms');
define('WP_HOME',    'http://' . $_SERVER['SERVER_NAME'] . '');
define('WP_CONTENT_DIR', __dir__ . '/content');
define('WP_CONTENT_URL', 'http://' . $_SERVER['SERVER_NAME'] . '/content');

/**
 * Disable external requests
 *
 * This is so that users dont see update requests since things are managed throu
gh git
 */
define('WP_HTTP_BLOCK_EXTERNAL', true);

/**
 * For developers: WordPress debugging mode.
 *
 * Change this to true to enable the display of notices during development.
 * It is strongly recommended that plugin and theme developers use WP_DEBUG
 * in their development environments.
 */
define('WP_DEBUG', false);

/* That's all, stop editing! Happy blogging. */

/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
        define('ABSPATH', dirname(__FILE__) . '/');

/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');
 has no method 'match'
    at EventEmitter.<anonymous> (c:\dev\wp\node_modules\generator-wordpr
ess\util\wordpress.js:81:24)
    at EventEmitter.emit (events.js:96:17)
    at c:\dev\wp\node_modules\generator-wordpress\util\wordpress.js:55:7

    at fs.readFile (fs.js:176:14)
    at Object.oncomplete (fs.js:297:15)

c:\dev\wp>

[wesleytodd]

Looks like the same as issue #12. Which version of node are you running?

[mastef]

v0.8.22

[mastef]

Yes, seems to be exactly same issue. Apologies as I haven't been able to find it before.

I have upgraded to node.js v0.10+ and that part passes through now :)

[wesleytodd]

Glad it is working for you! Let me know if you have any other issues or suggestions!