Updating Links

[jjw]

Updating links when renaming or moving a topic seems insanely slow in Flare 11. Maybe I'll go for a walk around the block ...

... Nope, still "computing dependency set".

J

[Nita Beck]

I assume that by now it's either resolved or you've used task manager to shut down Flare. You need to rebuild the Analyzer folder, as clearly it's gotten hosed or corrupted. With Flare closed, delete the Analyzer folder and then restart. Flare will rebuild it and you should be good to go.

[jjw]

Well I was enjoying the walk - but yes I did close it down.

I wondered if it might be the Analyser database, but I had recently pulled down the repository (without the analyser folder) so I assumed it would be OK. Will try your suggestion next week.

Thanks,

J

[jjw]

Flare's been going haywire all day. Finally disconnected it from git and all is well. Think I might stick with Git Extensions for now.

J

[SteveS]

Just a quick question - why are you including the Analyser folder in source control?

When I've had to use source control I've only added the original content. Things like topics, stylesheets, master pages and so on. Anything that can be created from original content (source) such as output I don't include. So, I wouldn't be including the analyser folders...

[Nita Beck]

I missed that subtlety. Yes, the Analyzer folder should never be put under version control, and nor should the Project\Users folder. (I also do not put the Output folder under source control, but others have a use case for doing so.)

In the Flare 11 Source Control Guide: Git guide (http://docs.madcapsoftware.com/FlareV11 ... ideGit.pdf, on page 7, you'll find a discussion about which files and folders to put into Git, if you're doing so manually. Otherwise, if you bind the project to Git from within Flare, Flare has been programmed not to include the Analyzer, Output, and Project\Users folders.

[jjw]

The Analyzer folder was not under source control (nor were the Output or the Project/Users folders). That's why it wasn't in the project when I pulled it down and I didn't think that deleting it would solve the problem. I did try deleting it later, but it didn't solve the problem.

As time went on, the problems became more widespread than just having difficulty updating links. Flare was pretty much unusable - just opening a folder would give it a conniption fit. As I said, I've disconnected it from Git and all is sweet. Perhaps I just didn't have it set up right, but it's beyond my troubleshooting skills and I have a git workflow that works outside of Flare.

J

[Nita Beck]

If you haven't already done so, pleaes report this as a bug. With the Git integration being so new, there may be some bugs that shake out now that weren't uncovered during the beta period.

[jjw]

I would have, but it's hard to know what to say that would be helpful in replicating the problem. I didn't receive any error messages - it would just hang or try to do the same thing over and over. And, since it was a Flare 10 project, it wasn't a nice, clean start.

So I'm not sure that reporting a bug would help much. If I try the Git integration again, I'll start from scratch rather than try to retrofit it to an existing project. Then I can grow my bugs in a sterile medium.

J

[Quirijn Vermeulen]

I don't think Git has anything to do with it. I'm working without any source control and I have also experienced this behaviour today. After killing Flare and then waiting for my floating license to become available again, I could reopen the project and perform the same task again without any delays or problems. I haven't had it return so far. *knock on wood*

[jjw]

You could well be right, but because the symptoms are so vague and difficult to reproduce it's hard to pin the cause down, or to submit a meaningful bug report. The only diagnostic information I have is that I removed the link to git (by editing the project file), and the application is now working correctly.

J

[nicholerich]

I am also experiencing the same issues when trying to move/delete/rename files. Yesterday afternoon Flare crashed on me several times and it's starting again this morning. I used the integration in Flare to bind the project to Git so I don't have the Analyzer or User folders in the repository. I'm new the whole Source Control thing but I followed the directions exactly as they were in the Flare user guide and everything seemed to be okay at first. It wasn't until I started editing the files that things became unstable.

[sdcinvan]

Flare's been going haywire all day. Finally disconnected it from git and all is well. Think I might stick with Git Extensions for now.

J

Hello jjw,

Just curious, are you using the git integration? Without ssh support?

[sdcinvan]

I am also experiencing the same issues when trying to move/delete/rename files. Yesterday afternoon Flare crashed on me several times and it's starting again this morning. I used the integration in Flare to bind the project to Git so I don't have the Analyzer or User folders in the repository. I'm new the whole Source Control thing but I followed the directions exactly as they were in the Flare user guide and everything seemed to be okay at first. It wasn't until I started editing the files that things became unstable.

Well that's concerning.

I can't use the git integration until it supports ssh. When it does, I expect the git integration to make my life easier, not more difficult.

[nicholerich]

I spoke with support and she had me delete the Analyzer, Output and Project>Users folders from the local project and it improved things considerably. However I am still experiencing some crashing but it could be my computer. I'm due for a new one and just waiting for the upgrade from IT.

[jjw]

Flare's been going haywire all day. Finally disconnected it from git and all is well. Think I might stick with Git Extensions for now.

J

Hello jjw,

Just curious, are you using the git integration? Without ssh support?

I was using the Flare integration. I can manage without the ssh support, it's just a nice-to-have for me. I've abandoned the in-Flare integration for now because of the performance issues.

J