Trouble Shooting FAQ

Given that this information is already recorded in Archie, we are working with the IMS Team to provide this information as content for the entity web sites.

Taking the information directly from Archie, and not re-writing it into the Website Source (or module text) will alleviate entity of the need to ensure several representatives of the same information remain up-to-date and consistent with each other.

How content can be corrected depends on the source of the content: either the Website Source itself, or some other source from which the content is provided. To identify the source of any particular content item, open the Website Source in Archie. (Locate the Website Source in Archie and choose to edit it.) In the Website Source form, you will be able to see that: the content of items whose source is the Website Source itself is displayed in text areas where you can edit the content; the content of items which are provided from other sources is displayed, but cannot be editted.

So if, in the Website Source form, the content you want correct is displayed in a text area, then go ahead and make the correction where you see the mistake.

If, on the other hand, the content is not displayed in a text area, then the correction must be made at the source of the content, from which it is provided.

The idea here is to re-use information which is already recorded elsewhere (to reduce work for the entity's Web Publishers, and to reduce confusion due to inconsistency for visitors to the web sites). The hope is that errors noticed in the web site will be corrected in all places where it appears by being corrected just once, at its source.

In fact, each page in the form could have one or more content items in it. The content items of some pages, though, might not apply to your kind of entity.

For example, the page listing Cochrane Reviews. When a Web Publihser of a Cochrane Review Group opens her Website Source to edit it, she will see that this page can include a list of the group's Reviews. But, when a Web Publisher of a Cochrane Centre sees that the same page in his Website Source form, it will be blank: the page's content items have not been found for the Centre (because a Centre does not have a list of Reviews).

If you see a blank page in the form, you can either choose to not include it in the web site and ignore it, or you can contact the Web Team to suggest what content items (pieces of information) you would like to have available to include in the page.

Upon clicking View Website, a new web browser window should open and display the home page of the entity's web site. If this page is for some reason not created when the site is published (as it should be), then the new web browser window will display an error message.

To ensure that the home page is created when the web site is published, return to the Resources view in Archie, locate the entity's Website Source, and Edit it. In the Website Source form, be sure to click on the check box and, thereby set to include, the Welcome page in the web site. Save this setting, and re-publish the web site.

This is what happens if a page is selected to be included in the published web site without have any content items also selected to be included. In the absence of any content items on the page, the menu appears on the right.

For the time being: please don't include a page in your web site without including also at least one content item on that page.

Short answer: you can't.

Long answer:

The alignment of text and images on web pages varies greatly across the various media by which a web page is accessed. Ensuring an exactly consistent appearance across even only the most popular clients (Internet Explorer and Firefox, for example) is difficult to impossible. Remember that the content of the entity web sites will be accessed by people and machines using a variety of: operating systems, screens, projectors, PDAs, web browsers, web-browser-window shapes and sizes, character sets, printed-paper shapes and sizes, colour-sets, screen readers, etc.

We endeavour to make the content good-looking to the vast majority of their intended audience, while at the same time ensuring that the content is easily accessible using all known media.

When you enter content into a text area in the Website Source form, it is automatically marked up with HTML so that it will look good in the published web site.

This automatic marking-up, though, doesn't always work perfectly the first time. If you are familiar with HTML, you can inspect the source HTML code of the generated web pages after publishing the web site.

I have found, for example, that sometimes when I enter text into a text area and then publish the web site, my text is not marked up as it should be, inside an HTML paragraph element. Instead, on the generated web page, it is inside an HTML division (div) element.

<div>
    Here is some text which I have entered into
    a text area in the Website Source form.  Note 
    that this text is inside a division (div) 
    element but not, as it should be, inside several
    paragraph (p) elements.
</div>

After making this discovery, I return to the Website Source form and enter and then remove (using the backspace key) a couple of apparently blank lines above my text. When I then re-publish the web site, the text is properly marked up into paragraph elements.

<div>
    <p>
        Here is some text which I have entered into
        a text are in the Website Source form.
    </p>
    <p>
        Note that this text is in seperate paragraphs.
    </p>
</div>

If a paragraph or portion of text on a page appears incorrectly, place your cursor in the paragraph and select a heading ('Heading 1', 'Heading 2', etc.) from the drop-down in the EWB form, save and then select 'Normal' from the drop-down and save again. Publish the site and text should appear correctly.