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: Some pages are showing an error after Update of EE to 7.3.5

Status Resolved
Add-on / Version Publisher 3.9.1
Severity
EE Version 7.3.5

Werner Gusset

Jul 06, 2023

The site was on EE 7.2.x before we updated to 7.3.5.
Now we get this error on a certain page.

[code
Exception Caught
Unknown model “Site”. Used in model “publisher:Category” for a relationship called “Site”.
ee/ExpressionEngine/Service/Model/RelationGraph.php:245

Stack Trace: Please include when reporting this error
#0 ee/ExpressionEngine/Service/Model/RelationGraph.php(212): ExpressionEngine\Service\Model\RelationGraph->prepareRelationshipData()
#1 ee/ExpressionEngine/Service/Model/RelationGraph.php(89): ExpressionEngine\Service\Model\RelationGraph->makeRelation()
#2 ee/ExpressionEngine/Service/Model/DataStore.php(187): ExpressionEngine\Service\Model\RelationGraph->getAll()
#3 ee/ExpressionEngine/Service/Model/DataStore.php(171): ExpressionEngine\Service\Model\DataStore->getAllRelations()
#4 ee/ExpressionEngine/Service/Model/DataStore.php(110): ExpressionEngine\Service\Model\DataStore->initializeAssociationsOn()
#5 ee/ExpressionEngine/Service/Model/Facade.php(79): ExpressionEngine\Service\Model\DataStore->make()
#6 user/addons/publisher/mod.publisher.php(491): ExpressionEngine\Service\Model\Facade->make()
#7 ee/legacy/libraries/Template.php(1808): Publisher->translate_category()
#8 ee/legacy/libraries/Template.php(1483): EE_Template->process_tags()
#9 ee/legacy/libraries/Template.php(624): EE_Template->tags()
#10 ee/legacy/libraries/Template.php(247): EE_Template->parse()
#11 ee/legacy/libraries/Template.php(177): EE_Template->fetch_and_parse()
#12 ee/legacy/libraries/Core.php(811): EE_Template->run_template_engine()
#13 ee/legacy/controllers/ee.php(53): EE_Core->generate_page()
#14 [internal function]: EE->index()
#15 ee/ExpressionEngine/Core/Core.php(268): call_user_func_array()
#16 ee/ExpressionEngine/Core/Core.php(124): ExpressionEngine\Core\Core->runController()
#17 ee/ExpressionEngine/Boot/boot.php(184): ExpressionEngine\Core\Core->run()
#18 index.php(173): require_once(’...’)
#18 index.php(173): require_once(’...’)

]

The page was OK before the EE update.

#1

Werner Gusset

Sorry, I had again to restore to the situation before updating EE 7.2.14 to 7.3.5 because of our customer. Now everything is running ok. Currently, we are not updating anything.

#2

BoldMinded (Brian)

Did you upgrade Publisher to the latest version?

#3

BoldMinded (Brian)

Did you upgrade Publisher to the latest version?

#4

BoldMinded (Brian)

“Now we get this error on a certain page” - What is on this page? What is special about it?

#5

Debra Weiss

I just upgraded to 7.3 and am getting this:

BadMethodCallException Caught Call to undefined method block_display_field()

ee/ExpressionEngine/Service/Template/Variables/ModifiableTrait.php:34 Stack Trace: Please include when reporting this error

#0 [internal function]: EE_Fieldtype->__call('block_display_f...', Array)
#1 user/addons/bloqs/Controller/FieldTypeWrapper.php(293): call_user_func_array(Array, Array)
#2 user/addons/bloqs/Controller/FieldTypeWrapper.php(348): BoldMinded\Bloqs\Controller\FieldTypeWrapper->call('display_field', Array, false)
#3 user/addons/bloqs/Controller/PublishController.php(565): BoldMinded\Bloqs\Controller\FieldTypeWrapper->displayField('<h1>Galleywinte...')
#4 user/addons/bloqs/Controller/PublishController.php(221): BoldMinded\Bloqs\Controller\PublishController->publishAtom(258, Object(BoldMinded\Bloqs\Model\AtomDefinition), 33, 'blocks_block_id...', '<h1>Galleywinte...')
#5 user/addons/bloqs/Controller/PublishController.php(109): BoldMinded\Bloqs\Controller\PublishController->renderBlock(33, Object(BoldMinded\Bloqs\Model\Block))
#6 user/addons/bloqs/ft.bloqs.php(291): BoldMinded\Bloqs\Controller\PublishController->displayField(33, Array, Array)
#7 ee/legacy/fieldtypes/EE_Fieldtype.php(325): Bloqs_ft->display_field(' ')
#8 ee/legacy/libraries/api/Api_channel_fields.php(383): EE_Fieldtype->display_publish_field(' ')
#9 ee/ExpressionEngine/Model/Content/FieldFacade.php(270): Api_channel_fields->apply('display_publish...', Array)
#10 ee/ExpressionEngine/Model/Content/Display/FieldDisplay.php(78): ExpressionEngine\Model\Content\FieldFacade->getForm()
#11 ee/ExpressionEngine/View/publish/partials/publish_form.php(133): ExpressionEngine\Model\Content\Display\FieldDisplay->getForm()
#12 ee/ExpressionEngine/Service/View/View.php(137): include('...')
#13 ee/ExpressionEngine/Service/View/View.php(106): ExpressionEngine\Service\View\View->parse('...', Array)
#14 ee/ExpressionEngine/Service/View/View.php(165): ExpressionEngine\Service\View\View->render(Array)
#15 ee/ExpressionEngine/View/publish/entry.php(5): ExpressionEngine\Service\View\View->embed(Object(ExpressionEngine\Service\View\View))
#16 ee/ExpressionEngine/Service/View/View.php(137): include('...')
#17 ee/ExpressionEngine/Service/View/View.php(106): ExpressionEngine\Service\View\View->parse('...', Array)
#18 ee/legacy/libraries/View.php(40): ExpressionEngine\Service\View\View->render(Array)
#19 ee/legacy/libraries/Cp.php(343): View->render('publish/entry', Array, false)
#20 ee/ExpressionEngine/Controller/Publish/Edit.php(558): Cp->render('publish/entry', Array)
#21 [internal function]: ExpressionEngine\Controller\Publish\Edit->entry('33')
#22 ee/ExpressionEngine/Core/Core.php(268): call_user_func_array(Array, Array)
#23 ee/ExpressionEngine/Core/Core.php(124): ExpressionEngine\Core\Core->runController(Array)
#24 ee/ExpressionEngine/Boot/boot.php(184): ExpressionEngine\Core\Core->run(Object(ExpressionEngine\Core\Request))
#25 galleywinter.dreamhosters.com/admin.php(139): require_once('...')
#25 galleywinter.dreamhosters.com/admin.php(139): require_once('...') 
#6

BoldMinded (Brian)

Debra are you working on the same project as Werner? Have you upgraded Publisher to the latest version?

#7

Debra Weiss

No, I just upgraded, saw that Bloqs was all kablooey, saw this thread, and posted my error. I should have posted in the Bloqs area. I’m going to try to upgrade from bloqs 5.5 to the most recent version to see if it helps. I will report back in a minute.

#8

BoldMinded (Brian)

Debra, after upgrading all add-ons if you still have issues please create a separate ticket. Thanks!

#9

Debra Weiss

Upgrading worked. So sorry to bother you!!!!

#10

Werner Gusset

Brian I am back to EE 7.2.14 and Publisher is on 3.9.1 and Bloqs on 5.0.6.

We first updated EE to latest and then Publisher and Bloqs to lastest, This situation lead into errors.

Should we first update your software and after that EE? We only could that sometimes next week.

BTW: Couldn’t you modify the dark page here a bit to have more visible input fields and buttons (why a black button on a black background)? It is always a little exhausting.

#11

BoldMinded (Brian)

I feel like this error is coming from a different field type, perhaps not one of mine. Have you tried to simplify your template to render only a single block at a time, and only a single field in a block at a time? The error is happening from this, line 292 of FieldTypeWrapper.php

} elseif (method_exists($ft, 'block_' . $methodName)) {
            $result = call_user_func_array(array($ft, 'block_' . $methodName), $args);

Which indicates that a field inside of Bloqs is trying to get called, and its ft.whatever.php file does not contain a “block_display_field” method or the method is not callable. None of my add-ons have an actual “block_display_field” method, so this looks like its coming from another 3rd party add-on… but you’ll need to simplify your template and figure out which it might be.

#12

Werner Gusset

I cannot do the things you request for testing. The site is live, and updating it will break some pages. It would only be possible if I set up a copy, which would only be sometime next week.

The only third-party field type within our Bloqs is from Wyvern (5.4.2). And we also use Simple Grids & Tables.

#13

BoldMinded (Brian)

You don’t have a local dev, remote dev, or remote staging site to test against?

#14

BoldMinded (Brian)

Search your add-ons directory for “block_display_field” and see if anything comes up.

#15

Werner Gusset

None of the add-ons contain that word.

#16

BoldMinded (Brian)

On the page in which the error is happening, what does your Bloqs template code look like? I don’t need to see extra HTML tags, just share the EE tags.

#17

BoldMinded (Brian)

Never mind, the issue is happening inside the CP, not front-end based on that error. I’m not able to replicate this. I’m using 7.3.5 as well and everything is working fine. I’m going to need more help from you to debug this. What are all the add-ons, specifically field types, that you have installed? Have you tried creating a new EE environment with only Bloqs installed to replicate the error? If this is happening in your CP, something is calling the LegacyParser library, which is what is causing the issue.

#18

BoldMinded (Brian)

Are you using Publisher’s Diff feature?

#19

BoldMinded (Brian)

Comment has been marked private.

#20

Werner Gusset

I will supply more details as soon as I have them, sometime this week.

#21

Werner Gusset

I don’t use the Diff feature. I have set up twice a test install that is on EE 7.2.14 and updated Publisher from 3.9.1 to 3.10.1 and the error happened twice. I know you would need more details and what’s the difference is between home and pages that do work. I cannot investigate for some days as there is another project I need to work on. As soon there is time I can come back to this.

Login to reply