Page 1 of 2 12 LastLast
Results 1 to 10 of 11

Thread: Publishing animated gif files (NOF auto generates new file names using "a_" )

  1. #1

    Default Publishing animated gif files (NOF auto generates new file names using "a_" )

    NOF previews/publishes picture files (jpg and gif), by regenerating a new file name using a_ in front of the original file name, rendering animated gifs useless. Is there a way to turn this off within the program or am I stuck having to edit the final published HTML file? Can't seem to figure this one out...thanks in advance NOF Forum members!

  2. #2
    Senior Member
    Join Date
    Feb 2010
    Location
    Brantford, Ontario, Canada
    Posts
    120

    Default

    Hello,

    I am not sure that I understand you.

    Is this animated gif in the navigation.
    I do not see that NOF renames any files that I have done.

    Please explain how you are using the gif file.

    Gary

  3. #3

    Default

    Simply selecting the picture icon, pasting the animated gif into one of the 3x1 frames of a table. Worked no problem in NOF11, but not so lucky in NOF12. The animated gif is not being used in navigation.

  4. #4
    Senior Member gotFusion's Avatar
    Join Date
    Jan 2010
    Location
    www.gotHosting.biz
    Posts
    4,529

    Default

    Are you selecting the images from the assets tab or are you going and getting another image from a folder on your computer?

    You should select your images from the assets tab (in the fusion assets folder) if they have previously been used otherwise Fusion will rename subsequent usages of the same image to avoid overwriting existing images in the Fusion assets folder when an image of the same name is used.
    NetObjects Fusion Cloud Linux enabled Web Hosting, support + training starts at $14.95
    NetObjects Fusion web Hosting and support + ASP + PHP + ColdFusion + MySQL + MS SQL
    FREE NetObjects Fusion Support & training comes with all web hosting accounts
    NetObjects Fusion Web Hosting: http://www.gotHosting.biz

  5. #5
    Senior Member
    Join Date
    Feb 2010
    Location
    Brantford, Ontario, Canada
    Posts
    120

    Default

    I see what you mean, all graphics in my test are renamed with an a_ in front too and they are all put in the autogen folder in assets in local publish.

    On the positive side, KWB, I do not know why you have to rename the graphics back, as NOF points to the renamed graphic with the correct file name in the html file that calls it.

    In my test site I have put them in from a location out of the site, and also have put them in from the assets folder and there does not seem to be any difference.

    Autogenerated image output is set at not optimized.

    Mike: Could you test yours and see if you have the same behaviour?

    Gary

  6. #6

    Default

    I am getting the image from the NOF11 assets folder (not using the assets tab in image bank). It's easier for me to just use the picture icon at the top of the program and find the pic by typing the first few letters of the file name (have hundreds of photos in the NOF11 assets folder as the site has a lot of graphical content - - - NO IT'S NOT A PORN SITE). Don't see how using the assets tab makes it any faster having to scroll down trying to find the graphic you need to put in the page. However, tried your suggestion, but to no avail...still will not preview or publish the original file name without the a_ in front of the file name.

  7. #7

    Default

    Actually, when I publish, I do so to a Temp directly, I don't use the default NOF directory for publishing, but do for previewing.

    Quote Originally Posted by garydumbleton View Post
    I see what you mean, all graphics in my test are renamed with an a_ in front too and they are all put in the autogen folder in assets in local publish.

    On the positive side, KWB, I do not know why you have to rename the graphics back, as NOF points to the renamed graphic with the correct file name in the html file that calls it.

    In my test site I have put them in from a location out of the site, and also have put them in from the assets folder and there does not seem to be any difference.

    Autogenerated image output is set at not optimized.

    Mike: Could you test yours and see if you have the same behaviour?

    Gary

  8. #8

    Default

    Also, my settings are set to not optimized on graphics, and I publish setting is set to "flat"

  9. #9

    Default

    A little more background on this fellas...I originally exported this site from NOF11 using the template method and it works fine in NOF12. The preview and publish features have no ill effects on animated gifs what-so-ever. However, thought I would give the 82 page site a facelift and redo it from scratch in NOF12...and this is where this problem arose. I copied all the files from the original NOF11 assets folder and placed them into the new version of this sites asset folder in NOF12. So I have all the graphics files necessary to complete the site without having to link to another folder outside the confines of the new sites nod file. I really shouldn't be having any issues with this as all the settings (as far as I can tell), are identical between NOF11 and NOF12, and I am compiling the site exactly as I would have in NOF11. Below is a snippet of the code that NOF12 is spitting out after I locally publish that page in question:

    <td width="425"><img id="Picture28" height="344" width="425" src="./a_Rotator.gif" border="0" alt="Rotator" title="Rotator"></td>

    NOF12 is essentially renaming the animated graphic "Rotator.gif" to "a_Rotator.gif" and in the process of doing so, rendering it a static gif file (no bueno). Any ideas on this one guys?

    Here's the same page as from the original site as published in NOF12 (installed in NOF12 via the template method), and the copy from that published code:

    <img id="Picture17" height="344" width="425" src="./Rotator.gif"

    as you can see, for some reason, NOF12 didn't rename the animated gif in this example when the site was imported from a template from NOF11. I suspect it kept the original source coding from NOF11 when it was imported via the template.
    Last edited by KWB; 01-17-2011 at 01:32 AM. Reason: updated info

  10. #10
    Junior Member
    Join Date
    Jan 2011
    Posts
    17

    Default

    The reason is that NOF XII reoptimizes images even if you set it to no optimization, and it renames the file to a_image.file. I also posted about this, hope it will be fixed on the next update. You have to set it to 'not optimized' on the picture properties window (one by one on each and every image on the website - because 'Tools>Options>Application>Auto-generated image output>Not optimized' doesn't work -- A bug in NOF XII.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •