Posted by sun on March 31, 2009 at 8:02am
Jump to:
| Project: | Whizzywig - A complete WYSIWYG Editor |
| Version: | 6.x-1.x-dev |
| Component: | Documentation |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Now that Wysiwyg API supports Whizzywig, I wonder whether we can put a notice on the project page like for TinyMCE and NicEdit:
<dl class="messages error">
<dd>This module has been replaced by <a href="http://drupal.org/project/wysiwyg">Wysiwyg API</a>, which (also) integrates the NicEdit editor with your Drupal site and provides the same functionality. Users should install or migrate to Wysiwyg API instead.</dd>
</dl>Or is something missing in Wysiwyg API's implementation?
Regarding IMCE integration, IMCE Wysiwyg API bridge would have to be enhanced for Whizzywig support.
Just let me know. Let's get the ball rolling. :)
Comments
#1
Hi,
I've added the message to the project page.
I'll see if I can help adding the IMCE integration, and perhaps other features that came with Whizzywig module and might not (yet) be in WYSIWYG API (if any).
Sven
#2
Thank you, Sven!
#3
Automatically closed -- issue fixed for 2 weeks with no activity.
#4
This seems to have regressed. Is there any reason for this?
#5
I have no idea why that happened.
drupal-id.com is also the maintainer of http://drupal.org/project/openwysiwyg (equally supported by Wysiwyg module already), and, he also seems to commit to http://drupal.org/project/tinymce (which is more than abandoned).
The project got transferred due to this d.o webmasters issue: http://drupal.org/node/583428
That's a really, really unfortunate duplication of efforts. The Wysiwyg project badly needs more contributors and welcomes everyone who wants to help.
#6
I'd also like to know what's going on here.
#7
Additional details are in #583428: Change project ownership of whizzywig module now, but I'd still like to hear from drupal-id about what's going on.
#8
Should we also file an issue since the drupal-id user seems to be a 'company' and not an actual user. I think we have a policy of such user accounts having CVS accounts.
#9
This is the message shown when a user creates an account.
I would suggest to keep the issues separated, though. Differently it will seem we are trying to block him just because he didn't do things as we hoped.
So far, I have not seen any accounts being blocked with such motivation (or they didn't open a report in the Drupal.org webmasters queue, but I doubt it). I think it would also difficult to demonstrate it is really used from more than one user; even if it would be possible, then the same operation should be done for other accounts as well (differently, it would seem it is just an excuse to block this account only to avoid somebody would keep to develop a module that was supposed to be abandoned, but then its ownership has never been passed to the user ).
In this case I imagine he will say it has been the previous maintainer to pass him the ownership, and the previous maintainer will say he advised him that the project was abandoned, but he insisted.
#10
Note that I'm perfectly fine if drupal-id says that he cannot or does not want to join forces. The only thing I'd like to ask for is a (visible) note on the project page that points to the Wysiwyg module, so users don't get confused of whether they have to install this module to make the Whizzywig editor work with Wysiwyg module. That confusion sadly happens way too often, and people only really understood it when there was the big red note on the project page.
#11
That's fine, and it is perfectly legitimate from you asking for that.
I would have preferred the previous maintainer didn't first accept to mark the project as abandoned, and then passed its ownership to somebody else.
#12
I have add:
@sun:
We must use your Wysiwyg module instead our own? I found easier to maintenance stand alone module rather than catch them all in one module (conflict between modules and libs will generate new issues as shown - Bug reports xx open, yy total in your Wysiwyg module). So, lets' people choose their own modules.
#13
#14
Automatically closed -- issue fixed for 2 weeks with no activity.