Site moved

hello

I have moved my Acquia Drupal site from one server to another.
But after moving to new server I have one issue which I can't solved myself because I don't know where to find such files.
I can't use on my site any editor by wysiwyg module. Second issue with this is I can't use national chars in textarea field during adding new node eg. ł, ó, ń etc. because my site is for Polish speaking people.

Could you get me any advice where I can find files responsible for these task like generating textarea field in admin side?

Regards

Adam

cwaid's picture
Collin Waid
Acquia Staff

Hi Adam, If I understand

Posted on February 8, 2010 - 4:58pm by Collin Waid.

Hi Adam,
If I understand your question correctly, you are having trouble finding a few files after switching your site to a new server? To which now a few of your modules are not working?

If this is the case, you should be able to locate your added modules in the same location as before...which is sites/all/modules. You may also want to ensure they are still enabled by going to Administer > Site Building > Modules.

To modify forms, go to Administer > Content management > Content types and select 'edit' or 'manage fields' for the content type you wish to modify.

Please let me know if I misunderstood any of the questions or if you have further ones.

---
Regards,
Collin Waid
Acquia Client Advisory Team

hello Collin Thank you for

Posted on February 8, 2010 - 5:56pm by Adam Sobkowicz.

hello Collin

Thank you for your answer.
I see that my English was a little poor. :)
So I will try to explain my situation. The problem is after moving my site from one server to another I can't load wysiwyg editor in textarea field when I try to add content to a node.
In anyone template is the same, in Garland too.
When I try to switch between input formats eg. Plain text to Full HTML I can see Drupal doesn't react. I can only get empty textarea field.
I can't see the button 'Split summary with cursor' above textarea field.

In all templates I have print $scripts in head and print $clouser in the bottom of page.tpl.php file. So I would like to know which Drupal files generate textarea field in admin?

Hope this is more clear explanation :)

Regards
Adam

cwaid's picture
Collin Waid
Acquia Staff

Ah, okay. What WYSIWYG

Posted on February 9, 2010 - 12:38pm by Collin Waid.

Ah, okay. What WYSIWYG editor are you using with the WYSIWYG Module?

Also, go to admin/settings/wysiwyg and let me know if it says the editor you want is properly installed or not installed.

---
Collin Waid
Acquia Client Advisory Team

hello I am using WYSIWYG

Posted on February 16, 2010 - 8:04am by Adam Sobkowicz.

hello

I am using WYSIWYG module with FCKeditor and TinyMCE. Both of them are installed ok.

cwaid's picture
Collin Waid
Acquia Staff

A few basic things to check

Posted on February 16, 2010 - 11:42am by Collin Waid.

A few basic things to check (you may have done this already):

- Set your theme to a default theme that has not been modified at all. Does it work? An error in custom theming is often the cause of WYSIWYG failing to load.
- Check what version of WYSIWYG you have...is it the latest? Also check FCK and TinyMCE versions and make sure they're compatible with your WYSIWYG module (compatible versions listed here: http://drupal.org/project/wysiwyg)
- Have you configured the settings? Check the Edit menu for both FCK and TinyMCE via admin/settings/wysiwyg and make sure they are enabled.
- Are your filters too strict to allow WYSIWYG to work?

If you have checked and verified those aren't the issues, try this. Open up firefox and use a developer tool, such as FireBug (http://getfirebug.com/), to check if there are an JavaScript errors being thrown. If there is a javascript error, what is it?

Also, check this page for common issues with WYSIWYG. Your answer may be there.
http://drupal.org/node/417166

---
Collin Waid
Acquia Client Advisory Team

hello Collin Thank you for

Posted on February 18, 2010 - 6:26am by Adam Sobkowicz.

hello Collin

Thank you for your support.
I checked all your points.

- Set your theme to a default theme that has not been modified at all. Does it work? An error in custom theming is often the cause of WYSIWYG failing to load.

I checked it. It doesn't work with Garland also.

- Check what version of WYSIWYG you have...is it the latest? Also check FCK and TinyMCE versions and make sure they're compatible with your WYSIWYG module (compatible versions listed here: http://drupal.org/project/wysiwyg)

Yes, I use the newest version of editors, both are supported.

- Have you configured the settings? Check the Edit menu for both FCK and TinyMCE via admin/settings/wysiwyg and make sure they are enabled.

Yes they are enabled

- Are your filters too strict to allow WYSIWYG to work?

Here I don't know what exactly do you mean in this point
I use 4 filters
- end line converter,
- HTML correction,
- Insert node
- Encode email addresses

- If you have checked and verified those aren't the issues, try this. Open up firefox and use a developer tool, such as FireBug (http://getfirebug.com/), to check if there are an JavaScript errors being thrown. If there is a javascript error, what is it?

Yes probably here is this issue. I suppose.
Now I got errors
1. warning: Invalid argument supplied for foreach() in /home/site/20212/www/includes/menu.inc on line 1023. - I am not sure if it is an error for editor issue because I didn't get this error earler. Yesterday my hosting provider moved mysql server to other machine so this maybe from that hosting provider activity. Or maybe not.
2. In the FireBug I have got error: uncaught exception: Syntax error, unrecognized expression: )
But I don't know how to find where this expression is

- Also, check this page for common issues with WYSIWYG. Your answer may be there.
http://drupal.org/node/417166

Yes I checked but I can't find it there.

cwaid's picture
Collin Waid
Acquia Staff

Let's first figure out

Posted on February 18, 2010 - 4:07pm by Collin Waid.

Let's first figure out whether or not those errors are related to WYSIWYG. Try disabling the WYISYG module and see which errors still come up. Then let me know.

Some other thoughts:
Do you use any JavaScript Optimization modules or setting? If so, try disabling them, clearing the cache, and see if the issue still appears.

The issue may be related to another contributed module causing javascript issues. Try disabling your contributed modules (other than wysiwg) and see if the problem goes away. If so, enable the modules back 1 by 1 until you know which module is causing the issue.

Another possibility, but I doubt this is the issue:
http://drupal.org/node/417166#tinymce-invisible
Basically, limit your editor to have as few buttons as possible and make them simply ones like bold or similar.

---
Collin Waid
Acquia Client Advisory Team

hello Collin I hope I have

Posted on February 18, 2010 - 7:11pm by Adam Sobkowicz.

hello Collin

I hope I have found this issue. I check step by step what can make problem. And I know now which module it is. It was jQuery Update module dev version.

Thank you very much for your help

cwaid's picture
Collin Waid
Acquia Staff

That's great to

Posted on February 18, 2010 - 10:14pm by Collin Waid.

That's great to hear!

---
Glad to have helped,
Collin Waid
Acquia Client Advisory Team

Post new comment