Wysiwyg API allows to use client-side editors (a.k.a. WYSIWYG editors) for
editing content in the Drupal CMS. It simplifies installation of editors
and allows you to define which editor to use depending on the input format.
This module replaces all existing editor integration modules and no other
Drupal module is required.
It is capable of supporting any kind of client-side editor as long as there
are support files for it that integrate the external library with Wysiwyg
API. A client-side editor can be a regular HTML-based editor, a
"pseudo-editor" (that just provides buttons to insert HTML markup into a
plain textarea), or even a Flash-based editor. Support for various editor
libraries is built-in.
The Wysiwyg API also allows Drupal modules to register plugins (or
"buttons") for editors.
WWW: http://drupal.org/project/wysiwyg
===> The following configuration options are available for drupal6-wysiwyg-6.x.2.0_1:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Remove expired ports:
2016-04-24 www/drupal6-content_access: www/drupal6 upstream is EOL and port
expired 2016-04-24
2016-04-24 www/drupal6-google_analytics: www/drupal6 upstream is EOL and port
expired 2016-04-24
2016-04-24 www/drupal6-seo_checklist: www/drupal6 upstream is EOL and port
expired 2016-04-24
2016-04-24 www/drupal6-pathauto: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-wysiwyg: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-advanced_help: www/drupal6 upstream is EOL and port
expired 2016-04-24
2016-04-24 www/drupal6-path_redirect: www/drupal6 upstream is EOL and port
expired 2016-04-24
2016-04-24 www/drupal6-webform: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-imce: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-mimedetect: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-tagadelic: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-panels: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-zeropoint: www/drupal6 upstream is EOL and port expired
2016-04-24
2016-04-24 www/drupal6-geshifilter: www/drupal6 upstream is EOL and port expired
2016-04-24
(Only the first 15 lines of the commit message are shown above )
www/drupal6-*: deprecate all drupal6-modules. Also set expiration date
to 2016-04-24 to stay in sync with www/drupal6.
PR: 209954
Submitted by: Yonas Yanfa <yonas@fizk.net>
Approved by: junovitch (mentor)
Remove OPTIONS_DEFINE out of Mk/Uses/drupal.mk (affects many drupal ports)
The USES= fragments are not supposed to modify OPTIONS_* because they are
loaded after bsd.options.mk.
In the particular case of drupal, this resulted in SELECTED_OPTIONS and
DESELECTED_OPTIONS being incorrect. A second problem was that the "="
was used for assignment rather than "?=", meaning that any port with
USES=drupal got their options overwritten at some point (this included
the main www/drupal6 and www/drupal7 ports).
This commit adds OPTIONS_DEFINE=DOCS to almost every port that had set
USES=drupal to correct the mistake of setting options in Mk/Uses.
PR: 206060
Reassign several ports maintained by Nick Hilliard. Thank you very much for
all your work on these.
All to ports@FreeBSD.org, except p5-Rcs-Agent to perl@ (almost certainly won't
see any updates), and give drupal[67] to flo@.
While here, update to OPTIONSng.
PR: ports/174741
Begin process of removal of drupal5 ports:
- Stop using the bsd.drupal.mk in drupal5/ and use the Mk/ version
- Deprecate the drupal5 ports for removal on 29/Aug
Submitted by: Nick Hilliard <nick@foobar.org> (maintainer)
Wysiwyg API allows to use client-side editors (a.k.a. WYSIWYG editors) for
editing content in the Drupal CMS. It simplifies installation of editors
and allows you to define which editor to use depending on the input format.
This module replaces all existing editor integration modules and no other
Drupal module is required.
It is capable of supporting any kind of client-side editor as long as there
are support files for it that integrate the external library with Wysiwyg
API. A client-side editor can be a regular HTML-based editor, a
"pseudo-editor" (that just provides buttons to insert HTML markup into a
plain textarea), or even a Flash-based editor. Support for various editor
libraries is built-in.
The Wysiwyg API also allows Drupal modules to register plugins (or
"buttons") for editors.
WWW: http://drupal.org/project/wysiwyg
PR: ports/135230
Submitted by: Nick Hilliard <nick at foobar.org>
