Madcap Flare 6 breaks PushOK SVN plugin
March 25th, 2010 7 Comments
A word of warning for Flare users who also use the Subversion version control system (SVN). The PushOK plugin that provides SVN support in Flare does not work in Flare 6. As a result, although my team have licences for Flare 6, we may stick with Flare 5. If you're considering an upgrade to version 6 you may want to think again if you're currently using the PushOK plugin.
Flare has had built-in version control support for some time now - but only for Microsoft's Team Foundation Server and Visual Source Safe. If you use a non-Microsoft version control system you have to make other arrangements.
If you're a CVS or SVN user then, of course, you can just use something like TortoiseCVS or TortoiseSVN from within Windows Explorer. But in the past Madcap have pointed Flare/SVN users in the direction of the SVNSCC plugin produced by PushOK Software as a solution that allows you more or less the same functionality offered to TFS/VSS users, in terms of being able to work with a source control repository directly within Flare.
This worked OK in Flare 5. It wasn't brilliant, it was a little clunky, but it did work, and it provided real benefits. Specifically it made it easier for writers to update the repository and it made it less likely that you'd forget to get the latest version of a file before starting to work on it. Using the plugin has definitely resulted in fewer version conflicts to resolve.
Unfortunately, after installing Flare 6, try and get the latest version of files and you get this:
Unexpected exception: Access violation - KERNEL32.dll
After clicking OK, the Progress dialog box shows an error message like this:
Querying source control server. This could take several minutes.
: D:\Alistair\ITauthor\Flare-demo-project\itauthorflare\: CustomScc:GetLatestVersion - call failed with error code -15 (Nonspecific error.)The source control operation finished with warnings and/or errors. Press Close when you are done reviewing the messages.
This is really disappointing for a number of reasons:
- I'd obviously prefer us to use the latest version of Flare rather than having to stick on version 5.
- Flare 6 has been out a few weeks now and the forum shows no positive response from Madcap or indication that they're going to fix this. Yes, I know the plugin is third-party software, but Madcap do not provide their own alternative and have, in the past, suggested SVN users use this plugin: I found out about it via Madcap.
- I had to push to get my purchase request for plugin licences signed off and right now that's looking like a bad decision. I don't want to use something else. I don't want to write off that purchase. I won't get another similar purchase signed off next time.
- I generally have a high regard for Madcap, but in this instance I feel they've let me down. Subversion is not some weird, new, little used system. If you have Microsoft blinkers on you might think that, but you'd be wrong. Subversion has been around since 2000, it's the successor to CVS and is used in software companies around the world.
For more tales of Flare/SVN woes go to: http://forums.madcapsoftware.com/search.php and search for pushok.
Potentially similar posts
- Use the existence of a file on the server to determine Javascript behaviour in the browser – November 2010
- Madcap Flare tip – given key error – November 2010
- Madcap giveth and they taketh away – August 2010
- Madcap fixes PushOK issue in Flare 6.1 – July 2010
- Review of MadCap Flare V6 – April 2010
March 25th, 2010 at 11:32 am (#)
Thanks for pointing this out. I'll be keeping an eye out for this. I'm especially concerned with the last point you made: I also have very high regard for Madcap and their responsiveness. They don't always say yesto every request (nor should they), but I've come to appreciate that they usually have some kind of constructive answer.
March 25th, 2010 at 11:38 am (#)
Yes, I agree. They're usually pretty good at listening to their user community. So I'm hoping they will get together with PushOK and fix this - or provide an alternative solution to help us out.
March 27th, 2010 at 8:01 am (#)
Madcap have been in touch to say that they are "absolutely working on this issue actively." They hope to have a solution shortly.
I hope so too. Us SVN/Flare users just want to have the same version control functionality in Flare 6 that we enjoyed in Flare 5.
March 29th, 2010 at 9:36 am (#)
What version PushOk SVNSCC plug-in do you try to use?
What version OS do you use?
March 29th, 2010 at 11:34 am (#)
The file version of the file PushokSVNSCC.dll is 1.6.3.1.
The OS is Vista with SP2.
May 5th, 2010 at 7:54 am (#)
Any success on this yet? Have you tried the latest plugin 1.6.6.2 which support Subversion 1.6
http://www.pushok.com/user_view_subscr_archive.ph...
The article is dated May 16 2010 which is in the future so I don't know what that means.
Personally I would prefer if MadCap would support common source control systems directly instead of relying to 3rd party plugins. Visual Sourcesafe which they DO support is no longer being developed and TFS is a very expensive solution if you're a small team. Directly supporting SubVersion or any other open source system is the way forward.
May 5th, 2010 at 7:54 am (#)
Any success on this yet? Have you tried the latest plugin 1.6.6.2 which support Subversion 1.6
http://www.pushok.com/user_view_subscr_archive.ph...
The article is dated May 16 2010 which is in the future so I don't know what that means.
Personally I would prefer if MadCap would support common source control systems directly instead of relying to 3rd party plugins. Visual Sourcesafe which they DO support is no longer being developed and TFS is a very expensive solution if you're a small team. Directly supporting SubVersion or any other open source system is the way forward.