Project

General

Profile

feature request #3385

install enable and configure WYSIWYG editors be default

Added by Andreas Kohlbecker over 7 years ago. Updated about 2 months ago.

Status:
New
Priority:
Priority11
Category:
cdm-dataportal
Start date:
04/09/2013
Due date:
% Done:

0%

Severity:
normal

Description

install enable and configure WYSIWYG editors by default

  • put into installation profile
  • existing portals should be updated => update function ?

steps required:

  1. enable the wysiwyg modules (see #5913)
  2. automatically install TinyMCE > 3.5.11
  3. "import" default profile, here we seem to have these options: a. via the ctools exportable feature, see also https://www.drupal.org/node/624018 now see c. b. export/import directly from the database, see https://www.drupal.org/node/701608#comment-3740206 c. via the Features module

wysiwyg_editing-7.x-1.0-beta1.tar (9.5 KB) Andreas Kohlbecker, 06/18/2020 01:30 PM

History

#1 Updated by Andreas Kohlbecker about 4 years ago

  • Target version changed from cdm_dataportal - Next Major Release to Release 4.3
  • Priority changed from New to Priority14

#2 Updated by Andreas Kohlbecker about 4 years ago

Using the ctools exportable feature seems to be rather complicated.

Directly operatinng on the database in contrast is quire straight forward:

  1. export (e.g.):
drush -l http://portal.cybertaxonomy.org/flora-cuba/ sql-dump --tables-list=flora_cuba_wysiwyg
  1. copy the INSERT statement from the output

  2. apply 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

#3 Updated by Andreas Müller almost 4 years ago

  • Target version changed from Release 4.3 to Release 4.4

#4 Updated by Andreas Müller over 3 years ago

  • Target version changed from Release 4.4 to Release 4.5

#5 Updated by Andreas Müller over 3 years ago

  • Target version changed from Release 4.5 to Release 4.6

#6 Updated by Andreas Müller over 3 years ago

  • Target version changed from Release 4.6 to Release 4.7

#7 Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 4.7 to Release 4.8

#8 Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 4.8 to Release 4.9

#9 Updated by Andreas Müller about 3 years ago

  • Target version changed from Release 4.9 to Release 4.10

#10 Updated by Andreas Müller almost 3 years ago

  • Target version changed from Release 4.10 to Release 4.12

#11 Updated by Andreas Müller over 2 years ago

  • Target version changed from Release 4.12 to Release 4.13

#12 Updated by Andreas Müller over 2 years ago

  • Target version changed from Release 4.13 to Release 4.14

#13 Updated by Andreas Müller over 2 years ago

  • Target version changed from Release 4.14 to Release 5.0

#14 Updated by Andreas Kohlbecker about 2 years ago

  • Target version changed from Release 5.0 to Release 5.1

#15 Updated by Andreas Müller about 2 years ago

  • Target version changed from Release 5.1 to Release 5.2

#16 Updated by Andreas Kohlbecker almost 2 years ago

  • Target version changed from Release 5.2 to Release 5.3

#17 Updated by Andreas Kohlbecker almost 2 years ago

  • Target version changed from Release 5.3 to Release 5.4

#18 Updated by Andreas Kohlbecker almost 2 years ago

  • Target version changed from Release 5.4 to Release 5.5

#19 Updated by Andreas Kohlbecker over 1 year ago

  • Target version changed from Release 5.5 to Release 5.6

#20 Updated by Andreas Kohlbecker over 1 year ago

  • Description updated (diff)
  • Priority changed from Priority14 to Priority11
  • Target version changed from Release 5.6 to Reviewed Next Major Release

#21 Updated by Andreas Kohlbecker over 1 year ago

  • Private changed from Yes to No

#22 Updated by Andreas Kohlbecker about 2 months 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>

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 40 MB)