Wysiwyg API is installed but editors (FCK and TinyMCE) are not working.
I have installed Wysiwyg API and installed both FCKeditor and TinyMCE, both separately and together and followed all of the configurations demanded. The editor does not appear on the content.
I tried installing FCKeditor as a stand alone and it does not work either. I have installed FCK and TinyMCE on other versions of Drupal and they worked fine.
Is there a difference between Acquia and the garden variety Drupal that may be causing this?
I noted that the video on Wysiwyg API was done with an earlier version, that may be the problem, but still, the editors on stand alone should work. I am trying other editors, but I think the problem may be more profound
FS
PS: I have just installed Wysiwyg API on my local system, not using Acquia and it works. I notice that when the system works it has a check mark beside the filter and on the Acquia site it does not even though it says it is installed. I loaded them both in the same way, save for the fact the Acquia site used Filezilla.
PPS: I am doing a clean reinstall to see if that will make it work properly.
Updated Database, still no joy
Bryan Ruby
Not sure which version of
Not sure which version of Wysiwyg API you're using, but newer versions have moved the location of the editors. So TinyMCE would now be placed in sites/all/libraries/tinymce and FCKeditor is now placed in sites/all/libraries/fckeditor.
I have the Wysiwyg API located at: sites/all/modules/wysiwyg
Bryan Ruby
CMSReport.com
First, I found there was a
First, I found there was a problem with the installation that gave me a real problem, but I have solved that one with a reinstall and a very great deal of help from the host (Hot Drupal) now I have the site running but the system does not recognise ANY of the contributed modules I put into sites/all/modules. Back to square one. that is what it was doing originally and just disappeared. I am going to try removing them and re-entering them. No idea what is causing this.
FYI I am using FileZilla and I am not all that familiar with it, but they seem to be listed. I should also say, for your information and for the information of those who may follow me with the same problem, I took out the entire instalment of Acquia Drupal because I assumed when I first had this problem it was a bad install.
My reinstall was not cooperating at all, not letting me install Drupal at all. I went to my hosts and asked them. After much bashing at it, we found the settings.php file was still there from the old install and causing problems.
Deleting that was a chore. First I thought the permissions 0777 were what I needed, I now know it is really 0755. I also found that this permission has to be applied to the holding folder as well. That took a bit for me to find!
In any case I got the Acquia Drupal back up and the modules included are working fine this time, or at least as far as I have found thus far. Solr is not connecting, but I assume I can solve that over time and practice.
However, no contributed modules show. Back to square one again. The first time this happened I cleared the cache and the module appeared as if by magic. This time I have done that and there is no joy.
I must have done something very stupid and now need some gentle guidance.
Cheers
F.S.
PS: The Drupal forums are not throwing up anybody else with this problem, if that helps. Still looking. I have also updated the database and that has had no effect.
I am now stripping the site
I am now stripping the site again and starting over for the third time. Hopefully third time lucky. This module problem is really inconvenient.
No luck! New installation
No luck! New installation and it still does not register any contributed modules, at least not Wysiwyg API. It is after 1 AM and I have been going since seven. I think I will go to bed and hope there is some response by the morning.
F S
Hi Frank, I just responded
Hi Frank,
I just responded to your support ticket. It looks like you created a modules directory with an upper case "M" ("Modules") instead of a lower case m ("modules")
I believe if you rename the directory you should be all set.
If you haven't got too far into the installation I notices that you did not install Acquia distribution using SVN. We support SVN and it is by far the easiest way to keep your Acquia distribution up to date.
If you're willing to start from scratch again (note it can be done without losing data, but easiest is to start blank) you can do the install in shell using SVN and it will make your life much easier when upgrading.
------
HotDrupal.com
Drupal Friendly Hosting
The very nice people at my
The very nice people at my hosting found the problem. My sites/all modules seems to have been sites/all/Modules.
Yes I do feel foolish, very foolish indeed!
Don't worry about it, many
Don't worry about it, many people using Microsoft products miss that UNIX
is case sensitive.
It's something that happens to a *lot* of people :)
------
HotDrupal.com
Drupal Friendly Hosting
Post new comment