Publish vs Update

Hi there,
One question is still confusing me after the iWeb v1.1 update: the issue of publishing vs updating.
It seems to me that the only way to get new content (i.e., a new photo page) onto my iWeb (published to .Mac) site is to click the "Publish" button at the bottom of the iWeb "Site Organizer" list (or to select this same option from the "File" menu.
Every single time I add just a new photo page to my site and click "Publish," iWeb goes onto .Mac and goes through the "Creating Page: ..." process (via the progress bar window that pops up).
This takes forever and since I have not made any changes to any of the pages (except for, I suppose, the name of the new page being added to the list of available photo pages in the list at the top of each page) I do not see why each page needs to be republished.
My point is, I don't understand the second part up the uploading process when the little progress wheel comes up next to each site in the "Site Organizer" menu. It seems like this is when the new content is being added, so why is the first part (the "Creating Page: ...") necessary?
Does iWeb really need to recreate each page every time I want to add a new photo page to my site or is there a quicker way that I am missing?
I'm currently studying abroad and my internet connection leaves something to be desired (in terms of upload speed) so I'm looking to streamline this process as much as possible.
Thanks!!
Allen

It's a 2-step process. 'Creating pages' does exactly what it says. It's like publishing to a local folder, but with .Mac functionality included. Actual uploading to .Mac only commences when page creation is complete. That's when the progress indicator(s) appear, and it's only then that you regain control of the application.
As to your concern that the process takes a long time when you add 'just a new photo page', you go on yourself to explain why doing this necessitates re-creation of every page in the site — it's precisely because of 'the name of the new page being added to the list of available photo pages in the list at the top of each page'. Once you add a page and include this on the navigation bar, every page which displays the navigation bar has to be updated.
[ Visit here for iWeb Tips, Tricks and Hack ]

Similar Messages

  • Cannot publish Flash Updates Verification of file signature failed for file SCUP 2011, SCCM 2012 R2 and WSUS all on same Windows Server 2012 machine

    I am attempting to distribute Adobe Flash updates using SCUP 2011, SCCM 2012 R2, WSUS ver4 and Windows Server 2012.  Everything installs without error.  I have acquired a certificate for SCUP signing from the internal Enterprise CA.  I have
    verified the signing certificate has a 1024 bit key.  I have imported the certificate into the server's Trusted Publishers and Trusted Root CA stores for the computer.  When I attempt to publish a Flash update with Full content I receive the following
    error:
    2015-02-13 23:00:48.724 UTC Error Scup2011.21 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
    \\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab
    I have redone the certificates three times with no luck.  I can import metadata, but any attempt to download content results in the verification error.
    TIA

    Hi Joyce,
    This is embarrassing, I used that very post as my guide when deploying my certificate templates, but failed to change the bit length to 2048.  Thank you for being my second set of eyes.
    I changed my certificate key bit length to 2048, deleted the old cert from all certificate stores, acquired the a new signing cert, verified the key length was 2048, exported the new cert to pfx and cer files, imported into my Trusted publishers
    and Trusted Root Authorities stores, reconfigured SCUP to use the new pfx file, rebooted the server and attempted to re-publish the updates with the following results:
    2015-02-16 13:35:44.006 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file:
    \\SCCM\UpdateServicesPackages\a2aa8ca4-3b96-4ad2-a508-67a6acbd78a4\3f82680a-9028-4048-ba53-85a4b4acfa12_1.cab.
    Is there a chance this content was already created and signed with the old cert, so installing the new cert has no effect?  In ConfigMgr software updates I see 4 Flash updates, all marked Metadata Only (because they were originally published as "Automatic." 
    No Flash updates in the ConfigMgr console are marked as downloaded.  I can't find any documentation on how the process of using SCUP for downloading content for an update marked Metadata Only actually works. 
    Comments and suggestions welcome.

  • Updated to Adobe Muse 2014 this morning and have worked in it for the last 8 hours. Now when I try to publish the updated site to Business Catalyst for my client to preview it crashes everytime. I have tried just publishing altered files only, then tried

    Updated to Adobe Muse 2014 this morning and have worked in it for the last 8 hours. Now when I try to publish the updated site to Business Catalyst for my client to preview it crashes everytime. I have tried just publishing altered files only, then tried the whole site again, and then tried publishing as a new site altogether. Thought I would then try to export as HTML in the hope of uploading the files via an FTP client and Muse crashes and locks up again. I am extremely stressed about this as I am in the last few days of of website I have been working on now with no issues since December. We are due to go live and my client needs to see it. I am desperate for an answer. It is not looking good. I am on an Apple Mac and have not had any isses publishing it for the last 6 months. Not very happy to say the least. Need desperate help.

    Hi Zak, I got onto Adobe Customer Care Live Chat this morning and gave them the error message. After some trouble shooting with them it appears the older archived file of the site still publishes. I have now reverted back to the old file and copied and pasted out of the new file and from some ideas given to me by support I am now able to publish to Business Catalyst. It seems there was something corrupt within the new pages added yesterday. I have no idea if this would have still happened if I hadn't updated but I am glad it wasn't a Muse specific problem. I am loving using Muse and the support from Adobe has been excellent. Thanks everyone. By the way I do love the new version and apart from this hick up that lost me a few hours, aged me some more and gave me grey hair I really love Muse. Thanks again.

  • Publishing Website Updates via FTP

    Hi,
    I've just published my first iWeb site to an external domain. It's a fairly big site and took a while to upload via FTP due to restrictions in their upload bandwidth (no files larger than 2 meg).
    I've just added some additional photos to the photo album page and want to publish the update to the site. Which files do I need to replace on the FTP in order for this change to happen? I figured I'd just replace the 'photos' page folder and the 'photos.html' page file and that this would be sufficient. I can see the new photos in the 'photos' folder on the FTP but the page hasn't updated. What am I doing wrong? Surely I don't have to re-upload all of the iWeb files? Surely I only need to re-upload the files that were amended?
    Thanks
    Simon

    This tutorial may be of help: #2 - Uploading only those published new or newly edited files when using a 3rd party FTP client
    OT

  • Using iweb 11 I can no longer publish site updates, please help.

    I am using iweb 11 and Lion and I can no longer publish site updates, please help.

    What a brilliant solution, Roddy.  Never would have thought of that.

  • IWeb-No way to publish only 'updated' files?

    I am gathering by everyone's comments that there is no feature in iWeb to only update changed files, pages, etc? Please help if I am incorrect on this one.
    This seems like a major goof on apple's part ... I just wanted to change some font color today and I had to re-upload all my videos on unrelated blog pages. I would suggest everyone use the 'provide iWeb feedback' option under the iWeb drop down menu on this one...
    EK

    When you using .Mac, publishing only updates pages
    which have been changed (they are shown in red on the
    list at the left).
    Good info, but still doesn't make sense why my individual blog pages would be re-uploaded when I only changed the font color on the blog main page. It did turn red, though, indicating all would be uploaded upon publish. This definitely deters me from including videos in my blogs.... maybe just links to static locations on the iDisk would work around this?

  • Since moving from MobileMe to iCloud I can't seem to publish the update done on iWeb.

    Does anyone know how I could figure out a way to publish my updates on iweb since moving from mobileme (the host) to icloud?
    Thank you,

    Do this:
    go to the System/MobileMe preference pane and log out of MMe.
    login with a bogus username and password like "Ying" and "Yang". This clears the caches.
    login with your correct username and password.
    launch iWeb and try again.
    OT

  • Problem with AUTO PUBLISH nd update NEW POLICY to Client .

    To : who may concern , which really need urgent help .
    after few days of setting up the ZESM , but then i was unable to find is there any setting which can "AUTO PUBLISH " into the Client side . Without the Client need to use the manual "UPDATE POLICY " button ?
    Because , we find it that to make it silent update without the CLIENT side need to manually click the UPDATE POLICY , so i would wonder is there any way to have the AUTO UPDATE the policy from SERVER side ?
    thank alot first .
    From : NX ( which this few days has been keep on try and explore the ZESM 3.5 , 4.0 , 4.1IR )
    Which really need help in here , due to we are almost to the end of the setup server and the IT infrastructure .

    I would recommend that you READ and UNDERSTAND the Installation and Administration guides from the Documentation (somebody took the job to write those, so be kind enough to read it)
    Main Doc
    http://www.novell.com/documentation/zesm41/
    Your question is answered here:
    http://www.novell.com/documentation/...a/bnk7bdx.html
    See "Update Interval".
    Lastly, this is a public support forum, served on a best-effort basis from the community. As such, there's no guarantee that you'll get an answer, and if you get one, that works and is correct. So, if you have un urgent or important issue, go ahead an open a support ticket with Novell Technical Services in order to be served by professional support engineers backed up by the engineers who wrote the code.
    http://support.novell.com/contact/
    >>>
    From: nxgame<[email protected]>
    To:novell.support.zenworks.endpoint-security-management
    Date: 12/11/2010 3:06 pm
    Subject: problem with AUTO PUBLISH nd update NEW POLICY to Client .
    To : who may concern , which really need urgent help .
    after few days of setting up the ZESM , but then i was unable to find
    is there any setting which can "AUTO PUBLISH " into the Client side .
    Without the Client need to use the manual "UPDATE POLICY " button ?
    Because , we find it that to make it silent update without the CLIENT
    side need to manually click the UPDATE POLICY , so i would wonder is
    there any way to have the AUTO UPDATE the policy from SERVER side ?
    thank alot first .
    From : NX ( which this few days has been keep on try and explore the
    ZESM 3.5 , 4.0 , 4.1IR )
    Which really need help in here , due to we are almost to the
    end of the setup server and the IT infrastructure .
    nxgame
    nxgame's Profile: http://forums.novell.com/member.php?userid=99703
    View this thread: http://forums.novell.com/showthread.php?t=427947

  • Line-height problem in publishing after update!

    This was how it looked before the update.
    This is how it look now.
    same line-height value. but it only happens when i publish it when i view it locally there's no problem.

    Fisrt, this problem only happens in the published content which has edge runtime js file in minified form.
    There is one issue with the minification due to which this issue happens.
    1. What´s the difference between the code you gave me and the "textShadow" with ts:"textStyle" you gave that other guy?
         Since your edge runtime code is hosted in CDN which we don't have acces to modify, that's why you need to add one line extra code. If edge runtime is hosted in your server itself then you can modify it as I suggested earlier. But I would recommend to add extra one line code, which will be cleaner way to do it.
    2. Should I always insert the code you gave me before starting a new project? So this problem doesn´t happen along the way?
         You can add this one line to every new project if it's using line-height. One we fix the issue in the next release, you no longer need to do that then. But till then, use it.
    -Vivekuma

  • Adobe Publishing Suite update v24 is not compatible with current Adobe Content Viewer

    I updated the Adobe Publishing Suite to  v24 and updated my folio to v24. Now I can't view it in Adobe Content Viewer. When will the Adobe Content Viewer be updated to be compatible with the new v24?

    Sjekk out this post:
    http://forums.adobe.com/message/4830471#4830471

  • IWeb not publishing site updates

    Starting today - 5/18/09, A site I have in iWeb is no longer publishing updates. The site publishes to my mobile me account, and is redirected to my domain. This is the page in question - http://www.pitassidesigns.com/Portfolio/Web_Design.html
    Besides the code iWeb puts out I have added the favicon code, and Google Analytics Code. For some reason when I made some changes to some images, they do not appear as they should. The first image should be swapped with the second, and now the second image is gone. The google code, and favicon code it still there, and I usually have to re-input it after updates. Also the page in iWeb remains red, as if it was not published. I tried to delete that page and file folder from my idisk, and iweb doesn't publish a new one as it should. I tried restarting and nothing. I tried publishing the whole site, and it remains the same.
    Any help would be great, I don't feel like manually writing this page out in Dreamweaver, iWeb is so much easier.

    Ignore this. As usual when I decide to post this it works on the 10th try. Not sure what happen there.

  • Blog post Publish vs Update

    This question was asked in February here and answered, but it clearly was never addressed.
    When a blog post is saved as a draft, the PUBLISH button becomes the UPDATE button and there is no longer any clear indication to the client of whether their post is public or not. 
    This includes the post list which does not show the status of a blog post.  Is a fix coming?
    Best,
    Rob

    It's a 2-step process. 'Creating pages' does exactly what it says. It's like publishing to a local folder, but with .Mac functionality included. Actual uploading to .Mac only commences when page creation is complete. That's when the progress indicator(s) appear, and it's only then that you regain control of the application.
    As to your concern that the process takes a long time when you add 'just a new photo page', you go on yourself to explain why doing this necessitates re-creation of every page in the site — it's precisely because of 'the name of the new page being added to the list of available photo pages in the list at the top of each page'. Once you add a page and include this on the navigation bar, every page which displays the navigation bar has to be updated.
    [ Visit here for iWeb Tips, Tricks and Hack ]

  • Local Folio hyperlinks get published without updating article

    When creating a local folio, I don't even have to update the article and the hyperlinks are published and functioning when using preview folio. How is this possible? I haven't tried this with a remote folio yet.

    Hi Andrew,
    can't help unfortunatly, but I get the same error when trying to download a retina display folio using a normal dps account. Download is "prepared" for about 5 minutes after which I get the error message:
    An error has occurred while exporting the folio.
    Failed to download the folio to your local disk.
    [downloadIssueFailed]
    However, normal resolution folios can be exported and exporting a retina folio from a professional DPS account works.
    Best greetings,
    Philip

  • Publish Server Update status using IIS

    Hi, I had setup the WSUS on a 2012R2 for my server environment. My job is to approve the updates and work with server owners (eg. Application team). May I know how to publish the server update status/report using WSUS server with IIS.
    My other IT team can go to the site for checking their servers' update status and carry on the manual update job via remote desktop. Rather than remote to each of their server to check the updates been push.
    I saw this feature before when I was with my ex-company. The WSUS team will send us a link and I will use the site to sort out those server which belongs to me to verify any new updates been pushed.
    Appreciate your feedback soon.

    Hi,
    As far as I know, there is no web management UI for WSUS.
    If we want to manage the WSUS server remotely, we can install the WSUS Administration console.
    To download WSUS Administration console, please click the link below:
    http://www.microsoft.com/en-us/download/details.aspx?id=5216
    Best Regards.
    Steven Lee Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Digital Publishing: Managing Updates | Learn Digital Publishing Suite | Adobe TV

    Adobe updates the components of the Digital Publishing Suite about every six weeks. Some users have been confused about which updates to install and when to do this. Adobe Digital Publishing Evangelist Colin Fleming helps clear up this confusion.The two major components are the Folio Builder and Folio Producer Tools downloads. This video discusses these and other components, when one should install these updates, and when one should wait to install them.
    http://adobe.ly/HZlv9M

    In Scenario 2. When updating DPS APP. Am I correct in understanding that you use the VIEWER BUILDER to build a new APP and submit for approval and THEN load the new Folio Producer Tools. What I am confused over is how can you build your app if the content has not been structured using the new toolset yet? Are the App markets simply approving the architecture of the document/viewer versioning and NOT the content per se?

Maybe you are looking for