feature request #3385
openinstall enable and configure WYSIWYG editors be default
0%
Description
install enable and configure WYSIWYG editors by default
- put into installation profile
- existing portals should be updated => update function ?
steps required:
- enable the wysiwyg modules (see #5913)
- automatically install TinyMCE > 3.5.11
- "import" default profile, here we seem to have these options:
a.
via the ctools exportable feature, see also https://www.drupal.org/node/624018now see c. b. export/import directly from the database, see https://www.drupal.org/node/701608#comment-3740206 c. via the Features module
Files
Updated by Andreas Kohlbecker almost 8 years ago
- Target version changed from cdm_dataportal - Next Major Release to Release 4.3
- Priority changed from New to Priority14
Updated by Andreas Kohlbecker almost 8 years ago
Using the ctools exportable feature seems to be rather complicated.
Directly operatinng on the database in contrast is quire straight forward:
- export (e.g.):
drush -l http://portal.cybertaxonomy.org/flora-cuba/ sql-dump --tables-list=flora_cuba_wysiwyg
copy the
INSERT
statement from the outputapply the insert on the target db:
3.a. in case of the installation profile :
{TABLE_PREFIX}wysiwyg
3.b. to update existing databases:
{TABLE_PREFIX}wysiwyg
Updated by Andreas Müller over 7 years ago
- Target version changed from Release 4.3 to Release 4.4
Updated by Andreas Müller over 7 years ago
- Target version changed from Release 4.4 to Release 4.5
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.5 to Release 4.6
Updated by Andreas Müller about 7 years ago
- Target version changed from Release 4.6 to Release 4.7
Updated by Andreas Müller almost 7 years ago
- Target version changed from Release 4.7 to Release 4.8
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.8 to Release 4.9
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.9 to Release 4.10
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.10 to Release 4.12
Updated by Andreas Müller over 6 years ago
- Target version changed from Release 4.12 to Release 4.13
Updated by Andreas Müller about 6 years ago
- Target version changed from Release 4.13 to Release 4.14
Updated by Andreas Müller about 6 years ago
- Target version changed from Release 4.14 to Release 5.0
Updated by Andreas Kohlbecker almost 6 years ago
- Target version changed from Release 5.0 to Release 5.1
Updated by Andreas Müller over 5 years ago
- Target version changed from Release 5.1 to Release 5.2
Updated by Andreas Kohlbecker over 5 years ago
- Target version changed from Release 5.2 to Release 5.3
Updated by Andreas Kohlbecker over 5 years ago
- Target version changed from Release 5.3 to Release 5.4
Updated by Andreas Kohlbecker over 5 years ago
- Target version changed from Release 5.4 to Release 5.5
Updated by Andreas Kohlbecker about 5 years ago
- Target version changed from Release 5.5 to Release 5.6
Updated by Andreas Kohlbecker about 5 years ago
- Description updated (diff)
- Priority changed from Priority14 to Priority11
- Target version changed from Release 5.6 to Reviewed Next Major Release
Updated by Andreas Kohlbecker almost 4 years ago
- Description updated (diff)
The Features apparently has all the functionality needed: "Features focus on the complementary use case of sharing configuration among multiple sites."
Export module dependencies and configuration setting as feature, which can be installed as any other module
Basic introduction: https://www.drupal.org/node/580026
Using features with drush is explained here: https://www.drupal.org/docs/7/contrib/features/features-drush
With drush downloading and enabling a feature should work like this:
drush pm-download <feature-url> drush enable <feature-name>
Updated by Andreas Kohlbecker almost 4 years ago
attaching a test feature which has been created from http://edit.test/d7/phycobank/admin/structure/features/create