• Do not register here on develop.twiki.org, login with your twiki.org account.
• Use View topic Item7848 for generic doc work for TWiki-6.1.1. Use View topic Item7851 for doc work on extensions that are not part of a release. More... Close
• Anything you create or change in standard webs (Main, TWiki, Sandbox etc) will be automatically reverted on every SVN update.
Does this site look broken?. Use the LitterTray web for test cases.

-- ML

This is a known & documemnted issue. It can be done once the TWiki:Codev.PluginHandlerForContentMove is implemented.

-- PTh

And it's a bug, so there should be a bug report.

What you appear to be saying is that this bug will remain for all 4.0.releases, since the new handler, if agreed to, will presumably be only in develop, as the proposed handler is a enhancement and thus won't go into 4.0.x. I hope I am drawing the wrong inference from what you said, since it would be a shame for people not to be able to use the plugin because of this.

A better choice would be to fix it so that it follows TWiki:Codev.PluginsApiPolicie: then it would work properly with 4.0.x installations. Given your prominence, it's important for you to set a good example for other plugin developers.

How you wanted to bundle it with the Cairo version would be up to you, of course.


This has nothing to do with the API policies. If the Plugin cannot be notified of a topic rename there is no way to fix the data in the Plugin, also if done in the work area.

I am discarding this item since I track bugs in the TagMePluginDev topic.

Feel free to open an enhancement item and implement TWiki:Codev.PluginHandlerForContentMove

-- PTh

"This has nothing to do with the API policies."

I'm sorry, but that's not the case. The Plugin API policy specifically states to avoid writing files within the TWiki database, except for the plugin's work area, which I believe your plugin does. It doesn't (or shouldn't) matter who has written a plugin: if it violates API, there may be problems, as is the case with this plugin. It's especially important for the core developers to set a good example for other plugin writers by adhering to the policies, so that there need not be a major effort to fix plugins upon the next non-patch release.

While there are good reasons to add a handler of some sort when a topic or an attachment is moved to DEVELOP, Dakar doesn't have it. Something as fundamental as a plugin failing if a topic is renamed is, IMO, a bug.

"I track bugs in the TagMePluginDev topic."

AFAIK, all bugs -- aside from pre-Dakar or twiki.org bugs -- are supposed to be tracked in the Bugs database. f bugs are not tracked in Bugs, then it makes it very difficult to know the status of code and documentaiton. (If I'm wrong about this, I'm sure CDot will correct me.)


I am sorry you did not get my point: Even if I use the workarea I have no way of finding out of topic renames.

Where bug tracking of extensions is done: This is up to the developer to decide. Except for the preinstalled ones, which have to be tracked here.

-- PTh

That's because you're storing the information in the pub directory. If you were stored it in in meta data then there would be no need to find out about renames. It would just work.

But in the end it's up to you. It's a shame that many sites can't use your implementation of tagging, because it's a valuable asset, but it's your choice to make.


Summary TagMePlugin loses tags when a topic is renamed
ReportedBy TWiki:Main.MeredithLesly
Codebase 4.0.0, 4.0.1, 4.0.2, ~twiki4, ~develop
SVN Range Tue, 30 May 2006 build 10392
AppliesTo Extension
Component TagMePlugin
Priority Normal
CurrentState No Action Required


TargetRelease n/a
Edit | Attach | Watch | Print version | History: r11 < r10 < r9 < r8 < r7 | Backlinks | Raw View |  Raw edit | More topic actions
Topic revision: r11 - 2006-06-02 - PeterThoeny
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback