Latest revision as of 12:34, 9 February 2008

Site

• Remove "index.php" from the URL.

Followed by: http://www.mediawiki.org/wiki/Manual:Short_URL/wiki.example.com/Page_title--Enabling_a_wiki_using_Apache_Rewrite

• Possibly point the root ("/") to Main_Page, redirecting the logo and the navigation box to it.

skins/MonoBook.php add in line 73:

<?php $this->data['nav_urls']['mainpage']['href'] = "/"; ?>

skins/MonoBook.php, line 161, replace:

<?php echo htmlspecialchars($val['href']) ?>

with:

<?php echo ($val['href'] == "/Main_Page") ? "/" : htmlspecialchars($val['href']); ?>

• Remove the PDF extension.

Commented out

require_once $IP . "/extensions/wikipdf/wikipdf.php";

in LocalSettings.php

FCKeditor 2.x - User's Guide

• Create "Introduction to the User's Guide" as the first section in the guide. (needs review)
  
• Replace textual examples with screenshots.
  
• InSpell Checking, introduce ieSpell, explaining the the spell checker depends on the editor settings.(need review)
  
• InCompatibilityadd a section for "Incompatible Browsers", explaining what happens on those browsers intead. (need review)
• "Anchors, Links and E-Mails" should be renamed to "Links, E-Mails and Anchors" (most used first). The page structure should follow the same order.
  
• Rearange the Formatting page using this order:
  • Bold, italic, underlined
    
  • Styles
    
  • Text layout and format
    
  • Fonts
    
  • Size and color
    
  • Subscript and superscript
    
  • Templates
• Move "Templates" fromText Formattingto a dedicated section.
  
• InContext Menu, use the standard screenshot box for the example, possibly containing a text with a link, and the context menu for the link (it's a little bit richer).
• The HTML samplein theSource Editorpage is wrong. The link is out of the <p> tag. It should be <p>This is my standard text written in the <a href="http://www.fckeditor.net">FCKeditor.</p>
• Document the File Browser.
  

CKFinder - Configuration

• Quick Start (enabling, license, baseUrl, baseDir)
• Access Control
• Images
  • Thumbnails
  • Scaling
• Resource Types
  • Built-in resource types (and their relation to FCKeditor)
  • Adding new resource type
• Security
  • Double File Extension (Apache issue)
  • Image Uploads (validating image size)
  • Html Extensions (to prevent against XSS File Header injection)
• Miscelanous (actually for now in PHP only: PHP doesn't support UTF-8 natively, that's why FilesystemEncoding exists in config.php. Linux stores file names as UTF-8, so we are ok there... but on Windows we have more complicated situation. Try to upload files with chinese and polish characters. Change FilesystemEncoding to see the difference (Make sure that you have enabled iconv in php.ini - modify xampp/apache/bin/php.ini + restart Apache)). For example on my Computer (Win XP/SP2 PL), creating and deleting folder named "żółtko" is possible only with FilesystemEncoding set to CP1250.

In the example with three roles (admin, user, guest)Access Controlthe default configuration should be to deny everything.

• Actually, we have to change it. Separate function is now used to authenticate user. So default permissions to allow everything to everyone remained. We should remove the wrong examples and give instead something less complicated:
  All other connectors could have something similar: Developers_Guide/PHP/Configuration/Access_Control
  
• We should warn users about direct access to files via URL.
  

• CKFinder for ASP.NET i snot anymore using an XML file for the configurations. It uses now config.ascx, so the documentation must be changed to reflect it.

FCKeditor - Developers Guide

• write the descriptions of some of the configuration option left :Configuration Options
  • EditorAreaStyles
  • RemoveFormatTags
  • HtmlEncodeOutput
  • IgnoreEmptyParagraphValue
  • DisableFFTableHandles
  • FloatingPanelsZIndex
  • ShowDropDialog
  • ToolbarLocation
  • AllowQueryStringDebug
  • PreloadImages
  • LinkBrowserURL
  • ImageBrowserURL
  • FlashBrowserURL
  • LinkUploadURL
  • ImageUploadURL
  • FlashUploadURL
  • SpellerPagesServerScript
• also the configuration option should be categorized
• write the Debug and Debug Object section of theDebuggingpage
• review the guide for links that should appear in the text linking to sections which weren't build yet
  • I found that inUpgradingthere's a link to the SVN section. We must detrmine if the SVN section should be build or not
• actually this is more a wiki issue: some sample code can't be applied to the site because of the wiki security settings which sometimes unables to write a full example in the instruction. E.g .AFP - handling the posted data and Updating Aspell on Unix. We should work it out somehow.