The Metadata Plugin
Metadata Management for Manila
 
Site last updated
2/24/2006; 12:33:21 PM
 
Home

Why

Features

FAQ

Updates

Documentation

Download

Developers

Bugs

Feedback

Discuss

Planned
Features

 
 

Current Bugs

Author:   John VanDyk  
Posted: 8/9/2000; 9:21:13 AM
Topic: Current Bugs
Msg #: 213 (top msg in thread)
Prev/Next: 212/214
Reads: 21104

This is a list of current bugs.

BugReasonWorkaroundStatus
replyBehavior has not been defined Incorrect pref table assumption in behavior.dsp_buildForm Update metadata.root. Fixed in 4.16
A meta type named true appears. Name verification choking on empty string. Update metadata.root. Fixed in 3.62
Fields don't show up in new stories. Changes to custom input form logic. Update metadata.root. Fixed in 3.61
Can't coerce "table: 6 items" to an address Userland changed the value returned from manilaSuite.discuss.getDiscussionGroupAddress Update metadata.root. Fixed in 3.52
More reports expected
Can't find a sub-table named "MemberEmailAddress" Bogus assumption that deletion parameter always numeric. Update metadata.root. Fixed in 3.14
Can't evaluate the expression because the name "Changes" hasn't been defined. Uh...programmer error. Update metadata.root. Fixed in 3.02
Can't call "isStaticRendering" because there are too many parameters. Your manila.root is out of date. Update manila.root.
Can't find a sub-table named "0000000". calling mainresponder.
getCurrentMessageTable but it's a new message so there is none
Update metadata.root. Fixed in 2.23
Can't evaluate the expression because the name "selectname" hasn't been defined selectname variable was eliminated during ISO encoding changes in 2.20, but two instances were missed Update metadata.root. Fixed in 2.21
Can't find a sub-table named "prefs"." Behaviors pref has never been set so prefs table doesn't exist. Update metadata.root. Fixed in 2.02
Built-in meta type member is replaced by an empty string when members edit messages under some conditions. Possibly related to the security bug in metaEdit.act_processForm Disable members meta type when not in use. Possibly fixed in 2.00
constrainBy parameter nonfunctional in query() macro. Undefined variable, targetNum. Update metadata.root. Fixed in 1.90.
Messages deleted from the Admin box were not removed from the index. Userland changed key for deleting messages from Admin box. Update metadata.root, or delete using Admin page instead. Fixed in 1.87.
Sorry! There was an error: Can't find a sub-table named 'adrStorage' Bug in metaEdit.act_finalFilter in v1.84. Update metadata.root. Fixed in 1.85.
Incredible growing mailto tags in multiple templates Each time a template is edited, any e-mail address it contains is expanded by Manila Each time you edit, delete extraneous tags Fixed in 1.85.
URLs entered in text fields get munged. Manila's ActiveURLs don't respect our form! None. Fixed in 1.71.
Index gets out of sync with deleted pages. We need to trap for use of delete form in discuss view. Use Admin page to delete messages. Fixed in 1.72.
Macro error: Can't compile this script because of a syntax error when updating multiple templates. More... Namespace collision in IE5. Use Netscape. Fixed in 1.5.4.
Updating metadata.root fails and says something about madrid.userland.com. Something has stomped on your user.rootUpdates.servers.metaData table. Delete this table, run metaDataSuite.install again, and the new table will have the correct values. We haven't figured out what's stomping on this table; if you have an idea, let me know. Update: no reports in 6 months; we'll consider this one gone. Gone.
When Managing Meta Types, the Add button doesn't work for some people.POST/GET gridactions were not prioritizing correctly.Add subtables manually to the index or update to 1.5.3Fixed in 1.53
After enabling the plugin, a message about the table "#templates" not being found appears.subTemplate script did not handle the value nil.Update to 1.5.1.Fixed in 1.51.

If you can provide any information about current bugs, please do.

You can also enable logging to help you debug:

  1. create a boolean at scratchpad.safeguard
  2. in the script you are interested in, make sure the inital lines where myname and flDebug are defined are not commented out
  3. uncomment debugging code as needed
  4. the debug log will be an outline at scratchpad.metadatadebuglog

Don't forget to reverse all above steps, including destroying scratchpad.safeguard, when you're done.

Or, as of version 3.02, use the Debugging capabilities of the plugin.


There are responses to this message:


This page last updated Thursday, January 31, 2002 at 8:47:23 AM. (21104)