August 26, 2014 at 22:05 #5979ingridstrauhsParticipant
Hey guys, I saved my project for editing it later, but now when I try to open it I see the following message: “(011) Currently we are not able to load the project. Please try later”.
Can you help me, please?
August 27, 2014 at 07:31 #5980
What’s the name of your project? we’ll check it out
August 27, 2014 at 19:09 #5982
We’ve checked your project and it seems that there was an un-identified glyph in it, must be some character you added manually.
We removed this character and you should now be able to open your project!
If you can please tell us what was that glyph Unicode value, we will then try to find the problem with it
August 29, 2014 at 01:20 #5983ingridstrauhsParticipant
The glyph Unicode value was U+0040 (@). I can open my project now, thank you!
August 29, 2014 at 09:39 #5984
It seems that we found the problem causing this bug…
When adding a new glyph manually (@ for example) you can type it’s Unicode value in one of two options:
Any other way to write the value (U+40 U+040 x40). may result with an undefined glyph, and prevent the project from loading.
We’re adding a fix to this issue, Thanks!
April 27, 2016 at 09:00 #6636FontAlphaParticipant
Please Help..! My saved file won’t load up! It stuck at “51/110 y”.. I’m almost done designing the fonts.. project name ” Cyrillic English Ark”
April 27, 2016 at 10:11 #6638
October 29, 2016 at 18:28 #6679AaronParticipant
I saved my project for later and tried to open it and its displaying the 011 error code, can you help?
October 29, 2016 at 19:21 #6680
Yes, what’s your project’s name?
October 29, 2016 at 19:38 #6681AaronParticipant
October 29, 2016 at 19:59 #6682
OK, I think that the problem is with the project’s name, the “_” might cause a problem when trying to load the project.
Please open a new project, and save it as LGBT-font (use – instead of _)
Tell me when you’ve done it and I’ll insert the content of the other one into the new one, and we’ll see if it’ll work.
October 29, 2016 at 20:26 #6683
Well, I have found the bug somewhere else and fixed it. Please try to reload the original LGBT_Font and report if it is loading fine or not.
You must be logged in to reply to this topic.