Update your settings

I created my first group and created a blog entry and when it came down to who has visible access to it there was a ton of selections. At first I selected Realms Knight as that's the subscription I have and it was all fine for viewing. Then I decided to make it public so anyone visiting the site could view it and then I got this attached image message...and when I went back I switched it to Wrealms members and got the same thing...

Now when I click on the blog on my own page of the blog that I created I can't access it? xD

How does the creator of a group not have permission to their own blog? xD I am still logged into my own account so I am at a loss. Especially if I wasn't I had made it for Wrealms members/public?

Can you please share with me the name of the blog? (Or link?) I'm cycling through things right now but can't seem to figure out which blog it is. I'm trying to recover the blog for you, as blogs are disabled for most members in our group settings. Blogs weren't meant to be used in groups, as we felt it would take away from the initial blog section of the website. However, as the group settings have yet to be configured, there was a loophole where subscribers were allowed to make blogs. 

Attached is the screenshot from my page under the Blogs. I had to create a duplicate Blog though this is the specific one and whenever I click on it I get that link previously screenshotted.

this is the link: http://wrealms.site/blog/dorian-s-homes

and this is the screenshot to help for viewing on my page if possible?

There is another blog over it with the same title and that other one is the new one I had to create which is fine though it is this one specifically when I click onto it, it will not allow me to view or even edit or anything.

This issue has been "fixed" as blogs were never meant to be posted in groups which is why they only showed for a short time before becoming unviewable.

As usual, I am closing this topic in order to keep up with bugs that have been fixed/completed. If an issue persists or a new bug is found, please feel free to open a new topic and we'll address it as soon as possible!