AcuWeb™ Reference Library

Contact AcuWeb™ Support

If you cannot find the answer to your question in our online support resources, please submit a ijenti help ticket by clicking on the button below, and one of our ijenti support team members will assist you as soon as possible.

ijenti Help Desk

Content Saving & Posting

Home : Updater 4.2 Support: Content Saving & Posting

» Are you a visual learner?
   Check out our concise, step-by-step Video about Saving and Posting Updater Content video tutorial on Saving and Posting Updater Content.

  1. To edit content, choose "Content" from the AcuWeb Menu.
  2. Once the content list view is pulled up, a more detailed search can be used to find content. Use keywords (separated by a space) OR choose a specific page and press the Search button.

    Search
  3. To edit the content, click the title to continue.

Once you've made any additions, deletion or other change to your content, follow the steps below to save your content and post it to the web.

  1. Click on the "Save Changes" button at the top of the page.

    Save Changes
  2. You may use the blue "Preview" button to check your work before publishing it.  If further revisions are needed, make them; "Save Changes" again, and Preview as needed.
  3. When you are ready for your content to go live on the website, click the large "Post to Web" button at the top of the page.

    Post to Web
  4. After a brief pause, you should see a success message that indicates your site is in line for publication, including a link to your site's home page, from which you may navigate the site to verify that all of your changes published as you intended.

Because Updater quite literally checks every content element and every page of your site to see what elements have been revised, the "publishing cycle" may take a minute or two to complete, so you may need to refresh your browser a few times before the newly-published version of your site appears.  Refreshing, or re-loading your browser, is important.  Without refreshing, the browser may still be caching, or persistently "remembering" the prior version of your site.