All add-ons currently require PHP 7.4 or greater.
On July 4th 2024 PHP 8.2 will be the new minimum requirement for all add-ons. Expect any add-on released after that date to require 8.2 or greater. Some releases may not immediately take advantage of 8.x specific features in PHP, which means you might, be able to continue using new releases in PHP 7.4, however, if you experience an error the first thing you should do is update to PHP 8.2 then create a support ticket if the error persists.
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: Structure Listings not
| Status | Resolved |
| Add-on / Version | Publisher 3.10.1 |
| Severity | |
| EE Version | 6.4.13 |
Jelle / Karres en Brands
Jun 30, 2023
Hi Brian,
experiencing an odd one. I updated publisher to v 3.10.1 and my paginated listing stopped working if they were in a Structure managed page.
If i stick the exact same channel entries tag in a structure managed page i get no results, but in a template_group/template scenario it works just fine
This is what the template debugger says:
{exp:channel:entries channel="news" disable="categories|member_data|relationships|trackbacks" paginate="bottom" limit="30"}
0.024535 / 8.0MB Calling Extension Class/Method: Publisher_ext/pagination_create
0.024783 / 8.0MB Calling Extension Class/Method: Structure_ext/pagination_create
0.025337 / 8.0MB Returning No Results Content
I have now solved the issue by reverting Publisher to 3.9.3 so not very urgent now
BoldMinded (Brian)
Can you share your pagination code and entries tag? Just the bare necessities, no extra HTML or EE tags in the mix.
Jelle / Karres en Brands
Hi Brian, I’m currently setting up a test server for this one, also to exclude server environment as a culprit. I’ll get back to you asap when i have more news, and maybe rule out Publisher
BoldMinded (Brian)
Yeah this one is a little weird b/c that pagination method hasn’t been updated in 2 years (long before v3.9). I guess it’s possible something further down the chain is causing the issue. I’m on vacation for the next few days so I might not be able to look into this one too much until the end of next week or the beginning of the next.
Jelle / Karres en Brands
Hi Brian, we can close this. somehow it fixed itself…
Jelle / Karres en Brands
So… somehow it’s come back. when i visit a pagination page i’m getting this from the debugger: 0.000031 / 8.6MB - Begin Template Processing - 0.000047 / 8.6MB URI: nieuws/P30 0.000050 / 8.6MB Template: _structure/_news_listing 0.000073 / 8.6MB Retrieving Template from Database: _structure/_news_listing 0.000504 / 8.6MB Retrieving Template from File 0.001339 / 8.6MB Calling Extension Class/Method: Publisher_ext/template_fetch_template 0.001392 / 8.6MB Template Type: 404
simplified template looks like {layout=”_layouts/_main_layout”} {layout:set name=”body_content”} {exp:channel:entries channel=”news” disable=”categories|member_data|relationships|trackbacks” paginate=”bottom” dynamic=”no” limit=”30”} stuff standard EE pagination tag {/exp:channel:entries} {/layout:set}
Exact same template works on another site that doesn’t have publisher in the mix
BoldMinded (Brian)
Are you viewing the page in the default language or another language?
Also, for shits and giggles, remove everything from the template except the channel:entries tag… remove the layout stuff and everything else.
Jelle / Karres en Brands
So I stripped it down to the bare essentials, and the same happens. But when i put my full template into a template group, so that it isn’t structure managed, everything works flawless. My guess is that Publisher isn’t looking for the right template when it’s an paginated page managed by structure.
BoldMinded (Brian)
Can you be more descriptive? Publisher doesn’t know what kind of templates they are. Do you mean you changed Structure’s setting so the channel was not managed by Structure?
Jelle / Karres en Brands
The site is managed by Structure, So in Structure we pointed the /news url use the “_structure/_news_listing” template. Which fails with: 0.000025 / 8.5MB - Begin Template Processing - 0.000039 / 8.5MB URI: news/P20 0.000042 / 8.5MB Template: _structure/_news_listing 0.000054 / 8.5MB Retrieving Template from Database: _structure/_news_listing 0.000572 / 8.5MB Retrieving Template from File 0.001120 / 8.5MB Calling Extension Class/Method: Publisher_ext/template_fetch_template 0.001153 / 8.5MB Template Type: 404
What i did was make a copy of the above mentioned template, and stuck it in the “dev/test-pagination” template So template routing for this url is not done by structure. And when i access that template on the frontend, pagination works just fine. 0.000033 / 8.6MB - Begin Template Processing - 0.000051 / 8.6MB URI: dev/pagination-check/P30 0.000055 / 8.6MB Template: / 0.000398 / 8.6MB Template Group Found: dev 0.000654 / 8.6MB Retrieving Template from Database: dev/pagination-check 0.001019 / 8.6MB Retrieving Template from File 0.001810 / 8.7MB Calling Extension Class/Method: Publisher_ext/template_fetch_template 0.001909 / 8.6MB Template Type: webpage
Howeer, this gave me an insight. Somehow it seems to bork on the leading underscore in the template name. because now i’ve changed the “_structure/_news_listing” template to “_structure/news_listing” and it works as it should. So kind of fixed…
BoldMinded (Brian)
Templates prefixed with an underscore are considered “hidden”, but I don’t think there is any logic in Publisher that cares about that.