Flare is crashing when I toggle the File Review Inbox pane to ALL so that I can see others submitted reviews. I closed the file but now can't find the review file to accept the reviewers comments. It's a fatal crash loop at this point blocking my ability to retrieve any submitted files. Crash report was submitted but I cannot complete any review work at this point.
Anyone experience this too?
Error:MadCap:creatorCentralUserId' is a duplicate attribute name
-
Kathleen McC
- Jr. Propeller Head
- Posts: 7
- Joined: Tue Nov 15, 2022 12:34 pm
Re: Error:MadCap:creatorCentralUserId' is a duplicate attribute name
Hi Kathleen McC,
I am facing the same issue. Did your issue get resolved?
If yes, let me know the workaround or solution.
Regards,
Ruchira Joshi
I am facing the same issue. Did your issue get resolved?
If yes, let me know the workaround or solution.
Regards,
Ruchira Joshi
-
Kathleen McC
- Jr. Propeller Head
- Posts: 7
- Joined: Tue Nov 15, 2022 12:34 pm
Re: Error:MadCap:creatorCentralUserId' is a duplicate attribute name
Hi Ruchira!
Yes, I did receive assistance and a fix that’s worked for two team members who’ve run into the issue with a third on the horizon. We received stellar support from Technical Customer Support Specialist Thamina who helped us resolve the issue—5 stars Thamina
Apparently a previously known issue in Flare has been rectified and the most recent MadCap Flare 2023 r2 has been fixed. We use MadCap Central as our source control repository and content delivery platform, so the following fix applies to that configuration. The fix is all about clearing cache and performing consistent Flare/Central hygiene on your local files. A good best practice is to Install Git for Windows.
Instructions
With Flare closed, and from the Windows File Explorer,
1. Launch your html 5 output
2. Open your browsers Developers tools console and then right-click the Reload/Refresh page button.
3. From the drop-down menu select Empty cache and hard reload/refresh
Back in File Explorer,
1. Delete the following folders from whatever Flare project you’re working in:
• Analyzer (lives at the root level)
• Output (lives at the root level)
• Users (lives under Project/Users)
2. Restart your whole machine.
You should be good to go!
(the image i tried to insert after step 2 doesn't seem to stick...)
Yes, I did receive assistance and a fix that’s worked for two team members who’ve run into the issue with a third on the horizon. We received stellar support from Technical Customer Support Specialist Thamina who helped us resolve the issue—5 stars Thamina
Apparently a previously known issue in Flare has been rectified and the most recent MadCap Flare 2023 r2 has been fixed. We use MadCap Central as our source control repository and content delivery platform, so the following fix applies to that configuration. The fix is all about clearing cache and performing consistent Flare/Central hygiene on your local files. A good best practice is to Install Git for Windows.
Instructions
With Flare closed, and from the Windows File Explorer,
1. Launch your html 5 output
2. Open your browsers Developers tools console and then right-click the Reload/Refresh page button.
3. From the drop-down menu select Empty cache and hard reload/refresh
Back in File Explorer,
1. Delete the following folders from whatever Flare project you’re working in:
• Analyzer (lives at the root level)
• Output (lives at the root level)
• Users (lives under Project/Users)
2. Restart your whole machine.
You should be good to go!
(the image i tried to insert after step 2 doesn't seem to stick...)