ThemeManager export bugs & ideas

A place to discuss the testing process in beta cycles or against SVN for the CMS Made Simple CORE package.
Locked
User avatar
kermit
Power Poster
Power Poster
Posts: 693
Joined: Thu Jan 26, 2006 11:46 am

ThemeManager export bugs & ideas

Post by kermit »

1. custom menus referenced in a template using the shorthand {menu} tag are NOT exported. if the menu is called using the full {module module='menumanager' .... } tag, they are.

2. global_content / html_blobs that are embedded in a template should be exported, as missing global content blocks cause smarty errors on page output; with the option to export the entire contents of these referenced blocks, or just export 'empty' ones of the same name (which is enough to eliminate the smarty errors in the target system until the user can populate them).

3. when exporting images, should have option to export the *actual* image, or generate 'blank' (some colored pattern or something) ones that are the same size (dimensions), type & filename as the originals. this goes along with #2 as images can be contained in embedded blocks, too (as can modules and tags, see #4)

2-3 notes: exporting 'blank' or 'generic' data allows an exported theme to be 'generic' and not branded to a particular site... some people may not want their graphics, logos or other content going along for the ride. but that content may be crucial to a template's layout...

4. theme manager should be smart enough to know if a template references items (modules, tags, etc) that aren't present in the target install and alert the user. perhaps a warning should also be given when someone exports a template containing 'non-core' modules and tags or other items that won't be included in the exported xml.

5. theme manager should give the option, on import, of renaming the 'theme' before it is imported.

6. themes need the option, at export time, to add 'readme' data to the output xml file (that is human-readable in the file, and not encoded like embedded files are). this information should be shown, if present, before import. the person exporting the theme could then include details about graphics requirements, custom menu and/or news templates, modules and tags used, and other design or layout info...

7. is there a stand-alone program available that can extract the contents of a theme xml file to the local filesystem? create one from files on it?
Last edited by kermit on Thu Mar 01, 2007 9:43 pm, edited 1 time in total.
eternity (n); 1. infinite time, 2. a seemingly long or endless time, 3. the length of time it takes a frozen pizza to cook when you're starving.
4,930,000,000 (n); 1. a very large number, 2. the approximate world population in 1986 when Microsoft Corp issued its IPO. 3. Microsoft's net profit (USD) for the quarter (3 months) ending 31 March 2007.
CMSMS migration and setup services | Hosting with CMSMS installed and ready to go | PM me for Info
Locked

Return to “[locked] Quality Assurance”