Closed (won't fix)
Project:
Outline Designer
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
27 Feb 2009 at 05:39 UTC
Updated:
25 Jul 2010 at 00:27 UTC
Jump to comment: Most recent file
Comments
Comment #1
btopro commentedIt's in the future direction of the project, when I learn more about how to implement it then I'll quickly throw it in. I'm hoping to get inspired at DC and throw up a new release. It's definitely intended though as I know most don't use Tiny anymore.
Comment #2
dm0 commentedHere is my quick-fix for this. The WYSIWYG API normally adds its JavaScript to the page when altering a form, but the page has already been printed by the time an AJAX request gets an edit form. This patch basically runs some code from their form_alter function to define each input format profile that the current user's roles have permission to use on page load.
Comment #3
btopro commentedUnfortunately seems to create some issues where it won't submit anymore. Also can't switch between input formats once one has been loaded and I had a weird thing where two text editors appeared once I hit the "disable rich text editor" button.
Comment #4
dm0 commentedOkay, I had the toggle link disabled in my preferences and didn't catch that. I didn't have any problems submitting, however. Do you get a JavaScript error?
The attached prevents the mix-up from changing filters or toggling the editor (at least in my setup).
Comment #5
btopro commentedversion 1.1 and forward no longer support inline edit forms as they were a huge bloat on the user experience. They have been replaced with an edit button that's a shortcut to editing the node form (popup)
Comment #6
tallsimon commentedWhat about using the modal frame API - does this not work with WYSIWYG?
Comment #7
btopro commentedThat could work but there's way too much js bloat in the process for not much gain imho. If someone wants to make an add on module to add this functionality to outline designer id promote that but it won't be in the core package of this product.
Comment #8
tallsimon commentedOK cheers. I found a more serious problem, however - http://drupal.org/node/863864