Damn, spoke too soon again. It displays the text if it is on its own page
(config.update.link.inline = false) but doesn't actually save any change.
Again, it works perfectly if using the ajax form.

Carl

On Thu, Jun 4, 2009 at 7:55 AM, Carl Anderson <[email protected]> wrote:

> The new version works in both cases. Awesome.
>
> Carl
>
>
> On Thu, Jun 4, 2009 at 7:44 AM, Carl Anderson <[email protected]> wrote:
>
>> No, I only overrode the show and list columns for the columns that use
>> TinyMCE. I'll try it with the new bridge and see if that makes a difference.
>>
>> Carl
>>
>>
>> On Thu, Jun 4, 2009 at 3:06 AM, Sergio Cambra .:: entreCables S.L. ::. <
>> [email protected]> wrote:
>>
>>> On Miércoles, 3 de Junio de 2009 22:28:29 Carl Anderson escribió:
>>> > Sorry about posting that wall of text, it didn't look that way when I
>>> > pasted it into the window. Weird.
>>> >
>>> > Anyway, I found that on some models it works and some it doesn't, but I
>>> > can't figure out why since they are so similar (but see next paragraph
>>> for
>>> > partial explanation). One the pages where it doesn't work, it looks
>>> like
>>> > the params for that field aren't even being sent through (I looked at
>>> the
>>> > log and that field isn't present in params.) And even stranger, one of
>>> the
>>> > ones where it doesn't work on it's own edit page, does work when that
>>> > record is shown on the edit page for a related model.
>>>
>>>
>>> I have used it in many projects without problems, loading the form by
>>> AJAX or in a page. Have you overriden those forms?
>>>
>>>
>>> I have added the tiny_mce bridge to active_scaffold, you don't need that
>>> file anymore, and you don't need to add include_tiny_mce to your layout,
>>> it's added with active_scaffold_includes in controllers using tiny_mce.
>>>
>>>
>>> >
>>> > I figured out why it works sometimes and not others, but it really
>>> isn't
>>> > solved. If you use the ajax forms, it works. If you don't, it fails.
>>> I'd
>>> > like both of them to work, just in case, but I have no idea why this
>>> > happens. But if I have config.update.link.inline = false in the
>>> controller
>>> > it always shows up blank and doesn't save (same is true for
>>> > config.create.link.inline = false) but if I don't have that it works
>>> > perfectly.
>>> >
>>> > Carl
>>> >
>>> --
>>> Sergio Cambra .:: entreCables S.L. ::.
>>> Nicolás Guillén 6, locales 2 y 3. 50.018 Zaragoza
>>> T) 902 021 404 F) 976 52 98 07 E) [email protected]
>>>
>>>
>>>
>>> >>>
>>>
>>
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"ActiveScaffold : Ruby on Rails plugin" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/activescaffold?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to