We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

← Previous Ticket
Next Ticket →

Opened 15 years ago

Closed 15 years ago

#3721 closed Task (fixed)

CKeditor: Add a parseable version string

Reported by:	Daniel F. Kudwien	Owned by:
Priority:	Normal	Milestone:
Component:	General	Version:	3.0 Beta 2
Keywords:		Cc:

Description

We are trying to add CKeditor support to Drupal's Wysiwyg API in http://drupal.org/node/462146

Wysiwyg API needs to identify the (exact) version of the library though.

Currently, the only version string seems to be located in CHANGES.html, but that is HTML and the version cannot be really parsed easily.

Ideal would be a simple JSDoc directive at the top of ckeditor.js:

/**
 * @version 3.0-beta2
 */

However, any other way would probably work as well. We just need something reliable, ideally located at the top of a file.

Change History (1)

comment:1 Changed 15 years ago by Daniel F. Kudwien

Resolution:	→ fixed
Status:	new → closed

Current nightly build contains a version string in ckeditor.js.

Also contains much more, and a lot less bugs. How about a new beta release?

Note: See TracTickets for help on using tickets.

Download in other formats: