Adding features support for WYSIWYG config is a major new "feature" (see #624018: Exportables and Features support for WYSIWYG 7.x). Thanks a lot for that! I spent the weekend playing around with a git checkout of WYSIWYG with features support and it just works for me. Given the importance of this feature, I think it warrants a new point release. Could you please cut a new stable release?

Comments

helmo’s picture

+1 for getting the features code in a stable release.

As per #735346: Wysiwyg battle plan Wednesday the 30th of November would be the target date.

skwashd’s picture

@helmo thanks for the link, I didn't know about that. I'm happy to help if there are tasks for the this point release that I can assist with.

sun’s picture

helmo’s picture

It's nice that you want to solve all problems but that might be a bit broad.

Adding a filter for 7.x issues from the categories bug and task: open issues

Liam Morland’s picture

It has been so long since a release that I think there should be a new release ASAP, even if no more issues are fixed; the fixes already in are valuable enough. If the current -dev is better than the current release, it should be made a release candidate.

ressa’s picture

It would be great to get a new release, if for nothing else, just to add features support for WYSIWYG.

AdrianB’s picture

Yes, I second that. The issues in #3 seem to be as many now as half a year ago, and will probably continue to be for a long time. And it's almost a year since last release now.

gagarine’s picture

As their is no major issue, I think a new release will not hurt and will avoid to have to patch this modules so much.

It will also certainly reduce the number of duplicate and frustration.

jim0203’s picture

Adding Features support to WYSIWYG would be massively useful for me, too :)

TwoD’s picture

Some of the issues from #4 aren't really that difficult to do so everyone with Wysiwyg experience are welcome to help out with testing/reviewing/improving. I was going to commit the "editors detach on AJAX form submission" issue - which would fix a very common complaint - a few days ago but I ran into a problem with the D6 port so I could use some help there. (Haven't updated the issue with those details yet).

I'm currently in the process of buying and moving into my first house (yay!), which is why I've been even more disoriented and in lack of coding time than usual. ;)

kolafson’s picture

Agreed, we have been using the dev version of WYSIWYG for quite some time now as we rely on the Features functionality. This feature alone is worth a new release.

sanguis’s picture

I have to agree w/ kolafson, this is one of those things that need to come into the age of features

Bernsch’s picture

I would also want a new release. I think it's time for a recommended release 7.x-2.2

There are so many patches since 7.x.2.1 - that it is very confused...
And it will also certainly reduce the number of duplicate and frustration.

Tom Verhaeghe’s picture

Agreed, please do a new release. It saves a lot of time and frustration. We develop with features so we had to use a dev release in a project.

orendain’s picture

Agreed. Too many patches to include for use with 7.x-2.1

John Pitcairn’s picture

Please please roll a new release. We are not permitted to deploy dev versions for this particular project, yet we desperately need the patch from #1155678: Implement Drupal.behaviors.attachWysiwyg.detach.

btopro’s picture

Agreed, am currently rolling the dev in several distros and require it for a feature to work that contains the text editor (which is odd saying, oh go use the dev for the best piece of functionality ever).

sun’s picture

Status: Active » Postponed (maintainer needs more info)

A range of patches have been committed. :) Some testing would be helpful!

John Bickar’s picture

@sun are you suggesting that if people were to go through the list of 7.x-2.x issues that have been marked "fixed" and test them that this issue could be set to RTBC and we could see a 7.x-2.2 with Features support?

Liam Morland’s picture

@sun could you roll a beta release?

John Pitcairn’s picture

@sun, if the patches have been reviewed and committed (as have the two mentioned in this thread), and there have been no further issues raised against those patches by anyone using the dev version, then what is there to test/review? What is preventing an official release containing already-committed patches?

sun’s picture

I didn't see positive confirmations after manual testing here yet?

Aside from that, there's at least one follow-up clean-up still to do, since we've committed a patch that wasn't 100% clean:
#356480: Lazy-load editors

Liam Morland’s picture

University of Waterloo has been running the development version successfully for almost a year now, most recently the dev version from 2012-07-22. I have put the dev version from 2012-09-17 on our testing server. So far, it is working fine.

gagarine’s picture

Status: Postponed (maintainer needs more info) » Active

@sun don't think is the way to go, if someone has a problem he will open a new issue.

Say that, I run the dev version from various date on all website made the past 6 months (around 8). I add no other problems than the once that was already reported.

Why you don't put an alpha out and write the issue you want to fix for beta on the project? Lot of potential tester have a hard time to manage git/patch.

ParisLiakos’s picture

Title: New Drupal 7.x-2.x Release? » New Wysiwyg 7.x-2.x Release?

For what it matters, i am using the latest dev version for 2 of my latest projects, no issues at all

sun’s picture

Meanwhile, people started to test the most recent dev snapshot and there are two known release blockers:
http://drupal.org/project/issues/search/wysiwyg?status[]=Open&issue_tags=release+blocker

sun’s picture

The last blocker, #356480-218: Lazy-load editors, just landed.

That has been quite a drastic change. It would be awesome if you could download + test the new development snapshot (in <=12 hours from now) on your sites to double-check that we didn't break anything, and report back on this issue if something got seemingly related to this is broken, but also, positive confirmations are very helpful, too!

Please make sure that you're testing the latest code. The development snapshot must have the version 7.x-2.1+39-dev! (38 is too old)

xtfer’s picture

I have +39 working successfully. I specifically tested CK editor in a Panels modal, without difficulty.

robcarr’s picture

Having been patching and following #356480: Lazy-load editors (and a few related issues) for some months, the latest DEV (+39) snapshot seems to work well with TinyMCE and Panels IPE. Good job and thanks for all your effort.

mradcliffe’s picture

I tested ckeditor loading in a custom ctools modal with the latest git 7.x-2.x from #356480: Lazy-load editors and I am seeing the behavior I expect including closing and re-opening. I only tested that behavior, but didn't find anything out of the ordinary going on.

steinmb’s picture

Tested wysiwyg HEAD, Drupal 7.15 and TinyMCE 3.5.7. It works, but 'Block format' got removed in my profiles and had be be enabled again, have it moved? Everything else seems to be working just fine, great work! :) RTBC.

Kars-T’s picture

Just a quick check if the ckeditor works with latest 7.x-2.x wysiwyg inside of ctools modal. Works without any problems.

betoscopio’s picture

Tested with 7.x-2.1+39-dev version, Drupal 7.15, CKEditor 3.6.4 and Media 1.2. I had to update my features with Wysiwyg Profile exportables because I was using this old solution http://drupal.org/node/624018#comment-4033330 for export configurations. After this, all worked as it was configured before, ctools modal works great too, while using Panels IPE.

sun’s picture

Title: New Wysiwyg 7.x-2.x Release? » New Wysiwyg 7.x-2.2 Release?
Status: Active » Fixed
sun’s picture

Forgot to say:

Thanks to everyone for manually testing the latest dev snapshot and providing feedback and positive confirmations!

The only report that sounded problematic was @steinmb's

It works, but 'Block format' got removed in my profiles and had be be enabled again, have it moved?

...and TBH, this might be an actual bug in the new 2.2 release. If others experience this as well after updating, let's make sure to create an issue for it.

Lastly, there's only a new D7 release. I'm personally not very interested in maintaining the D6 branch any longer (instead thinking of opening up a D8 branch, potentially replacing major parts of the code with VIE/Create.js). However, @TwoD might have a different perspective, and he has all what it takes to create new release. ;) [ping me on skype if you have questions or need help]

sanguis’s picture

Oh, Richard, I'm so happy. Hold me

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.