This is probably related to the missing comments problem.
It’s on the Home page, just like before. Or do it as WayChung suggested, these are equivalent. Usually the idea is that you just publish from the Home page, and use the “Publication Queue” page if you need to check something.
I’m not sure if this is a mistake on my part. I copied and pasted 152 blurbs from my notepad this morning into bilara. Somehow, 15 of them didn’t get committed. I’ll monitor the situation to see if it happens again. If it doesn’t happen again in the future, then I’ll chalk it up as my mistake.
Probably these should be linked here because they are likely associated with the recent changes to the data structure:
Oh! It seems the first has already been fixed. Bravo!
To reproduce this issue, while the system is still writing (while the box is still in orange as shown below), go to another blurb, make a quick modification, and then press enter before the previous write goes green.
This issue is reproducible if you commit another change while the previous write is still ongoing. I think this issue is a potential showstopper because changes may be lost and the translator may not be aware unless they check.
It seems only those files are present in our projects where something had already been committed in the old Bilara. Files where nothing had been committed in the old Bilara are missing. This affects comments as well as sutta or vinaya files. Probably site and blurb files as well.
Before even typing one single character in the new Bilara I have 1353 changed files in my publication queue. I believe these are comments that were never meant to be published, but just as notes to myself. Except for 1 file: there should perhaps be the bu-pm somewhere, of which I have translated a few segments. However it won’t be easy to find it in the midst of 1353 files …
Question: What is the “my remarks” column meant for?
In the first case: do I have to move all the 1353 comments from the “comment” column to the “my remarks” column manually one by one? 
Actually, I don’t mind that much after all. I’ll likely publish primarily from the Home page as before.
Hi @ayyasoma I have adjusted the search parameters, and the issue has now been resolved.
On the navigation page, the “Publish” button currently appears only for projects one owns; this needs to be modified so that the button is also displayed for project participants.
@HongDa I have still a few outstanding pull requests for DE that have been created with the old Bilara. I am not sure whether or not new pull requests might interfere with them? Perhaps it is safer to merge these old ones before I start work in the new Bilara? (Whenever you find the time—you are of course quite busy right now! 
)
A post was split to a new topic: Partially translated pages show raw localization keys
Is Billara up and running?
At the old Bilara link I get only “500 Internal Server Error” message.
This is probably because the URL structure is slightly different in the new Bilara. If you go to the Home page https://bilara.suttacentral.net you should be able to get where you want to via the navigation.
Thank you, Venerable!
Now it is MUCH better 
My old link was https://bilara.suttacentral.net/browse
BUT, now I see Welcome to Bilara page and that’s it.
No tree with languages as before.
I clicked the right up corner link: Log in with Github, logged in, authorized igondha for something and got back to Welcome page. I’m stuck.
I don’t know … maybe your account needs to be activated? @HongDa ?
What is also strange is that after logging into Github and it brings me back to Bilara Welcome page, I still see “Log in With GitHub” button in the upper right corner. As if I was not logged in.
Hi @Brankoo
May I ask for your GitHub ID?
I have activated all the new accounts, you can have a try when you are have time.
Ven. @sabbamitta Got it, I will merge these PR.
That’s a pretty classic race condition bug, sounds like due to lacking logic to handle that in the workflow change:
I imagine old Bilara had logic to handle the race condition, so it is probably easiest to replicate that.
This is still a bug as a wrong link shouldn’t give a 500 error. It should generally either be a 404 or a redirect.
(a 500 is an unhandled server error and is pretty much always a bug in some way)
My GitHub ID is 58522757
My Username is Bundy-py and, as advised, in the profile I added my real neme: Branko
Thanks for taking care of this issue 
