1.0.3

Yes, I've overridden some controllers.  That shouldn't matter, however, because 
as I said, it worked fine in development mode and not in productions mode.  
Obviously, the controllers are overridden in both modes.


On Jun 3, 2010, at 5:40 AM, Bruno Bornsztein wrote:

> You shouldn't have to do that. What version of CE are you running? Are you 
> overriding any controllers or helpers?
> 
> Thanks,
> Bruno
> 
> On Tue, Jun 1, 2010 at 3:51 PM, Patrick Minton <[email protected]> 
> wrote:
> Copying the CE mce_options.rb file my app's config/initializers fixed this:
> 
> cp vendor/plugins/community_engine/config/initializers/mce_options.rb 
> config/initializers/
> 
> But...I HAVE NO IDEA WHY. (There was previously no mce_options.rb file in my 
> app's config/initializers directory).  If anyone knows why this would have 
> been necessary, let me know.  Again, it only appears to matter when the app 
> is running in production mode.
> 
> Should I be worried about other initializers that aren't in my apps 
> config/initializers directory?
> 
> On Jun 1, 2010, at 1:44 PM, Patrick Minton wrote:
> 
>> To elaborate on this, in development mode tinyMCE is getting the full 
>> treatment when calling tinyMCE.init(), but in production mode it's getting 
>> almost no options.  From the HTML:
>> 
>> In development mode:
>> 
>>     //<![CDATA[
>>     tinyMCE.init({
>>     browsers : "msie,gecko,safari",
>>     cleanup : true,
>>     cleanup_on_startup : true,
>>     convert_fonts_to_spans : true,
>>     convert_urls : false,
>>     editor_deselector : 'mceNoEditor',
>>     extended_valid_elements : 
>> 'img[class|src|flashvars|border=0|alt|title|hspace|vspace|width|height|align|onmouseover|onmouseout|name|obj|param|embed|scale|wmode|salign|style],embed[src|quality|scale|salign|wmode|bgcolor|width|height|name|align|type|pluginspage|flashvars],object[align<bottom?left?middle?right?top|archive|border|class|classid|codebase|codetype|data|declare|dir<ltr?rtl|height|hspace|id|lang|name|style|tabindex|title|type|usemap|vspace|width]',
>>     media_strict : false,
>>     mode : 'textareas',
>>     plugin_preview_height : '650',
>>     plugin_preview_pageurl : '../../../../../posts/preview',
>>     plugin_preview_width : '950',
>>     plugins : "media,preview,curblyadvimage,inlinepopups,safari,autosave",
>>     relative_urls : false,
>>     theme : 'advanced',
>>     theme_advanced_buttons1 : 
>> "bold,italic,underline,separator,justifyleft,justifycenter,justifyright,indent,outdent,separator,bullist,numlist,separator,link,unlink,image,media,separator,undo,redo,code",
>>     theme_advanced_buttons2 : "",
>>     theme_advanced_buttons3 : "",
>>     theme_advanced_layout_manager : 'SimpleLayout',
>>     theme_advanced_resize_horizontal : false,
>>     theme_advanced_resizing : true,
>>     theme_advanced_statusbar_location : 'bottom',
>>     theme_advanced_toolbar_align : 'left',
>>     theme_advanced_toolbar_location : 'top'
>>     });
>> 
>> 
>> In production mode:
>> 
>> //<![CDATA[
>> tinyMCE.init({
>> mode : 'textareas',
>> theme : 'simple'
>> });
>> 
>> Again, I can't find anything in my config files that should dictate this 
>> discrepancy in behavior.  Anyone else?
>> 
>> On Jun 1, 2010, at 1:27 PM, Patrick Minton wrote:
>> 
>>> Hi all,
>>> 
>>> When I run my app in development mode, the rich text editor has more 
>>> features than in production mode.
>>> 
>>> for instance, for the /posts/new?post[category_id]=1 url:
>>> 
>>> production mode:
>>> 
>>> <Screen shot 2010-06-01 at 1.23.58 PM.png>
>>> 
>>> development mode:
>>> 
>>> <Screen shot 2010-06-01 at 1.25.38 PM.png>
>>> 
>>> Note that in dev mode, there are options for html, images, video, etc.  And 
>>> the toolbar is on the bottom in production but in the top in dev mode.
>>> 
>>> I've looked in application.yml, development.rb, and production.rb and can't 
>>> find any reason that the tiny_mce_options would be different from one 
>>> environment to the next.  Does anyone have any ideas?
>>> 
>>> Patrick
>> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "CommunityEngine" 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/communityengine?hl=en.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"CommunityEngine" 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/communityengine?hl=en.

Reply via email to