DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/doc</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/events</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/events/(?P<id>\d+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/events/by-slug/(?P<slug>[^/]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/venues</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/venues/(?P<id>\d+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/venues/by-slug/(?P<slug>[^/]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/organizers</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/organizers/(?P<id>\d+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/organizers/by-slug/(?P<slug>[^/]+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/categories</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/categories/(?P<id>\d+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/tags</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
DEBUG HOOK IS WORKING!

Function Name: register_rest_route
Message: The REST API route definition for <code>tribe/events/v1/tags/(?P<id>\d+)</code> is missing the required <code>permission_callback</code> argument. For REST API routes that are intended to be public, use <code>__return_true</code> as the permission callback.
{"id":6440,"date":"2024-12-11T13:47:28","date_gmt":"2024-12-11T12:47:28","guid":{"rendered":"https:\/\/www.trienale-jablonec.cz\/?page_id=6440"},"modified":"2024-12-11T14:32:10","modified_gmt":"2024-12-11T13:32:10","slug":"triennial-2023","status":"publish","type":"page","link":"https:\/\/www.trienale-jablonec.cz\/en\/triennial-2023\/","title":{"rendered":"Triennial 2023"},"content":{"rendered":"<\/div><\/div><\/div><\/div><\/div>
<\/div>
\n

Triennial 2023<\/h1>
<\/div><\/div><\/div>\n\n

Profile of the Event<\/h2>
<\/div><\/div><\/div>
\n
\n
\n

The Museum of Glass and Jewellery in Jablonec nad Nisou holds the International Triennial of Glass and Jewellery once every 3 years, a showcase of the best that has appeared on the Czech glass and costume jewellery market in the last 3 years.<\/em><\/p>\n

Project characteristics:<\/h4>\n

The project is focused on supporting cultural and creative industries. It builds on the tradition of international exhibitions of jewellery and glass, which were held regularly from the 1960s until 1989, attracting immense public interest. It is the largest non-commercial showcase of contemporary Czech glass and jewellery in the Czech Republic.<\/p>\n

Except during the museum’s reconstruction, the event has been organized on a three-year cycle. The 9th edition will take place in 2023. Thanks to its unique programming, it has been included among the most significant events of the Ministry of Culture of the Czech Republic and is regularly provided with substantial financial support.<\/p>\n

In 2023, the project will feature four thematic exhibitions, two symposia, and several accompanying events organized in collaboration with partners.<\/p>\n