Be sure to checkout our newest add-on Reading Time Pro!

EE4 compatibility updates:

  • Publisher is EE4 and EE5 compatible, but it does not currently support the Fluid field (it's in the works).
  • Reel is EE4 and EE5 compatible, but it does not currently support the Fluid field.

Ticket: Categories issue: Entries do not show in some categories and sure not in new created ones

Status Resolved
Add-on / Version Publisher 2.10.6
Severity
EE Version 5.1.2

Werner Gusset

Jan 14, 2019

Hi
Have a live site that after upgrade from EE3 has a problem with new entries to a certain category set. If the new entry is assigned to the first category of the set, we don’t see it on the web. If we set the entry to other categories in the set, it shows up on the web.

If I create a new category in that set and assign an new entry to it, it doesn’t show on the web. I mean, it doesn’t show on that category page.

I know how difficult such a bug description is. But what shall I do? My customer is in anger.

PS: the site has the small fix to show the categories in the translation section.

Werner

 

#1

BoldMinded (Brian)

Jan 14, 2019

Few questions:

Did you try to replicate this in a brand new EE 5 environment?

What is a “category set”? - Do you mean category group?

Can you provide a video of what you’re describing b/c it is hard to understand what you’re describing.

#2

Werner Gusset

Jan 15, 2019

Category set is a category group. Sorry

What happens is this: we have categories 1 to 4. A new entry assigned to category 1 does not show, but assigned to category 2, 3 or 4 does show it.

Creating a new category and assigning the entry to it does not show it on the sites category page.

Earlier yesterday a created a new channel, a new category group and categories and new entries that were assigned to does categories. All worked well. So no need to test on a brand new EE 5 because doing things new seems to do well.

It is with the existing category group where we have troubles.

BTW: This we can see in the Developer Logs

Deprecated function url_title() called in /user/addons/publisher/vendor/litzinger/file-field/src/FileField.php on line 81.
Deprecated since 4.0.0. Use ee('Format')->make('Text', $str)->urlSlug() instead.
#3

Werner Gusset

Jan 15, 2019

Comment has been marked private.

#4

BoldMinded (Brian)

Jan 15, 2019

The deprecation warning is nothing to worry about, its totally unrelated to anything having to do with categories, and it’s just a deprecation notice, nothing is broken.

I am traveling for work for the next 3 days, so it may be awhile before I can look into this. In the mean time, can you please record a video of what you are describing and add it to the ticket? (a link to a Dropbox file or something similar is fine)

#5

Werner Gusset

Jan 16, 2019

It will take some time to do the video. My client wants me to fix the problem now. So we put the content from that not showing category 1 into a new channel and change template. I need to do such a fix subito and continue with other new stuff. So it’ll take a while to get to that video.

#6

BoldMinded (Brian)

Feb 15, 2019

Comment has been marked private.

#7

Werner Gusset

Feb 15, 2019

Comment has been marked private.

#8

BoldMinded (Brian)

Feb 15, 2019

I don’t know when Publisher 3 will be ready. I have some things working in Fluid fields, but not others, so it’s going to take more time. It also requires 4 new hooks to EE’s core codebase, so EllisLab would need to approve those and then release a version of EE that contains the hooks. It could be 1-3 months before its completed and released. Have you considered trying Bloqs? It works fine with Publisher.

#9

Werner Gusset

Feb 15, 2019

Comment has been marked private.

#10

BoldMinded (Brian)

Feb 15, 2019

The two main differentiators are that Bloqs has a nesting feature, which lets you build and nest your content as you normally would if you were building static html pages. https://eebloqs.com/documentation/nesting. The other main difference is that each block is a group of fields (atoms). With Fluid, you add 1 field at a time and they have no relationship to each other. With Bloqs, you can have 2 or more fields in the same block, so they’re more related to each other. For example, you can add fields to a block that give that block certain characteristics… basically configuring the block as you build it. There are advantages to using a native solution, I won’t argue that, but Bloqs does have additional features that Fluid probably will never have.

#11

Werner Gusset

Feb 16, 2019

Comment has been marked private.

Login to reply

Contact

For add-on support, please use the Support section. General inquries and pre-sale questions can be sent to support@boldminded.com.