| T O P I C R E V I E W |
| JazzcatCB |
Posted - 15 Jul 2005 : 01:35:03
I'm having MAJOR problems trying to get my exported HTML to run on my web host. The exported HTML has statements in it like these:
<SCRIPT LANGUAGE=javascript src='file://C|/Documents and Settings/Chris Barnhill/My Documents/files//dhe.js'></SCRIPT>
<link rel='stylesheet' href="file://C|/Documents and Settings/Chris Barnhill/My Documents/files//mfvTemplate.css"></link>
<img src='file://C|/Documents and Settings/Chris Barnhill/My Documents/files//blank.gif'
etc...
It keeps mapping the directory path on MY local machine, but that path does not exist on the web host! Why does it keep putting in the wrong directory path? I thought it was supposed to simply reference "files" from the current directory.
But even when I edit the exported HTML so that it looks for "files" off of the current directory (which is where it is on the web host) this *still* doesn't fix the problem.
HELP! I am at a loss here. What should I do? Any help would be appreciated. Thanks! |
| 4 L A T E S T R E P L I E S (Newest First) |
| s.dav |
Posted - 18 Jul 2005 : 13:22:59
All Dynamic HTML Editor versions (from 1.0) work using relative path so I cannot figure out why you are experiencing these problems...
I've created many sites using Dynamic HTML Editor and it correctly links external files in relative mode.
Obviously you have tyo specify a subfolder of the first one for external files so if you export your page in the directory "c:pippo" you should use a subforlder of this like "c:pippo........"
In the export dialog (for version 1.x) you have always to use absolute paths |
| JazzcatCB |
Posted - 17 Jul 2005 : 20:27:56
The honeymoon is over [2 :-(]
While I still think Dynamic HTML Editor is a great WYSIWYG HTML editor, I have discovered some poor or poorly-thought-out design issues. For instance, the inability to get the exported code to work on a web host without making substantial changes to it. I can understand that maybe every web host handles things a bit differently, so it may not be possible to tune the exported code properly to fit every web host, BUT in that case, I think it would have been appropriate to put a notice on the Export dialog box explaining this and offering suggestions on what problems one might encounter and how to fix them. But as it is, Dynamic HTML Editor exports code and the developer believes that the code will run "as-is" but it doesn't and that can cause great frustration and confusion for the developer (as I can personally attest to.)
Furthermore, I just discovered that the "Picture Tiling" feature does not work like I expected it to. I had a small image that I wanted tiled across a large area. The *reason* I wanted it tiled was so that the user's browser would only have to download the small image, and then the user's browser could tile that image on the user's machine. This is the *entire purpose* of tiling, as I understand it: it's supposed to help the user to avoid having to download a *huge* image file. But when you "tile" a picture on Dynamic HTML Editor 1.8, I discovere that it actually creates one big graphic file from the resulting tiled image and it exports that big graphic file, so now the user's browser has to download a big graphic image consisting of many tiled images. This totally defeats the purpose of tiling in the first place. In HTML, it is possible to create a table and tile an image in the background. Dynamic HTML Editor 1.8 should have implemented it's tiling feature this way, IMO, instead of creating one big image of all the tiled images.
|
| JazzcatCB |
Posted - 16 Jul 2005 : 13:23:08
I've discovered that in order to get Dynamic HTML Editor 1.8's exported html to work, it is necessary to make a number of undesirable folder and file changes as well as a number of corrections to the final code itself. Here is a list of the required changes:
2. Create the ?Destination Filename? off of ?D:\? (put exported html files in root)
3. In ?Put additional files in this directory? specify ?D:\files? (files directory must be off of root)
4. Click ?Export?
5. Open the exported html with an editor
6. Find ?files/? and replace with ?/files/?
7. Find /" and replace with "
8. If this html contains included html, copy the .CSS reference and make a new reference for each html file that is supposed to be included (because my web host does not support SSI)
9. If exporting the Home page, change the ".htm" extension to ".html"
10. The exported html is now ready to be uploaded to the host
It was a *major* hassle figuring out why Dynamic HTML Editor's exported code wouldn't run properly. Davide, I really think you ought to correct these problems in Dynamic HTML Editor 1.8 because they can cause serious problems for the developer.
|
| JazzcatCB |
Posted - 16 Jul 2005 : 08:24:57
Okay, I figured out why my edits to the exported HTML code weren't working. I have to replace the full local path name with "/files/[filename]" and it works. But I would still much prefer that Dynamic HTML Editor export the HTML with the correct "/files/[filename]" path in the first place. |
|
|
