Files extracted...now what? (Plug-in activation)

The project page specifically states:

IMPORTANT 1) the module must be installed in {basepath}/sites/all/modules/tinytinymce or it won't work properly.

you state:

The TinyTinyMCE files are now located in sites/all/modules/tinymce

please confirm the folder name.

I understood the instructions to mean: put the tar file in sites/all/modules, and untarring would result in the tinytinymce folder being created. Instead, it created tinymce, so my final path was sites/all/modules/tinymce.

Should I create sites/all/modules/tinytinymce, put the tar inside it, untar, and end up with sites/all/modules/tinytinymce/tinymce?

seems to me you don't even have the tinytinymce module installed. When I look at the module itself downloaded from drupal.org, it has in it a tinytinymce folder, this should be extracted to sites/all/modules where it will then be a path like sites/all/modules/tinytinymce

then you must install the tinymce library in the folder provided by the tinytinymce module

I think the fact that this is a two part process, may be confusing you and would explain why you've not go the proper INSTALL.txt file ?

see below:

This module has been written to provide a simple way of linking Moxiecode's TinyMCE rich text editor into Drupal 6

RATIONALE
=========
This module was written because the Drupal's tinymce module seems to be quite difficult to configure and many people seem to be having problems with it under Drupal 6. It is intended to be simple to set up.

It offers two modes, simple and advanced. You control which users get which mode in Drupal's user permissions screen.
- simple mode offers a very limited set of controls (bold, italic, underline, stikeout, undo, redo, unordered/ordered list
- advanced mode offers most of TinyMCE's features. A few features, such as layers, have been removed but you can alter the configuration, if you wish.

By default, all textareas will have a toggle for turning the rich text editor on or off. Some textareas are excluded from this (and you can configure which ones).

INSTALLATION
============
1) Install all the files into the following directory
{basepath}/sites/all/modules/tinytinymce

***********************************************
It is VITAL that you use the correct directory.
The only correct location for this module is:
{basepath}/sites/all/modules/tinytinymce
Some modules will work if you put them in with the core modules, ie {basepath}/modules/..., however use of this location is deprecated.
This module won't work there; it could crash your site.
***********************************************

2) Download the latest version of TinyMCE from Moxiecode (http://tinymce.moxiecode.com). Install it in a subfolder called {basepath}/sites/all/modules/tinytinymce/tinymce
If you have done this correctly, the file tiny_mce.js should be located at:
{basepath}/sites/all/modules/tinytinymce/tinymce/jscripts/tiny_mce/tiny_mce.js

3) Copy or move the contents of the folder tinymce-jscripts-tiny_mce-plugins-pagebreak into tinymce/jscripts/tiny_mce/plugins/pagebreak.
This will overwrite part of TinyMCE's code. TinyMCE's pagebreak plugin has been modified to insert a Drupal Teaser break <--break-->.
(You could regard this step as optional, if you don't want this functionality.)

4) Enable the tinytinymce module using admin/build/modules.

5) Set up user permissions using admin/user/permissions. To see the rich text editor, users will need one of these two permissions:

use tinytinymce simple
use tinytinymce advanced

CONFIGURATION
=============
You can customise the installation at admin/settings/tinytinymce. The interface is quite "raw" in that you are directly editing the initialisation parameters - but also very flexible. There are some examples in the help text and loads more at http://wiki.moxiecode.com/examples/tinymce/installation_example_00.php.

You can configure the parameters for both the simple and advanced modes. This lets you add or remove any of the features of TinyMCE

You can also specify where the rich text toggle should NOT appear. By default it appears on all textareas with some specific exclusions.

IMPORTANT: The module is incompatible with aggressive caching. Normal caching should be OK provided you don't grant access to the module to anonymous users. If you grant anonymous users with access to the module you need to fully disable caching.

INTEGRATION WITH IMCE
=====================
If you have the IMCE module installed, this module will detect it and add the necessary scripts. Once you have done this, the image popup will have a Browse button in addition to the URL field. The Browse button will invoke the IMCE popup.

The Drupal page downloads this file: http://ftp.drupal.org/files/projects/tinytinymce-6.x-1.7.tar.gz

It refers to these instructions: http://drupal.org/project/tinytinymce (which, again, I may have misinterpreted based on behavior of other installs).

There's no mention of an install.txt file, and I see that nowhere in my directories, so I didn't see the instructions you've pasted above. You're right that I'm confused.

I'm going to start over with a tinytinymce directory and see if that fixes things.

the INSTALL.txt file is inside the archive : of tinytinymce-6.x-1.7.tar.gz. I can open the link you posted above and go inside the archive and see the INSTALL.txt

For now - assuming you've posted the installation instructions I would find there - here is where I am.

I have removed the tinymce directory from sites/all/modules/tinymce.

I have started over by creating, instead, modules/tinytinymce. Within that I have extracted all the files. So now I have sites/all/modules/tinytinymce/tinymce/jscripts and so on.

For now I have skipped the optional step that reads "Copy or move the contents of the folder tinymce-jscripts-tiny_mce-plugins-pagebreak into tinymce/jscripts/tiny_mce/plugins/pagebreak." (I skipped it because I see no directory called tinymce-jscripts-tiny_mce-plugins-pagebreak to copy from. Where is that?)

Instead I have moved on to admin/build/modules on my Drupal site to attempt to enable the module. Tinytinymce does not appear in my list of modules, however. How do I activate it?

you don't see that directory, because it sounds like you still aren't actually unarchiving the tinytinymce drupal module and are only unarchiving the tinymce library

you must extract and add to sites/all/module the tinytinymce.module which is downloaded from the link you posted in the thread above. Without it the tinymce library cannot communicate with drupal.

so

step one get http://ftp.drupal.org/files/projects/tinytinymce-6.x-1.7.tar.gz
extract it to sites/all/modules
then browse to THAT folder and follow the remainder of the instructions.

I used a tar command to extract. Since apparently that's the hangup, can you please give me the exact tar command that will give me the correct result?

Thanks.

I don't use the command line for extraction. I use 7zip. Though either method of extraction doesn't explain why you don't see/have an INSTALL.txt in the directory.

I have it now, and it's showing in Drupal. Thanks!

However, the editing window created by TinyTinyMCE is wider than the main content area in my theme (Barlow). Is there some way to adjust this? I'm not quite seeing all the icons on the right side. (I can't tell exactly how much is cut off -- I'm seeing about half of the paint palette icon, if that helps.)

I don't deploy editors, have only tested them in the past and on default themes. I'd guess you are running into a css issue with the theme or the editor itself.

Test on a defaul theme like garland. If it works correctly there, consider filing a support request against the theme.

At this point I am marking this as fixed since you now have tinytinymce up and running.

Thanks for dealing with this Ken. The remaining issue does, indeed, sound like some tweak is needed to the CSS.

I'd also like to suggest a rewording of instructions to make it clearer where to put and extract the tar file (not where it should end up - since this is handled during extraction / installation).

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