North Dakota State University

Detailed description

Currently, page cache is cleared when a page or any of its content elements is saved. This strategy is appropriate when using the Live workspace. In the context of workspaces, page cache clearing is delayed and occasionally authors do not see their changes if the cache is re-populated before a page is published. There is rumor that the page cache clearing hook may be available for a future release of TYPO3, or at the very least, that general purpose hooks would be added for developers to use.

Detailed description

A page history is only queried with respect to the current page ID. When using workspaces, this means that only part of the history is shown. Consider Page created (pid=1) Version 1 - modifications (pid=2, on publish copies values into pid=1) Version 2 - modifications (pid=3, on publish copies values into pid=1) *Version 3 - modifications (pid=4) While making edits in Version 3, the history within Version 3 is visible, however history of 1 and 2 are not visible because the history is associated with pid 2 and 3, not 4. On publish, Version 3 history also becomes hidden because only pid=1 history is shown.

Message

Date: 2009-04-08 13:11 Sender: Jill Peterson
 Works as expected. Authors should use Versioning to select an old version (see the drop-down menu at the top of each page).

Detailed description

When logging into TYPO3 and editing non-ndsu.edu Web sites, a certificate error is displayed in IE7 There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended). More information If you arrived at this page by clicking a link, check the website address in the address bar to be sure that it is the address you were expecting. When going to a website with an address such as https://example.com, try adding www to the address, https://www.example.com. If you choose to ignore this error and continue, do not enter private information into the website. For more information, see "Certificate Errors" in Internet Explorer Help. The certificate used by the CMS virtual host is a wildcard NDSU certificate, e.g. *.ndsu.edu so it is indeed a mismatched host for *.ndus.edu hosts. Investigate a way to have another SSL certificate for the ndus.edu hosts to alleviate this issue.

Message

Date: 2010-02-24 17:37 Sender: Jill Peterson Ref. Incident #95502 and #172914 that are related.

Detailed description

TYPO3's XHTML cleaning pads horizontal rule (<hr />) tags in paragraph (<p>|</p>) tags. So a paragraph that is intended to read <p>Hello</p><hr/><p>World</p> is rendered as <p>Hello<p><hr/></p>World</p> This breaks XHTML validation because block-level elements, including horizontal rules and paragraphs, cannot go inside of paragraphs. There is a bug report at bugs.typo3.org/view.php The impact of this problem is reduced by HTML Tidy cleaning.

Detailed description

When using human readable (HR) URLs for tt_news articles, all 404 error reasons are displayed as Reason: Segment "foo" was not a keyword for a postVarSet as expected! instead of Reason: "help/foo/" could not be found, closest page matching is help/ The same behavior is observed at news.typo3.org (for example news.typo3.org/news/community/foo should have reason "news/community/foo/" could not be found, closest page matching is news/community/).

Detailed description

If a visitor searches "in site" and visits a page other than the first page, the siteURL is included in the search query. Selecting "Search NDSU" re-submitting the query does not remove the siteURL from the query, which effectively means the visitor is "locked" into the search in site option unless they manually remove that part of the query from the search box. It is possible to work around this shortcoming by manually deleting that part of the search query, but some visitors might not intuitively know this as a work-around.

Detailed description

This is a known problem. bugs.typo3.org/view.php

Detailed description

If you use header cells for tables (top example below) it forces them > to be "Justified" (i.e., stretched out to fill the available space). > As you can see below, that doesn't work well. > > I did an end-run by removing the header cell specification and making > the text in each cell bold. (see bottom example below)

Message

Date: 2010-02-17 13:59 Sender: Jill Peterson Unable to duplicate any of the described issues. Copying tables in from another source, such as MS Excel, may bring with it undesirable formatting. Automatically assuming the author's desired format cannot be accommodated by CMS (or any other tool that uses rich formatting). Recommend removing formatting before/after paste and then applying the desired alignment within the CMS RTE. Documentation that demonstrates setting the alignment for an entire table is at www.ndsu.edu/cms/kb/tables/ /examples/ . Viewed the demonstration page in browsers Firefox 3, Firefox 3.5, Internet Explorer 8 w/Compatibility mode and Internet Explorer 8. Please provide details of what system displays this page with justified text or provide a link to a page that demonstrates this behavior and that does not have the justify property set to the cell. Keep in mind that any styles applied to an individual row or cell will override anything that is set to the table, including any styles that are brought in from a copy/paste from an external source.

Date: 2009-04-27 13:03 Sender: Jill Peterson Unable to duplicate in either Firefox or IE7 in a table created using the Insert Table wizard unless I set the alignment for those cells or the table to Justified.

Detailed description

Disable AllowOverride - Requires merging .htaccess files into the vhost config, but Jill has operated other TYPO3 environments with the RealURL/rewrite rules in a vhost config for several months without issue. - Need to merge the file protecting (deny) .htaccess rules into the vhost root. - Don't remember why the FileInfo override is enabled or if it's needed at all. This arguably improves security. It will improve performance, even if the amount is not be human-noticeable.

Detailed description

Change rendering of "select multiple" form option in FORM object to display a series of checkboxes in a fieldset instead of a select with multiple="multiple" . Some browsers/tools don't provide the ability for the visitor to actually select multiple simultaneously. Alternatively, consult with Jim Ross for another accessible option. Specifically change code like <!-- start code snippet --> <div class="field"> <label for="ndsumailformChoose_more_than_one">Choose more than one</label> <select name="Choose_more_than_one[]" id="ndsumailformChoose_more_than_one" size="5" multiple="multiple"> <option value="Lorem">Lorem</option> <option value="Ipsum">Ipsum</option> <option value="dolor sit amet">dolor sit amet</option> <option value="consectetur adipiscing elit">consectetur adipiscing elit</option> <option value="Nulla hendererit mauris sit amet mi">Nulla hendererit mauris sit amet mi</option> </select> </div> <!-- end code snippet --> to <!-- start code snippet --> <div class="check"> <fieldset id="ndsumailformChoose_more_than_one"> <legend>Choose more than one</legend> <label for="lorem">Lorem</label> <input value="Lorem" id="lorem" name="lorem" type="checkbox" /><br/> <label for="ipsum">Ipsum</label> <input value="Ipsum" id="ipsum" name="ipsum" type="checkbox" /><br/> <label for="dolor">dolor sit amet</label> <input value="dolor sit amet" id="dolor" name="dolor" type="checkbox" /><br/> <label for="consectetur">consectetur adipiscing elit</label> <input value="consectetur adipiscing elit" id="consectetur" name="consectetur" type="checkbox" /><br/> <label for="nulla">Nulla hendererit mauris sit amet mi</label> <input value="Nulla hendererit mauris sit amet mi" id="nulla" name="nulla" type="checkbox" /><br/> </fieldset> </div> <!-- end code snippet -->

Detailed description

In Firefox, within the "Frame1" option of a "Border Content" content area, the left margin for bulleted lists <UL> seems to align too far to the left of the natural margin of the text to where the bullets appear to be butted up against the left border of the frame. I realize that Firefox & IE have differing spacing rules for bullets, but hopefully a correction can be made at the CSS level (or has already been remedied in v1.1) to move the bullets away from the border and more inline with the starting left margin of the text. Thanks!