I hope some FrontPage expert can assist with this.
We have a Web gallery generator program (Shozam) which creates online galleries on the user's computer, that can then be uploaded to any Web host. Some users then integrate the gallery with their Web site and FrontPage workflow. FrontPage users that have Server Extensions installed are having an issue that I am trying to correct. The code of the HTML slideshow page gets altered by Frontpage and images are forced to display at 31px x 31px.
Our fix so far has been to advise users to disable Server Extensions. I would like to get a less drastic fix.
Is there a way to tell FrontPage/ServerExtensions to NOT touch the code in the file? Forcing the img to be 31px x 31px will have all images display tiny. The way the slidehsow works normally is using JavaScript to dynamically replace images one by one, and if I do not specify a size, they will display at their own native size.
Users are not using FrontPage to explicitly do any alteration to the code. They are just uploading the Shozam generated gallery to their Web host that has Server Extensions enabled. I believe the edit happens either during the upload process, or when files are written to the server or maybe when someone tries to access the files (to view then in their Web browser).
I am not myself a FrontPage user. I would appreciate information I can pass along to my Shozam users that will help them with this frustrating experience.
Code as modified after uploading to Web host with Server Extensions on: http://www.westwoodgolf.info/MFCWebgallery/ (click Slideshow link and you will see the tiny images cycle; if you view the source code you will see that somehow, at some point, FronPage Server Extensions has added code forcing the image to display at 31px).
I don't think it is FrontPage Server Extensions (FPSE) that is doing it - I might be wrong but I think this usually happens on the FrontPage client side (usually if the user clicks on the image in FrontPage to "alter" it.
However, I might be wrong. I could be wrong - but try this:
I am pretty sure the code is intact on the client side. The files are not opened in FrontPage. Shozam has a built-in FTP uploader but my understanding is that a server with Server Extensions enabled excludes further FTP uploads. So they probably just use FrontPage to upload the Shozam generated HTML files. At some point during that process the code in files changes!
I will ask one of our power-users that is familiar with FrontPage to chime in as well.
Is the code you suggested a command for some Server Extension related automatic process to skip that part of the code?
Below is a solution posted to our forums by one of our power users. Basically I am trying to see if there is a simpler way or something we can do to the Shozam code (like what you are suggesting) such that it will not trigger automatic edits by FP or Server Extensions.
---------------------------------------
After installing [Shozam] and creating a gallery, I found out that the slideshow had tiny images when I published it with FP 2003 just as others here have. Knowing that FP and its extensions can cause problems at times, I tried every trick I knew to fool it. I finally gave up and emailed the FP guru I host my sites with. After 5 minutes he called me by phone with the fix and sent the directions by email. I thought I would pass it on.
You need 2 rules:
1. DO NOT generate a gallery into your web folders on your computer. Save it in My Documents somewhere else. 2. DO NOT name a folder in the web folders on your computer the same as a folder on your web server.
Now, you need to create a folder within your site on your web server.
Because it works with FP 2003, I presume it will work with previous versions and Expression.
1. Open your site directly on your web server using FP. 2. Create a folder in your root directory with a name that is NOT in the FP web on your computer (Rule 2). 3. After the folder is created, right click on it and choose "Convert to Web". 4. Close the site.
Now, you can FTP your gallery to that folder using whatever program you want other then FP. I use WS_FTP.
As a side note, using FTP could potentially corrupt FPSE - most FrontPage users will not recommend using FTP on any website managed by FrontPage. Now there are some FrontPage users that will say it is OK, and usually it is but for some that rely on the FPSE (especially forms), not recommended. I mean, if your website contact form does not work and that is the only method, how will users contact you (to let you know something is wrong). The Shared Borders are another one that will get picky at times.
Glad the solution I proposed worked though - and thanks for the offer. Interesting product - I am sure it helps a lot of users. I have a photo album now that I use (and only two 'albums' behind), fairly happy with it.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot delete your posts in this forum You cannot edit your posts in this forum You cannot create polls in this forum You cannot vote in polls in this forum
![]](/frontpage/skins/invision/forum_images/top-left.gif)
![]](/frontpage/skins/invision/forum_images/spacer.gif){kind=spacer}
![]](/frontpage/skins/invision/forum_images/top-right.gif)
![]](/frontpage/skins/invision/forum_images/left-side-table-bg.gif)
![]](/frontpage/skins/invision/forum_images/right-side-table-bg.gif)
![]](/frontpage/skins/invision/forum_images/bottom-left.gif)
![]](/frontpage/skins/invision/forum_images/hide_min.gif)
![]](/frontpage/skins/invision/forum_images/hide_off.gif)
Topic: How tp stop ServExt from modifying code?
