Jim M

This has been resolved for you. Please see your ticket.

Could you please elaborate where you're receiving that? Is that in the ACP? If so, please ensure that your account is not limited.

As you're on V5, you can also click the "Quick Links" drop down in the ACP and click it there:

The database itself is the problem as it contains the template so you need to change the database settings for that database to use a new template which is unmodified.

You will want to adjust the settings for your Database so that either your users do not have the ability to read/view the record or disable the database setting for "Users can see records posted by other users?"

Are you seeing any errors in ACP -> Support -> System Log?

Try clearing the cache by going to ACP -> Support -> Clear system cache.

You would switch the template to a different if the template is not compatible

This is not currently possible. You can certainly request this in the Feedback forum.

This is currently by design that you can do this and has been this way for some time.

You would contact Backblaze for instructions on how to manually move things to their storage.

It can take some time for Google to remove the warning.

This is an access log, you'll want to get the error log to find the actual error.

Are your background tasks running? You can check this by search "Tasks" in the ACP and ensure that they are processing.

Have you tested in an incognito window in Chrome to see if this is related to any extensions/plugins in the browser itself?

It is not possible to move a topic to a blog. You can create a blog entry which has content which is just a link to the topic but that's about it.

If you do not have a category available for your Blog, you will need to create one.

Keep in mind that there are categories to categorize your blogs and categories to categorize your blog entries within your blog. When creating a blog entry, you need to select to create a new category or use an existing one:

We're trying to login to your site and look at the error in question so we can troubleshoot it. We need access in order to do that. Currently, the credentials are invalid.

This would be the one on file in the Client Area.

The notification options are still available at: /notifications/options/ You can access them by going to the notification bell -> notification settings.

Google will only crawl the site a set amount per attempt. Our software helps prioritize certain content over others natively via robots.txt, metatags, etc... Google though has it's own internal algorithm on how and what to crawl. A site map will help guide it crawling your site but is by no means, it's only roadmap. You, theoretically, could manually submit certain forums (or other content types) sitemaps which our software generates to search engines. I, personally, do not see much value in doing so. It may just in slow down the speed at which Google indexes content of your website with limited to no other value. Personally, I would focus my efforts on gaining traction to the new domain, whether that is social media, emailing your previous members, other forums, etc... That will hopefully help revitalize the community and get new posts going which Google will pick up and like as it also goes through older posts. In the end, content is king. If the content is good, Google and other search engines will crawl it and pick it up in accordance to their algorithms. Correcting errors and guiding it with our native SEO improvements should help along the way.

Unfortunately, this bug is still open and being investigated. We're hoping for 5.0.6 but again, that is not set in stone. I apologize it is taking so long. We often triage bugs in order of mass impact to our customer base, additionally, some bugs simply take longer to resolve than others, may require a more involved resolution than may be initially apparent once we get into QA, or many other scenarios which may impact its release.

I'm sorry you didn't like my reply but as I mentioned, you are actually receiving a reply significantly faster than current policy states. All replies in this topic have been less than 2 hours after your posted question or follow up. I'm more than happy to pass along any feedback on how we can do better though.

To confirm, it was working on 5.0.4 but not on 5.0.5? If so, if you upload the same photo here from the user does it do the same?