images of the editable page is not loading up

[jerrydeng]

The images of the editable page is not loading up in the snippet editor, why?
What is the permission needed for snippet to work?

[admin]

Images that don't contain an absolute path will not be able to display in the editor.  This is not a bug, but is part of the design.  Since the editor does not know the location of the original file, it is unable to determine where the images are located..

Don't worry, though.. even if the images don't display in the editor they will still be there for the preview, and live page, etc..

All WYSIWYG editors share this problem..

[KingSky]

I would recommend you take a look at a solution provided by a similar script to Snippetmaster.  Although it is a perl script, it uses the same internal WYSIWYG components.

http://www.bookcms.com/

I would revise your statement:

All WYSIWYG editors share this problem..

Although this problem is common to WYSIWYG editors, it is not universal and some editors have solved the problem.  The solution bookcms came up with was to put in the url each time there is an image.  Seems to work quite well.  Couldn't something similar be done with Snippetmaster?  It would solve a lot of problems, and eliminate a LOT of client complaints.

[admin]

Yes, actually the next version of SnippetMaster does exactly this same process..

The problem is that there are several ways to call an image file.

ie:  ../../../../../../image.gif  is a valid call.  This would be very difficult for the editor to make work.

But if you used /image.gif, then it is easy.  The problem is that our programming must account for EVERY possible variation of calling an image, which is a lot of work to do.  The new version of SnippetMaster is able to handle both variations.. if you sign up for the newsletter mailing list you'll know when we're looking for beta testers and when the new version is released.

Thanks!

[apollo]

Why not let the editor use the path defined in the upload images section in the cofiguration, by matching the current directory and then appending the matching directory from allowed upload configuration.  i.e.  if you are editing a page in http://mydomain.com/myclient/...  the it should use "/myclient/" plus the allowed upload folder ".../myclient/photos/" making the final path "http://mydomain.com/myclient/photos"  Since you have to define the allowable upload directory it should look there for the images.