Completely get it. My work building Drupal websites is my side gig. Wish I had more time to devote to it, because it is great fun. Appreciate all the help you provided here as well as those that the module authors and maintainers are able to devote to it.
Well, I did look into it and there is ALOT of code out there for this module and I really don't have time to figure out what the right solution is. My workaround is to add an extra field in my content type that is a SmartDate and I wrote a small ECA model that sets it based on my DateTime field and I use the SmartDate field in FullCalendar. Would really be nice to have that default duration back in FullCalendar but I'm good for now.
Thank you @erutan, that is exactly what I need added to this module. I'm a site builder but know my way around code, just not PHP. I guess in the meantime, I will see if I can find how this used to be implemented and try my hand at a patch for my local installation.
Sorry, this appears to be a duplicate and a fix seems to be in the current dev branch.
dbdrupal → created an issue.
Thanks @dpagini. I have a use case that is very similar to this, however, there is a default duration for events. We run a youth sports league and all games are an hour in duration. The hour duration is common knowledge so we don't set an end date for the field. However, this doesn't play nice with the current version of FullCalendar. I would like to see (and it used to be there) a default duration added that can be set in the view to tell fullcalendar that if it does not see and end date, to add X number of hours to the start date.
Hi, it's been a month since I first posted and am just looking for clarification or some feedback on this as it is a big deal to the web site I'm developing. Can one of the maintainers at least address this question? Thank you and please let me know if I wasn't clear or didn't provide enough information in my initial post.
dbdrupal → created an issue.
@freelock just realized that there has been an issue out there for over a year addressing this specifically. It is in Needs Review status: https://www.drupal.org/project/tooltip/issues/3394050 🐛 Remove hard dependency on CKEditor Active I'm not a PHP developer so I'm probably going to just need to sit back and wait until this gets absorbed into the module. Thanks.
Appreciate the work on this. Have a question. My need for this module is to provide tooltips on views (so not CKEditor related). I need to have CKEditor 5 on my site (and not 4). Is there anyway to disable to CKEditor functionality/dependency so I can install this module and use it with my views? If not, is anyone aware of another tooltip type module that I can use with views? Thanks.
That did it @andileco, thanks! Works fine now with multiple displays.
Can the writers/maintainers of this module provide any guidance on how to cleanup this issue in the database or via some other method? Thanks.
FYI, this patch does not solve the problem. I continue to receive the error when attempting to delete any column from any table. It also screws up some of my ECA models when I do this. This is a bad error and weaves a tangled web of issues.
I am seeing this as well. I cannot create more than one chart page in a single view. On Drupal 10.3.2. I can always create the initial display as a chart fine and it works great. Every single time I create a 2nd display in the view that is a chart, it works, but when I toggle back to the first display, it gives me the error below. I go up to the Chart settings on that initial display, and see that nothing is chosen for the Label (but it was before I created the 2nd display). I choose the correct value again and save that and the preview for the initial display now works again but then I have an issue with the second display. When I do get an error it shows with a red background in the Content area in the preview: Data column(s) for axis #0 cannot be of type string×
I will test out the fix dpi and see if that works. For those that write and deploy PHP code, a mess might be less cumbersome than for those that are site builders such as myself. I will report back if removing that function seems to solve the problem for me.
I'm having the same issues as others have described. This is a major issue that has been open for over a year? I understand and appreciate those that volunteer their time to build and maintain contrib modules, but could you at least put a disclaimer on the main page warning people not to install this anymore? Are there any manual steps that can be taken to cleanup the mess?
@hockey2112, did you ever find a workaround for this. I'm experiencing the exact same behavior when trying to implement this on 10.3
dbdrupal → created an issue.
Thanks Jurgen. I added these to settings.php and it isn't capturing anything new nor is there more information on the browser console (I"m using Chrome). From what I can tell, while this is super annoying and I want to figure it out, it is not keeping my models from saving or running correctly so for the time being, I will just need to deal with it. At some point, I will stand up a new instance of Drupal 10.3 and see if I continue to have this issue. In the meantime, thank you for addressing this for me. I think it is fair to close out this issue as it is a non-issue for the code base and must be something with my environment.
I will keep poking around @jurgenhaas, but there is nothing in the dblog for this issue and I'm not finding anything in my PHP error log either. Very odd. I will try to find some time this weekend to look deeper and report back on my findings.
Per Jurgen's suggestion, I ran something I did not initially which was the drush eca:update. This did not solve the problem and I am uploading an export of the module per his suggestion. Thank you.
dbdrupal → created an issue.
@hyperlogos,
Did you ever figure this out? I'm having the same issue with D10 and I swear I have the mappings correct. But am getting the following error. I've tried OH, Ohio, etc ... in that field and it doesn't matter. I'm mapping state to this: Facility Address (field_facility_address): The top-level administrative subdivision of the country
Thanks!
An entity of type "content" failed to validate with the following errors:
- field_facility_address.0.administrative_area: State field is not in the right format.
Please check your mappings
My bad Mingsong, you are correct, I was using the FullCalendar module in D7. I guess I will have to find a way around this constraint with this module, which is otherwise great. Thanks.
dbdrupal → created an issue.
Hey, appreciate that @AlfTheCat, I will give it a look. Based on Jurgen's post, it looks a bit cumbersome, but I should have time to try it out in the next week or so and I suppose if it works, it is just getting it setup once and testing it out. I will let you know what I find out. Thanks again.
I'm spinning up a new Drupal 10 site and am going to be using ECA to trigger all kinds of things including SMS messages. Is there any timeline on when this module might be "integrated" with ECA. The primary of maintainer of ECA told me: "If not already possible, what would be required is an action plugin that receives the data and sends the SMS in the module you want to use." I'm a site builder so this doesn't mean much to me but I wanted to see if it was on your roadmap, even if it is for another alpha release. Thanks
Follow up on this, thanks for the description Jurgen. I'm able to make this work for fields on the Webform that are enterable (i.e. text box,etc ...). However, there are a few fields in my item webform that are item type fields (display only) and when I reference those in the Field Name, I'm unable to access them. Does this module only make available enterable fields? Follow up question ... can multiple fields be access in a single Get Data event or do I need to create an event for each field I want to read from the webform submission? Thanks!
Thanks wombatbuddy! This looks extremely promising. I will check it out.
Basically, the rules are triggered off of entityform create or update. When a form is created, the rules will create an entity and populate fields in the entity. This is easy because you can say entity.field= entityform.field. Whereas with webform, you have to create a variable, etc ... convert data types, and then set entity.field = variable created in rules.
I have loads of use cases, but this is it at the simplest level.