You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
if you create a custom entity and register it for massive search for using in admin and website search, you get an error message that the custom entity is set private. Through this, you cannot save or delete posts in den custom entity.
It is an error in Sulu or in massive search? How can be fixed it?
Tested in Sulu Workshop, Sulu Demo (Sulu Rocks) and own projects
Expected Behavior
No 500 Error "Cannot access private property App\Entity..."
Actual Behavior
if you create a custom entity and register it for massive search for using in admin and website search, you get an error message that the custom entity is set private. Through this, you cannot save or delete posts in den custom entity.
It is an error in Sulu or in massive search? How can be fixed it?
Tested in Sulu Workshop, Sulu Demo (Sulu Rocks) and own projects
Expected Behavior
No 500 Error "Cannot access private property App\Entity..."
Steps to Reproduce
E.G. Sulu Workshop
Setup Repository:
https://github.com/sulu/sulu-workshop
Create Folder:
config -> massive-search
Create File:
massive-search -> Event.xml
Code:
<?xml version="1.0" ?> <massive-search-mapping xmlns="http://massiveart.io/schema/dic/massive-search-mapping"> <mapping class="App\Entity\Event"> <id property="id" /> <title expr="join(' ', [object.getTitle()])" /> <url expr="'/events/' ~ object.id" /> <index value="event" /> <locale property="locale" /> <fields> <field name="title" type="string" /> <field name="url" type="int" /> </fields> </mapping> </massive-search-mapping>
Create File:
config -> packages -> sulu-search.yaml
Code:
sulu_search: indexes: events: name: 'Events' icon: 'su-user' view: name: app.event_edit_form result_to_view: id: id locale: locale website: indexes: - events - contact
in terminal:
bin/adminconsole massive:search:reindex
The text was updated successfully, but these errors were encountered: