Publisher does not support the Fluid field type. Please do not contact asking when support will be available.
If you purchased an add-on from expressionengine.com, be sure to visit boldminded.com/claim to add the license to your account here on boldminded.com.
Ticket: Creating a new article automatically selects a particular category (that is not wanted)
| Status | Resolved |
| Add-on / Version | Publisher 3.1.1 |
| Severity | |
| EE Version | 5.3.0 |
Bruce Sabalaskey
Jan 09, 2020
I am not sure if this is related to the other category DB problem in the other ticket of mine, but I notice the following behavior.
When I create a new article of a content type which has Category group ID 2 (Topics), one of those is always selected upon creation, cat ID 31 (Special Reports). This category is stand alone, that is without parents or children. If you uncheck it and save the article, it remembers. No categories should be automatically enabled.
BoldMinded (Brian)
Yeah, something is definitely out of whack. I’ve never seen Publisher move a category to a different group. It just isn’t designed to work that way, it doesn’t need to, that isn’t Publisher’s responsibility. Take a look at your exp_publisher_categories table and find that rogue category and manually set the group_id to the correct value. Then see if it fixes this issue and the other one you reported.
Bruce Sabalaskey
The exp_publisher_categories table is empty. The standard EE table exp_categories is correct. What is the next step?
BoldMinded (Brian)
Are you using Publisher or Pubilsher Lite?
Bruce Sabalaskey
Publisher 3.1.1 build 7b7aee1f
BoldMinded (Brian)
So if there is nothing in the exp_publisher_categories table it means you’ve never translated a category, is that right?
Bruce Sabalaskey
Correct. At this point, we do not use translations at all, everything is in English. Our use case of your add-on is the draft management and approvals by editors.
BoldMinded (Brian)
I can’t replicate this either. At this point, you’ll need to re-create the issue in a brand new EE environment with only Publisher installed, or provide a very very detailed steps to replicate and a video, otherwise I’m just walking around in the dark hoping to catch something.
Bruce Sabalaskey
This happens every time with any of my sites, multiple dev sites or the production site. Have you tried my main dev site https://dev.lifesitenews.com? (login details provided in the ticket regarding category Db not saving - I can send again if needed). I cannot even run without add-ons Assets, Structure and Tag modules, plus my own custom add-on with various template helper features. In the backend I use Wygwam and Zenbu. I guess I have to try uninstalling the backend modules and see what happens. All I know is that after I upgraded to 3.1.1 the problems started. Is there a method to revert back to 2.11.1?
BoldMinded (Brian)
Just letting you know that it’ll be a couple days until I can look into this and your other ticket. I have a company wide conference all week so my time is limited.
BoldMinded (Brian)
I just spent more time trying to replicate this, in two different environments. One being my dev environment and the other a large production site very reliant on category features. I can’t replicate it. Run the query in the other ticket to see if it might fix it. If it does not you’ll need to create the new/clean EE environment displaying the issue, then I’ll investigate it more.
Bruce Sabalaskey
Since this type of bug is somehow related to the data combination in my system, when I get a chance I will have to try and “renumber” the category using the add new, copy over, then delete old category and see what happens. Will let you know when I get a chance for that.
BoldMinded (Brian)
Sounds good. Until then I’m going to mark this resolved. Feel free to re-open it at a later date though.
Bruce Sabalaskey
Brian, After a while the problem was finally found. There was an entry in exp_category_posts table and exp_publisher_category_posts where the entry_id was 0 with that category which was always selected. That must have been related to the upgrade process fro 2.11 to 3.1. Once that row in the DB was deleted everything worked fine. Just wanted to document this in case it helps in the future.