Jump to content
  • Status: Not a bug

When creating a blog entry, an option is missing : "Use an existing entry category".

usecategory.png

This option exists in moderator editing.

User Feedback

Recommended Comments

Esther E.

Invision Community Team

I can't reproduce this. Is this the first entry in that particular blog?

Adlago

Clients
7 hours ago, Esther E. said:

I can't reproduce this. Is this the first entry in that particular blog?

Follow this scenario:

1. Create a blog category in ACP

2. Create a blog in this category again in ACP.

3. Open Blogs-This Category in site, and click on Add New Entry. From the drop-down menu, select the blog created in ACP from this category.

The loaded form is missing the option that I am reporting here.

Esther E.

Invision Community Team

Yes, it's a bit confusing, but it's not a bug. Blog categories and Entry categories are not the same thing.

Adlago

Clients
12 minutes ago, Esther E. said:

Yes, it's a bit confusing, but it's not a bug. Blog categories and Entry categories are not the same thing.

But why is there no option to choose, and now it is forced to create a category.

It turns out that I only have one category (in settings the same as the others) in which this option exists.

It seems that there is some kind of mess in blog templates - and blog installation for me is clean - before version 5 I have not used blog APP.

If this is not a bug, please create a support ticket and remove this mish-mash from my blog.

thanks

Esther E.

Invision Community Team

There's nothing for us to remove. There are categories for blogs and then within each blog, there are categories for entries. If this is the first entry in that blog, you would be forced to create an entry category.

Adlago

Clients
10 minutes ago, Esther E. said:

There's nothing for us to remove. There are categories for blogs and then within each blog, there are categories for entries. If this is the first entry in that blog, you would be forced to create an entry category.

I saw that, thanks. But why don't you remove this confusing category within the category - wouldn't it be more correct to be a subcategory?