I get a WSOD after I click save on a BEE enabled entity
InvalidArgumentException: Field field_use_open_hours is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 580 of drupal-8.5.3/html/core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Comments
Comment #2
socialnicheguru commentedIn the module neither of these has storage configurations:
field_open_hours
field_use_open_hours
Comment #3
acrollet commentedHi there,
I've attempted to reproduce this without success. Could you post step by step instructions to reproduce this error on a new simplytest site? thanks!
Comment #4
socialnicheguru commentedcreate a bee type
on the manage display add Office Hours -> rendered entity to the display
hit save
create the bee entity from the content type
hit save
WSOD
Comment #5
socialnicheguru commentedComment #6
acrollet commentedHi there, I don't have an option for 'rendered entity' when setting the display - could you post screenshots?
Comment #7
socialnicheguru commentedok so I create a content type called scheduler
I enabled BEE on that
I then created an entity type called organization
I created an entity reference between organization and scheduler. I allow for more than one schedule ie. walk-ins, call times
I made that an inilne_entity_form.
On the display for the entity reference I have the option to render entity for scheduler
If I include office_hours I get a WSOD.
I do not know if I even need to include it or not.
Comment #8
acrollet commentedIs this a bug with how we're using the office hours module, or does it not support inline_entity_form? Have you tried adding an office hours field to a non bee-enabled entity and displaying that field with IEF? thanks!
Comment #9
acrollet commentedComment #10
gebiss commentedHi,
I am using BEE 8.x-1.0-beta7 on Drupal 8.7.7
I get exactly the same error while trying to update availability (node with the calendar > tab Availability > Update availability > Available/Unavailable, Start date/End date > Update availability button).
I have setup content type with the calendar as:
Booking length:
- Daily Bookings (allows bookings of 1 or more full days)
Availability:
- Generally available (Use for resources that are usually available unless there is a booking. Examples are meeting rooms and equipment).
+Add Reservation button works file, just problems with updating Availability.
Full error message:
InvalidArgumentException: Field field_availability_hourly is unknown. in Drupal\Core\Entity\ContentEntityBase->getTranslatedField() (line 587 of /home/d3signeu/bee.com/core/lib/Drupal/Core/Entity/ContentEntityBase.php).
Jacek
Comment #11
acrollet commented@gebiss can you provide instructions for reproducing this error from a new d8 site? thanks!!
Comment #12
gebiss commentedHi,
Of course:
Fresh D8 install (Drupal 8.7.7) plus following modules: admin_toolbar, adminimal_admin_toolbar, bat, bat_api, bee, ctools, facets, fullcalendar_library, ludwig, office_hours, search_api, services.
Downoaded all required libraries: jquery-ui-slider-pips.min.css, jquery-ui-slider-pips.min.js and the roomify/bat (via Ludwig module: https://www.drupal.org/project/ludwig)
Created content type for the availability calendar > Make this entity type bookable:
Booking length:
- Daily Bookings (allows bookings of 1 or more full days)
Availability:
- Generally available (Use for resources that are usually available unless there is a booking. Examples are meeting rooms and equipment).
Created content with the calendar.
ISSUE: As I said in previous post I receive error when trying to update availability for Daily bookings. +Add Reservation button works file. I can create reservations.
Today I also created content type for Flexible Bookings (allows bookings of any length) and created availability calendar. Here everything works fine (changing availability and adding reservations).
If this helps I can share access to the backend for you.
Regards,
Jacek
Comment #15
acrollet commentedThanks for the clear bug report! Fixed in -dev (I'll be releasing beta8 shortly)
Comment #16
gebiss commentedGreat! Tested beta8 and it works fine. Thanks for the fix
Comment #17
acrollet commented:-)