• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Filemanager WYSIWYG Error

R

rperea

Guest
After upgrading to Plesk 9, the file manger no longer works as it should. In particular, the WYSIWYG editor doesn't work correctly.

It works fine for editing any html files in which all the images contained within the file exists, but whenever you try to edit a file in the WYSIWYG editor that contains img tags in which the src is not a file that exists, I get:
ERROR: PleskFatalException
Domain ID is undefined.

Additionally, an exception has occurred while trying to report this error: PleskFatalException
Domain ID is undefined.

0: /usr/local/psa/admin/plib/common_func.php3:108
psaerror(string 'Domain ID is undefined.')
1: /usr/local/psa/admin/htdocs/spaw/spaw_save.php:6

I initially thought that this may just be a problem with the old domains, so I created a new domain and got the same results.

I am using Plesk 9.0 on CentOS 5. I also have a lot of the newer OS packages installed like php5.2.6 and apache http-2.2.10 so I am not sure if that is breaking it (I don't think so since Plesk uses its own versions of apache and php, but you never know)

Anyway, I want to see if anybody else is having this problem. So if anyone out there is kind enough to do a quick test.

1. Login to Plesk 9.0.
2. Go to the file manager for a domain.
3. Click on httpdocs
4. Create a new .html file
5. Place the following HTML in the file.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>Untitled</title>
</head>

<body>
<img src="nonexistent.gif" alt="This image doesnt exist" />
</body>
</html>
6. Save the file.
7. Open up the new .html file using the WYSIWYG editor.
8. Don't make any changes to the content and click on "OK" - See if you get the error.

It took me a while to figure out why this was happening on some files and not others. The reason this is happening is that the file "nonexistent.gif" doesn't exist. Also, this happens even when the file does exist but you have put additional parameters after the image. So if the document contains:
<img src="/images/getimage.gif?name1=value1" />
You still get the error even though /images/getimage.gif exists.

Any help on this would be appreciated.
 
WOW, nobody willing to do the quick test and simply post your results??
 
maybe it is because there are a lot more issues around the Plesk 9 Version which hurts more as the wysiwig issue.

However i cant reproduce your issue on my Box (Plesk 9.0.0.2 & Suse 10.2) no error

Brujo
 
Thank you for the reply.
Your test results are greatly appreciated.
I also agree with you that Plesk 9 needs some work.
I will look deeper into the issue and post my results.
 
relative image paths may be the problem

I had the same problem with the WISIWYG editor. I had my pages in a directory at the same level as my images directory. I changed the image paths in my htm pages to absolute paths e.g. http://mydomain.co/images/anyimage.gif. This solved the problem. Alternately, put all your pages in the root and then use a relative path like this images/anyimage.gig.

Hope this helps
 
Can anyone tell me which (if any) version of plesk 9 this issues has been resolved. I can reproduce the error on Plesk 9.2 Centos 5
 
Back
Top