View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002075 | Composr | news | public | 2015-11-13 00:08 | 2015-11-13 00:30 |
| Reporter | Patrick Schmalstig | Assigned To | Chris Graham | ||
| Severity | Minor-bug | ||||
| Status | resolved | Resolution | fixed | ||
| Product Version | |||||
| Fixed in Version | |||||
| Summary | 0002075: Composr 9.0.21: Blogs now considered high impact content instead of mid-impact | ||||
| Description | A user came to me telling me they weren't allowed to post blogs, getting an error "there are no categories at this time". After playing around with permissions and user level account permissions, I have determined the problem is somehow Blogs are on the same impact level as news now (high), instead of where they used to be (mid). | ||||
| Steps To Reproduce | 1. Use Composr 9.0.21. 2. Turn off submission of high level impact for users in global permissions. 3. Try to submit a blog as a user. 4. Error is thrown about no available categories. 5. Turn on submission of high impact content for users. 6. Repeat step 3. 7. User can now submit blogs. | ||||
| Tags | No tags attached. | ||||
| Time estimation (hours) | |||||
| Sponsorship open | |||||
|
|
It is mid from the cms_blogs module, it is high from the cms_news module. Nothing has changed. |
|
|
The user can't use the blogs though. The blogs is treated as high as well. I have confirmed this by going to the user's blogs tab (logged in as user) and clicking add blog entry at the bottom, giving me the no categories error unless I have high impact submission allowed. This didn't occur when I had version 9.0.20 |
|
|
You may be right about a bug actually, but I'm 99% sure it isn't 9.0.20, this release had a relatively small number of patches, and definitely nothing in the news library code. I think I can see where the issue is. |
|
|
Okay. It's probably another incompatibility then because I haven't modified blog/news recently either. |
|
|
I think it is that the *2nd* blog post by a non-admin didn't work, and never did, without this privilege. |
|
|
Really? I've had regular users post more than one blog before and it worked fine in the past. |
|
|
Fixed on your site now. It may be it did go wrong in some patch release, but not the last one. Issue was that it filtered by permissions on an EXISTING news cat, but not on a POTENTIAL news cat. So it worked once (for POTENTIAL) then failed. I have added special case handling for existing self-owned blog cat. |
|
|
Okay. Thanks Chris. I confirmed the fix worked. |
