Could anyone assist in how to report this problem as an issue on codeberg?

I was only able to post this as a “Link”

Strangely, a post is made as I can view it from my profile, but it’s just not visible in the magazine unless I log out.

Here is the error I receive.
The post is visible in my profile.
Not visible in the magazine.
Unless I log out, then it IS visible

I just don’t know how to word this to report an issue. It’s so strange.

I have not been able to post “Thread” or “Photo” for over a week. There is another post about this as well, but it doesn’t seem to be seen by many either.

  • QualifiedKitten@kbin.social
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    I am also having this problem. I don’t have any domains blocked and when I check my profile from a logged out browser, my attempted posts are NOT visible there either. I’ve been unable to post pictures since at least 17th of August, and haven’t had any other types of content worth trying to post.

  • e569668@fedia.io
    link
    fedilink
    arrow-up
    2
    ·
    1 year ago

    Check if your issue is https://codeberg.org/Kbin/kbin-core/issues/1019
    the last few posts to this magazine have all been people saying they can’t view posts / comments when logged in but can when logged out (which you might not be able to see of course if it is this issue, as they were all posts and not links). Try removing all blocked domains to see if you can see them again.

    Edit: To be clear, this is to fix being able to see the posts after the error, not fixing the error. My current working theory is:

    1. users on kbin.social get an error when posting. the post is made, but with an empty domain field
    2. kbin.social users with any domains blocked, regardless of what they are, will not be able to see the post or comments if they open the post via url
    • McBinary@kbin.socialOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Hmm, I had ‘exploding-heads’ blocked. I unblocked that domain and now I am able to see the old thread I posted while logged in. Very weird.

      I still get the error when creating new threads, but they do show up now.

    • McBinary@kbin.socialOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Oh wow. I could not see any of those other threads about the issue either! Now I see a bunch of them after unblocking that domain.

  • cacheson@kbin.social
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    What seems to be happening is that your post is being sorted incorrectly in the default “hot” view. This was also happening when I first joined kbin, albeit without the error page when posting. Your “logged out” image shows the “newest” sort order, however.

    The workaround is to immediately go back to the magazine’s main page after posting and switch to the “newest” sort order. Your post should then show up at the top. Upvote your own post, and then it should appear correctly at or near the top of the default “hot” view.

    • McBinary@kbin.socialOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      This was totally the answer - it appears having any instance blocked at all is causing threads to be filtered out of view, even my own. Unblocking all domains fixes the issue for me and there are a LOT more recent posts than I was seeing previously.

      • cacheson@kbin.social
        link
        fedilink
        arrow-up
        2
        ·
        1 year ago

        Gotcha. On my end I haven’t blocked any domains, so I’ve just been experiencing the sorting bug.

        • FfaerieOxide@kbin.social
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          I just tried unblocking the only domain I had blocked (lemmy.nsfw) but any attempt at new threads or photos (although clearly not replies) Shows up “We Are Working On The Error”.

            • FfaerieOxide@kbin.social
              link
              fedilink
              arrow-up
              1
              ·
              1 year ago

              Threads may be working like 80% (still some reported issues from other users about first replies) after I unblocked lemmy.nsfw