Closed eikhart closed 1 year ago
Are there any errors in your web browser's network monitor or in the Craft logs involving Neo?
Console:
I found this in web-log, at the same moment I made the request:
2023-10-05 07:15:11 [web.INFO] [yii\db\Connection::open] Opening DB connection: mysql:host=db;dbname=db;port=3306 {"memory":1853088} 2023-10-05 07:15:11 [web.INFO] [yii\web\Session::open] Session started {"memory":3607288} 2023-10-05 07:15:11 [web.INFO] [nystudio107\codeeditor\CodeEditor::bootstrap] CodeEditor module bootstrapped {"memory":3850768} 2023-10-05 07:15:11 [web.INFO] [nystudio107\codefield\CodeField::init] Code Field plugin loaded {"memory":4209328} 2023-10-05 07:15:11 [web.INFO] [lilthq\craftliltplugin\Craftliltplugin::init] Lilt plugin loaded {"memory":5876552} 2023-10-05 07:15:11 [web.INFO] [nystudio107\emptycoalesce\EmptyCoalesce::init] Empty Coalesce plugin loaded {"memory":5965640} 2023-10-05 07:15:11 [web.INFO] [jalendport\fetch\Fetch::init] Fetch plugin loaded {"memory":6043512} 2023-10-05 07:15:11 [web.INFO] [mmikkel\retcon\Retcon::init] Retcon plugin loaded {"memory":6901192} 2023-10-05 07:15:11 [web.INFO] [craftsnippets\tableofcontents\TableOfContents::init] Table of contents plugin loaded {"memory":7374104} 2023-10-05 07:15:11 [web.WARNING] [craft\web\View::createTwig] Twig instantiated before Craft is fully initialized. {"memory":7490000} 2023-10-05 07:15:11 [web.WARNING] [craft\elements\db\ElementQuery::prepare] Element query executed before Craft is fully initialized. Stack trace:
2023-10-05 07:15:11 [web.INFO] [application] Request context: $_GET = [ 'p' => 'admin/actions/elements/recent-activity' 'site' => 'com' 'dontExtendSession' => '1' 'v' => '1696490111213' ]
If possible, could you please send your composer.json/lock and database backup to plugins@spicyweb.com.au, along with information about which site/section this happens with, and we'll have a look at it.
Cool, the latest update to "spicyweb/craft-neo": "3.9.5", seems to have squished this bug :) \0/
Oh awesome, I'm guessing it was related to us not passing through the site ID when lazy loading new blocks, which had some other side effects as well (e.g. issue with entries fields #800). I'll update the changelog to note this is fixed in 3.9.5, but please do let me know if it happens again.
Bug Description
Have a multisite setup. Neo works just fine in site A site B is in the same site group, but another language
I try to add a new entry to site B, but a new Neo block is not created. Instead the loading spinner keeps loading.
Good to know, possibly related: within the neo block, an entry field is used (i use it to wrap a link around the block that points to a related entry). Why possibly related? Because that is the big difference betwene site A and site B: site B doesn't have entries in this section yet
In console.log in can see that script hangs on this bit of code:
Input.js, line 1155:
So it seems that Tabs aren’t loaded. I have no idea why tbh
Steps to reproduce
Expected behaviour
No response
Neo version
3.9.4
Craft CMS version
Craftcms pro 4.5.6.1
What is the affected Neo field's propagation method?
Well, tried all of them. Currently using ‘Save block to all sites the owner element is saved in'
Does this issue involve templating, and if so, is eager-loading used?
This is not a templating issue