-
Notifications
You must be signed in to change notification settings - Fork 17
Saving Location Cdb #67
Comments
We didn't add createActor() etc. in EntryApi.php because the locations are typically embedded in the events. It is however provided on http://tools.uitdatabank.be/docs/entry-api but we were thinking to remove this method in the next version because nobody uses it (and the locations object type is not the same anymore in UDB3, @zuuperman knows). And we like to move as fast as we can to the new - more stable - Entry API of UDB3. So to wrap it up, it is possible if you add the methods in the libraries by yourself, but we will have some upgrade troubles then when moving to the new api. Do you really need them? ;) |
Is this related to having reusable locations ? As we have a client that added 500 events spread over a limited number of locations, but since they can't select locations that were previously entered, they have to re enter it for every event and now we have a lot of duplicate locations that are written slightly different. |
At the moment, when you add an event in agenda/e/add, you can select an existing UIT-location. When it's not in the list you can create a custom one, however I noticed when you enter custom location data, it just gets added to the event, and it does not create a location in the UIT database. For a client, they want to create locations in Drupal, and have the option to also add them to UIT upon creating them. But after digging in the Culturefeed code, I couldn't find a way to save location data to UIT. |
any info regarding @yannickonsea his issue @svenhoutmeyers ? Thanx |
Is it possible to save a Location to the UIT database?
Upon saving a location node, I want to create a new Location in UIT, but I can't find a way to do this using Culturefeed.
After checking the REST docs for the Entry API, I couldn't find anything either.
Could it be that the documentation is outdated, and that meanwhile there is a way to do this? Or is it just not possible?
Thanks in advance.
The text was updated successfully, but these errors were encountered: