more .js path parsing problems

devin M. arnold
03/29/2006 07:01 am

I opened a .js file that was downloaded and parsed by OE and noticed the same issue with OE adding additional backslashes into the file paths it generates.

Here`s a few examples of what the .js file looks like BEFORE OE downloads the file. I say downloads because I think this issue is happening as the file is being downloaded and parsed by OE but i am not 100% sure.


Here`s what the paths to these files looks like AFTER OE parses and exports the .js file:


Again you`ll notice that OE is replacing the second character in the file path and file name with a backslash character. I am begining to see a pattern here.

My OE export settings are as follows:

Do Not Create subdirectories: FALSE
Make Autorun CD: TRUE
Put files to: The Above Directory
Filenames format: Joilet - CD-R 64 symbols
Use standard extensions for file with known file types: FALSE
Preserve Online Links: TRUE
Create Contents File: TRUE

When OE downloads the data locally BEFORE exporting it out to off-line content, where does OE store the downloaded data? Does OE parse the downloaded data for pathing etc while it`s downloading or does OE parse ONLY when exporting? I am trying to figure out if OE is creating this pathing problem while it`s downloading the files from the web OR when it parses out the data on export.


Oleg Chernavin
03/29/2006 07:01 am

I set the same settings in the Export dialog and exported our Web site ( again. But still I got no problem. Does it happen only with links inside .js files?

devin M. arnold
03/29/2006 07:01 am

This is happening in .js files as well as .asp files and .htm files. Basically any file that OE is parsing is having this problem. It seems like its only affecting files that are coming from subdomains.