Writing a journal post not possible in Traditional Project?

I want to add a journal to a newly created Traditional Project. I am the creator and admin of that project, but cannot find a link to start a new journal post. However, I can edit the URL by adding /journal to bring me to the project’s journal page. It won’t let me finish it, though.

Platform: Website

Browser: Firefox

URLs (aka web addresses) of any relevant observations or pages:

Screenshots of what you are seeing:
https://www.inaturalist.org/projects/trems-bfw/journal leeds me here:

I can start a new post…

…but clicking on ‘Publish’ won’t let me save.

I open my project and link is under the map. https://www.inaturalist.org/projects/birds-with-deformed-beaks

you are admin, but you have neither the manager nor curator role. was that on purpose, or is this another case similar to what’s described here (https://forum.inaturalist.org/t/problem-creating-a-custom-project-list-for-a-traditional-project/29683/9)?

1 Like

@carnifex it looks like you were able to publish a journal post? https://www.inaturalist.org/projects/trems-bfw/journal/62784-test

For what it’s worth, I tried to replicate the issue but couldn’t.

I created a new traditional project: https://www.inaturalist.org/projects/new-tony-test

I saw the “create a post” text under the map:

And was able to publish a journal post: https://www.inaturalist.org/projects/new-tony-test/journal/62790-this-is-a-test

I’m also both an admin and manager:


Yes, eventually I was able to do this. Here’s how:

Upon creating the project, I apparently, as pisum mentioned, did have neither a manager nor a curator role.
I then asked another user to join the project, passed my admin role over, and subsequently received the role back.

Only then I could see the ‘create a post’ field

that’s at least the 3rd time this has been reported in the forum on the last few days. seems like there’s a bug somewhere. these are the other 2 reports:

it doesn’t seem like this is consistently reproducible, but i think iNat staff have a way to look through old server logs to see what exactly happened when the problematic projects were created, and that might be the most efficient way to troubleshoot.


Similar with mine, I created the project and while I was listed as Admin, I wasn’t listed as Manager or Curator and couldn’t do a lot of things with the project. I ended up deleting the old and remaking it, which fixed the problem.

1 Like

@carnifex I tested out a few different things here based on your proejct and when I create a new traditional project and include a required observation field, I think I’m able to get my project into the same dire straits. I wrote a bug report on GitHub.

@pisum thanks for bringing up those other reports.

1 Like

Now, this is probably unrelated, but I noticed this in the course of tackling the issues:

In the project’s member view it is stated:

Managers can do everything curators can do as well as editing project settings and write project journal posts.

However, having a Curator role I could also write journal posts.
Intended behaviour but text needs to be corrected?

1 Like

@carnifex I think that aws part of the problem. An update has been released to prevent it from happening again and any project which suffered from this issue should be fixed as well, so I’m going to close this.