MadCap Software Forums

Hmm...I wonder if the odd names are causing the entire issue?

The odd file names cause me an error on the OneDrive side, not the Flare side.
OneDrive doesn't like certain files (name too long, odd characters, whatever?) especially fllnks files in the \DepSets directory within the |Temporary ...

I'm wondering since I'm using a non-standard folder to backup if I can exclude \Analyzer and \Output folders from my backup using the method form the Microsoft link. Besides the file lock error, some files in those folders have odd names that cause issues with my OneDrive backups.

I store my files in a directory not automatically synced by OneDrive, but used the mklink /j command to make OneDrive back up that folder.
I don't see the problem continuously, but when I do it can either be the Temporary folder under output or the actual output folder for the target that causes the ...

We keep documentation in a folder outside on the Windows documents folder on out PCs.
I used the mklink command to make this separate directory part of my OneDrive backup.
I'm wondering why this appeared out of nowhere? Did OneDrive change something a few months back?

When I had the problem with Adobe collab sync, I could see the Adobe program was holding onto the problem file by using Resource Monitor.
When I use Resource Monitor to see what is holding open the problem files now I get no results.

I'm glad you tried disabling OneDrive backup. I see that was one ...

I am familiar with the Adobe problem and work around it by removing the collabsync file, and I've been harassing Adobe to fix that for some time.

But this new problem affects both HTML and PDF output and for the PDF it's not the Adobe process holding the files now. It may affect other outputs but ...

It just seems odd that Flare would have less permissions than I do as the user on this PC. I don't run it as an admin.

I may try running Flare as an administrator which involves jumping through a whole set of hoops with IT.

I am regularly getting this error. It started with Flare 2024 and continues with Flare 2024R2.
The path in the error can be the output folder for the Target or the Temporary folder under Output. And it's everything in that folder. I have to manually delete the folders. However, there is no problem ...

(2) Target has "Add content to head" enabled, with only the default "IE=edge" meta tag => The "Add content to head" setting is now disabled, but shows the new CSP meta tag (so this is added if enabled).

This WAS NOT my case.
I had projects with the 2023 default tag enabled in 2023R2. When I opened ...

Yes, that is what I already figured out.
My larger question is why Flare has decided to, by default, put different text in that box depending on the version of Flare running with no documentation on this that I can find in their release documents.

It appears that any inline formatting is broken with this change from 2023 to 2024 due to changes in content security.
Unfortunately I have to rely on inline formatting due to off capitalization rules for product names. I could eliminate the centering issue here by using styles rather than the ...

I have several Flare projects, many of which I inherited from other writers.
When I upgraded to 2024, I noticed some outputs had changed with text that is no longer centered on the web page. NotCentered.png
Previously the output looked like this.
Centered.png
Not every project did this, and I ...

When I have long parameter names in tables (or even headings) that cause problems with text being too long for the space allocated for it, I use a Zero Width Space (ZWSP) character (&#8203), inserting it where the break could occur. The advantage is the text won't wrap unless it is necessary. There ...

If I downgrade Ghostscript, our corporate policy may remove it from my PC (we are required to use latest versions of software for security reasons, subject to removal of older versions).
So I've started converting my EPS files to other formats.

A completely off-the-wall suggestion, but if she is an ex-colleague, could you get the IT bods at your work to see if they can recover the Flare project from her machine?
Ideally, yes. But since everyone is working offsite, we have not been able to get the laptop from her.
I am hoping someday we ...

It is in Source Control, but not bound to it, so it requires manual check ins which she did not do. ;(

I am sad to see this isn't an easy option. I am left in a situation where a former co-worker did not properly back her work up to our network and I have no way to recover her work.

I did import the Flare output into a new project. There is a pattern to what needs deleted in the files so I can ...

I'm getting this warning for several files in my project:
Warning: The file "filename.htm" has been modified after the build started.
The error can be repeated for several files. The most I have seen is 30 different files listed.

The odd thing is the files listed aren't ones I've been working on ...

I have to say I've been pretty disappointed with Flare 2019 R2.
I've been working with support but still don't have these issues fully resolved.

2019R2 obviously changed something in the way Flare displayed the tooltip and language selection lists.
Based on support's input I've been altering the ...

Second issue I am still seeing

I had some time to test, so I installed the December release of 2019r2. Unfortunately the same issues exist and I had to again roll back to the first Flare 2019 release. I've opened a new support case since neither of my original problems have been addressed.

I submitted this to MadCap technical support. After some research they reported that this is a new feature, added for section 508 compliance. I guess this fell under "Accessibility Improvements for HTML5 Output".
Per their response, the blue outline can be disabled by adding this code to the ...

Between these two issues and this one:
viewtopic.php?f=9&t=32054
I've rolled back to Flare 2019 after uninstalling 2019 R2.

Flare has confirmed the Tool Tip issue as a bug.
I have sent a sample translated project for the investigation of the second issue.

I think I'm going to roll back to the original Flare 2019 version for now, and skip the R2.

Still no update for this issue.
I haven't heard from MadCap support, but our organization sometimes blocks replies from them.